Your message dated Tue, 27 Dec 2022 23:24:11 +0000
with message-id <e1pajip-00cbio...@fasolo.debian.org>
and subject line Bug#1027107: Removed package(s) from unstable
has caused the Debian Bug report #907977,
regarding python-minimal: please consider adding argparse to minimal modules
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 ow...@bugs.debian.org
immediately.)
--
907977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-minimal
Version: 2.7.15-3
Severity: wishlist
I am one of the upstream maintainers of GNU libc. We are considering
starting to use Python for scripts run during the build. This obviously
adds some version of Python to the set of packages that need to be built
early in the process of bringing up a new architecture, and we want to
minimize the hassle for people doing that work. We think it would help
if we made sure sure that all Python scripts run during the build work
with only Debian's python-minimal installed; thus, most of the external
libraries pulled in by the full Python stdlib would not be required.
We've looked over the set of modules included in python-minimal, and the
only one that's missing that we're sure we want to use is argparse.
Would you please consider adding argparse to the set of modules included
in python-minimal? This would also require adding copy and copy_reg, but
in Python 2 all of those appear to be pure-Python modules (no C component)
so I should think it wouldn't be a huge extra maintenance burden.
The discussion about using Python scripts during the build of glibc starts at
https://sourceware.org/ml/libc-alpha/2018-08/msg00190.html and continues at
https://sourceware.org/ml/libc-alpha/2018-09/msg00025.html . We currently
plan to keep our scripts compatible with both Python 2 and 3 at least through
upstream EOL for Python 2, so I'm going to file a copy of this bug against
python3-minimal.
Thanks,
zw
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python-minimal depends on:
ii dpkg 1.19.0.5+b1
ii python2-minimal 2.7.15-3
ii python2.7-minimal 2.7.15-4
Versions of packages python-minimal recommends:
ii python 2.7.15-3
python-minimal suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.7.18-3+rm
Dear submitter,
as the package python-defaults 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/1027107
The version of this package that was in Debian prior to this removal
can still be found using https://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
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
