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

Bug#818592: marked as done (control: split and improve dependency handling for disk detection)

Your message dated Sun, 03 Apr 2016 09:52:23 +0000
with message-id <E1amehj-0005fD-Jv@franck.debian.org>
and subject line Bug#818592: fixed in s390-zfcp 1.0.2
has caused the Debian Bug report #818592,
regarding control: split and improve dependency handling for disk detection
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.)


-- 
818592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818592
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: s390-zfcp
Version: 1.0.1
Severity: important
Tags: d-i

To improve and provide a "guided" flow, split the harddrive
detection dependency for s390-dasd and s390-zfcp as follows:

- s390-dasd provides harddrive-detection-dasd
- s390-zfcp provides harddrive-detection-zfcp

The disk-detect package depends on
  -> harddrive-detection-dasd
  -> harddrive-detection-zfcp

and continues to provide the harddrive-detection.  With this split,
installation on mixed DASD and SCSI disks are possible.  Also move
the module before the disk-detect module in the Debian installer
menu.

See also related Debian Bug #818586 for the disk-detect package.

Patch for the control file will follow.

Thanks and kind regards,
  Hendrik

--- End Message ---
--- Begin Message --- 
Source: s390-zfcp
Source-Version: 1.0.2

We believe that the bug you reported is fixed in the latest version of
s390-zfcp, 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 818592@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 s390-zfcp 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, 03 Apr 2016 11:34:08 +0200
Source: s390-zfcp
Binary: s390-zfcp
Architecture: source s390x
Version: 1.0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description:
 s390-zfcp  - Activate and configure FCP devices for installation (udeb)
Closes: 818592
Changes:
 s390-zfcp (1.0.2) unstable; urgency=medium
 .
   [ Hendrik Brueckner ]
   * Split and improve dependency handling for disk detection and
     move the module before the disk-detect d-i module (Closes: #818592)
Checksums-Sha1:
 9e8ea0c55099f7ab3b4300e5055aaff5e8c814b0 1374 s390-zfcp_1.0.2.dsc
 9542ac5047334dd10a67aa019001e0d0c0ac78dc 24092 s390-zfcp_1.0.2.tar.xz
 79034f2f64e2f76e25d9bae73820ad051c78983e 12340 s390-zfcp_1.0.2_s390x.udeb
Checksums-Sha256:
 e7a7a861d83644e27147b4033a421e43c6b5c71e01ed24ac60a42289987b0a1b 1374 s390-zfcp_1.0.2.dsc
 34324173d4f6933e14910622a41f96c2f155fb40cd8716d0ed6d93e3819d830c 24092 s390-zfcp_1.0.2.tar.xz
 788a891a26b1b2c38b1a0dde99adcf8b4c9d95c9a7775129211e7f06112a1174 12340 s390-zfcp_1.0.2_s390x.udeb
Files:
 fd3d8bc84f0fee940ee5a4465e51a2fc 1374 debian-installer standard s390-zfcp_1.0.2.dsc
 b538d3e0d535e2f3cb517ecf3476a4b4 24092 debian-installer standard s390-zfcp_1.0.2.tar.xz
 5f1ca6ec924590b54673a29e07c93e62 12340 debian-installer standard s390-zfcp_1.0.2_s390x.udeb

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

iQEcBAEBCAAGBQJXAOQlAAoJEERuJUU10FbsYIYH/As99QD0DJea+vNU2xRulBLC
zr9DxOY1rJ9epQcYQvDMtnwg1VH94kycPLQh9sKGTVcrePIP+APwDh3TVLH4F5xW
ZKJgU94IZT4NccBX2diT88cLfyjSVt/+r/3hYZNvkQK9SDdcVhwWBAuylkgABkHd
o94HTnlSF4Xr0szuPXfAwUaxN9UD/2U7za3+yk4L09svHzVWg7aSO7Frj0+JOjnc
Z+RJoGBF2fjs2bhJtH3wHyKO/gNaqq2etCJmAS+jryXdxeJCJVXzVC4m3Uo77usv
yVDbRnaeW286aErIMz5RgLAImVOPphHZDS6UvjLhJ+PUnfYGewyDbgdZbuEaUmw=
=NDhx
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: