Change log for parted package in Ubuntu
| 76 → 150 of 169 results | First • Previous • Next • Last |
parted (2.3-13ubuntu2) saucy; urgency=low
* Remove tests/Makefile.in from debian/patches/gptsync.patch; this must
not be present now that we're using dh-autoreconf.
* Backport upstream patches to handle GPT labels with fewer than 128
partition entries (LP: #1187560).
-- Colin Watson <email address hidden> Mon, 17 Jun 2013 18:42:45 +0100
Available diffs
- diff from 2.3-13ubuntu1 to 2.3-13ubuntu2 (2.7 KiB)
parted (2.3-13ubuntu1) saucy; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.patch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- loop-partitions.patch: Backport some changes to allow use of
partitionable loop devices.
- udevadm-settle.patch: Run 'udevadm settle' either side of rereading
the partition table if not chrooted, to avoid a variety of races.
- dmraid.patch: Don't probe dmraid devices unless they are whole disk
devices, not partitions. Also set UUID of newly created dmraid
partition devices.
- 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.
- 16-dos-partitions.patch: Handle >16 partitions on DOS partition
tables.
- dm-part-sync.patch: Backport fix to allow modifying partitions on
dmraid disks while other partitions are in use.
- skip-floppy.patch: Don't probe floppy drives.
- hfs-probe-corrupt.patch: Don't let a corrupt FS evoke a failed
assertion.
* Drop changes, applied in Debian:
- Avoid assuming that gets is declared.
Available diffs
- diff from 2.3-11ubuntu1 to 2.3-13ubuntu1 (26.2 KiB)
| Superseded in saucy-release |
| Obsolete in raring-release |
| Deleted in raring-proposed (Reason: moved to release) |
parted (2.3-11ubuntu1) raring; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.patch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- loop-partitions.patch: Backport some changes to allow use of
partitionable loop devices.
- udevadm-settle.patch: Run 'udevadm settle' either side of rereading
the partition table if not chrooted, to avoid a variety of races.
- dmraid.patch: Don't probe dmraid devices unless they are whole disk
devices, not partitions. Also set UUID of newly created dmraid
partition devices.
- 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.
- 16-dos-partitions.patch: Handle >16 partitions on DOS partition
tables.
- dm-part-sync.patch: Backport fix to allow modifying partitions on
dmraid disks while other partitions are in use.
- skip-floppy.patch: Don't probe floppy drives.
- hfs-probe-corrupt.patch: Don't let a corrupt FS evoke a failed
assertion.
* loop-partitions.patch: refresh, one hunk moved into debian's
md-partitions.patch.
* Apply eglibc-2.16 FTBFS gnulib patch, from bison package.
Available diffs
- diff from 2.3-10ubuntu2 to 2.3-11ubuntu1 (2.8 KiB)
parted (2.3-8ubuntu5.1) precise-proposed; urgency=low
* Fix dm-part-sync.patch to canonicalize the dm name when constructing
the partition device path (LP: #1012946)
-- Phillip Susi <email address hidden> Sat, 16 Jun 2012 21:26:34 -0400
Available diffs
- diff from 2.3-8ubuntu5 to 2.3-8ubuntu5.1 (2.6 KiB)
parted (2.3-10ubuntu2) quantal; urgency=low
* Fix dm-part-sync.patch to canonicalize the dm name when constructing
the partition device path (LP: #1012946)
-- Phillip Susi <email address hidden> Tue, 17 Jul 2012 15:50:56 +0100
Available diffs
- diff from 2.3-10ubuntu1 to 2.3-10ubuntu2 (2.6 KiB)
| Superseded in quantal-release |
parted (2.3-10ubuntu1) quantal; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.patch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- loop-partitions.patch: Backport some changes to allow use of
partitionable loop devices.
- udevadm-settle.patch: Run 'udevadm settle' either side of rereading
the partition table if not chrooted, to avoid a variety of races.
- dmraid.patch: Don't probe dmraid devices unless they are whole disk
devices, not partitions. Also set UUID of newly created dmraid
partition devices.
- 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.
- 16-dos-partitions.patch: Handle >16 partitions on DOS partition
tables.
- dm-part-sync.patch: Backport fix to allow modifying partitions on
dmraid disks while other partitions are in use.
- skip-floppy.patch: Don't probe floppy drives.
- hfs-probe-corrupt.patch: Don't let a corrupt FS evoke a failed
assertion.
Available diffs
| Superseded in quantal-release |
parted (2.3-9.1ubuntu1) quantal; 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: Backport some changes to allow use of
partitionable loop devices.
- udevadm-settle.patch: Run 'udevadm settle' either side of rereading
the partition table if not chrooted, to avoid a variety of races.
- dmraid.patch: Don't probe dmraid devices unless they are whole disk
devices, not partitions. Also set UUID of newly created dmraid
partition devices.
- 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.
- 16-dos-partitions.patch: Handle >16 partitions on DOS partition
tables.
- dm-part-sync.patch: Backport fix to allow modifying partitions on
dmraid disks while other partitions are in use.
- skip-floppy.patch: Don't probe floppy drives.
- hfs-probe-corrupt.patch: Don't let a corrupt FS evoke a failed
assertion.
Available diffs
- diff from 2.3-8ubuntu5 to 2.3-9.1ubuntu1 (3.5 KiB)
parted (2.3-8ubuntu5) precise; urgency=low
* Backport from upstream:
- HFS/HFS+ probe: don't let a corrupt FS evoke failed assertion
(LP: #796891).
-- Colin Watson <email address hidden> Tue, 20 Mar 2012 20:13:53 +0000
Available diffs
- diff from 2.3-8ubuntu4 to 2.3-8ubuntu5 (1.2 KiB)
| Superseded in precise-release |
parted (2.3-8ubuntu4) precise; urgency=low
* At least some Intel Macs get rather upset if we revert to a protective
MBR, so try harder to avoid this and to do a better job of writing a
hybrid MBR:
- Write a type code of 0x83 for more filesystems, and 0xda for
non-filesystem partitions.
- Do not rely on filesystem probing to recognise EFI System Partitions.
- Write a protective partition starting at LBA 1 if we find an EFI
System Partition or BIOS Boot Partition in the first position, even if
it does not really begin at LBA 1 (LP: #856826).
- Ensure that protective partitions corresponding to an ESP or BBP
always have starting cylinder 0, head 0, sector 1.
- Don't revert to a protective MBR just because the first GPT partition
wasn't recognised as anything in particular.
- Add tests for hybrid MBR syncing.
-- Colin Watson <email address hidden> Thu, 08 Mar 2012 15:44:55 +0000
Available diffs
- diff from 2.3-8ubuntu3 to 2.3-8ubuntu4 (4.3 KiB)
| Superseded in precise-release |
parted (2.3-8ubuntu3) precise; urgency=low * Probe non-dmraid device-mapper devices again (LP: #922646). -- Colin Watson <email address hidden> Fri, 27 Jan 2012 22:59:12 +0000
Available diffs
- diff from 2.3-8ubuntu2 to 2.3-8ubuntu3 (487 bytes)
| Superseded in precise-release |
parted (2.3-8ubuntu2) precise; urgency=low
* Add 16-dos-partitions.patch: Fix parted to correctly handle
more than 16 partitions on dos partition tables.
* Add dm-part-sync.patch: Backport fix to allow modifying partitions
on dmraid disks while other partitions are in use.
* Replace dmraid.patch: Reimplemented and forwarded upstream,
allows dmraid raid10 disks to show up (LP: #311179)
* Replace loop-partitions.patch: this patch used to make sure that
we don't try to partition loop devices. Now it backports a few
upstream changes to allow partitioning loop devices since that is
supported on Linux since 3.0. It includes a change that also fixes
support for > 16 partitions.
* Add skip-floppy.patch: don't probe floppy drives. (LP: #910379)
-- Phillip Susi <email address hidden> Sat, 03 Dec 2011 09:50:05 -0500
Available diffs
- diff from 2.3-8ubuntu1 to 2.3-8ubuntu2 (7.7 KiB)
| Superseded in precise-release |
parted (2.3-8ubuntu1) precise; 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.
* Merge Matthew Garrett's dmidecode changes (from 2006!) to find SMBIOS
tables on EFI systems.
Available diffs
- diff from 2.3-6ubuntu3 to 2.3-8ubuntu1 (5.2 KiB)
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
Available diffs
- diff from 2.3-6ubuntu2 to 2.3-6ubuntu3 (584 bytes)
| Superseded in oneiric-release |
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
Available diffs
- diff from 2.3-6ubuntu1 to 2.3-6ubuntu2 (1.4 KiB)
parted (2.2-5ubuntu5.2) lucid-proposed; urgency=low * Don't call 'udevadm settle' when chrooted (LP: #664115). -- Colin Watson <email address hidden> Thu, 30 Jun 2011 09:11:45 +0100
Available diffs
| Superseded in oneiric-release |
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.
Available diffs
- diff from 2.3-5ubuntu6 to 2.3-6ubuntu1 (4.5 KiB)
| Superseded in oneiric-release |
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
Available diffs
- diff from 2.3-5ubuntu5 to 2.3-5ubuntu6 (1.8 KiB)
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
Available diffs
- diff from 2.3-5ubuntu4 to 2.3-5ubuntu5 (1.4 KiB)
| Superseded in natty-release |
parted (2.3-5ubuntu4) natty; urgency=low
* Add fix-head-size-assertion.patch:
Fix probe_partition_for_geom() to fail gracefully rather
than abort with PED_ASSERT(). (LP: #545911)
* Add 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".
* Refresh dasd-sync.patch, dmraid.patch, tiny-disk-constraint.patch,
udevadm-settle.patch.
* debian/control: Breaks versions of dmraid not
patched to follow the same 'p' behavior.
-- Phillip Susi <email address hidden> Sat, 12 Feb 2011 16:37:05 -0500
Available diffs
- diff from 2.3-5ubuntu3 to 2.3-5ubuntu4 (2.9 KiB)
| Superseded in natty-release |
parted (2.3-5ubuntu3) natty; urgency=low
* Update dmraid.patch to add the 'p' before the partition
number for dmraid devices. This fixes a regression from
dropping fix-dmraid-regression.patch (LP: #711616).
-- Phillip Susi <email address hidden> Wed, 02 Feb 2011 10:16:09 +0000
Available diffs
- diff from 2.3-5ubuntu2 to 2.3-5ubuntu3 (581 bytes)
| Superseded in natty-release |
parted (2.3-5ubuntu2) natty; urgency=low * Update udevadm-settle.patch to apply on top of dasd-sync.patch. -- Colin Watson <email address hidden> Fri, 24 Dec 2010 20:44:31 +0000
Available diffs
- diff from 2.3-5ubuntu1 to 2.3-5ubuntu2 (1.8 KiB)
| Superseded in natty-release |
parted (2.3-5ubuntu1) natty; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table if not chrooted, to avoid a variety of races.
- dmraid.dpatch: 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.
Available diffs
- diff from 2.3-4ubuntu2 to 2.3-5ubuntu1 (1.7 KiB)
parted (2.3-2ubuntu2) maverick-proposed; urgency=low * Don't call 'udevadm settle' when chrooted (LP: #664115). -- Colin Watson <email address hidden> Mon, 06 Dec 2010 16:47:27 +0000
Available diffs
- diff from 2.3-2ubuntu1 to 2.3-2ubuntu2 (1.1 KiB)
| Superseded in natty-release |
parted (2.3-4ubuntu2) natty; urgency=low * Don't call 'udevadm settle' when chrooted (LP: #664115). -- Colin Watson <email address hidden> Mon, 06 Dec 2010 16:29:47 +0000
Available diffs
- diff from 2.3-4ubuntu1 to 2.3-4ubuntu2 (1.6 KiB)
| Superseded in natty-release |
parted (2.3-4ubuntu1) natty; urgency=low
[ Colin Watson ]
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid.
* Drop change to add -fno-stack-protector on sparc; we no longer support
sparc in Ubuntu.
[ Phillip Susi ]
* Drop fix-dmraid-regression.patch: dmraid now does add the 'p'.
Available diffs
- diff from 2.3-3ubuntu1 to 2.3-4ubuntu1 (3.1 KiB)
| Superseded in natty-release |
parted (2.3-3ubuntu1) natty; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid.
Available diffs
- diff from 2.3-2ubuntu1 to 2.3-3ubuntu1 (12.6 KiB)
parted (2.3-2ubuntu1) maverick; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid.
Available diffs
- diff from 2.2-7ubuntu1 to 2.3-2ubuntu1 (539.4 KiB)
| Superseded in maverick-release |
parted (2.2-7ubuntu1) maverick; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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.
- put-back-BLKPG.patch: Upstream removed the code using the new BLKPG
ioctls instead of the old BLKRRPART ioctl to update the in-kernel
partition table. This patch reverses that change.
- error-check-BLKPG.patch: Add error checking to the BLKPG code to fix
up the old BLKPG code to satisfy upstream.
- extended-geom.patch: Always allow at least two sectors for extended
boot record.
- loop-limits.patch: Remove limits on loop labels.
- ext4-detection.patch: uninit_bg and flex_bg features should indicate
ext4.
- limit-diagnostics.patch: Fix diagnostics about exceeding partition
limits.
- fix-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid.
Available diffs
- diff from 2.2-5ubuntu6 to 2.2-7ubuntu1 (22.0 KiB)
parted (2.2-5ubuntu5.1) lucid-proposed; urgency=low
[ Phillip Susi ]
* fix-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid (LP: #568050)
(Note that this patch is likely to be reverted in Maverick once
udev/lvm2 switch to the new naming scheme, per the upstream mailing list
discussion.)
-- Colin Watson <email address hidden> Mon, 14 Jun 2010 11:20:45 +0100
Available diffs
- diff from 2.2-5ubuntu5 to 2.2-5ubuntu5.1 (1.5 KiB)
| Superseded in maverick-release |
parted (2.2-5ubuntu6) maverick; urgency=low
[ Phillip Susi ]
* fix-dmraid-regression.path: Reverse upstream change that broke
installation on dmraid disks for lucid (LP: #568050)
(Note that this patch is likely to be reverted in Maverick once
udev/lvm2 switch to the new naming scheme, per the upstream mailing list
discussion.)
-- Colin Watson <email address hidden> Mon, 14 Jun 2010 11:07:13 +0100
Available diffs
- diff from 2.2-5ubuntu5 to 2.2-5ubuntu6 (1.5 KiB)
parted (2.2-5ubuntu5) lucid; urgency=low
* limit-diagnostics.patch: Fix diagnostics about exceeding partition
limits.
* loop-limits.patch (update): Rebuild libparted/labels/pt-limit.c from its
gperf source (LP: #543838).
-- Colin Watson <email address hidden> Wed, 21 Apr 2010 14:18:50 +0100
Available diffs
- diff from 2.2-5ubuntu4 to 2.2-5ubuntu5 (1.4 KiB)
| Superseded in lucid-release |
parted (2.2-5ubuntu4) lucid; urgency=low * Only probe DMI on i386/amd64 (LP: #561426). -- Colin Watson <email address hidden> Tue, 13 Apr 2010 13:41:53 +0100
Available diffs
- diff from 2.2-5ubuntu3 to 2.2-5ubuntu4 (1.3 KiB)
| Superseded in lucid-release |
parted (2.2-5ubuntu3) lucid; urgency=low
* ext4-detection.patch: uninit_bg and flex_bg features should indicate
ext4 (LP: #561599).
-- Colin Watson <email address hidden> Tue, 13 Apr 2010 00:29:14 +0100
Available diffs
- diff from 2.2-5ubuntu2 to 2.2-5ubuntu3 (1.3 KiB)
| Superseded in lucid-release |
parted (2.2-5ubuntu2) lucid; urgency=low * loop-limits.patch: Remove limits on loop labels (LP: #543838). -- Colin Watson <email address hidden> Fri, 09 Apr 2010 15:13:57 +0100
Available diffs
- diff from 2.2-5ubuntu1 to 2.2-5ubuntu2 (769 bytes)
| Superseded in lucid-release |
parted (2.2-5ubuntu1) lucid; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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.
- put-back-BLKPG.patch: Upstream removed the code using the new BLKPG
ioctls instead of the old BLKRRPART ioctl to update the in-kernel
partition table. This patch reverses that change.
- error-check-BLKPG.patch: Add error checking to the BLKPG code to fix
up the old BLKPG code to satisfy upstream.
- extended-geom.patch: Always allow at least two sectors for extended
boot record.
Available diffs
- diff from 2.2-1ubuntu4 to 2.2-5ubuntu1 (13.0 KiB)
| Superseded in lucid-release |
parted (2.2-1ubuntu4) lucid; urgency=low
[ Phillip Susi ]
* put-back-BLKPG.patch: Upstream removed the code using the new
BLKPG ioctls instead of the old BLKRRPART ioctl to update the
in-kernel partition table. This patch reverses that change.
* error-check-BLKPG.patch: Add error checking to the BLKPG code to
fix up the old BLKPG code to satisfy upstream. (LP: #540940)
* Refresh quilt patches.
[ Colin Watson ]
* extended-geom.patch: Always allow at least two sectors for extended boot
record.
-- Colin Watson <email address hidden> Mon, 29 Mar 2010 14:45:28 +0100
Available diffs
- diff from 2.2-1ubuntu3 to 2.2-1ubuntu4 (5.6 KiB)
| Superseded in lucid-release |
parted (2.2-1ubuntu3) lucid; urgency=low
* gptsync.patch (update): Set OSType 0xee (same as EFI System Partitions)
for bios_grub partitions, since otherwise the Linux kernel won't
recognise us as GPT on Apple systems. Also remove a stray & which
completely broke GPT syncing on such systems (LP: #538536).
-- Colin Watson <email address hidden> Mon, 15 Mar 2010 00:41:43 +0000
Available diffs
- diff from 2.2-1ubuntu2 to 2.2-1ubuntu3 (1.1 KiB)
| Superseded in lucid-release |
parted (2.2-1ubuntu2) lucid; urgency=low
* Refresh quilt patches.
* Drop sparc-new-label.patch. The relevant part of this was merged
upstream in 2.2, and the rest was cosmetic.
-- Colin Watson <email address hidden> Mon, 08 Mar 2010 16:44:56 +0000
Available diffs
- diff from 2.2-1ubuntu1 to 2.2-1ubuntu2 (4.2 KiB)
| Superseded in lucid-release |
parted (2.2-1ubuntu1) lucid; urgency=low
* Resynchronise with Debian experimental (albeit from the NEW queue).
Relevant upstream changes:
- gpt: read-only operation could clobber MBR part of hybrid GPT+MBR
table (LP: #529904).
* Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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.
Available diffs
- diff from 2.1-4ubuntu1 to 2.2-1ubuntu1 (641.7 KiB)
| Superseded in lucid-release |
parted (2.1-4ubuntu1) lucid; urgency=low
* Resynchronise with Debian experimental. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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.
Available diffs
- diff from 2.1-3ubuntu1 to 2.1-4ubuntu1 (1.0 KiB)
| Superseded in lucid-release |
parted (2.1-3ubuntu1) lucid; urgency=low
* Resynchronise with Debian experimental. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: 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.
Available diffs
- diff from 2.1-2ubuntu1 to 2.1-3ubuntu1 (1.2 KiB)
| Superseded in lucid-release |
parted (2.1-2ubuntu1) lucid; urgency=low * Resynchronise with Debian experimental (LP: #511075). Remaining changes: - gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a protective MBR. - Add -fno-stack-protector on sparc. - sparc-new-label.dpatch: Fix sparc disk label generation. This is required for LDOM and parallel installations with Solaris 10. - loop-partitions.dpatch: Loop devices can only have one partition, so don't generate device names such as "/dev/loop0p1". - udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading the partition table, to avoid a variety of races. - dmraid.dpatch: 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. * Upstream fixes: - Supports non-512-byte logical sectors (LP: #505549). - Do not discard bootcode from extended partition on msdos label when some of the logical partitions are changed (LP: #445067). - Don't use msftres flag for FAT/NTFS partitions on GPT (LP: #397386).
Available diffs
| Superseded in lucid-release |
parted (1.8.8.git.2009.07.19-5ubuntu2) lucid; urgency=low * Rebuild for current uuid-dev. -- Marc Deslauriers <email address hidden> Sun, 07 Feb 2010 19:22:06 -0500
Available diffs
| Superseded in lucid-release |
parted (1.8.8.git.2009.07.19-5ubuntu1) lucid; urgency=low
* Resynchronise with Debian. Remaining changes:
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- When building with gcc-4.3, add -Wno-array-bounds to CFLAGS.
- Cell partition tables are misdetected as pc98, so disable pc98 support
on powerpc.
- disable_o_direct.dpatch: Replace the use of O_DIRECT with calls to
fsync() at appropriate times.
- unpartitioned-disks.dpatch (update): Just return immediately from
ped_disk_commit if running on an unpartitioned disk, to avoid failures
in case we end up in _kernel_reread_part_table.
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
- dmraid.dpatch: Restored. Ensures 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.
* Upstream fixed destruction of first 446 bytes of protective MBR on GPT
write (LP: #351414).
Available diffs
parted (1.8.8.git.2009.06.03-1ubuntu6) karmic; urgency=low
* baseline-symbols-update.dpatch (update): Add ped_file_system_alias_*
functions.
* debian/rules: Bump DEPVER to -1ubuntu5. This just adds interfaces and so
doesn't require a soname change.
-- Colin Watson <email address hidden> Mon, 05 Oct 2009 12:14:16 +0100
Available diffs
| Superseded in karmic-release |
parted (1.8.8.git.2009.06.03-1ubuntu5) karmic; urgency=low
* rationalise-linux-swap.dpatch: Backport upstream change to rationalise
linux-swap fs names, and add a "linux-swap" alias (LP: #399428).
-- Colin Watson <email address hidden> Mon, 05 Oct 2009 10:55:31 +0100
Available diffs
| Superseded in karmic-release |
parted (1.8.8.git.2009.06.03-1ubuntu4) karmic; urgency=low * Build-depend on libreadline-dev instead of libreadline5-dev. -- Matthias Klose <email address hidden> Sat, 19 Sep 2009 23:00:13 +0200
Available diffs
| Superseded in karmic-release |
parted (1.8.8.git.2009.06.03-1ubuntu3) karmic; urgency=low * dmraid.dpatch: Restored (LP: #392246). Ensures 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. -- Colin Watson <email address hidden> Fri, 24 Jul 2009 11:54:10 +0100
Available diffs
| Superseded in karmic-release |
parted (1.8.8.git.2009.06.03-1ubuntu2) karmic; urgency=low
* Actually apply patches during the build.
* baseline-symbols-update.dpatch (update): Fix to apply properly. Remove
obsolete s390 symbols.
-- Colin Watson <email address hidden> Thu, 25 Jun 2009 20:42:49 +0100
Available diffs
| Superseded in karmic-release |
parted (1.8.8.git.2009.06.03-1ubuntu1) karmic; urgency=low
* Resynchronise with Debian. Remaining changes:
- swap-uuid.dpatch: Create UUIDs on new swap partitions.
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- When building with gcc-4.3, add -Wno-array-bounds to CFLAGS.
- Cell partition tables are misdetected as pc98, so disable pc98 support
on powerpc.
- disable_o_direct.dpatch: Replace the use of O_DIRECT with calls to
fsync() at appropriate times.
- unpartitioned-disks.dpatch (update): Just return immediately from
ped_disk_commit if running on an unpartitioned disk, to avoid failures
in case we end up in _kernel_reread_part_table.
- udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading
the partition table, to avoid a variety of races.
Available diffs
parted (1.8.8.git.2008.03.24-7ubuntu8) intrepid-proposed; urgency=low
* gptsync.dpatch (update): Add "Apple Inc." as a possible Apple DMI vendor
string (LP: #222126).
-- Colin Watson <email address hidden> Thu, 04 Jun 2009 20:12:55 +0100
Available diffs
parted (1.7.1-5.1ubuntu9.2) hardy-proposed; urgency=low
* gptsync.dpatch (update): Add "Apple Inc." as a possible Apple DMI vendor
string (LP: #222126).
-- Colin Watson <email address hidden> Thu, 04 Jun 2009 17:22:24 +0100
Available diffs
parted (1.8.8.git.2008.03.24-11.1ubuntu6) jaunty; urgency=low
* gptsync.dpatch (update):
- Treat ext4 like ext3 for the purposes of the protective MBR.
- Add "Apple Inc." as a possible Apple DMI vendor string (LP: #222126).
-- Colin Watson <email address hidden> Sat, 28 Mar 2009 13:02:52 +0000
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11.1ubuntu5) jaunty; urgency=low
* udevadm-settle.dpatch: Run 'udevadm settle' either side of rereading the
partition table, to avoid a variety of races (LP: #340188).
-- Colin Watson <email address hidden> Tue, 10 Mar 2009 21:28:11 +0000
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11.1ubuntu4) jaunty; urgency=low
* unpartitioned-disks.dpatch (update): Fix reversed logic that caused us
never to commit partitionable disk changes to the kernel (LP: #317709).
Whoops!
-- Colin Watson <email address hidden> Fri, 16 Jan 2009 12:43:36 +0000
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11.1ubuntu3) jaunty; urgency=low
* unpartitioned-disks.dpatch (update): Just return immediately from
ped_disk_commit if running on an unpartitioned disk, to avoid failures
in case we end up in _kernel_reread_part_table (encountered during a
Wubi installation of Ubuntu).
-- Colin Watson <email address hidden> Thu, 15 Jan 2009 00:47:01 +0000
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11.1ubuntu2) jaunty; urgency=low
* ext4.dpatch: Add skeletal ext4 support.
* dm-null-target.dpatch: Fix segfault in case DM_DEVICE_TABLE returns no
targets.
-- Colin Watson <email address hidden> Thu, 08 Jan 2009 15:00:22 +0000
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11.1ubuntu1) jaunty; urgency=low
* Resynchronise with Debian. Remaining changes:
- swap-uuid.dpatch: Create UUIDs on new swap partitions.
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- When building with gcc-4.3, add -Wno-array-bounds to CFLAGS.
- Cell partition tables are misdetected as pc98, so disable pc98 support
on powerpc.
- array-bounds.dpatch: Backport patch from git to allow building with
gcc-4.3.
- disable_o_direct.dpatch: Replace the use of O_DIRECT with calls to
fsync() at appropriate times.
Available diffs
| Superseded in jaunty-release |
parted (1.8.8.git.2008.03.24-11ubuntu1) jaunty; urgency=low
* Resynchronise with Debian. Remaining changes:
- swap-uuid.dpatch: Create UUIDs on new swap partitions.
- gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a
protective MBR.
- Add -fno-stack-protector on sparc.
- sparc-new-label.dpatch: Fix sparc disk label generation. This is
required for LDOM and parallel installations with Solaris 10.
- loop-partitions.dpatch: Loop devices can only have one partition, so
don't generate device names such as "/dev/loop0p1".
- When building with gcc-4.3, add -Wno-array-bounds to CFLAGS.
- Cell partition tables are misdetected as pc98, so disable pc98 support
on powerpc.
- array-bounds.dpatch: Backport patch from git to allow building with
gcc-4.3.
- disable_o_direct.dpatch: Replace the use of O_DIRECT with calls to
fsync() at appropriate times.
Available diffs
parted (1.8.8.git.2008.03.24-7ubuntu7) intrepid; urgency=low * Replace the use of O_DIRECT with calls to fsync() at appropriate times. -- Soren Hansen <email address hidden> Fri, 12 Sep 2008 15:40:45 +0200
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu6) intrepid; urgency=low
* debian/patches/parted-dmraid.dpatch: Removed some hunks that somehow
made their way into the patch when I was editing it at some point.
these hunks reverted functionality from unpartitioned-disks.dpatch.
We don't want that.
-- Luke Yelavich <email address hidden> Wed, 10 Sep 2008 16:18:33 +1000
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu5) intrepid; urgency=low
* debian/patches/parted-dmraid.dpatch:
- Simplify code in _is_dmraid_device, as it was needlessly complex.
- Add _is_dmraid_major function to check whether a dmraid evice node
is for a partition, or the master node of the array. This results
in only the master dmraid device node being probed.
-- Luke Yelavich <email address hidden> Tue, 19 Aug 2008 11:56:04 +1000
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu4) intrepid; urgency=low
* debian/rules: Remove leftovers from a debugging session when
adding dmraid code.
-- Luke Yelavich <email address hidden> Sat, 16 Aug 2008 21:41:40 +1000
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu3) intrepid; urgency=low
* debian/patches/parted-dmraid.dpatch: Patch to educate libparted about
dmraid arrays, which use device mapper. Libparted was naming new partition
nodes incorrectly, and not setting the UUIDs for dmraid device nodes.
-- Luke Yelavich <email address hidden> Thu, 14 Aug 2008 10:52:22 +1000
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu2) intrepid; urgency=low
* unpartitioned-disks.dpatch (update): Don't tell device-mapper to create
partitions on unpartitionable disks.
-- Colin Watson <email address hidden> Thu, 10 Jul 2008 16:21:07 +0100
Available diffs
| Superseded in intrepid-release |
parted (1.8.8.git.2008.03.24-7ubuntu1) intrepid; urgency=low * Resynchronise with Debian (LP: #237568). Remaining changes: - swap-uuid.dpatch: Create UUIDs on new swap partitions. - gptsync.dpatch: On Intel Mac systems, write a synced MBR rather than a protective MBR. - Add -fno-stack-protector on sparc. - sparc-new-label.dpatch: Fix sparc disk label generation. This is required for LDOM and parallel installations with Solaris 10. - loop-partitions.dpatch: Loop devices can only have one partition, so don't generate device names such as "/dev/loop0p1". - unpartitioned-disks.dpatch: Don't try to call BLKPG ioctls on unpartitionable disks (only implemented for loop devices at the moment), as they will always fail. - When building with gcc-4.3, add -Wno-array-bounds to CFLAGS. - Cell partition tables are misdetected as pc98, so disable pc98 support on powerpc. - array-bounds.dpatch: Backport patch from git to allow building with gcc-4.3.
Available diffs
parted (1.7.1-5.1ubuntu9.1) hardy-proposed; urgency=low
* fat-partition-table.dpatch: Instead of checking for FAT file system
signatures (which has false positives), check whether the boot indicator
on each partition is 0 or 0x80 (LP: #232175). This matches the behaviour
of both the Linux kernel and fdisk.
-- Colin Watson <email address hidden> Fri, 30 May 2008 13:09:57 +0100
Available diffs
| Superseded in intrepid-release |
parted (1.7.1-5.1ubuntu11) intrepid; urgency=low
* array-bounds.dpatch: Backport patch from git to allow building with
gcc-4.3 (closes: #474822, LP: #185882).
-- Colin Watson <email address hidden> Thu, 29 May 2008 21:14:14 +0100
Available diffs
| Superseded in intrepid-release |
parted (1.7.1-5.1ubuntu10) intrepid; urgency=low
* fat-partition-table.dpatch: Instead of checking for FAT file system
signatures (which has false positives), check whether the boot indicator
on each partition is 0 or 0x80 (LP: #232175). This matches the behaviour
of both the Linux kernel and fdisk.
-- Colin Watson <email address hidden> Thu, 29 May 2008 12:09:09 +0100
Available diffs
parted (1.7.1-5.1ubuntu9) hardy; urgency=low
* gptsync.dpatch: Only write a synced legacy MBR on Apple systems;
otherwise, write a protective MBR per the EFI standard (LP: #107326).
This behaviour may be overridden by setting the environment variable
PARTED_GPT_APPLE to 1 (always write synced legacy MBR) or 0 (always
write protective MBR).
-- Colin Watson <email address hidden> Sun, 30 Mar 2008 21:35:47 +0100
parted (1.7.1-5.1ubuntu8) gutsy; urgency=low
* Cell partition tables are misdetected as pc98, so disable pc98 support
on powerpc.
-- Colin Watson <email address hidden> Wed, 26 Sep 2007 12:52:08 +0100
| Superseded in gutsy-release |
parted (1.7.1-5.1ubuntu7) gutsy; urgency=low
* When building with gcc-4.3, add -Wno-array-bounds to CFLAGS.
LP: #138638.
* debian/control*: Update maintainer address.
-- Matthias Klose <email address hidden> Sat, 15 Sep 2007 08:45:15 +0000
| Superseded in gutsy-release |
parted (1.7.1-5.1ubuntu6) gutsy; urgency=low
* unpartitioned-disks.dpatch: Don't try to call BLKPG ioctls on
unpartitionable disks (only implemented for loop devices at the moment),
as they will always fail.
-- Colin Watson <email address hidden> Fri, 07 Sep 2007 12:08:04 +0100
| Superseded in gutsy-release |
parted (1.7.1-5.1ubuntu5) gutsy; urgency=low * Fix up lvm2.dpatch to apply again. -- Colin Watson <email address hidden> Mon, 20 Aug 2007 16:35:00 +0100
| Superseded in gutsy-release |
parted (1.7.1-5.1ubuntu4) gutsy; urgency=low
* loop-partitions.dpatch: Rearrange test order so that this actually
works.
-- Colin Watson <email address hidden> Mon, 20 Aug 2007 15:31:02 +0100
| 76 → 150 of 169 results | First • Previous • Next • Last |
