On 2021-06-15 13:18:23, Sebastiaan Couwenberg wrote: > On 6/15/21 1:00 PM, Sebastian Ramacher wrote: > > If neither you as maintainer nor upstream care about upgrade without > > data loss, I don't think postgis is suitable to be included in a stable > > release. Best option moving forward is to get postgis and its reverse > > dependencies removed from bullseye. > > Removing postgis during distribution upgrade does not cause data loss. > Don't try to make this issue bigger than it is.
Again: how are users supposed to upgrade their postgis installation while retaining their data? So far I only found upstream's instructions which you told me are "shit". There are also not instructions or hints included in the release notes for bullseye. If I am not mistaken, Andreas proposed in another thread to introduce a postgis-2.5-built-against-postgresql-13 package to help with the upgrades. Would this be a viable option? We're trying to find solutions here to help user's with their postgis upgrades. After all, this discussion started after a user experienced issues. If we cannot provide users of the postgis package with an upgrade path, then yes, this is a grave bug. It needs to be dealt with. "Don't bother" and "it's shit" is not good enough. One of the judgment calls we as maintainers have to make is whether a piece of software is suitable for a Debian stable release and if we can support upgrades from one stable to the next one. The information that I got so far from you, is that postgis does not care about the second part. I'd love to be convinced otherwise. Cheers -- Sebastian Ramacher
