Re: Boost and Python 3 in f18

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 6, 2012 at 11:33 AM, David Malcolm <dmalcolm@xxxxxxxxxx> wrote:
> On Mon, 2012-08-06 at 11:51 +0200, Petr Machata wrote:
>> David Malcolm <dmalcolm@xxxxxxxxxx> writes:
>>
>> > On Sat, 2012-08-04 at 21:30 +0530, Parag N(पराग़) wrote:
>> >
>> >> 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=a2450339dffbaadf0e31879429cc026862ec2439
>> > seems to have dropped the python3 subpackage which confused me and my
>> > scripts.
>>
>> Temporarily, as I wanted to get out mostly-working Boost 1.50 out.  I'll
>> look at re-enabling Python 3 this week, but I'm thinking that I'll
>> actually build it only after the merge.  I'd need to do so anyway, and
>> presumably that would impact ABIs of boost-python3, so there's no value
>> in having the build in a tag.
>>
>> > It's not clear to me that anything actually uses boost-python3
>>
>> I put in Python 3 support at a user request, as it seems sensible to me
>> to support both Python versions, and it was reasonably easy to put the
>> support in.  It is quite possible there are no direct users in Fedora
>> itself.
>>
>> > 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?
>>
>> I'm thinking the end of this week.  This gives about a week for fixes
>> and rebuilds before Alpha.
> Feature freeze for Fedora 18 is tomorrow (2012-08-07), and git is about
> to be branched after that for Fedora 19, as per:
>   http://fedoraproject.org/wiki/Releases/18/Schedule
> It seems less than ideal to me to be merging this work into f18 *after*
> feature freeze (though I'm hardly sinless here, I've left things very
> late with the Python 3.3 stuff).
>
> In the meantime, this bad interaction between our two features is
> breaking the build of every package in f18 that has a build-time
> requirement on "boost".  (Sorry everyone)
>
> Some possible ways of unbreaking this:
> (a) rebuild a new boost-1.48 into f18 dropping the python3 subpackage
> for now
> (b) rebuild a new boost-1.48 into f18 against python 3.3
> (c) move the boost-1.50 from f18-boost into f18 proper
> (d) something else I'm not thinking of
>
> I'm not sure of the exact git/koji/fedpkg incantations to best do (a) or
> (b) [and I didn't want to go stomping on the boost stuff in git without
> coordinating with you]
>
> How should we go about fixing this?

My understanding is that tonight dgilmore will be doing c.

-J


>> Anyone knows if there is a way to address maintainers of packages
>> dependent on boost?  That's about 100 packages that depend on runtime
>> libraries, and then those that have Boost as BR.  I guess I may need to
>> crawl package database.  Apparently, without direct pings, people won't
>> rebuild the client packages.
> FWIW for the Python 3.3 rebuild (also about 100 packages) I used
> skvidal's excellent "mockchain" tool to rehearse the builds locally,
> fixing issues, and establishing a build order.  See:
> http://fedorapeople.org/cgit/skvidal/public_git/scripts.git/tree/mock
>
> Hope this is helpful
> Dave
>
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel



-- 
http://cecinestpasunefromage.wordpress.com/
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love

-d. bowie
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux