Marc Haber
2023-12-12 11:30:02 UTC
Package: release-notes
Severity: wishlist
Control: affects -1 1033728
Hi,
Paul suggested that I file this bug as a reminder.
The sudo team is considering to remove sudo-ldap after the trixie
release. A possible migration path would be to use libsss-sudo instead.
See also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033728
https://salsa.debian.org/sudo-team/sudo/-/blob/master/debian/NEWS
The version of sudo that currently ships in unstable has a corresponding
NEWS entry and displays a corresponding debconf message.
Me and the sudo team are not yet sure about what we're going to do with
sudo-ldap post-trixie. We can
(1) remove the package without replacement
(2) replace the package with a transitional package depending on
(2a) libsss-sudo or
(2b) sudo
(3) make sudo-ldap uninstallable so that an upgrade will error out
before breaking sudo-ldap
(4) keep sudo-ldap around
(5) a different method
I am open to suggestions.
I think this is worth mentioning in the trixie release notes. While
trixie will still have a fully functional sudo-ldap, users SHOULD use
the trixiecycle to migrate away from sudo-ldap so that their systems
won't break when sudo-ldap finally goes away in trixie+1.
The final wording for the trixie release notes depends on what we decide
to do post-trixie. Again, I am open to suggestions how to word things.
Feel free to remind me in case I don't keep this on my radar by myself.
Greetings
Marc
Severity: wishlist
Control: affects -1 1033728
Hi,
Paul suggested that I file this bug as a reminder.
The sudo team is considering to remove sudo-ldap after the trixie
release. A possible migration path would be to use libsss-sudo instead.
See also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033728
https://salsa.debian.org/sudo-team/sudo/-/blob/master/debian/NEWS
The version of sudo that currently ships in unstable has a corresponding
NEWS entry and displays a corresponding debconf message.
Me and the sudo team are not yet sure about what we're going to do with
sudo-ldap post-trixie. We can
(1) remove the package without replacement
(2) replace the package with a transitional package depending on
(2a) libsss-sudo or
(2b) sudo
(3) make sudo-ldap uninstallable so that an upgrade will error out
before breaking sudo-ldap
(4) keep sudo-ldap around
(5) a different method
I am open to suggestions.
I think this is worth mentioning in the trixie release notes. While
trixie will still have a fully functional sudo-ldap, users SHOULD use
the trixiecycle to migrate away from sudo-ldap so that their systems
won't break when sudo-ldap finally goes away in trixie+1.
The final wording for the trixie release notes depends on what we decide
to do post-trixie. Again, I am open to suggestions how to word things.
Feel free to remind me in case I don't keep this on my radar by myself.
Greetings
Marc