Bug#825759: marked as done (nmu: some Ada libraries, dw: to reflect order of build dependencies)
Your message dated Tue, 31 May 2016 17:10:10 +0200
with message-id <c8d5981b-b05d-9bf0-a2f1-7451d44158bc@debian.org>
and subject line Re: Bug#825759: nmu: some Ada libraries, dw: to reflect order of build dependencies
has caused the Debian Bug report #825759,
regarding nmu: some Ada libraries, dw: to reflect order of build dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
825759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825759
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Hello.
Every package containing an Ada library embeds checksums of its
recursive dependencies, in files suffixed with .ali. Everytime
something attempts to build against the library, gcc checks that the
sources of all dependencies match the checksum in the ALI files, else
fails with a message about "obsolete ALI files".
Between gcc-6.0 and gcc-6.1, the GNAT Ada runtime has changed. A
library already built against gcc-6.0 and recursively depending on the
modified part now contains an invalid checksum. All reverse
dependencies are broken until the library is rebuilt against gcc-6.1.
Ada libraries Build-Depend: gnat per policy, and gnat Depends: gnat-6
(>= 6.1) since a few hours, so a bin-NMU will automatically wait for
gcc-6.1 on architectures where it is not available yet.
However, some dw commands are required to express that a library must
only be rebuilt after its (library) dependencies.
The already existing binNMU for libgnatcoll and asis on some
architectures causes two version number to be involved, and the syntax
in such an unusual case is not specified by the documentation. I hope
that the intent is evident enough for any syntax issue to be easily
fixed.
For libaws on some architectures, no NMU is necessary because the
build has always failed until now.
Thanks for rescuing poor ALIs lost in Wonderland.
nmu libaunit_3.7.2-1 . ANY -ppc64 . -m 'Update ALI files for gnat-6.1'
nmu libgmpada_1.0-3 . hurd-i386 . -m 'Update ALI files for gnat-6.1'
nmu libtexttools_2.1.0-7 . amd64 hurd-i386 sparc64 . -m 'Update ALI files for gnat-6.1'
nmu opentoken_6.0b-5 . amd64 hurd-i386 sparc64 . -m 'Update ALI files for gnat-6.1'
nmu libxmlada_4.5.2015-7 . hurd-i386 . -m 'Update ALI files for gnat-6.1'
nmu libgtkada_3.8.3-1 . ANY -ppc64 . -m 'Update ALI files for gnat-6.1'
nmu libtemplates-parser_11.10-3 . amd64 . -m 'Update ALI files for gnat-6.1'
nmu libtemplates-parser_11.10-3 . hurd-i386 . -m 'Update ALI files for xmlada'
dw libtemplates-parser_11.10-3 . hurd-i386 . -m 'libxmlada-unicode6-dev (>= 4.5.2015-7+b1)'
nmu libgnatcoll_1.7gpl2015-1+b1 . i386 mips mipsel ppc64el kfreebsd-i386 . -m 'Update ALI files for gnat-6.1 gtkada'
nmu libgnatcoll_1.7gpl2015-1 . ANY -i386 -mips -mipsel -ppc64el -kfreebsd-i386 -ppc64 . -m 'Update ALI files for gnat-6.1 gtkada'
dw libgnatcoll_1.7gpl2015-1+b1 . i386 mips mipsel ppc64el kfreebsd-i386 . -m 'libgtkada3.8.3-dev (>= 3.8.3-1+b1)'
dw libgnatcoll_1.7gpl2015-1 . ANY -i386 -mips -mipsel -ppc64el -kfreebsd-i386 -ppc64 . -m 'libgtkada3.8.3-dev (>= 3.8.3-1+b1)'
nmu asis_2015-1 . ANY -mips -mipsel -ppc64el . . -m 'Update ALI files for gnat-6.1 gnatcoll'
nmu asis_2015-1+b1 . mips mipsel ppc64el . -m 'Update ALI files for gnat-6.1 gnatcoll'
dw asis_2015-1 . ANY -i386 -mips -mipsel -ppc64el -kfreebsd-i386 -ppc64el . -m 'libgnatcoll1.7-dev (>= 1.7gpl2015-1+b1)'
dw asis_2015-1 . i386 kfreebsd-i386 . -m 'libgnatcoll1.7-dev (>= 1.7gpl2015-1+b2)'
dw asis_2015-1+b1 . mips mipsel ppc64el . -m 'libgnatcoll1.7-dev (>= 1.7gpl2015-1+b2)'
nmu libaws_3.3.2-1 . ANY -mips -mipsel -ppc64el . -m 'Update ALI files for gnat-6.1'
dw libaws_3.3.2-1 . ANY -mips -mipsel -ppc64el . -m 'libasis2015-dev (>= 2015-1+b1)'
dw libaws_3.3.2-1 . hurd-i386 . -m 'libxmlada-unicode6-dev (>= 4.5.2015-7+b1)'
dw libaws_3.3.2-1 . amd64 hurd-i386 . -m 'libtemplates-parser_11.10-3 (>= 11.10-3+b1)'
dw libaws_3.3.2-1 . mips mipsel ppc64el . -m 'libasis2015-dev (>= 2015-1+b2)'
dw adacontrol_1.17r3.1-3 . kfreebsd-i386 ppc64 sparc64 . -m 'libasis2015-dev (>= 2015-1+b1)'
--- End Message ---
--- Begin Message ---
On 29/05/16 17:27, Nicolas Boulenguez wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
>
> Hello.
>
> Every package containing an Ada library embeds checksums of its
> recursive dependencies, in files suffixed with .ali. Everytime
> something attempts to build against the library, gcc checks that the
> sources of all dependencies match the checksum in the ALI files, else
> fails with a message about "obsolete ALI files".
>
> Between gcc-6.0 and gcc-6.1, the GNAT Ada runtime has changed. A
> library already built against gcc-6.0 and recursively depending on the
> modified part now contains an invalid checksum. All reverse
> dependencies are broken until the library is rebuilt against gcc-6.1.
>
> Ada libraries Build-Depend: gnat per policy, and gnat Depends: gnat-6
> (>= 6.1) since a few hours, so a bin-NMU will automatically wait for
> gcc-6.1 on architectures where it is not available yet.
>
> However, some dw commands are required to express that a library must
> only be rebuilt after its (library) dependencies.
>
> The already existing binNMU for libgnatcoll and asis on some
> architectures causes two version number to be involved, and the syntax
> in such an unusual case is not specified by the documentation. I hope
> that the intent is evident enough for any syntax issue to be easily
> fixed.
There is no need to specify the +bN suffix in nmu commands (not sure if it's
just not necessary or actively harmful, but I've just removed them). For dw on
the -m switch it is correct.
> For libaws on some architectures, no NMU is necessary because the
> build has always failed until now.
>
> Thanks for rescuing poor ALIs lost in Wonderland.
All scheduled.
Cheers,
Emilio
--- End Message ---
Reply to: