Your message dated Thu, 29 Jan 2026 08:20:48 +0000
with message-id <[email protected]>
and subject line Bug#1119672: fixed in libapache2-mod-ldap-userdir 1.1.19-2.2
has caused the Debian Bug report #1119672,
regarding libapache2-mod-ldap-userdir: Intend to Orphan:
libapache2-mod-ldap-userdir
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 [email protected]
immediately.)
--
1119672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119672
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libapache2-mod-ldap-userdir
Version: 1.1.19-2.1
Severity: important
X-Debbugs-Cc: John Morrissey <[email protected]>, [email protected], Package
Salvaging Team <[email protected]>
Hi,
This is an attempt to introduce a new procedure, which I propose to call
Intend To Orphan. While we have an established process for making minimal,
fine-grained changes to a package, it does not cover broader
improvements such as migrating to Salsa, updating the Standards-Version,
or adjusting the debhelper compatibility level. However, some packages
could benefit from more extensive changes, and this procedure aims to
provide a structured way to implement them. Unlike the well-established
Package Salvage procedure[1] which requires an active Uploader, the goal
here is to allow collaborative work on a package on Salsa, even if no
active uploader expresses interest in maintaining it.
--> Maintainer set to Debian QA Group <[email protected]>
If you do not agree to large-scale changes to this package, including
maintaining it on Salsa, feel free to close this bug or tag it as
'wontfix' to inform others. There is no obligation to continue reading
if your stance is clear, and that decision will, of course, be
respected.
Otherwise, I will follow the well-established timing of the ITS
procedure, waiting 21 days before performing a QA Upload to delayed=10.
This procedure has not yet reached consensus--I am simply exploring
whether it could be accepted. It was disussed at DebConf25 but some
consensus is pending. Please keep in mind that the goal of this process
is to help ensure that packages remain up to date and well maintained.
If you have suggestions for improving it, your feedback is most welcome.
I'm interested in orphaning the package libapache2-mod-ldap-userdir. It
meets the following criteria:
- NMUs
- Bug filed against the package do not have answers from the
maintainer.
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- No maintainer upload in the last 13 years
- Standards-Version < 4
I have set up a repository within Debian/[2]. This team functions
similarly to the former collab-maint on Alioth, allowing any Debian
Developer to make team uploads[3]. I understand that some maintainers
may prefer not to transition to collaborative maintenance, and I want to
emphasize that this is not intended as a hostile action. My goal is to
make the transition to using a Git repository on Salsa smoother and more
convenient for you.
This package was highlighted in the Bug of the Day[4] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to help newcomers become familiar
with a consistent Git-based workflow.
Kind regards
Andreas.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/debian/libapache2-mod-ldap-userdir
[3]
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group
[4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- 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
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-ldap-userdir
Source-Version: 1.1.19-2.2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libapache2-mod-ldap-userdir, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <[email protected]> (supplier of updated
libapache2-mod-ldap-userdir 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 19 Jan 2026 08:29:10 +0100
Source: libapache2-mod-ldap-userdir
Architecture: source
Version: 1.1.19-2.2
Distribution: unstable
Urgency: medium
Maintainer: John Morrissey <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 989941 1119672
Changes:
libapache2-mod-ldap-userdir (1.1.19-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
Closes: #1119672
* Set Homepage to Github
* Maintain package in Debian team on Salsa
* d/watch: Point watch file to Github commits in case there might
be some new commit
* d/rules: Short dh
Closes: #989941
* d/control: Do not manually create debug package
* debhelper-compat = 13
* d/copyright: Point Source to Github
* Standards-Version: 4.7.3
* debputy lint --auto-fix (routine-update)
* Exclude -branch from hardening options
Checksums-Sha1:
84475e429cf027d2f70c2979f6654c66b61ee9bb 2118
libapache2-mod-ldap-userdir_1.1.19-2.2.dsc
935882b92e85d6dd0c45e344def4691fdb09b123 2992
libapache2-mod-ldap-userdir_1.1.19-2.2.debian.tar.xz
88608a61bcb69c3165aa0aea7b754135599dfc41 7370
libapache2-mod-ldap-userdir_1.1.19-2.2_amd64.buildinfo
Checksums-Sha256:
de7ca0157d63bfeb611d146e3842b084eae2f69536893f2ee778909f433af2cc 2118
libapache2-mod-ldap-userdir_1.1.19-2.2.dsc
f864490d3ef3bc8d17f4f007c6aead47362192e4facbb65a1cdabd251e1efaad 2992
libapache2-mod-ldap-userdir_1.1.19-2.2.debian.tar.xz
295094a72c8ca32da76ee8367d8b83ecadbb552b5376922180698b40f83f6194 7370
libapache2-mod-ldap-userdir_1.1.19-2.2_amd64.buildinfo
Files:
303a3fb9c6bf4732d9597e4c4885186e 2118 httpd optional
libapache2-mod-ldap-userdir_1.1.19-2.2.dsc
927bcc3fd649092e3d18ab588c029ca8 2992 httpd optional
libapache2-mod-ldap-userdir_1.1.19-2.2.debian.tar.xz
4ce3828e0b48d4752d40c97b5b73bf91 7370 httpd optional
libapache2-mod-ldap-userdir_1.1.19-2.2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlt4DYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHYww/+Md9/k9BZ+Eo3Irc59tOHgLs+mrvFPwti
g3FGRwHTxeDchO5zkc+lkd77eB0YenVNuqxQLfWQclUHsUcpDygWvvwkr21fxCJh
XqCSch+fPEAIcCnEuaU509aXbDOhE0CtAhizpjMsMW3i/y/lxagMe4TdXRtTMqiH
SELSxOcXqgbCxUG8kXoHcP8ZyYfUG5GitK12uIpMc8OLdvO9DOe1xdol9uHuK7Ws
3VmS0tkOz9H/irLEf/QQEeP7Cg3eV423lPcr/i68rTodRNgu7CLsSv4pJNqHCiUf
TTGuQLlZdcq39VlkaaD8cVvFmOr4thyMZxp9/OjDdGvzcIgCHk2vQGpxTz0bIgaV
sOyHCmdSeu1/5V1Fcj5Od1QoCivdBFvpq6xmxr3f5tqoD79cQMnOHguWnkBLBwBc
UOTXW1jE/0Hji6KNRTNXHv/MT8wooyDtkiO+X5zKnmOakkLKbDpoWoYU3cwa1dvk
dohQ3eC9096tBNSxJgJAj7/OSQGnYQDqt+e7bpV6zdQtarf+sY2FXvHe4IfoM8O3
ri8lZ62eQa9k4wz4sqc6hb0mU1SMS7oFLYF6r+G3g7S37+7IHQQ2oAqMnc2cqzym
s1mb6l5a6h49kl+uOcKvDNZEbVYQt1FlYLqIjfD5MAvxj+Y5PPP8CDpGhmz0e3B+
IpBc6vmcQDQ=
=/Y4z
-----END PGP SIGNATURE-----
pgp1Obj82obps.pgp
Description: PGP signature
--- End Message ---
