Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.

  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-python@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects <bug number of blocking py2removal bug> + src:libgnatcoll-bindings

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-python@lists.debian.org mailing list.

Hello.

An upload to unstable is planned as part of the gnat-9 transition.
It will include explicit python2 dependencies.

This bug was in fact duplicated by #952549, which has been closed now.

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:libgnatcoll-bindings)Build-Depends->python2-dev
(source:libgnatcoll-bindings)Build-Depends->libpython2-dev
(binary:libgnatcoll-python18-dev)Depends->libpython2-dev
(binary:libgnatcoll-python18)Depends->libpython2.7

Re-opening, so that they can be taken care of.

Popcon for gnat-gps is just above the 300 limit.  The main reason to
package libgnatcoll-bindings is that gnat-gps depends on the python
module.  libgnatcoll-bindings is mostly ready for python3, but not
gnat-gps.  For now, libgnatcoll-bindings is stuck with Python2.

Upstream of both packages intends to update the python support for the
middlef 2021 if all goes well.  Libgnatcoll-bindings and gnat-gps will
most probably have to skip next Debian release.

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.

Dear submitter,

as the package libgnatcoll-python has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1011991

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note 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.

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)