On Tue, 2012-04-10 at 20:03 +0200, Robert Luberda wrote: > Adam D. Barratt wrote: > > Source: subcommander > > Version: 2.0.0~b5p2-3 > > That version compiled fine some time ago. > What has changed in 3+b1 and why do you think it is a subcommander issue?
+b1 was a rebuild against boost 1.49, as the build logs I linked from my report indicate. The fact that the package built okay previously doesn't necessarily imply that it will continue to do so in the face of new compiler or dependent library versions. Sometimes a failure in a later rebuild is an issue in the compiler or library, sometimes it's a bug in the package that has only been exposed by the rebuild; when not sure, filing the bug against the package which no longer builds and trusting the maintainer to re-assign if appropriate seems like the most sensible strategy imho. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
