vcswatch reports that
this package seems to have a new changelog entry (version
3.2-26, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit b0d2d3d689ba2898adf745df3851927369833d48
Author: Colin Watson <cjwatson@ubuntu.com>
Date: Sat Aug 3 12:50:42 2019 +0100
Use debhelper-compat instead of debian/compat
commit f22e1de79c569c5298faa1edd768d35aa4c235c8
Merge: a76d1db 0c083fb
Author: Colin Watson <cjwatson@ubuntu.com>
Date: Tue Jul 30 09:47:27 2019 +0100
Add missing test files for fdasd
The original upstream commit was incomplete.
commit 0c083fb7342bc74e6a819461ce1f627ab2756af6
Author: Brian C. Lane <bcl@redhat.com>
Date: Fri Jun 5 14:40:00 2015 -0700
libparted: BLKPG_RESIZE_PARTITION uses bytes, not sectors (#1135493)
This results in the extended partition vanishing after adding another
partition.
Resolves: rhbz#1135493
Bug-Debian: https://bugs.debian.org/926735
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1641308
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit/?id=c6dc6e5d0f49a26242d2b28622514814a53d92e1
Last-Update: 2019-04-15
Patch-Name: blkpg-resize-partition-uses-bytes.patch
commit b0fe2b83da524892242e4c9341290deba61ad935
Author: dann frazier <dann.frazier@canonical.com>
Date: Fri Sep 7 13:31:15 2018 -0600
Read NVMe model names from sysfs
parted currently shows the same generic model name for all NVMe devices:
# parted /dev/nvme0n1 -s print | grep Model
Model: NVMe Device (nvme)
If the model information is available in sysfs, display that instead:
# parted /dev/nvme0n1 -s print | grep Model
Model: THNSN5512GPU7 NVMe TOSHIBA 512GB (nvme)
Signed-off-by: Brian C. Lane <bcl@redhat.com>
Bug-Debian: https://bugs.debian.org/911273
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit/?id=279bd5540a59e3bdc4e3702ff062f87fd842c0e9
Last-Update: 2018-10-22
Patch-Name: nvme-model-names-from-sysfs.patch
commit c07d9ae8338eb1240775005858bed36f5c56908d
Author: Richard W.M. Jones <rjones@redhat.com>
Date: Sat Mar 24 17:37:02 2018 +0000
linux: Include <sys/sysmacros.h> for major() macro.
Since glibc 2.27 this header is required.
Bug-Debian: https://bugs.debian.org/910326
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit/?id=ba5e0451b51c983e40afd123b6e0d3eddb55e610
Last-Update: 2018-10-05
Patch-Name: sysmacros-for-major-minor.patch
commit 68f38806462d0527f6474629b76e36799c46301a
Author: Curtis Gedak <gedakc@gmail.com>
Date: Sun Apr 10 11:38:41 2016 -0600
lib-fs-resize: Fix recognition of FAT file system after resizing
When resizing a FAT partition, an extra boot_sector memory allocation
was causing the original boot_sector information to be lost. The
resulting FAT file system was still recognized by GNU/Linux, but not
recognized by the proprietary Windows operating system.
The problem with Windows FAT32 recognition was introduced with:
Fix filesystem detection on non 512 byte sectors
80678bdd957cf49a9ccfc8b88ba3fb8b4c63fc12
Fix by removing the extra boot_sector memory allocation.
Note that since parted-3.0 another code path to the extra memory
allocation of fat_create(...) via ped_file_system_create(...) is
inaccessible. In an effort to maintain the ability to re-instate the
code, add a new boot_sector memory allocation where it is needed in
the alternate code path.
GNU bug report logs - #22266
[libparted] jump instruction and boot code is corrupted with random
bytes after fat is resized
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22266
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit/?id=c0d394abac4d6d2ce35c98585b6ecb33aea48583
Bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22266
Bug-Debian: https://bugs.debian.org/840710
Last-Update: 2018-04-09
Patch-Name: fat-resize-retain-boot-code.patch
commit f4b5debc99fde428730181fc38846ddac6dc19e2
Author: Mike Fleetwood <mike.fleetwood@googlemail.com>
Date: Sun Feb 28 15:36:10 2016 +0000
lib-fs-resize: Prevent crash resizing FAT with very deep directories
Resizing a FAT file system crashes in libparted/fs/r/fat/count.c
flag_traverse_dir() if the length of any path name in the file system
overflows the 512 byte file_name local buffer. Increase buffer to 4096,
PATH_MAX on Linux.
Reported in
https://bugzilla.gnome.org/show_bug.cgi?id=762448
Signed-off-by: Brian C. Lane <bcl@redhat.com>
Origin: backport, https://git.savannah.gnu.org/cgit/parted.git/commit/?id=6242ad71d855be62d99ec345e52393be86ca9900
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=762448
Bug-Debian: https://bugs.debian.org/840709
Last-Update: 2018-04-09
Patch-Name: fat-resize-long-path.patch
commit e2791daf90750b55063552fe148f884a4d578040
Author: Wang Dong <dongdwdw@linux.vnet.ibm.com>
Date: Wed Oct 26 04:22:49 2016 +0200
libparted/dasd: add test cases for the new fdasd functions
The test case uses a temporary file in libparted/tests under
Check framwork. It can be issued by "make check" in the test dir.
Signed-off-by: Wang Dong <dongdwdw@linux.vnet.ibm.com>
Signed-off-by: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Signed-off-by: Brian C. Lane <bcl@redhat.com>
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit?id=571e078406b59e8dcf02db3e8fe28d8eb4d2cef0
Origin: upstream, https://git.savannah.gnu.org/cgit/parted.git/commit?id=c11f5c005270d24bc3905ab3b743e96fc1a9a507
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1737144
Last-Update: 2019-07-30
Patch-Name: libparted-dasd-add-test-cases-for-the-new-fdasd-func.patch
![[bug history graph]](https://qa.debian.org/data/bts/graphs/p/parted.png){kind=link}