Bug#653823: transition: boost-defaults
On Wed, 2012-04-11 at 21:13 +0100, Adam D. Barratt wrote: On Fri, 2012-04-06 at 17:21 +0100, Adam D. Barratt wrote: On Tue, 2012-03-27 at 18:49 +0200, Julien Cristau wrote: http://release.debian.org/transitions/html/boost1.49.html I've scheduled binNMUs for the packages listed in level 1 on the tracker. Level 2 have now been (mostly) scheduled. and level 3, with the exception of those which already have FTBFS bugs filed. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653823: transition: boost-defaults
On Fri, 2012-04-06 at 17:21 +0100, Adam D. Barratt wrote: On Tue, 2012-03-27 at 18:49 +0200, Julien Cristau wrote: http://release.debian.org/transitions/html/boost1.49.html I've scheduled binNMUs for the packages listed in level 1 on the tracker. Level 2 have now been (mostly) scheduled. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653823: transition: boost-defaults
On Tue, 2012-03-27 at 18:49 +0200, Julien Cristau wrote: On Mon, Mar 26, 2012 at 20:54:02 -0500, Steve M. Robbins wrote: On Sun, Mar 11, 2012 at 08:11:06PM +0100, Julien Cristau wrote: It'd probably be best to have kde sorted before the boost defaults change. Otherwise it sounds like it should be fine. So I see KDE transition is over. I should be able to upload new boost defaults now? Can you switch the tracker to track 1.49? Ack, tracker moved to http://release.debian.org/transitions/html/boost1.49.html I've scheduled binNMUs for the packages listed in level 1 on the tracker. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653823: transition: boost-defaults
On Mon, Mar 26, 2012 at 20:54:02 -0500, Steve M. Robbins wrote: On Sun, Mar 11, 2012 at 08:11:06PM +0100, Julien Cristau wrote: On Sun, Mar 11, 2012 at 13:21:19 -0500, Steve M. Robbins wrote: kdebase-workspace: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libplasma_applet-system-monitor.so.4.6.0': No such file or directory kdeedu: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakregatorinterfaces.so.4.6.0': No such file or directory kdepim: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory kdepim-runtime: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory It'd probably be best to have kde sorted before the boost defaults change. Otherwise it sounds like it should be fine. So I see KDE transition is over. I should be able to upload new boost defaults now? Can you switch the tracker to track 1.49? Ack, tracker moved to http://release.debian.org/transitions/html/boost1.49.html Cheers, Julien signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
On Sun, Mar 11, 2012 at 08:11:06PM +0100, Julien Cristau wrote: On Sun, Mar 11, 2012 at 13:21:19 -0500, Steve M. Robbins wrote: kdebase-workspace: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libplasma_applet-system-monitor.so.4.6.0': No such file or directory kdeedu: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakregatorinterfaces.so.4.6.0': No such file or directory kdepim: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory kdepim-runtime: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory It'd probably be best to have kde sorted before the boost defaults change. Otherwise it sounds like it should be fine. So I see KDE transition is over. I should be able to upload new boost defaults now? Can you switch the tracker to track 1.49? Thanks, -Steve signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
Hello Release Team, On Sat, Mar 03, 2012 at 12:21:20PM -0600, Steve M. Robbins wrote: I need some guidance from the release team regarding Boost. Last Sunday I uploaded another new version (1.49). It's still in NEW, but I'd like to transition boost-defaults to 1.49 ASAP. I plan to do local rebuilds as I did for 1.48 prior to transitioning and submit any patches necessary to support Boost 1.49. OK, I have just finished the local rebuilds against boost-defaults set to 1.49. The good news is that of 249 packages, there are just TWO new issues related to boost 1.49! Thus I'd like to formally request that this transition (bug #653823) be changed to Boost 1.49 transition. My next steps are to work on the issues, described in detail below. IMHO, none of them seem to be show-stoppers so I'd like to get a sense of when you feel it would be appropriate to flip the boost-default and upload. What follows is a summary of my rebuilds. I use the shorthand package: #bug [tag] explanation, where #none means no bug is yet filed. New Issues -- luabind: #none [NEW] ./luabind/detail/call_member.hpp:319:1: error: missing binary operator before token ( This issue is described in upstream tracker ticket https://svn.boost.org/trac/boost/ticket/6631 . I'm discussing the options with upstream on the mailing list; see http://lists.boost.org/Archives/boost/2012/03/191073.php . It sounds like there may be a way to fix this in boost itself that I will investigate. Otherwise, it's a simple fix to luabind. vtk: #none [NEW] vtkBoostBreadthFirstSearchTree.cxx:56:14: error: 'const class boost::detail::reverse_graph_edge_descriptorvtkEdgeType' has no member named 'underlying_desc' This issue is upstream: the VTK code depends on Boost internals and needs patch for 1.49. I've filed the bug and will work with upstream http://vtk.org/Bug/view.php?id=12988 Old Issues -- These issues were uncovered when the defaults switched to 1.48, and remain unfixed. Two of these have a patch in PTS, the third is for a package (wesnoth-1.8) that is superceeded and won't be fixed. openvrml: #652790 [PENDING] /usr/include/boost/multi_index/detail/scope_guard.hpp:122:29: error: 'boost::mpl' has not been declared wesnoth-1.8: #653806 [WONTFIX] error: 'boost::noncopyable_::noncopyable::noncopyable(const boost::noncopyable_::noncopyable)' is private (known bug, fixed in wesnoth-1.10; won't be fixed in wesnoth-1.8) witty: #653807 [PATCH] random_device.cpp:45:63: error: 'const result_type boost::random::random_device::min_value' is not a static member of 'class boost::random::random_device' (patch known from boost 1.48) Unrelated to Boost -- These are all either due to inability to satisfy build-depends or a build failure unrelated to boost. All I plan to do is file FTBFS bugs where none yet exist. Tags used: [DEPS] Cannot install all build dependencies, not related to boost [FTBFS] Failed To Build From Source, not related to boost [SOVER] Package builds library with SOVERSION 4.7.0, but installs or links to version 4.6.0 csound: #660232 [FTBFS] scons: *** [_csnd.so] Implicit dependency `/usr/lib/libpython2.7.a' not found, needed by target `_csnd.so'. ember: #629767 [DEPS] Build-Depends dependency for ember cannot be satisfied because the package libceguiogre-dev cannot be found esys-particle: #none [DEPS] libvtk5-dev : Depends: libnetcdf-dev but it is not going to be installed feel++: #none [DEPS] Build-Depends dependency for feel++ cannot be satisfied because package libpetsc3.1-dev has no candidate version freecad: #none [FTBFS] AppPartPy.cpp:495:69: error: no matching function for call to 'BRepBuilderAPI_MakeFace::BRepBuilderAPI_MakeFace(Handle_Geom_Plane, double, double, double, double)' (verified failure on sid) gnuradio: #none [DEPS] dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. gofigure2: #none [DEPS] libvtk5-qt4-dev : Depends: libvtk5-dev (= 5.8.0-7) but it is not going to be installed gpsdrive: #646446 [FTBFS] mapnik.cpp:33:15: error: 'mapnik::Image32' has not been declared kdebase-workspace: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libplasma_applet-system-monitor.so.4.6.0': No such file or directory kdeedu: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakregatorinterfaces.so.4.6.0': No such file or directory kdepim: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory kdepim-runtime: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory libgdf: #none [FTBFS] make[1]: *** [override_dh_auto_install] Error 1 osmium: #none [FTBFS] ../include/osmium/osm/position.hpp:31:35: fatal error: geos/geom/Coordinate.h: No such file or directory performous: #none [FTBFS] CMake Error: Required library Pango NOT FOUND. player: #662593 [FTBFS] /usr/bin/ld: cannot find -lgeos smc: #none [FTBFS] video.h:26:62: fatal error:
Bug#653823: transition: boost-defaults
On Sun, Mar 11, 2012 at 13:21:19 -0500, Steve M. Robbins wrote: kdebase-workspace: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libplasma_applet-system-monitor.so.4.6.0': No such file or directory kdeedu: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakregatorinterfaces.so.4.6.0': No such file or directory kdepim: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory kdepim-runtime: #none [SOVER] cp: cannot stat `debian/tmp/usr/lib/libakonadi-xml.so.4.6.0': No such file or directory It'd probably be best to have kde sorted before the boost defaults change. Otherwise it sounds like it should be fine. Cheers, Julien signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
On Sat, Dec 31, 2011 at 01:29:58 -0600, Steve M. Robbins wrote: I would like to change Debian's default boost version from 1.46.1 to 1.48. This change does not directly impact any binary packages. However, it will affect the buildability of source packages. I set up http://release.debian.org/transitions/html/boost1.48.html to track the rebuild status of the reverse dependencies. Cheers, Julien signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
Hello, On Sat, Mar 03, 2012 at 06:09:33PM +0100, Julien Cristau wrote: On Sat, Dec 31, 2011 at 01:29:58 -0600, Steve M. Robbins wrote: I would like to change Debian's default boost version from 1.46.1 to 1.48. This change does not directly impact any binary packages. However, it will affect the buildability of source packages. I set up http://release.debian.org/transitions/html/boost1.48.html to track the rebuild status of the reverse dependencies. Thanks, Julien. I need some guidance from the release team regarding Boost. Last Sunday I uploaded another new version (1.49). It's still in NEW, but I'd like to transition boost-defaults to 1.49 ASAP. I plan to do local rebuilds as I did for 1.48 prior to transitioning and submit any patches necessary to support Boost 1.49. Based on my experience with 1.48, that will likely take some weeks (say 4). I'm not 100% sure what happens when a transition tracker is set up (as for boost1.48). But I fear it may consume release team resources scheduling rebuilds and the like. If so, the question for the release team is: do you want to do it for 1.48 or wait for the 1.49 transition? As far as I know, the Wheezy freeze is still on for June. The next boost release should be in late May, which I suspect means it will be too late for me to package for the June freeze. Thus my proposal is that 1.49 be the default version of boost for Wheezy. This is why I raise the idea of skipping 1.48 and concentrating on migrating boost defaults to 1.49. Appreciate any feedback. Thanks, -Steve signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
On Sat, Mar 3, 2012 at 12:21:20 -0600, Steve M. Robbins wrote: Hello, On Sat, Mar 03, 2012 at 06:09:33PM +0100, Julien Cristau wrote: On Sat, Dec 31, 2011 at 01:29:58 -0600, Steve M. Robbins wrote: I would like to change Debian's default boost version from 1.46.1 to 1.48. This change does not directly impact any binary packages. However, it will affect the buildability of source packages. I set up http://release.debian.org/transitions/html/boost1.48.html to track the rebuild status of the reverse dependencies. Thanks, Julien. I need some guidance from the release team regarding Boost. Last Sunday I uploaded another new version (1.49). It's still in NEW, but I'd like to transition boost-defaults to 1.49 ASAP. I plan to do local rebuilds as I did for 1.48 prior to transitioning and submit any patches necessary to support Boost 1.49. Based on my experience with 1.48, that will likely take some weeks (say 4). I'm not 100% sure what happens when a transition tracker is set up (as for boost1.48). But I fear it may consume release team resources scheduling rebuilds and the like. If so, the question for the release team is: do you want to do it for 1.48 or wait for the 1.49 transition? As far as I know, the Wheezy freeze is still on for June. The next boost release should be in late May, which I suspect means it will be too late for me to package for the June freeze. Thus my proposal is that 1.49 be the default version of boost for Wheezy. This is why I raise the idea of skipping 1.48 and concentrating on migrating boost defaults to 1.49. Sounds ok to me, I'll hold off on any binNMUs against 1.48 then. Cheers, Julien signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
Il 03/03/2012 19:21, Steve M. Robbins ha scritto: Last Sunday I uploaded another new version (1.49). It's still in NEW, but I'd like to transition boost-defaults to 1.49 ASAP. FYI, I just accepted it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653823: transition: boost-defaults
On Sat, Dec 31, 2011 at 12:13:46PM +0100, Julien Cristau wrote: On Sat, Dec 31, 2011 at 01:29:58 -0600, Steve M. Robbins wrote: There are 237 source packages in SID that build-depend on one of the packages in boost-defaults. I have done a test-build with all 237 packages in a chroot sid environment containing updated boost-defaults. There were 22 build failures related to the new boost. An additional 14 build failures were detected that are not related to boost. Sourceful uploads will be required to fix all these build failures. Thanks a lot for this Steve. OK, so what's the next step? Do you need me to do anything further before flipping the defaults? Thanks, -Steve signature.asc Description: Digital signature
Bug#653823: transition: boost-defaults
On Sat, Dec 31, 2011 at 01:29:58 -0600, Steve M. Robbins wrote: There are 237 source packages in SID that build-depend on one of the packages in boost-defaults. I have done a test-build with all 237 packages in a chroot sid environment containing updated boost-defaults. There were 22 build failures related to the new boost. An additional 14 build failures were detected that are not related to boost. Sourceful uploads will be required to fix all these build failures. Thanks a lot for this Steve. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653823: transition: boost-defaults
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Briefly, package boost-defaults provides libboost-dev and similar
unversioned -dev packages that depend on a default versioned package
such as libboost1.46-dev.
I would like to change Debian's default boost version from 1.46.1 to
1.48. This change does not directly impact any binary packages.
However, it will affect the buildability of source packages.
There are 237 source packages in SID that build-depend on one of the
packages in boost-defaults. I have done a test-build with all 237
packages in a chroot sid environment containing updated
boost-defaults. There were 22 build failures related to the new
boost. An additional 14 build failures were detected that are not
related to boost. Sourceful uploads will be required to fix all these
build failures.
The results are summarized below, with the 22 boost-related failures
broken down into two groups: 14 where the fix is known and/or pending,
and 8 where the source fix is presently not known. However, even the
latter group can be fixed immediately by changing the build-deps to
use libboost1.46-dev and similar versioned packages.
All the 36 FTBFS have bugs filed, as noted below, so there should not
be further impact for the QA automated archive rebuild folks.
Known fixes (14):
aptitude #653812 [pending] error: Boost install not found, too old, or
incomplete; install libboost-dev.
anytun #652767 [io_service] error: 'boost::asio::ip::tcp::acceptor' has no
member named 'io_service'
avogadro #653625 [moc] Parse error at BOOST_JOIN
fgrun #652775 [singleton,caused by #652788] error:
boost/pool/detail/singleton.hpp: No such file or directory
flightgear #652797 [singleton,caused by #652788] error:
boost/pool/detail/singleton.hpp: No such file or directory
libreoffice #652784 [fixed in 1.3.5.0~beta2-1] acceleratorcache.cxx:64:29:
error: no match for 'operator='
ovito #652795 [moc] has_binary_operator.hp:50: Parse error at BOOST_JOIN
pinot #652786 [singleton] Memory.h:184:11: error: 'singleton_default' in
namespace 'boost::details::pool' does not name a type
pion-net #653787 [io_service]
'boost::asio::ssl::streamboost::asio::basic_stream_socketboost::asio::ip::tcp
::lowest_layer_type' has no member named 'io_service'
qpid-cpp #653795 [singleton] fatal error: boost/pool/detail/singleton.hpp: No
such file or directory
qt-gstreamer #653796 [moc] has_binary_operator.hp:50: Parse error at
BOOST_JOIN
simgear #652788 [singleton] error: boost/pool/detail/singleton.hpp: No such
file or directory
sslsniff #652756 [io_service] error: 'boost::asio::ip::tcp::acceptor' has no
member named 'io_service'
yade #653817 [embed,pending] error: 'init' is not a member of 'traits {aka
boost::math::detail::fp_traits_nativefloat}'
Fix unknown (8):
-
drizzle #653627 [TODO] constructor
'boost::detail::shared_count::shared_count(P, boost::detail::sp_inplace_tagD)'
eiskaltdcpp # [TODO] error: 'boost::interprocess::detail' has not been declared
monotone #653764 [TODO] lgamma_small.hpp:483:38: error: expected
primary-expression before 'do'
openvrml #652790 [TODO] scope_guard.hpp:122:29: error: 'boost::mpl' has not
been declared
python-visual #652798 [TODO] random_device.cpp:30:63: error: 'const result_type
boost::random::random_device::min_value' is not a static member of 'class
boost::random::random_device'
vtk #653805 [TODO] vtkBoostBreadthFirstSearchTree.cxx:98:5: error: 'class
boost::detail::reverse_graph_edge_descriptorvtkEdgeType' has no member named
'Id'
wesnoth-1.8 #653806 [TODO]: error:
'boost::noncopyable_::noncopyable::noncopyable(const
boost::noncopyable_::noncopyable)' is private
witty #653807 [TODO] random_device.cpp:45:63: error: 'const result_type
boost::random::random_device::min_value' is not a static member of 'class
boost::random::random_device'
Failures not related to boost (14):
---
agave #652845 [pending,notboost] error: format not a string literal and no
format arguments [-Werror=format-security]
ball #653626 [notboost] error: passing 'const BALL::PeriodicBoundary' as 'this'
argument of 'BALL::Size BALL::PeriodicBoundary::addSolvent(const
BALL::String)' discards qualifiers [-fpermissive]
ember #629767 [notboost] FTBFS: build-dependency not installable:
libceguiogre-dev
esperanza #653814 [notboost] FTBFS: undefined reference to 'XKeysymToKeycode'
(and others)
getfem++ #653820 [notboost] FTBFS: install: cannot stat `macros/*.bin': No such
file or directory
gnash #651625 [patch,notboost] error: new declaration 'char*
NP_GetMIMEDescription()' ambiguates old declaration 'const char*
NP_GetMIMEDescription()'
gnuradio #642716 [notboost] FTBFS: gr_vmcircbuf_createfilemapping:
createfilemapping is not available
gpsdrive #646446 [notboost] mapnik.cpp:33:15: error: 'mapnik::Image32' has not
been declared
salome [notboost] multiple FTBFS
scenic #653821
