Source: libpsl
Version: 0.21.2-1.1
Severity: wishlist

Hello Tim, hello Daniel,

yeah, you already know about the new upstream releases. Tim, as upstream
author, has actually created them, and the Debian libpsl tracker[0]
prominently indicates them. So what is this bugreport about?

I noticed that this package hasn't seen much maintenance activity
recently. By pointing this out I am not trying to blame you or anyone or
to apply pressure, but rather this led me to wonder whether you might
be in need of some support. 

Well, I'd like to offer my help in packaging these new releases for
Debian. Just like (I hope) I did over the past year with the
publicsuffix list[1], I'd like to keep this package up-to-date, and I am
already somewhat familiar[2] with it as I am with library maintenance in
general[3], so I feel I can contribute. If you don't mind, that is, of
course.

My first steps would be to package the newest release (yes, many of the
changes[4] are not really relevant for Debian, but I like to keep the
delta small), investigate the multi-arch issue[5], check the lintian
warnings[6], and then let's see. But I'd prefer to not do this in some
sort of drive-by maintenance via NMU, but rather to take visible
responsibility, even if that means sticking my name to it by adding me
as an uploader.

If this doesn't suit you in any way, or you have any other plans, please
don't hesitate to mention it. In that case I can still find ways to
contribute in a less invasive way.

So, what do you think?

Cheers,
Flo


[0] https://tracker.debian.org/pkg/libpsl
[1] https://tracker.debian.org/pkg/publicsuffix and
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077255
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028857#40
[3] https://qa.debian.org/developer.php?login=florian%40debian.org
[4] https://github.com/rockdaboot/libpsl/compare/0.21.2...0.21.5
[5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111197
[6] https://udd.debian.org/lintian/?packages=libpsl

Attachment: signature.asc
Description: PGP signature

Reply via email to