Source: libnet-ldapapi-perl
Version: 3.0.7-4
Severity: normal
X-Debbugs-Cc: Bill MacAllister <[email protected]>, Russ Allbery
<[email protected]>, Debian Perl Group
<[email protected]>, Package Salvaging Team
<[email protected]>, [email protected]
Hi Bill and Russ,
I'm currently checking packages that are packaging CPAN modules which
are not maintained by the Debian Perl Group on Salsa whether it might
make sense to hand these over to Debian Perl Group. I stumbled upon
libnet-ldapapi-perl and can't find any good reason why not to move this
package to a team that has a great tradition to make team wide changes
and thus reducing the work for single maintainers.
In the past I've filed some ITS bugs for maintainers suspected to be
MIA but I know at least for Russ this is not the case. Thus asking
here before doing any work on the package first.
I'd volunteer to migrate your git repository[1] to Salsa (every DD
has push permissions to perl-team/modules), bring the packaging in
line with he Perl team policy and fix bug #1102826, if you agree to
this and will not insist into keeping the package outside the team
scope. This is perfectly fine - just tag this bug wontfix or close
it - whatever you prefer.
Kind regards
Andreas.
[1] https://github.com/whm/libnet-ldapapi-perl
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5,
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
