[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Permission to upload gnat-4.1 with 3 new binary packages?



Luk Claes writes:
> Ludovic Brenta wrote:
>> The uploaded gnat-4.1 has been in unstable for 10 days with no new
>> bugs reported.  Please allow it to migrate to testing, if not already
>> unblocked.  Thanks.
>
> Can you in short explain the huge differences below?

The build scripts for gnat-4.1 are the same as for gcc-4.1 and
gcj-4.1; their behaviour depends on the source package name as defined
in the first changelog entry.  We do not upload all three source
packages whenever the upload number changes, because not all changes
are relevant to all three packages.  The latest uploads were:

4.1.1-17  gcc  gcj
4.1.1-18  gcc
4.1.1-19  gcc      gnat
4.1.1-20  gcc  gcj
4.1.1-21  gcc
4.1.1-22           gnat

The rest is details... what you see are really the differences between
-19 and -22, and they include many things unrelated to Ada and which
do not affect the binary packages at all.  For example, we do not
apply the updated Java, Objective-C or Objective-C++ patches when
building gnat-4.1; nor do we apply the new m68k patches, since
gnat-4.1 doesn't support m68k.

svn-updates.dpatch deserves a separate explanation.  You will note
that that file contains the bulk of the changes.  It regularly tracks
the upstream gcc 4.1 branch and contains regression fixes only.  The
latest change to this file was made in -20, and is already in gcc-4.1
and gcj-4.1 in testing.  With this new upload, gnat-4.1 merely catches
up.  No changes in this patch affect the Ada front-end or library.

The files really affecting this new upload are those marked with *
below.  They contain the changes described in the changelog, and which
you (I mean the release managers) approved.

   (void)                                              |207746 +++++++++++++++++---
   debian/patches/libjava-backport3.dpatch             | 3739
   debian/patches/libjava-sjlj.dpatch                  |   65
   debian/patches/m68k-bitfield-offset.dpatch          |  192
   debian/patches/m68k-noautoinc-setjmp.dpatch         |   47
   debian/patches/pr29805.dpatch                       |   47
   debian/rules.d/binary-libobjc-cross.mk              |  117
   debian/rules.d/binary-objc-cross.mk                 |   60
   debian/rules.d/binary-objcxx-cross.mk               |   35
*  gnat-4.1-4.1.1/debian/README.Debian                 |   75
*  gnat-4.1-4.1.1/debian/changelog                     |   42
*  gnat-4.1-4.1.1/debian/control                       |   40
*  gnat-4.1-4.1.1/debian/control.m4                    |   62
   gnat-4.1-4.1.1/debian/patches/hurd-changes.dpatch   |   57
   gnat-4.1-4.1.1/debian/patches/m68k-fpcompare.dpatch |   22
*  gnat-4.1-4.1.1/debian/patches/svn-updates.dpatch    |174543 +---------------
   gnat-4.1-4.1.1/debian/rules.conf                    |    4
*  gnat-4.1-4.1.1/debian/rules.d/binary-ada.mk         |   48
   gnat-4.1-4.1.1/debian/rules.defs                    |    4
   gnat-4.1-4.1.1/debian/rules.parameters              |    8
   gnat-4.1-4.1.1/debian/rules.patch                   |    7
   gnat-4.1-4.1.1/debian/rules2                        |   11
   22 files changed, 199708 insertions(+), 187263 deletions(-)

PS.  How did you generate this report?  Why are some files reported
under debian/ and others under gnat-4.1-4.1.1/debian/?  How should I
read the numbers and the + or - signs on the right?

-- 
Ludovic Brenta.



Reply to: