Hi Ted,
On Tue, Jun 10, 2025 at 06:19:46PM -0100, Theodore Ts'o wrote:
> How important is this that we get thes fix into Trixie? I'm not sure
> how bad it will be that the diversion isn't going to be cleaned up.
> WDYT?
The affected code path is fuse2.postrm. Due to the use of ||, the
"remove" a
On Tue, Jun 10, 2025 at 08:26:12PM +0200, Helmut Grohne wrote:
> Hi Ted,
>
> I concur with your analysis am sorry for having introduced this. It's
> actually in the piuparts log
> https://piuparts.debian.org/sid/pass/fuse2fs_1.47.2-2.log, but it wasn't
> fatal.
No worries, it happens to all of us
Hi Ted,
On Tue, Jun 10, 2025 at 04:12:17PM -0100, Theodore Ts'o wrote:
> Many thanks for noticing this! This bug has been around since
> 1.47.2~rc1-2, in a botched attempt to fix Debian bug #1088838 ("Fix
> fuseext2 transition to account for /usr-move). The proposed patch in
> bug #1088838 had a
found 1107595 1.47.2~rc1-2
thanks
On Tue, Jun 10, 2025 at 02:36:49PM +0200, Eric Valette wrote:
> Package: fuse2fs
> Version: 1.47.2-2
> Severity: normal
>
> Unpacking fuse2fs (1.47.2-2) over (1.47.2-1+b1) ...
> /var/lib/dpkg/info/fuse2fs.postrm: 6: test: failed-upgrade: unexpected
> operator
M
Package: fuse2fs
Version: 1.47.2-2
Severity: normal
Unpacking fuse2fs (1.47.2-2) over (1.47.2-1+b1) ...
/var/lib/dpkg/info/fuse2fs.postrm: 6: test: failed-upgrade: unexpected operator
-- System Information:
Debian Release: 13.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'),
5 matches
Mail list logo
