Your message dated Wed, 08 Jun 2022 16:18:53 +0000
with message-id <e1nyyot-0002uq...@fasolo.debian.org>
and subject line Bug#1012327: fixed in bootcd 6.6.1
has caused the Debian Bug report #1012327,
regarding bootcd: No zstd support for initramfs, getting error about initrd 
being not in gzip format
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 ow...@bugs.debian.org
immediately.)


-- 
1012327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bootcd
Version: 6.6
Severity: important
X-Debbugs-Cc: juoza...@gmail.com

Dear Maintainer,

   * What led up to the situation?
Tried to build bootable cd using bootcdwrite, encountered error saying
that initramfs is not in gzip format upon execution. Having zstd
installed and initramfs in zstd format triggers this error.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Did not try to uninstall zstd, I guess boot cd build would work as long
as initramfs is not in zstd format.
   * What was the outcome of this action?
I've encountered an error as shown above, I've aborted boot cd build when 
prompted.
   * What outcome did you expect instead?
Boot cd build continue w/o error.

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

Kernel: Linux 5.17.0-3-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bootcd depends on:
ii  busybox             1:1.30.1-7+b3
ii  cpio                2.13+dfsg-7
ii  dosfstools          4.2-1
ii  e2fsprogs           1.46.5-2
ii  fdisk               2.38-4
ii  file                1:5.41-4
ii  genisoimage         9:1.1.11-3.2
ii  grub-efi-amd64-bin  2.06-2
ii  initramfs-tools     0.141
ii  isolinux            3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  lsb-base            11.2
ii  rsync               3.2.4-1+b1
ii  shellia             5.7.1
ii  syslinux            3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  syslinux-common     3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  util-linux          2.38-4
ii  uuid-runtime        2.38-4
ii  xorriso             1.5.4-2

Versions of packages bootcd recommends:
pn  wodim  <none>

Versions of packages bootcd suggests:
pn  aufs-tools            <none>
pn  discover | discover1  <none>
pn  elilo                 <none>
pn  ssh                   <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: bootcd
Source-Version: 6.6.1
Done: Bernd Schumacher <bernd.schumac...@hpe.com>

We believe that the bug you reported is fixed in the latest version of
bootcd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1012...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bernd Schumacher <bernd.schumac...@hpe.com> (supplier of updated bootcd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Tue, 07 Jun 2022 14:38:37 +0200
Source: bootcd
Architecture: source
Version: 6.6.1
Distribution: unstable
Urgency: medium
Maintainer: Bernd Schumacher <bernd.schumac...@hpe.com>
Changed-By: Bernd Schumacher <bernd.schumac...@hpe.com>
Closes: 1012327
Changes:
 bootcd (6.6.1) unstable; urgency=medium
 .
   * Fixed bug "bootcd: No zstd support for initramfs,
     getting error about initrd beeing not in gzip format"
     reported by Juozas Pocius <juoza...@gmail.com>. Closes: #1012327
   * Deleted Function check_initrd which contained old checks
     that are not needed anymore
   * Forward os-prober Warning seen in sid to stdout
Checksums-Sha1:
 2c7196c1591ab44406b848d65bae416d3eaf4c1b 1472 bootcd_6.6.1.dsc
 df5842427a0b208e12c755607632eaec3668af02 84004 bootcd_6.6.1.tar.xz
 7e264f8df355b2a1236ab21cfebf71d0c71ad23b 6266 bootcd_6.6.1_source.buildinfo
Checksums-Sha256:
 bcd4e4901ac7a915fa66c5561f314e8b00b40e071ee09b6b048ee07e4abfbe36 1472 
bootcd_6.6.1.dsc
 9f21b1f2a84ffa09ab42a1dec9b677bec4cbd36a3e5b520c47d850ad99f9b775 84004 
bootcd_6.6.1.tar.xz
 061b5f712af01ba5d3d99f41b4dc10d7a0bd421798edefa68aa0f897c3b0c4db 6266 
bootcd_6.6.1_source.buildinfo
Files:
 dff42d7cf5c3c39695e2aec68f022b5e 1472 utils extra bootcd_6.6.1.dsc
 256f4b0c9d0017c234eb7e01e7c919d4 84004 utils extra bootcd_6.6.1.tar.xz
 ae1c5c08fb951296e73a2b62d8b4ef03 6266 utils extra bootcd_6.6.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJNBAEBCAA3FiEEx5NNNf+H1Sb3l9vqxRmiDRIUYfcFAmKgxrAZHGJlcm5kLnNj
aHVtYWNoZXJAaHBlLmNvbQAKCRDFGaINEhRh9xy1D/sFYNVRs00IhNpeM7SlvZR4
45FryU1hfrL8P3X0IQ1zsKh/QM28m6GAqXnogFp0zuCbVW6qxevvStaQrMAPsYpO
lR+MZwTO4E4BuJgb5TU02n0cIMZlXs+2OeS3FekrFy2KGM2SsT6tNFpetMg0auyR
h9EPRXyTVRCYUsTwcra+iZ+TbuahhrbXKlEBPulaCJjVdkCN4BaOQKd/sG+PG2i6
Avbw5dB/G9Gh3O7vpyRyuFt0YOeflMJZf63voa2azIiVwahnOQkzi9BhZ5cHe1JC
FjX4MYCTlHZYKrXZG8ZWY5QShBHXIuUCeqmSEkuwZNC8gzkbZI3+PtBUNA+FG/0/
FXqWDR+KJhC1JmIQN+zsOaYGnpPHDIo8cLu6wiWvhAhNXBzNG3nil484VA4rvhxD
pZqs2AIe90nRs4bwl0/T6J9U0TKAyr6BOuQGxffu+99mRendFu/UqrOV5Km/FHjZ
VP9eCU0Zd2ZKFrHlVjhVG9yMyWqZAcSWyUM4qS0hIwO+f9wzLHS/33F23A0MW7Jm
Hsn5tM2wKsh1e3hCxvbbbFmlJcUehGfmul7lGT6lsfCYYHc9kEGeHJ4csK1CPWx7
mlOYX8+Gpd0EOL+WGE+x3flkIk1DP90wAFgLs4IZMVgp5FUuNZVts49UjtRJ1QIe
t2dvCL/vjO0DuBvoqDSn7w==
=UBt1
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to