[pkg-go] Bug#1121681: Future podman metadata backend deprecation/migration (nag message)

[Reinhard Tartler]

Control: tag -1 pending

Dear Jan,

Thanks for the report and for your patience, and I completely agree this 
is painful.

I’ve added a clear debian/NEWS entry 
https://salsa.debian.org/go-team/packages/podman/-/commit/0c395df48f33880e23321a9a5558548d1e69d5e9 
that documents the warning and the current lack of a migration path. The 
next upload will automatically close this bug via debian/changelog.

The real fix (a proper export/import or in-place conversion tool) needs 
to happen upstream, not in Debian. The most promising effort right now 
is https://github.com/semaphoreui/semaphore/issues/3296 (a community 
attempt at a BoltDB → SQLite converter). If you have complex setups you 
don’t want to reset, please consider testing or contributing there!

For the record: upstream deliberately provides no automated migration 
and recommends podman system reset because they treat the libpod 
database as ephemeral. Volumes and images survive the reset untouched. 
At this point, I don't think my personal opinion as packager matters a 
lot, the best way to improve the package at this time seems to be to 
document the situation in NEWS. Let me know what you think by responding 
to this email keeping this bug in CC.

In the meantime, export SUPPRESS_BOLTDB_WARNING=1 silences the nag 
instantly.

Thanks again for helping make Podman better!

Best,
Reinhard