Matthias Klose, le Thu 25 Dec 2014 13:14:44 +0100, a écrit : > On 12/25/2014 10:23 AM, Samuel Thibault wrote: > > Matthias Klose, le Thu 25 Dec 2014 10:17:19 +0100, a écrit : > >> On 12/25/2014 10:09 AM, Samuel Thibault wrote: > >>> Matthias Klose, le Thu 25 Dec 2014 08:42:05 +0100, a écrit : > >>>> please remove the upper dependency on a specific gcc package version. I > >>>> can't > >>>> see a reason why the package shouldn't work with GCC 4.8.3, but not with > >>>> GCC > >>>> 4.8.4. The dependency on the major gcc version is already there. > >>> > >>> Because the plugin ABI compatibility is not guaranteed between versions > >>> of gcc. A mere binNMU is needed to fix this. > >> > >> in this case, how do you guarantee this when updates from the branch are > >> taken? > > > > By hoping that branch updates do not break the ABI. > > What do you propose instead? > > well, first I would like to understand why you think that a subminor version > bump breaks the ABI.
I'm not saying it's the version bump which breaks the ABI, but the newer gcc release. I would be happy if gcc was asserting that no such break happens within a minor branch, but I haven't seen anything asserting this. Of course, the break can have happened in the svn version you have put on top of the previous version, but I don't really have a way in the starpu package to prevent against that, since the svn revision is not expressed in the gcc version numbering. Rebuilding against subminor versions only are a sort of mid-solution between rebuilding against each and every gcc build, and letting all potential ABI breaks within a minor branch come in. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
