Accepted: mdadm 2.6.3+200709292116+4450e59-3ubuntu1 (source)

[Scott James Remnant]

Accepted:
 OK: mdadm_2.6.3+200709292116+4450e59.orig.tar.gz
 OK: mdadm_2.6.3+200709292116+4450e59-3ubuntu1.diff.gz
 OK: mdadm_2.6.3+200709292116+4450e59-3ubuntu1.dsc
     -> Component: main Section: admin

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

Format: 1.7
Date: Wed, 12 Dec 2007 22:35:09 +0000
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source
Version: 2.6.3+200709292116+4450e59-3ubuntu1
Distribution: hardy
Urgency: low
Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Scott James Remnant <scott at ubuntu.com>
Description: 
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID)
Closes: 425576 427880 432585 434934 436998 439334 440703 442874 443436 444682
Changes: 
 mdadm (2.6.3+200709292116+4450e59-3ubuntu1) hardy; urgency=low
 .
   * Merge from debian unstable, remaining changes:
    * md activation:
     - We now have a single udev rule for both the real system and the
       initramfs, since doing things differently there will only result in bugs
       and confusion.
     - This rule runs "mdadm --assemble --scan --no-degraded", automatically
       activating any non-degraded device as their components are detected.
     - Drop the mdadm-raid init script, since this does the same thing.
     - Also drop mdadm-startall which uses the mdadm-raid init script, and its
       associated sgml file (thus dropping the build-dep on docbook-to-man)
     - Simplify the configuration, since we always autostart all devices so do
       not need to specify any required root devices, etc.
     - Drop the deprecated mdrun entirely.
     - Since udev autostarts arrays, much of the initramfs script can be
       dropped.
    * Install a new udev rule at 65 which runs vol_id on clean raid arrays.
      This will cause lvm, etc. to be run (since there is vol_id information
      present for the enclosed filesystem).
    * Depend on initramfs-tools, specifically a version that doesn't ship
      the mdrun script.  This way we can clean out a lot of the upgrade handling
      from the initramfs hook.
    * Just get initramfs to load the modules for us
 .
 mdadm (2.6.3+200709292116+4450e59-3) unstable; urgency=low
 .
   * Patch by Jérémy Bobbio which completes the fix for #444682.
 .
 mdadm (2.6.3+200709292116+4450e59-2) unstable; urgency=low
 .
   * Patch the routine loading v1 superblocks to fix a segfault on amd64
     (closes: #444682).
 .
 mdadm (2.6.3+200709292116+4450e59-1) unstable; urgency=low
 .
   * New merge from upstream @4450e59ffaf75623fa4261e244b0717a7463aa84
     - makes "--write-mostly" effective when re-adding a device to an array.
       (closes: #442874).
   * Do not call update-initramfs -k all, it can be set via
     /etc/initramfs-tools/update-initramfs.conf (closes: #439334).
   * Depend on udev|makedev instead of just makedev and invoke /dev/MAKEDEV,
     not /sbin/MAKEDEV (closes: #436998).
   * De-escalate the initramfs hook warning about an "emergency procedure" and
     simply note that this involves initramfs assembling arrays it finds
     automatically at boot. Also added a FAQ entry on how to turn off the init
     script warning when no arrays are found (closes: #434934).
   * Add --scan to the single-device-assembly-codepath in the initramfs
     local-top script; thanks to Mario 'BitKoenig' Holbe for the patch
     (closes: #440703).
   * Use short option in initramfs script mkdir call, so make it klibc-utils
     compatible; thanks maximilian attems for the patch (closes: #443436).
   * Handle module name synonyms in initramfs hook script (closes: #432585).
 .
 mdadm (2.6.2-2) unstable; urgency=low
 .
   * Fix typos in md(4) manpage; thanks Jeroen (closes: #425576).
   * Make init script not report failure when there are no arrays defined in
     config file.
   * Add /usr/share/doc/mdadm/examples/newdisk, a script to integrate
     a replacement disk into an existing array with minimal effort; will remain
     in examples/ until I had a chance to really test and understand it. Thanks
     to Arno van Amersfoort (closes: #427880).
   * Does some sanity checking for proper format of level= arguments in
     mdadm.conf and bails if an error is found. Since the RAID levels are used
     verbatim as module names, a discrepancy might lead to an unusable system.
     Instead, we thus use the emergency fallback. Thanks to Andrew
     Sackville-West for spotting this and helping me with the fix.
Files: 
 ff71241190d4a6c90e11bdcab43deb52 996 admin optional mdadm_2.6.3+200709292116+4450e59-3ubuntu1.dsc
 51764e41abd2bf967fb74f439018a705 195771 admin optional mdadm_2.6.3+200709292116+4450e59.orig.tar.gz
 e45e715c268cd0e08b2d1aadf5ed195b 105808 admin optional mdadm_2.6.3+200709292116+4450e59-3ubuntu1.diff.gz
Original-Maintainer: Debian mdadm maintainers <pkg-mdadm-devel at lists.alioth.debian.org>
Package-Type: udeb

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

iD8DBQFHYGW4SnQiFMl4yK4RAqdfAJ9UoKl+EWxLNDtSeI8AJh5U7h8yXgCfWezJ
yDXHAWXbWelPt7CFO0+3t5k=
=os4U
-----END PGP SIGNATURE-----