Change logs for parted source package in Oneiric

  • parted (2.3-6ubuntu3) oneiric; urgency=low
    
      * Fix dm_task_run error checking in _is_dmraid_device (LP: #580702).
     -- Colin Watson <email address hidden>   Tue, 06 Sep 2011 17:43:04 +0100
  • parted (2.3-6ubuntu2) oneiric; urgency=low
    
      * When creating a legacy MBR on Apple systems, only ever mark an existing
        partition as a fake protective partition if it is the first partition
        and it starts at LBA 1, otherwise GRUB and the Linux kernel respectively
        will fail to treat the disk as GPT; if there is no partition fitting
        these criteria, then fall back to creating a fake protective partition
        (LP: #837681).
     -- Colin Watson <email address hidden>   Wed, 31 Aug 2011 23:39:36 +0100
  • parted (2.3-6ubuntu1) oneiric; urgency=low
    
      * Resynchronise with Debian.  Remaining changes:
        - gptsync.patch: On Intel Mac systems, write a synced MBR rather than a
          protective MBR.
        - Add -fno-stack-protector on sparc.
        - loop-partitions.patch: Loop devices can only have one partition, so
          don't generate device names such as "/dev/loop0p1".
        - udevadm-settle.patch: Run 'udevadm settle' either side of rereading
          the partition table if not chrooted, to avoid a variety of races.
        - dmraid.patch: Ensure that device-mapper devices for dmraid arrays do
          not have extra nodes created needlessly, as well as making sure that
          partition nodes for dmraid devices are not probed.
        - fix-head-size-assertion.patch: Fix probe_partition_for_geom() to fail
          gracefully rather than abort with PED_ASSERT().
        - dm_p_separator.patch: Device mapper type should not automatically mean
          add 'p' before the partition number.  Fall back to adding it only if
          the previous character is a digit.  This complies with kpartx behavior
          and Linux behavior "since the dawn of time".
        - remove-dev_t-dep.patch: Remove incorrect code from arch/linux.c that
          made assumptions about the meaning of dev_t causing mounted partitions
          to not be identified on dmraid devices and extended partition numbers
          >= 16.
    
    parted (2.3-6) unstable; urgency=low
    
      * Backport from upstream:
        - Accommodate two-component Linux version numbers like 3.0
          (LP: #796865).
      * Rewrite package descriptions and add a Homepage field (thanks, Justin B
        Rye; closes: #615124).
     -- Colin Watson <email address hidden>   Thu, 16 Jun 2011 07:36:54 +0100
  • parted (2.3-5ubuntu6) oneiric; urgency=low
    
      * Add remove-dev_t-dep.patch: Remove incorrect code from arch/linux.c
        that made assumptions about the meaning of dev_t causing mounted
        partitions to not be identified on dmraid devices and extended
        partition numbers >= 16. (LP: #605975)
      * Refresh dasd-sync.patch, dmraid.patch, udevadm-settle.patch
     -- Phillip Susi <email address hidden>   Wed, 04 May 2011 21:22:16 -0400
  • parted (2.3-5ubuntu5) natty; urgency=low
    
      [ Dave Vasilevsky ]
      * Improve built-in gptsync implementation (LP: #757201):
        - Only the first partition may start at sector 1; don't modify later
          partitions that way.  This avoids overlap.
        - If no protective partition at all is found, place at the start of the
          MBR a tiny fake protective partition, covering the space from sector 1
          to the start of the first real partition.  Partitions that follow are
          moved up by one, so that the hybrid MBR only includes three real
          partitions.
     -- Colin Watson <email address hidden>   Fri, 15 Apr 2011 17:29:54 +0100