Boost and Python 3 in f18 (was Re: Python 3.3 (was Re: rawhide report: 20120804 changes))
On Sat, 2012-08-04 at 21:30 +0530, Parag N(पराग़) wrote:
Hi,
On Sat, Aug 4, 2012 at 8:57 PM, David Malcolm <dmalcolm(a)redhat.com> wrote:
> On Sat, 2012-08-04 at 12:32 +0000, Fedora Rawhide Report wrote:
>> Compose started at Sat Aug 4 08:15:03 UTC 2012
>>
>> Broken deps for x86_64
>> ----------------------------------------------------------
> [...snip numerous missing deps of the form
> requires python(abi) = 0:3.2
> requires libpython3.2mu.so.1.0()(64bit) ]
>
> I finally pushed python 3.3b1 into rawhide yesterday.
> https://fedoraproject.org/wiki/Features/Python_3.3
>
> I've rebuilt most python3-using packages, and am slowly working through
> the stragglers now.
Thanks. But I am getting this error for xs package scratch build.
DEBUG util.py:257: --> gc-devel-7.2c-3.fc18.x86_64
DEBUG util.py:257: --> readline-devel-6.2-5.fc18.x86_64
DEBUG util.py:257: Error: Package: boost-python3-1.48.0-16.fc18.x86_64 (build)
DEBUG util.py:257: Requires: libpython3.2mu.so.1.0()(64bit)
DEBUG util.py:257: You could try using --skip-broken to work around
the problem
I am not able to find boost-python3 subpackage from boost package build.
I think
this is a consequence of the latest boost packages being done in
a side tag for:
http://fedoraproject.org/wiki/Features/F18Boost150
Currently, the latest boost build in f18 seems to be:
boost-1.48.0-16.fc18
http://koji.fedoraproject.org/koji/buildinfo?buildID=326854
whereas the latest boost build is in "f18-boost":
boost-1.50.0-1.fc18
http://koji.fedoraproject.org/koji/buildinfo?buildID=344226
The commit for boost 1.50:
http://pkgs.fedoraproject.org/cgit/boost.git/commit/?id=a2450339dffbaadf0...
seems to have dropped the python3 subpackage which confused me and my
scripts.
It's not clear to me that anything actually uses boost-python3
[david@f18 ~]$ repoquery --whatrequires boost-python3
boost-0:1.48.0-16.fc18.x86_64
boost-devel-0:1.48.0-16.fc18.i686
boost-devel-0:1.48.0-16.fc18.x86_64
where "boost" is an "umbrella" package that pulls in all other boost
components so presumably when the new boost hits f18 properly this issue
will go away. Or maybe I'm misreading this.
In the meantime, it looks like my Python 3.3 rebuild has broken "boost"
installs in f18 buildroots until the boost-1.50 build lands in f18.
Sorry about that. Is there an ETA for when the boost stuff will be
merged?
Hope I'm correctly characterizing this; thanks to rdieter for help with
this on IRC.
Dave