[AUH] parted: upgrading to 3.8 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *parted* to *3.8* has Succeeded.

Next steps:
    - apply the patch: git am 0001-parted-upgrade-3.7-3.8.patch
    - check the changes to upstream patches and summarize them in the commit message,
    - compile an image that contains the package
    - perform some basic sanity tests
    - amend the patch and sign it off: git commit -s --reset-author --amend
    - send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-- >8 --
From 7a9e1dc5a9715d0bfa64d94810aacfdd0c6add19 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Fri, 25 Sep 2026 05:39:05 +0000
Subject: [PATCH] parted: upgrade 3.7 -> 3.8

version 3.8
NEWS: Releasing stable version 3.8
maint: Update to latest gnulib
maint: post-release administrivia
version 3.7.14
maint: Update to latest gnulib
NEWS: Update news for next release

hurd: Fix gnu_read problems with block size > 512b
This fixes offset calculations when the block size is larger than 512b
by checking for negative offsets, and skips the copy of the length is
zero.

NOTE: This error was found by an AI scan of parted by AISLE, and the
patch is mostly the patch suggested by the analysis. It has been
reviewed by Samuel and I.

Assisted-by: AISLE in partnership with Red Hat
maint: post-release administrivia
version 3.7.13
NEWS: Update news for next release

maint: Update copyright statements to 2026
by running make update-copyright

maint: Update to latest gnulib and bootstrap script

parted: Fix partition number allocation in do_print
GPT can have up to 8192 partitions, but we only allocate 4 bytes (two of
which are for a space and a \0). Increase this to 6 so that more than 99
partitions doesn't overflow the temporary variable.

fdasd: Make sure data set name is positive
Passing a negative value, eg. PART-999, to atoi could result in passing
a negative value to the setpos call when it writes f1_counter.

This adds an exception check to ensure the result of the atoi is always
positive, and it preserves the rest of the logic which depends on n being
1 less than the value.

resize: Make sure hfsc_new_cachetable cannot overflow on 32bit
Add a couple of PED_ASSERT checks on size to make sure the ped_malloc
call doesn't allocate less than expected.

resize: Make sure 32bit build cannot overflow frag_count
Add a couple of PED_ASSERT checks to fat_op_context_new that make sure
the frag_count value can be allocated. Does not effect 64bit
architectures.

libparted: Catch FAT metadata triggered errors
Bad metadata can trigger a buffer overflow in fat resize code. Trigger
an assert when the sector count is too large, or malloc is called with a
size of 0

Adds a new test that checks to make sure that the assert is triggered.
This includes a test for deep directory traversal which should be caught
by glibc and reported as 'buffer overflow detected'.

This also includes a check on the flag_traverse_dir dir_name length to
prevent an overflow of the 4k buffer with deeply nested directories.
Also include a test for this assertion.

WARNING: parted should be build with debug enabled (which is the
default) this enables a large number of PED_ASSERT checks which catch
various conditions like these.

This fixes two CVE's:
 - CVE-2026-89085 - heap buffer overflow in _init_fats / fat_table_read
 - CVE-2026-89088 - heap buffer overflow in duplicate_legacy_root_dir

Adding support for ExFAT filesystem
Added and registered exfat probing function
Updated msdos label probe to properly detect full-disk exfat fs
Reflected ExFAT support in doc
Added ExFAT detection test in t1700-probe-fs.sh

Cleanup zero as null pointer constant warnings
Pointer types should be set to NULL, not zero. gcc is now warning about
these with:
  warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]

This cleans up all the uses found when running make with gcc 16.0.1
README-release: Fix typos in doxygen instructions

maint: Distribute Doxyfile
This makes it easier for downstream packages to ship API documentation
(see e.g. https://bugs.debian.org/1119679).

bug#80795: [PATCH] build: mark functions with const attribute, per gcc warnings
fixes warning since glibc-2.43

For ISO C23, the functions wcschr that return pointers into their
input arrays now have definitions as macros that return a pointer
to a const-qualified type when the input argument is a pointer to a
const-qualified type.

../../parted/strlist.c: In function 'wchar_strchr':
../../parted/strlist.c:61:16: warning: return discards 'const' qualifier from
pointer target type [-Wdiscarded-qualifiers]
   61 |         return wcschr (str, ch);
      |                ^~~~~~

maint: post-release administrivia
---
 ...1-t9042-dos-partition-limit.sh-unconditionally-skip.patch | 5 +----
 meta/recipes-extended/parted/files/fix-doc-mandir.patch      | 2 +-
 .../recipes-extended/parted/{parted_3.7.bb => parted_3.8.bb} | 2 +-
 3 files changed, 3 insertions(+), 6 deletions(-)
 rename meta/recipes-extended/parted/{parted_3.7.bb => parted_3.8.bb} (96%)