Cyril Brulebois dijo [Sat, May 06, 2023 at 03:19:47AM +0200]:
> OK, so much fail on my part here, my bad.
A fair share of fail in my hands as well: I have been too busy, and
unable to react on this issue.
> That being said, it seems pretty clear to me at this point that the
> proposed update isn't reasonable: it would break autopkgtest (and
> possibly parts of ci.debian.net?), and it contains a bunch of
> irrelevant changes.
>
> We would need something much more targeted. I'm not commenting on
> whether the changes are even needed given the e2fsprogs package has
> dropped the new options (there are probably some combinations of
> source and destination environments that could benefit from a vmdb2
> update, but I'd like to avoid thinking about that again…).
Right. When I performed the upload, I didn't expect vmdb2 to be used
for autopkgtests. I completely agree with Elbrus: We cannot accept my
upload into bookworm.
What I plan to do (but please, others are welcome to do so 😇) is to
wait for a month, until bookworm is released, and upload to
stable-proposed-uploads a 0.26-2+1 or somesuch, including the
following, minimal diff thas has been accpted upstream:
https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/106/diffs?commit_id=5b91eb58673d43e27523877816169b14e1ab6dfc
There are some other reliability improvements in 0.27, some of which
could also be hand-picked to be backported to 0.26.
Greetings,
Attachment:
signature.asc
Description: PGP signature