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

Bug#813506: marked as done (zipl-installer: set up re-IPL to boot newly installed Debian/Linux)



Your message dated Sun, 14 Feb 2016 13:20:40 +0000
with message-id <E1aUwbQ-0008Qa-5J@franck.debian.org>
and subject line Bug#813506: fixed in zipl-installer 0.0.32
has caused the Debian Bug report #813506,
regarding zipl-installer: set up re-IPL to boot newly installed Debian/Linux
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.)


-- 
813506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813506
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: zipl-installer
Version: 0.0.30
Severity: normal
Tags: d-i

Hi,

I have a small enhancement on the zipl-installer package to prepare and
set up the re-IPL settings to boot into the newly installed Linux instance.

To set up the re-IPL settings, a call to chreipl is required from within
the installed system.  This is required beccause chreipl uses a helper
script to detect the IPL device for linear mapped devices, for example,
LVM or multipath devices.

Note that there is also a change required for the rootskel package to
reset the debian-installer/exit/always_halt to false.

Patches with changelog information will be added soon by me.

Thanks and kind regards,
  Hendrik

--- End Message ---
--- Begin Message ---
Source: zipl-installer
Source-Version: 0.0.32

We believe that the bug you reported is fixed in the latest version of
zipl-installer, 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 813506@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated zipl-installer 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Sun, 14 Feb 2016 13:41:57 +0100
Source: zipl-installer
Binary: zipl-installer
Architecture: source s390x
Version: 0.0.32
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description:
 zipl-installer - Make DASD bootable (udeb)
Closes: 813506
Changes:
 zipl-installer (0.0.32) unstable; urgency=medium
 .
   [ Hendrik Brueckner ]
   * Mount /sys and /dev before running zipl.
   * Setup re-IPL settings. (Closes: #813506)
Checksums-Sha1:
 91230190722ad2592f30618bb23dff7b8e1ae715 1346 zipl-installer_0.0.32.dsc
 ba28399f8d565d47bcd63421661b8d276ff03228 22112 zipl-installer_0.0.32.tar.xz
 d9b37f88c9588e4b6baf99e425d7fd721d480af6 4820 zipl-installer_0.0.32_s390x.udeb
Checksums-Sha256:
 442b7690142f12c4735afc7b2cb4292f4627ab2f55e70d44c5ded5e99e9bf915 1346 zipl-installer_0.0.32.dsc
 6b75924e60e6fbf3a0ae5e9ff5b4ecfc73d4ae0f139d43754d838f1243145695 22112 zipl-installer_0.0.32.tar.xz
 050f90aaa2d013fb6b6c7c89dd28aabae3083037e381391e9598c46aca6f4fc2 4820 zipl-installer_0.0.32_s390x.udeb
Files:
 b8e4434a776a751989fb9495d4ced1cb 1346 debian-installer standard zipl-installer_0.0.32.dsc
 ea886a58e3561d5ec17c36df9ea47ff2 22112 debian-installer standard zipl-installer_0.0.32.tar.xz
 fbad2c9cc37bfa624bb280e30f45294c 4820 debian-installer standard zipl-installer_0.0.32_s390x.udeb

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

iQEcBAEBCAAGBQJWwHgFAAoJEERuJUU10FbsF3AIAIOCB25V/+qTDYXbUleGD8dW
/Pokm6E1VKydzWvffFiSI0n1LTXclp6qUTT9vxYjMA+pkQvoYD089g/uetGsltUt
KqFOKbLfGrmL2QTcmeR9woAmEc/Ad6f78pPyBszTRKNVuH8DcTBPgPbPN1sW/XC/
KKdJNmUI+odbPmKikeeKpOXCRDrX7+01LQd+rO+HrUx5KCsGb/Fg4wvBj7UCUcT8
jjiqoElM3Xko5q8nU64MEhsFncVNc6ppElTzfw5SZ99t2IFGnSSdMlL7JOsXvqKc
HBmWFinB/1SL1DvQGNgUvT96Zyo2Qkni6mJCIBGsggPXc6+Jc4QlHVB9jiYCqlg=
=AmYy
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: