#905014 RFA: dhcpy6d -- MAC address aware DHCPv6 server written in Python

Package:
wnpp
Source:
wnpp
Submitter:
Axel Beckert
Date:
2021-08-25 00:27:03 UTC
Severity:
normal
Tags:
#905014#5
Date:
2018-07-30 14:33:20 UTC
From:
To:
Package: wnpp
Severity: normal
Tags: ipv6

Hi,

due to a job change a while ago, I'm no more using dhcpy6d and I
currently also don't have a setup where I'm able to test it properly
before uploading.

The listed co-maintainer, Henri Wahl (X-Debbugs-Cc'ed), is actually
upstream and he has started the package initially while I revamped it to
be uptodate with Debian standards.

Upstream does publish .deb packages of dhcpy6d, but they're meant for
Debian Stable and their packaging doesn't change much unless the package
in Debian Unstable changes. Upstream says, he's not experienced enough
with Debian's standards and procedures to maintain the Debian's official
dhcpy6d package himself alone. (And he would need a sponsor anyways.)

So we're basically searching for someone who can take over the main part
of packaging work for dhcpy6d. Anything which is related to upstream
code should be already covered by Henri as the communication with him
works very good (usually GPG encrypted :-). It works so good that we
currently do the Debian packaging in upstream's git repo at
https://github.com/HenriWahl/dhcpy6d in the branch "debian".

Currently the dhcpy6d package in Debian is multiple releases behind
upstream: 0.4.3 vs 0.7.2. So getting a new upstream version into Debian
would be the first thing to do for the prospective new maintainer of
this package. It's already a "3.0 quilt" package, but still at debhelper
9 and standards version 3.9.8 (as in Stretch).

Information about the package:

Package: dhcpy6d
Version: 0.4.3-1
Installed-Size: 255
Maintainer: Axel Beckert <abe@debian.org>
Architecture: all
Depends: adduser, ucf, python:any (<< 2.8), python:any (>= 2.7.5-5~)
Pre-Depends: dpkg (>= 1.16.5)
Suggests: python-dnspython, python-mysqldb, python-psycopg2
Description-en: MAC address aware DHCPv6 server written in Python
 Dhcpy6d delivers IPv6 addresses for DHCPv6 clients, which can be
 identified by DUID, hostname or MAC address as in the good old IPv4
 days. It allows easy dualstack transition, addresses may be
 generated randomly, by range, by arbitrary ID or MAC address. Clients
 can get more than one address, leases and client configuration can be
 stored in databases and DNS can be updated dynamically.
Homepage: https://dhcpy6d.ifw-dresden.de/
Tag: implemented-in::python, interface::daemon, network::configuration,
 network::server, protocol::dhcp, protocol::ipv6, role::program,
 scope::utility, use::configuring
Section: utils
Priority: optional
Filename: pool/main/d/dhcpy6d/dhcpy6d_0.4.3-1_all.deb
Size: 58434

Package: dhcpy6d
Binary: dhcpy6d
Version: 0.4.3-1
Maintainer: Axel Beckert <abe@debian.org>
Uploaders: Henri Wahl <h.wahl@ifw-dresden.de>
Build-Depends: debhelper (>= 9~), python-all (>= 2.6.6-3~)
Build-Depends-Indep: dh-python
Architecture: all
Standards-Version: 3.9.8
Format: 3.0 (quilt)
Files:
 3c202b1824f0381022c188d79cf1c086 1886 dhcpy6d_0.4.3-1.dsc
 429c1a0f66e6dd6453bb94ace7a1f03c 70668 dhcpy6d_0.4.3.orig.tar.gz
 4e1aeafd2655bf8962ff7d9542489e16 5732 dhcpy6d_0.4.3-1.debian.tar.xz
Vcs-Browser: https://github.com/HenriWahl/dhcpy6d
Vcs-Git: https://github.com/HenriWahl/dhcpy6d.git -b debian
Homepage: https://dhcpy6d.ifw-dresden.de/
Package-List:
 dhcpy6d deb net optional arch=all
Directory: pool/main/d/dhcpy6d
Priority: extra

		Regards, Axel

#905014#10
Date:
2019-03-07 19:19:33 UTC
From:
To:
Hi everyone,

I'm willing to adopt dhcpy6d.

I will create a project in the Salsa PAPT namespace for it.
Someone needs to add me to the upload ACL though.

Regards,
Moritz

#905014#25
Date:
2020-02-22 22:41:49 UTC
From:
To:
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:

Thanks, much appreciated!

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.

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

#905014#30
Date:
2020-03-01 11:54:18 UTC
From:
To:
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.

#905014#35
Date:
2020-04-03 10:50:43 UTC
From:
To:
Hi there,

I want just inform you that the 1.0 release is out now. Maybe this one
makes packaging easier.

Thanks and best regards
Henri

#905014#40
Date:
2020-08-30 21:02:11 UTC
From:
To:
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

#905014#45
Date:
2020-09-03 17:38:04 UTC
From:
To:
Hi,

Axel Beckert wrote:

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

#905014#50
Date:
2021-08-25 00:22:08 UTC
From:
To:
Hi Moritz,

Moritz Schlarb wrote in March 2019:
[…]

despite there was quite some more discussion in this bug report, I
unfortunately haven't read or seen any further activity of you in this
matter in the past 2.5 years. (I though see other Debian activity from
you, so you don't seem MIA. :-)

To allow others to adopt this package as well, I'm herewith setting it
back to RFA. Feel free to change it back to ITA if you still intend to
adopt this package. (It though would be nice to see some activity of
you towards that direction, too.)

To any potential adopter of this package, be it Moritz or someone
else:

As of 21st of August, the package in Debian Unstable and Testing is
again up to date with upstream after the freeze for the Debian 11
Bullseye release. https://salsa.debian.org/debian/dhcpy6d is up to
date as well as and all contain the package version 1.0.5-1.

Since I have a minimal test environment at home, I can rudimentarily
test the package and will do further updates of the package. But it
still holds true that I don't use it anymore in production — which is
suboptimal for a package maintainer. Accordingly I would like to see
someone adopting it who actually uses it in production — and who
preferably knows more Python than me. ;-)

But since Henri is a very helpful and responsive upstream, the amount
Python knowledge actually isn't such a hard adoption criteria. :-)

P.S.: Please be aware that the project's homepage URL (mainly the
domain) as well as upstream's e-mail address changed. With the upload
from yesterday, the package is also up to date with regards to this.

		Regards, Axel