[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1105979: marked as done (unblock: grml-debootstrap/0.121)



Your message dated Sun, 18 May 2025 12:19:18 +0000
with message-id <E1uGcz8-001H91-11@respighi.debian.org>
and subject line unblock grml-debootstrap
has caused the Debian Bug report #1105979,
regarding unblock: grml-debootstrap/0.121
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 owner@bugs.debian.org
immediately.)


-- 
1105979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105979
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: grml-debootstrap@packages.debian.org, team@grml.org
Control: affects -1 + src:grml-debootstrap

Please unblock package grml-debootstrap

[ Reason ]
0.121 contains three bug fixes for bugs reported directly into the 
grml bug tracker, and one small feature improving systemd 
integration.

We'd like them in, so installing Debian with grml-debootstrap 
doesn't trigger these bugs and users using systemd with partition 
autodetect should also get that to work OOTB.

[ Impact ]
The three bugs are on the scale from "quite annoying" to "unclear 
impact, possibly disastrous on the upgrade from trixie to forky".
1) "Don't set bogus debconf variable on grub-cloud packages" is the 
bug where we don't want to do something stupid now that might break 
upgrading trixie installs to forky.
2) "fix skipping initrd creation using INITRD=no" is annoying, but
also is a trivial fix
3) "Verify that GRUB configuration points to valid block device"
is the quite annoying bug, because users discover this only after 
waiting a long time for their install to complete and then abort.

[ Tests ]
We've got CI pipelines in Grml, and there is no regression. The 
submitters have done tests for their patches, and I've done a manual 
normal check on arm64, which went well.
One day we'll write autopkgtests, but not this cycle.

[ Risks ]
Honestly the diff is not very long and easy to understand. Also 
grml-debootstrap is a leaf package, so it shouldn't break other 
packages in testing.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
Nothing I'm aware of.

Thanks!
Chris

unblock grml-debootstrap/0.121

--- End Message ---
--- Begin Message ---
Unblocked.

--- End Message ---

Reply to: