Your message dated Fri, 24 Jan 2025 02:46:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#750072: Bug#754393: grml-rescueboot: add script to 
fetch iso image
has caused the Debian Bug report #750072,
regarding grml-rescueboot: Genericize package
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.)


-- 
750072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750072
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grml-rescueboot
Version: 0.4.5
Severity: wishlist
Tags: patch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

The Grml-invented loopback.cfg has become a de facto standard, used in a
number of other Linux distributions on their ISOs.  This is great,
though I wanted a way to easily take a directory of compatible ISOs and
build grub2 stanzas.  I've got an open ITP (#693774) for a package named
grub-loopback-iso, but recently found that the grml-rescueboot package
is perfectly capable of booting non-Grml loopback.cfg-compatible ISOs,
though you wouldn't know that from the package.

I'd like to propose genericizing the package, renaming it to and merging
it with my generic grub-loopback-iso, while providing a transtional
grml-rescueboot package.  The grub.d hook itself will continue to
provide backwards compatibility with existing grml-rescueboot
configurations (/boot/grml and /etc/default/grml-rescueboot).

A proposed merge against:
    http://git.grml.org/?p=grml-rescueboot.git
is at:
    https://github.com/rfinnie/grub-loopback-iso

A more thorough explanation of the changes is in the commit message.

(Full disclosure: I am the author of Finnix, technically a competitor to
Grml, so genericizing this package is in my/Finnix's best interests.)


- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13.0-24-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grml-rescueboot depends on:
ii  grub-pc  2.02~beta2-10

grml-rescueboot recommends no packages.

grml-rescueboot suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTivxoAAoJEH5go6aGro2YmEQP/iwYMW7NaUHcq0fRgHxmMOkk
yQpgcSi19PBGs3i4TzCmvowKslueu2RWSd8cqEt+mxlrGBWKN0zFJ26u11pP0LgK
DnoPkDJeLLmqLhCkB5c977B6PRjSWOlKBG4/4Ap5vUn+7wVfi8lGErFA6Yk88IRe
8h+lOZFkgC+7onhRO1EZTBsA8kYy8lH0MnicACMa6n+5HBofh8aO2VHxEvcc2K8K
agJIucwbZIc7UokzMkw3k9TAVS7Rj+XFJ2SXhWGuaH3+JLmbOiuKchcJUiFs6m4J
G0RJNrdhxdSCqc2O1HOfYvMMa7WYpfUervzpASbQmxu5lQxHw8JHwDT4GPahYiav
dDsOzVacQ7Mjp+EpFqvJrSu89hLnHfEaFNclpbi+vjY4ABE9PfUL4yKA0BVx6Xfm
eGt2aPY9bwMMD0rihc7A2Pve0kL61dDKfWhkkpUdQrUKsy29F+1S2O7hvt6bKRk0
FuledamzH2VUyHwm6IxzuH1lICJxS49nvldviQ5NBK1Vbq622uZgK/xNrK3NFkn5
BjYNLz4gH4/H+La2PKaTHx+H42bqzFrGJZtZgXXTY/g6NyHJ77HZ1Q2tucGpn4uT
kvfjFe6Nn2cQR2g7AM2wH1olyqgx1Asox1CQnAJy4V6ql/+DPK8rRC2ryC1Y1Loc
+e3z0dDZrqyWHn0bSNA8
=oTs/
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On Tue, Nov 04, 2014 at 09:49:52AM +0100, Michael Prokop wrote:
> * Fabian Greffrath [Tue Nov 04, 2014 at 09:24:55AM +0100]:
> 
> > Just wanted to say "yes, please"!
> 
> I fully agree, I just didn't manage to take care of it yet. :(
> Sadly we won't make it in time for the Debian/jessie freeze (same
> for #750072), sorry.

For a long time nothing happened, and in the meantime I closed a
similar request in the upstream repo. For generic image support,
grub-imageboot is a thing. It also could use some love.

I'm closing this bug report here too, as a non-grml-rescueboot
wouldn't be much of a grml-rescueboot anymore.

Chris

--- End Message ---

Reply via email to