[opensuse-factory] Boost 1.56 in Factory - couple failures
Dear Factory maintainers, Last night, boost 1.56 made it into Tumbleweed; as is almost usual by now with boost, a couple of packages (non-ring/DVD packages) break. Here a short list of the breaking ones I identified (no guarantee on completeness). Fixes for those are appreciated by all the users. Package name Devel repo -------------------------------------- avogadro KDE:Distro:Factory glom GNOME:Apps hugin graphics vegastrike games wt devel:libraries:c_c++ Not as bad as earlier boost updates :) Cheers, -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2014-12-04 at 10:17 +0100, Dimstar / Dominique Leuenberger wrote:
Dear Factory maintainers,
Last night, boost 1.56 made it into Tumbleweed; as is almost usual by now with boost, a couple of packages (non-ring/DVD packages) break.
Here a short list of the breaking ones I identified (no guarantee on completeness). Fixes for those are appreciated by all the users.
Package name Devel repo -------------------------------------- avogadro KDE:Distro:Factory glom GNOME:Apps hugin graphics vegastrike games wt devel:libraries:c_c++
Two of those (glom and vegastrike) seem actually to be due to an error in the boost packaging: the python2 bindings seem broken (readelf -a /usr/lib64/libboost_python.so.1.56.0 (the python 2 version) has a ton of undefined symbols that come from /usr/lib64/libpython3.4m.so.1.0, indicating that there is an issue in the way the py2 bindings are built) Can the boost maintainers please have a look at this? Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Dec 4, 2014 at 6:17 AM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Package name Devel repo -------------------------------------- vegastrike games
Not as bad as earlier boost updates :)
In this case, I think (after a quick look) it's because boost-python has been built against Python 3. Is that intentional? We do have support for python 3 on svn head, so I could backport it if needed, otherwise it'd be good to keep building boost-python with python 2. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2014-12-04 at 11:03 -0300, Claudio Freire wrote:
On Thu, Dec 4, 2014 at 6:17 AM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Package name Devel repo -------------------------------------- vegastrike games
Not as bad as earlier boost updates :)
In this case, I think (after a quick look) it's because boost-python has been built against Python 3.
Is that intentional?
We do have support for python 3 on svn head, so I could backport it if needed, otherwise it'd be good to keep building boost-python with python 2.
Claudio, As my follow-up mail on the thread indicated already, this is indeed a fallout of the python3 enablement of boost (which resulted in a libboost_python1_56_0 and libboost_python3-1_56_0 package, but both of them in fact were built against python3). I created a branch (home:dimstar:boost) and it shows that ALL but one (hugin) actually are results of the python mismatch in the end (something the boost maintainer either fixes or has to live with the consequence of having this change reverted). AS such, the only package left requiring attention is hugin Cheers, -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Dec 4, 2014 at 8:21 PM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
On Thu, 2014-12-04 at 11:03 -0300, Claudio Freire wrote:
On Thu, Dec 4, 2014 at 6:17 AM, Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Package name Devel repo -------------------------------------- vegastrike games
Not as bad as earlier boost updates :)
In this case, I think (after a quick look) it's because boost-python has been built against Python 3.
Is that intentional?
We do have support for python 3 on svn head, so I could backport it if needed, otherwise it'd be good to keep building boost-python with python 2.
Claudio,
As my follow-up mail on the thread indicated already, this is indeed a fallout of the python3 enablement of boost (which resulted in a libboost_python1_56_0 and libboost_python3-1_56_0 package, but both of them in fact were built against python3).
I created a branch (home:dimstar:boost) and it shows that ALL but one (hugin) actually are results of the python mismatch in the end (something the boost maintainer either fixes or has to live with the consequence of having this change reverted).
AS such, the only package left requiring attention is hugin
Even though I saw your post after I posted mine (and even though mine arrived afterwards), I hadn't understood that both were built against py3 until the second time I read your post (after reading the clarification). So, thanks for the clarification. :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Claudio Freire -
Dimstar / Dominique Leuenberger -
Dominique Leuenberger