Bug#1033730: adduser changes in bookworm

[Marc Haber]

Package: release-notes
Severity: normal

Hi,

adduser has changed quite a bit during the bookworm cycle. We have
deprecated a few command line and configuration options and have renamed
others to be less confusing and a bit more consistent to themselves.
There have also been behavioral changes regarding the
--disabled-password and --disabled-login options of adduser that might
affect package maintainer scripts. User might also be affected by
changes in the handling of primary and supplementary groups and the
permissions set by the home directories of newly created accounts.
Newly created system users also have their home directory set to
/nonexistent unless the --home option is given as well.

Whatever incomplete LDAP support that was present in Adduser was
removed.

Users of adduser are advised to check /usr/share/doc/adduser/NEWS.Debian
and /usr/shade/doc/adduser/README.Debian and the manual pages that come
with the package to find out which changes are planned for Debian's
release after bookworm, enabling them to do necessary changes to their
packages and code during the bookworm cycle to get ready for bookworm+1.

As adduser is a very widely installed package, this may warrant
mentioning in the release notes.

Greetings
Marc

[Holger Wansing]

I think, we don't want to have all of the text from the bugreport in the
release-notes, it's much to specific stuff for the majority of people IMO.

Maybe we just want some more generic text like:



Extensive changes in adduser for bookworm

There have been several changings in adduser during the development cycle of
bookworm. Users might be affected by this, and also developers of other
packages, if they use adduser in their maintainer scripts.

Remember to check /usr/share/doc/adduser/NEWS.Debian
and /usr/shade/doc/adduser/README.Debian as well as the manual pages that come
with the package for detailed information.

Developers also can find out there, which changes are planned for Debian's next
release after bookworm (trixie), enabling them to do necessary changes to their
packages and code during the bookworm cycle to get ready for trixie.

[Marc Haber]

Hi Holger,

thanks for your answer.
I'm fine with that.

Greetings
Marc

[Paul Gevers]

Control: tags -1 patch pending

Hi,

Post by Marc Haber
I'm fine with that.

I created this text with Marc:

https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/179

Paul

[Paul Gevers]

Hi Holger,

Again, thanks for working on the notes.

Post by Holger Wansing
Developers also can find out there, which changes are planned for Debian's next
release after bookworm (trixie), enabling them to do necessary changes to their
packages and code during the bookworm cycle to get ready for trixie.

I think you are addressing Debian Developers here? I don't consider the
Release Notes as the right platform for that.

Paul

[Holger Wansing]

Hi,

Post by Marc Haber
Hi Holger,
Again, thanks for working on the notes.

Post by Holger Wansing
Developers also can find out there, which changes are planned for Debian's next
release after bookworm (trixie), enabling them to do necessary changes to their
packages and code during the bookworm cycle to get ready for trixie.

I think you are addressing Debian Developers here? I don't consider the Release Notes as the right platform for that.

In that case we can just skip this last part and go with
the rest...

Holger

[Debian Bug Tracking System]

tags -1 patch pending

Bug #1033730 [release-notes] adduser changes in bookworm
Added tag(s) pending and patch.

[Debian Bug Tracking System]

Your message dated Sun, 28 May 2023 17:25:28 +0200
with message-id <2fb3539a-4c15-e643-3a99-***@debian.org>
and subject line Re: Bug#1033730: [release-notes] adduser changes in bookworm
has caused the Debian Bug report #1033730,
regarding adduser changes in bookworm
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 ***@bugs.debian.org
immediately.)