#1011991 RM: libgnatcoll-python -- ROM; NPOASR; temporary package not needed anymore

#1011991#5
Date:
2022-05-28 14:28:18 UTC
From:
To:
Hello.

Please remove these packages from unstable:
libgnatcoll-python:src
libgnatcoll-python19
libgnatcoll-python19-dev

I am the maintainer of libgnatcoll-bindings and libgnatcoll-python.

The normal situation is that
the libgnatcoll-bindings source package produces
  libgnatcoll-${COMPONENT}{SOVERSION} and
  libgnatcoll-${COMPONENT}{ALIVERSION}-dev
for various COMPONENTs including python.

A few years ago, the python component was ready for both python2&3,
but its only reverse dependency gnat-gps was requiring python2.

As a temporary measure, the separate libgnatcoll-python source package
was introduced.  This allowed the other components to be updated in
testing, while the python(2) component and gnat-gps were RC-buggy in
unstable (#936869 and #936624 respectively).

Nowadays
* gnat-gps has been RC-buggy for a while.
  It depends on libgnatcoll-python18 that no one is building anymore.
* If/when we manage to rebuild gnat-gps, latest upstream version is
  ready for python3. Hence the unblock command above.

There is no need for a separate package anymore, so
libgnatcoll-bindings builds the python(3) component again.
libgnatcoll-python3.1
libgnatcoll-python3.1-dev
These fully replace the removed packages.

Thanks.

#1011991#10
Date:
2022-06-05 08:50:51 UTC
From:
To:
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libgnatcoll-python |   21.0.0-2 | source
libgnatcoll-python19 |   21.0.0-2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libgnatcoll-python19-dev |   21.0.0-2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
------------------- Reason ------------------- ROM; NPOASR; temporary package not needed anymore ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1011991@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1011991 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)