Debian Bug report logs - #936391
dhcpy6d: Python2 removal in sid/bullseye

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: maintonly@bugs.debian.org

Subject: dhcpy6d: Python2 removal in sid/bullseye

Date: Fri, 30 Aug 2019 07:14:57 +0000

Package: src:dhcpy6d
Version: 0.4.3-1
Severity: normal
Tags: sid bullseye
User: debian-python@lists.debian.org
Usertags: py2removal

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:dhcpy6d

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.

Message #24 received at 936391@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: Moritz Schlarb <schlarbm@uni-mainz.de>

Cc: Henri Wahl <h.wahl@ifw-dresden.de>, 905014@bugs.debian.org, 936391@bugs.debian.org

Subject: Re: Bug#905014: I'm adopting dhcpy6d

Date: Sat, 22 Feb 2020 23:41:49 +0100

[Message part 1 (text/plain, inline)]

Hi Moritz,

I'm very sorry for the late reply, but I only discovered your mail
today when working on a python-3-supporting dhcpy6d package (c.f.
#936391). You only sent the mail to the bug report which doesn't
forward it to the bug report submitter — and I forgot to subscribe to
messages to this bug report (done now), so I never received your mail
and only downloaded it now from the bug report to be able to reply to
it.

Moritz Schlarb wrote in March 2019:
> I'm willing to adopt dhcpy6d.

Thanks, much appreciated!

> I will create a project in the Salsa PAPT namespace for it.

Ah, cool, so you're someone who has more Python knowledge than I have!

Currently despairing with good and bad python module paths, lintian
claiming that using dh_python3 would fix those paths while I already
use dh_python3 and it doesn't help... Also the test suite still fails
due to unrecognized, but generated commandline options I don't seem to
be able to influence.

See https://github.com/xtaran/dhcpy6d/tree/debian-python3 for my
effort so far.

> Someone needs to add me to the upload ACL though.

I assume you are a DM then. Is that something which someone from PAPT
will do or do you expect me to do that? In the latter case, I'd prefer
to sponsor one or two uploads first.

At least I haven't found a dhcpy6d git repo on Salsa yet, neither
under https://salsa.debian.org/python-team/applications nor with a
global search on Salsa.

		Regards from the Debian Snow Camp, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

[signature.asc (application/pgp-signature, inline)]

Message #29 received at 936391@bugs.debian.org (full text, mbox, reply):

From: Henri Wahl <h.wahl@ifw-dresden.de>

To: Axel Beckert <abe@debian.org>, 936391@bugs.debian.org, Moritz Schlarb <schlarbm@uni-mainz.de>

Cc: 905014@bugs.debian.org

Subject: Re: Bug#936391: Bug#905014: I'm adopting dhcpy6d

Date: Sun, 1 Mar 2020 12:54:18 +0100

[Message part 1 (text/plain, inline)]

Hi,

I pushed to branch master on https://github.com/HenriWahl/dhcpy6d a
version which at least produced working .deb file. Might be still a
little bit rough but maybe it helps to get it running.

I renamed main.py to dhcpy6d.py by the way and copy it to
/usr/sbin/dhcpy6d as starter.

-- 
Henri Wahl

IT Department

Leibniz-Institut für Festkörper- und Werkstoffforschung Dresden e.V.
Helmholtzstr. 20, 01069 Dresden, Germany

tel: +49 (3 51) 46 59 - 797
email: h.wahl@ifw-dresden.de
https://www.ifw-dresden.de

Nagios status monitor Nagstamon: https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d: https://dhcpy6d.ifw-dresden.de

S/MIME: https://nagstamon.ifw-dresden.de/pubkeys/smime.pem
PGP: https://nagstamon.ifw-dresden.de/pubkeys/pgp.asc

[0xFAC1C12483E6CEC2.asc (application/pgp-keys, attachment)]

[smime.p7s (application/pkcs7-signature, attachment)]

Message #38 received at 936391@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 905014@bugs.debian.org, 936391@bugs.debian.org

Cc: Henri Wahl <h.wahl@ifw-dresden.de>, Moritz Schlarb <schlarbm@uni-mainz.de>

Subject: Short status message about dhcpy6d in Debian Unstable and the Python 2 to 3 migration

Date: Sun, 30 Aug 2020 23:02:11 +0200

Hi,

just a short update on dhcpy6d in Debian Unstable (and the Python 2 to
3 migration):

I'm planning to do an upload of the 1.0.1 upstream version to Debian
Unstable soon (next few days) to fix the Python 2 to 3 migration issue
(#936391) and get the package back in shape.

The RFA (#905014) still stands as I still don't have use for dhcpy6d
anymore (due to a job change a while ago). I can only test the package
under an artificial conditions in a temporary environment with e.g. a
handful Raspberry Pis and a desktop switch.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #43 received at 936391@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 905014@bugs.debian.org, 936391@bugs.debian.org

Cc: Henri Wahl <h.wahl@ifw-dresden.de>, Moritz Schlarb <schlarbm@uni-mainz.de>

Subject: Re: Bug#905014: Short status message about dhcpy6d in Debian Unstable and the Python 2 to 3 migration

Date: Thu, 3 Sep 2020 19:38:04 +0200

Hi,

Axel Beckert wrote:
> just a short update on dhcpy6d in Debian Unstable (and the Python 2 to
> 3 migration):
> 
> I'm planning to do an upload of the 1.0.1 upstream version to Debian
> Unstable soon (next few days) to fix the Python 2 to 3 migration issue
> (#936391) and get the package back in shape.

Based on Henri's (binary-only) packaging changes for Python 3, I got a
version which builds as source and as binary package at
https://salsa.debian.org/debian/dhcpy6d

But it still throws a lot of lintian warnings, so there's still a lot
of work ahead before I can upload this.

You should be able to follow my packaging improvements in that git
repository.

Moritz: I've given you write access to the above mentioned git
repository. Feel free to join and maybe later take over?

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #50 received at 936391-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 936391-close@bugs.debian.org

Subject: Bug#936391: fixed in dhcpy6d 1.0.2-1

Date: Mon, 14 Dec 2020 06:06:30 +0000

Source: dhcpy6d
Source-Version: 1.0.2-1
Done: Axel Beckert <abe@debian.org>

We believe that the bug you reported is fixed in the latest version of
dhcpy6d, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 936391@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated dhcpy6d package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 14 Dec 2020 06:25:15 +0100
Source: dhcpy6d
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert <abe@debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Closes: 936391
Changes:
 dhcpy6d (1.0.2-1) unstable; urgency=low
 .
   * Prepare separating Debian packaging from upstream repo:
     + Update Vcs-* headers to point to Salsa.
     + Add debian/upstream/metadata file.
     + Generate pure Debian git history via "gbp import-dscs --debsnap",
       merge it with upstream's git history up to "debian/0.4.3-1".
     + Add a debian/gbp.conf.
   * Import upstream release 1.0.2 and parts of upstream's Python 3 based
     packaging. (Closes: #936391)
     + Upstream moved init.d script as well as systemd service file under
       debian/. The latter differs for /etc/default/dhcpy6d integration.
     + Minor wording fixes in the 0.4.2-1 changelog entry.
     + Switch packaging to Python 3 (only).
     + Bump debhelper build-dependency (but not compat) to 12.1.1.
     + Depend on lsb-base.
     + Move python*-dnspython from Suggests to Depends.
   * Fix upstream packaging as needed:
     + Drop X-Python*-Version headers.
     + Fix broken setup.py (which creates files during clean target) by
       creating debian/clean with an according entry.
     + Also add PKG-INFO, SOURCES.txt, dependency_links.txt, top_level.txt
       and dhcpy6d.egg-info to debian/clean.
     + Drop debian/rules lines related to hardcoded Python 3.7 version.
     + Merge usr/share/dhcpy6d/ and usr/share/dhcpy6d/default entries in
       dhcpy6d.dirs.
     + Drop var/lib and var/log from dhcpy6d.dirs.
     + Do not install log file.
     + Add missing ${misc:Pre-Depends} for --skip-systemd-native.
     + Add missing build-dependency on python3-setuptools.
   * Bump debhelper compatibility level to 13.
     + Build-depend on "debhelper-compat (= 13)" to replace debian/compat.
     + Drop build-dependency on dh-systemd.
     + Drop "--with systemd" from debian/rules.
   * Remove trailing whitespace and reduce all double blank lines between
     old debian/changelog entries.
   * debian/copyright: Use HTTPS for format URL.
   * Set "Rules-Requires-Root: binary-targets". (dh_python3 fails with
     "no".)
   * debian/rules: Drop unneeded "get-orig-source" target. Also fixes
     Lintian warning debian-rules-parses-dpkg-parsechangelog.
   * Declare compliance with Debian Policy 4.5.1. (No changes required.)
   * Bump debian/watch version from 3 to 4. Thanks Lintian!
Checksums-Sha1:
 857ea3a359f46713fd89166a95604dd71b2c7d0b 1926 dhcpy6d_1.0.2-1.dsc
 89c143d99310ab27516c5caa84e49de433a65a28 124998 dhcpy6d_1.0.2.orig.tar.gz
 63fd4412f3e30ce439bd41b4c376b90862633056 7600 dhcpy6d_1.0.2-1.debian.tar.xz
 650c6654e8904cf9b18f0bf688b6b37b9cc9ae5b 6876 dhcpy6d_1.0.2-1_source.buildinfo
Checksums-Sha256:
 a0f402a0b730b4cae3893f11581f89ccd8e3de3587605c1c3ada6c93cc039e1a 1926 dhcpy6d_1.0.2-1.dsc
 836906316c5b9aa108448dec5811db2631ce38864c6787a4993e2ae9ac7127cb 124998 dhcpy6d_1.0.2.orig.tar.gz
 545c956bbaf0254a0c37596b44cb77f533bb114b1113efa21af5688e25da96ad 7600 dhcpy6d_1.0.2-1.debian.tar.xz
 6ca12f860ef57cafa7d297a808f89b24529b1379cba267517b310b963428318c 6876 dhcpy6d_1.0.2-1_source.buildinfo
Files:
 562743e076bc62de8b83aa82849eca69 1926 net optional dhcpy6d_1.0.2-1.dsc
 ada185d45b9ec1edf1cc7505fe1a71ce 124998 net optional dhcpy6d_1.0.2.orig.tar.gz
 2831e5568fdd44968014181e189543b1 7600 net optional dhcpy6d_1.0.2-1.debian.tar.xz
 67f10dd064b84494f57f626638ba741e 6876 net optional dhcpy6d_1.0.2-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAl/W94EACgkQa+Zjx1o1
yXWFYxAAs9K4RiQxsnoh5KwTMC51jT4nwNBq/rbW2BcozlvnSBHWw8fFtEmo1zbb
BR6ip0tk156IKSccHwYoyiTSpJ6ad0jz+jhQkTMYu+pCvfLH4XqJyrIF/rBHSvUK
vH7VHIyOrCxIsGcOtkjMd/yL1QOxknXwqy+1vJ9cpN8N6AeL4RJOtM+8Z/3iSTIU
vuUOtbrkp9NP1N4W3igj/y06bVUPSNGn5DGVj3bA0XspVNag0x1+lAwqhav2/tY+
x6JuHoY3ah8uab2T0lqc1c6RtZWU0aP7/aT0oqCAhheceBwrc4Nzh2VPWPJBQ2lq
9av6UPbTvdy9P2IXmuCqzYtHaG84yFID4p68df7tp/dSXs/VcQA//FoPypcl0CLR
3QUpWthRf83WhyBTKU8IxR+kUXJufVcvfFyXNlXFxGuCAl0z0Rqse6+Jf9o9gpNW
UAtGI/5CqvQV9Ozyzn4lFgrJZ3ycyjjLvEb44KXB0f/YOW+PCmK/iiT2c9B+VdFr
QmkkrCWFR8lbzCAG9cSJkPQVU2JqsZB0Pc6Cludv4AbqcgZvTXpyuU/LGltg1ZgZ
0is1BY+/kuDe36ovfDHqb+mwtsvW2lFhAh3I5smHTTc2biXVfrTIQwcTwWDZEdjO
INWPgRAoOh+YHGGL8kXliegVf/RHGyrFqDU5PLgEdSz31St5mv0=
=uBIM
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.