On Thu, Dec 4, 2014 at 8:21 PM, Dimstar / Dominique Leuenberger firstname.lastname@example.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 email@example.com wrote:
Package name Devel repo
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.
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. :-)