Hello, 2013/5/21 Dmitrijs Ledkovs <x...@debian.org>: > reopen 704044 > thanks > > While sure the glibc-2.17/TIME_UTC name clash was a problem, my original > request in this bug report is still not satisfied. > > Both ogre and ogre-1.8 src packages fail to build from source against > boost1.53. > > With build failure similar as in this pastebin: > http://paste.ubuntu.com/5686723/ > > Please, upgrade to ogre 1.8.1 or higher; or cherry pick fixes to build > against boost1.53. > > This is still blocking boost1.53 transition.
Sorry that I closed this bug, I was mistaken it from one of the other related ones requiring packages B-D-ing on OGRE to upgrade. Upgrading OGRE to 1.8.1 would maybe require to change the SOVERSION and binary package name, having to go through ftp-new queue. 1.9-rc1 is already out, I think that it would be better to go with this one. I think that from your boost-transition POV, until all OGRE and their dependencies are removed, you cannot get rid of 1.49. But if you only want to move boost-defaults from 1.49 to 1.53 [1], all these packages are not a problem -- we depend specifically on 1.49, for the reasons stated in my first reply to this bug report. So if you change libboost-thread-dev to point to libboost-thread1.53-dev from 1.49, none of these packages (ogre and packages using it) will be affected. Is this correct, or I am missing something? Did OGRE packages fail to build in hist tests of #704032? Cheers. [1] from #704032: I would like to change Debian's default boost version from 1.49 to 1.53 or later -- likely to the most current Boost at the time the transition is scheduled. This change does not directly impact any binary packages. However, it will affect the buildability of source packages. -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org