#1141108 libblockdev: Behaviour changes in exfatprogs 1.4.0 and later breaks libblockdev

#1141108#5
Date:
2026-06-29 20:06:33 UTC
From:
To:
Hi,
exfatprogs 1.4.0 changed two things:
1. mkfs.exfat now creates a partition table by default
2. Formating in tune.exfat verbose mode changed

That seems to be the reason for the broken tests e.g.
https://ci.debian.net/packages/libb/libblockdev/testing/amd64/72658664/

Upstream I could find those two fixes:
https://github.com/storaged-project/libblockdev/pull/1198
https://github.com/storaged-project/libblockdev/pull/1199

#1141108#10
Date:
2026-06-29 21:26:52 UTC
From:
To:
On Sun, Jun 28, 2026 at 11:16:50AM +0200, Paul Gevers wrote:

Hello Paul,

I created now
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141108 for libblockdev
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141111 for udisks2

In the case of udisks2 I believe it's only a failing test case. The upstream
fix is adjusting the test case to format without partition table the way
exfatprogs mkfs.exfat did before.

For libblockdev I'm not sure where exactly things break for the user because something
relies on the tune.exfat verbose output.
I tried gnome-disks (package gnome-disk-utility) which I believe uses libbblockdev3
via udisks2, and that is still able to detect an exfat img and format one.

Sven