Your message dated Sat, 22 Mar 2025 11:28:37 +0100
with message-id <Z96Q1bf3uxB8io1N@lamella>
and subject line Re: Bug#1101001: chrony: Please cleanup dpkg-statoverrides
properly
has caused the Debian Bug report #1101001,
regarding chrony: Please cleanup dpkg-statoverrides properly
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.)
--
1101001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101001
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 4.6.1-1
Severity: normal
X-Debbugs-Cc: [email protected]
Hi Vincent,
I installed and removed chrony=4.6.1-1 in an unstable schroot and
afterwards dpkg complains:
dpkg: unrecoverable fatal error, aborting:
unknown system group '_chrony' in statoverride file; the system group got
removed
before the override, which is most probably a packaging bug, to recover you
can remove the override manually with dpkg-statoverride
E: Sub-process /usr/bin/dpkg returned an error code (2)
This appears to be because your package didn't clean up it's
dpkg-statoverrides:
$ dpkg-statoverride --list | grep chrony
root _chrony 640 /etc/chrony/chrony.keys
_chrony _chrony 750 /var/lib/chrony
_chrony _chrony 750 /var/log/chrony
--Daniel
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Le 2025-03-22 10:24, Daniel Gröber a écrit :
> Control: done -1
>
> Hi Vincent,
>
> On Fri, Mar 21, 2025 at 09:47:09PM +0100, Vincent Blut wrote:
> > Control: tags -1 + moreinfo
> >
> > Hi Daniel,
> >
> > Le 2025-03-21 16:57, Daniel Gröber a écrit :
> > > Package: chrony
> > > Version: 4.6.1-1
> > > Severity: normal
> > > X-Debbugs-Cc: [email protected]
> > >
> > > Hi Vincent,
> > >
> > > I installed and removed chrony=4.6.1-1 in an unstable schroot and
> > > afterwards dpkg complains:
> > >
> > > dpkg: unrecoverable fatal error, aborting:
> > > unknown system group '_chrony' in statoverride file; the system
> > > group got removed
> > > before the override, which is most probably a packaging bug, to
> > > recover you
> > > can remove the override manually with dpkg-statoverride
> > > E: Sub-process /usr/bin/dpkg returned an error code (2)
> > >
> > >
> > > This appears to be because your package didn't clean up it's
> > > dpkg-statoverrides:
> > >
> > > $ dpkg-statoverride --list | grep chrony
> > > root _chrony 640 /etc/chrony/chrony.keys
> > > _chrony _chrony 750 /var/lib/chrony
> > > _chrony _chrony 750 /var/log/chrony
> >
> > chrony does clean stat overrides on purge. From d/postinst:
> > for d in /var/lib/chrony /var/log/chrony /etc/chrony/chrony.keys; do
> > if dpkg-statoverride --list "$d" >/dev/null; then
> > dpkg-statoverride --remove "$d"
> > fi
> > done
> >
> > Since this issue does not seem to be reproducible outside schroot, I'm
> > assuming
> > it is due to the way it has been configured. By default, schroot copies some
> > files from the host (e.g. /etc/passwd, /etc/shadow, /etc/group) into the
> > chroot
> > each time a new session is started. Could this be the issue at play?
>
> Ah, I think you're spot on.
>
> I must have exited the session (I thought I didn't!) after removing but not
> purging chrony. I just tested this and my schroot does ofc. overwrite
> /etc/passwd which breaks the leftover statoverrides. My bad.
Thanks for reporting back Daniel!
signature.asc
Description: PGP signature
--- End Message ---
