According to a fast check, this is the same as what was reported and discussed in https://github.com/aptly-dev/aptly/issues/1399
The problem is about a corrupted DB, but our problem is not that we have a corrupted DB to work with (suggestions are about clean + re-create) but that we have an issue which corrupts the DB in the first place. Upstream considers the much newer version 1.6 to be fixed, but didn't point to a particular commit. IMHO this comes down to build upstream aptly from git, but using the system golang dependencies. With that if: - a) 1.6 is fixed but 1.4 is not - bisect which aptly change helps - b) 1.6 is broken as well, then iterate/bisect which of the dependencies needs to be bumped and then check the fix there - c) Or we ignore that and we build it with golang 1.17 again seeing if the original issue are due to changes in just that. @Allen - I'd leave this to you now as you did the original upload and might have reasons to not go back to 1.17 or any other implications you want to remain. ** Bug watch added: github.com/aptly-dev/aptly/issues #1399 https://github.com/aptly-dev/aptly/issues/1399 ** Changed in: aptly (Ubuntu) Assignee: (unassigned) => Allen Huang (allenpthuang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2140498 Title: aptly fails to create new mirrors or decode previous mirror data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/2140498/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
