Hi Alexandre, On Fri, 26 Oct 2018 13:15:45 -0400 Alexandre Viau <[email protected]> wrote: > The old package used to embed the msgpack decoder/encoder and this new > package will use Debian's version instead. > > You are going to have to re-create a new aptly database. > > I am not sure that upstream can even support this, even less so in > Debian since we wouldn't allow them to embed two versions of the library > to support the migration. > > The first step would be that upstream moves to the new version of > go/codec and/or go-msgpack. > > There would need to be backwards compatibility shipped in those > libraries which would allow upstream to support an upgrade path. > > Aptly works fine, it just doesn't support the migration. For this > reason, I will dial down the severity to wishlist and rename the bug > accordingly. Please let me know if you disagree. >
IMO, we should provide a smooth upgrading experience from stretch to buster. Just look at the code, it already has a code path to skip decode the time field. https://sources.debian.org/src/aptly/1.3.0+ds1-2/deb/remote.go/#L604 https://sources.debian.org/src/aptly/1.3.0+ds1-2/deb/snapshot.go/#L144 I think you can work around with the same method. Change the if condition should be enough I think. But I haven't tested yet. -- Shengjing Zhu
