Your message dated Wed, 24 May 2023 22:18:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#1036705: override: adduser:admin/required
has caused the Debian Bug report #1036705,
regarding override: adduser:admin/required
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.)
--
1036705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036705
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: [email protected]
Usertags: override
X-Debbugs-Cc: [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected]
Control: affects -1 + src:adduser
Hi,
I am requesting to override the priority of adduser to become required.
Rationale
apt used to depend on adduser and apt is required, so adduser is
transitively required in bullseye. Johannes and myself worked towards
making apt not depend on adduser and that work succeeded. Unfortunately,
that also removed adduser from the transitively required set and now
debootstrap --variant=minbase no longer contains adduser while it
earlier did. In the mean time, packages started using deluser for postrm
purge, so they effectively assume that it was essential, which it isn't.
We've now fixed such postrm scripts to no longer do that, but we agreed
with the release team that it should be difficult to remove for bookworm
in order to make purging packages left over from bullseye just work
after and upgrade to bookworm. Originally, the idea was to add back the
dependency from apt. Instead, we made apt "Protected: yes". This still
doesn't install it by default, but makes removal difficult which is what
saves postrm purge scripts, so all should be good. Except that this
makes piuparts unhappy as it tries to remove adduser and apt being
unhappy about it. This is presently breaking testing migration for a
number of packages. So now we thought about it again and got to the
conclusion that adduser should also be Priority: required for bookworm
(and unstable until bookworm is released). Doing so is a late change, I
know. However, it gets us back to the bullseye state and in being
required, debootstrap --variant=minbase will install adduser again,
which will fix piuparts. So an we do that?
Helmut
--- End Message ---
--- Begin Message ---
On Wed, May 24, 2023 at 09:58:42PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 trixie
We do not want this change in trixie. In trixe, adduser will just become
a "normal" package that is none of essential, protected nor required.
> At this stage of freeze, it's too late to experiment with Protected: yes
> in required that would work in theory, but where we know that one of
> them fail in practice (by breaking at least piuparts) and for the other
> we don't have any data.
Agreed.
> So, as discussed in today's RT meeting, let's postpone this change to
> trixie (or any other solution that isn't apt depending on adduser).
It's not postpone. The change was meant to be transitional. In trixie
that transition is over.
Helmut
--- End Message ---
