Processing commands for cont...@bugs.debian.org:
> severity 1035543 normal
Bug #1035543 [e2fsprogs] init-system-helpers: new systemd units may not get
enabled on upgrades from bullseye if systemd is installed
Severity set to 'normal' from 'serious'
> retitle 1035543 e2fsprogs: on an upgrade from
severity 1035543 normal
retitle 1035543 e2fsprogs: on an upgrade from bullseye e2scrub-reap.service may
be wanted by default.target instead of multi-user.target
thanks
On Thu, Jun 01, 2023 at 07:40:25PM +0100, James Addison wrote:
> > So it's not a big deal; is that correct so this patch is not
On Thu, 1 Jun 2023 at 15:48, Theodore Ts'o wrote:
>
> In addition to Bookworm being hard frozen, I question the importance
> of this patch, the bug priority, and whether the title is correct.
> After all, at least with respect to e2fsprogs systemd unit *will*
> still be enabled. It will just be
In addition to Bookworm being hard frozen, I question the importance
of this patch, the bug priority, and whether the title is correct.
After all, at least with respect to e2fsprogs systemd unit *will*
still be enabled. It will just be enabled using
../multi-user.target/wanted instead of
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: jspri...@debian.org
On Thu, 1 Jun 2023 13:53:18 +0200, Jochen wrote:
> * James Addison [2023-06-01 12:44]:
> >Would reverting the Install.WantedBy modification[1][2], restoring
> >e2scrub_reap
> >enablement using 'default.target' on
Package: e2fsprogs
Followup-For: Bug #1035543
Control: tags -1 patch
>From 9ad481148456520f15f92973cdd0cf6caa16a088 Mon Sep 17 00:00:00 2001
From: James Addison
Date: Thu, 1 Jun 2023 13:20:29 +0100
Subject: [PATCH] Revert "e2scrub: use WantedBy=multi-user.target in
e2scrub_reap.service"
This
* James Addison [2023-06-01 12:44]:
Would reverting the Install.WantedBy modification[1][2], restoring e2scrub_reap
enablement using 'default.target' on relevant systems, be a sensible approach
for bookworm until we can figure out the debhelper-system behaviour when that
setting changes?
No,
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org, debian-rele...@lists.debian.org
[ re-introducing the larger cc list audience, plus debian-release ]
Would reverting
Followup-For: Bug #1035543
On Wed, 31 May 2023 09:55:13 +0100, James wrote:
> On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> > If I install systemd into the bullseye chroot and upgrade that to
> > bookworm, both systemd and e2fsprogs are still installed, but
> >
Followup-For: Bug #1035543
On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> If I install systemd into the bullseye chroot and upgrade that to
> bookworm, both systemd and e2fsprogs are still installed, but
> /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service
> does *NOT* get
[trimmed the list of CCs]
Am 30.05.23 um 13:36 schrieb Jochen Sprickerhof:
# find / -name e2scrub_reap.service
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/e2scrub_reap.service
/var/lib/systemd/deb-systemd-helper-enabled/default.target.wants/e2scrub_reap.service
Hi Michael,
* Michael Biebl [2023-05-30 13:23]:
bullseye chroot upgraded to bookworm:
# find /etc/systemd/system/ -name e2scrub_reap.service
/etc/systemd/system/multi-user.target.wants/e2scrub_reap.service
/etc/systemd/system/default.target.wants/e2scrub_reap.service
But when you use a VM:
The title of this bug report is highly misleading.
Let's see what's actually happening here:
bullseye chroot:
# find /etc/systemd/system/ -name e2scrub_reap.service
/etc/systemd/system/default.target.wants/e2scrub_reap.service
bookworm chroot:
# find /etc/systemd/system/ -name
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
Would a 'move /etc/systemd/system/default.target.wants/e2scrub_reap.service
to
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
I've been 'approximately' testing this locally on bookworm by:
* Editing the Install.WantedBy in
On 28/05/2023 11.58, Jochen Sprickerhof wrote:
The point of piuparts is that an upgraded system is different to a newly
installed system, i.e. that the e2scrub_reap.service symlink lies in a
different directory.
Actually the difference is between the minimal bullseye chroot upgraded
to
Hi Ted,
* Theodore Ts'o [2023-05-27 19:45]:
So sure, /etc/systemd.d/system/multi-user.target.wants/e2scrub_reap.service
doesn't exist. *But* it still exists in .../default.target.wants/...
which seems to be enough to keep the e2scrub_reap service enabled. Right?
Yes, that's fine.
In any
On Sat, May 27, 2023 at 11:09:32PM +0200, Helmut Grohne wrote:
> Hi,
>
> I sat down with Jochen in Hamburg to try and fix this.
>
> On Sun, May 14, 2023 at 03:21:24PM -0400, Theodore Ts'o wrote:
> > Can someone send the instructions on how to fix this?
>
> We wish we could give you. Instead, we
Hi,
I sat down with Jochen in Hamburg to try and fix this.
On Sun, May 14, 2023 at 03:21:24PM -0400, Theodore Ts'o wrote:
> Can someone send the instructions on how to fix this?
We wish we could give you. Instead, we document our findings, so maybe the
next one looking into this bug has a
On Sun, 14 May 2023 15:21:24 -0400, Ted wrote:
> On Sun, May 14, 2023 at 06:03:59PM +0200, Michael Biebl wrote:
> > > Please reassign it there together with instructions how to fix it, i.e.
> > > what should be done in the maintainer scripts.
>
> Can someone send the instructions on how to fix
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: a...@debian.org, bi...@debian.org
I'm having trouble reconciling these two log lines during the upgrade without
systemd:
ls: cannot access '/etc/systemd/system/multi-user.target.wants': No such file
or directory
...
On Sun, May 14, 2023 at 06:03:59PM +0200, Michael Biebl wrote:
> > Please reassign it there together with instructions how to fix it, i.e.
> > what should be done in the maintainer scripts.
Can someone send the instructions on how to fix this?
I'm always amused by people who claim systemd is
Processing control commands:
> reassign -1 e2fsprogs
Bug #1035543 [init-system-helpers] init-system-helpers: new systemd units may
not get enabled on upgrades from bullseye if systemd is installed
Bug reassigned from package 'init-system-helpers' to 'e2fsprogs'.
No longer marked as found in
Control: reassign -1 e2fsprogs
Am 14.05.23 um 11:30 schrieb Andreas Beckmann:
On 09/05/2023 17.48, Michael Biebl wrote:
Andreas, you filed this with RC severity with the justification that
systemd units are not enabled. I don't see that, so could you please
clarify.
What I could find out so
On 09/05/2023 17.48, Michael Biebl wrote:
Andreas, you filed this with RC severity with the justification that
systemd units are not enabled. I don't see that, so could you please
clarify.
What I could find out so far is the change of WantedBy target not being
properly cleaned up on
25 matches
Mail list logo
