I dug a bit more and found we already had this issue when upgrading e2fsprogs to 1.47.0 in mantic [1]
At this time xnox fixed the issue by disabling this feature in the default conf of e2fsprogs and mentioned doing a SRU in jammy. I think that may be the best solution, instead of trying to handle this exception in snapd.
I dug a bit more and found we already had this issue when upgrading e2fsprogs to 1.47.0 in mantic [1]
At this time xnox fixed the issue by disabling this feature in the default conf of e2fsprogs and mentioned doing a SRU in jammy. I think that may be the best solution, instead of trying to handle this exception in snapd.
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ e2fsprogs/ +bug/2025339