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

Bug#380089: marked as done (lvm/mdadm take care of partial upgrades from sarge)

Your message dated Sun, 30 Jul 2006 09:32:19 -0700
with message-id <E1G7EDD-0000Z4-4A@spohr.debian.org>
and subject line Bug#380089: fixed in initramfs-tools 0.73
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: initramfs-tools
Version: 0.70b
Severity: critical
Justification: renders system unbootable

initramfs-tools no longer provides the RAID functionality but leaves
that to mdadm, which started to provide it with the 2.5-1 release.
As part of this transition, I thought it was agreed that
initramfs-tools would conflict with << 2.5-1 as soon as it drops the
RAID functionality. This conflict does not exist in the 0.70b
release. If someone with root on RAID ends up upgrading only
initramfs-tools (slow upgrade to etch, backports, etc.) without
upgrading mdadm to 2.5-1 or beyond, the initramfs will fail to bring
up the root system and hence render the system unbootable.

Please fix.

For completeness, here's the related IRC discussion:

15:18:11 < madduck> maks: uh, why exactly does initramfs-tools not conflict 
                    with mdadm?
15:19:08 < maks> madduck: no reason to do so
15:19:33 < madduck> except that if mdadm < 2.5.2-X is installed and 
                    initramfs-tools upgraded, RAID systems won't boot anymore?
15:19:48 < madduck> as they used to?
15:20:08 < madduck> i thought we had discussed this.
15:20:29 < maks> madduck: no i don't add gratious conflicts
15:20:48 < madduck> wtf?
15:21:21 < madduck> this sounds like a grave bug to me.
15:21:40 < maks> madduck: i'm watching you entering testing
15:21:47 < maks> and won't be there before so be cool
15:22:22 < madduck> maks: i disagree. we don't have package relations to 
                    manually make sure we don't need them.
15:22:25 < maks> madduck: and yes evms already handled that phase
15:22:29 < madduck> please add the conflict or do i need to go approach ctte?
15:25:13 < maks> madduck: it was not agreed
15:25:34 < madduck> maks: you still did not provide a reason. and you're 
                    starting to annoy me.
15:25:41 < maks> madduck: as i already told you mdadm will be in testing before 
                 initramfs-tools so get out of the way
15:25:56 < madduck> maks: i will now file a grave bug, and if you don't handle 
                    it appropriately which means fix or argue properly, i'l;; 
                    go to ctte.
15:26:12 < maks> madduck: loose your time if you feel so

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system

Attachment: signature.asc
Description: Digital signature (GPG/PGP)


--- End Message ---
--- Begin Message --- 
Source: initramfs-tools
Source-Version: 0.73

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive:

initramfs-tools_0.73.dsc
  to pool/main/i/initramfs-tools/initramfs-tools_0.73.dsc
initramfs-tools_0.73.tar.gz
  to pool/main/i/initramfs-tools/initramfs-tools_0.73.tar.gz
initramfs-tools_0.73_all.deb
  to pool/main/i/initramfs-tools/initramfs-tools_0.73_all.deb



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 380089@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems <maks@sternwelten.at> (supplier of updated initramfs-tools 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@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 29 Jul 2006 13:35:43 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.73
Distribution: unstable
Urgency: high
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: maximilian attems <maks@sternwelten.at>
Description: 
 initramfs-tools - tools for generating an initramfs
Closes: 380089
Changes: 
 initramfs-tools (0.73) unstable; urgency=high
 .
   * debian/initramfs-tools.postrm: Don't forget to remove config file
     modules on purge. Thanks piuparts verification.
 .
   * mkinitramfs: Add sections that deals with sarge mdadm and lvm2.
     Does nothing if etch package hooks are installed, will be dropped
     postetch as then we upgrade from mdadm and lvm2 packages with hooks.
     Taken from Dapper initramfs-tools-0.40ubuntu32. Adapt to add more
     modules and no need for mdrun.
 .
   * hooks/lvm: Remove handled by mkinitramfs itself.
 .
   * scripts/local-top/lvm: Add prereqs lvm2 + mdraid. Exit if lvm2 hook is
     present. Eases transition of lvm hooks to lvm2.
 .
   * scripts/local-top/mdraid: Enable all raid devices. Add mdadm as prereqs.
     Only run if no mdadm hook is in initramfs. (closes: 380089)
 .
   * urgency high upload to get RC fixes into testing.
Files: 
 be497322b60498c022adb09bb0bbc735 623 utils optional initramfs-tools_0.73.dsc
 1e8ec00ed1bbd4766b96564e7c68077d 45503 utils optional initramfs-tools_0.73.tar.gz
 f09946e87a999d86de849c885a93984a 50490 utils optional initramfs-tools_0.73_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEzNuO6n7So0GVSSARApM7AJ9Y5GSvmn6/o0HHFQ50UMzdFI/4CACeKi/6
3NNUW+xYy8GQ1phYOLqULug=
=nLs5
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: