On Sun, Nov 1, 2020 at 1:57 PM Klaumi Klingsporn <klaumi...@gmx.de> wrote: > On Sun, 1 Nov 2020 08:22:27 +0100 > =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= > <g...@debian.org> wrote: > > I will not be able to fix this due to how the > > packaging system works. [...] > you're right. But it might help the next time, if you could > add a conflict to the package to all versions of libssl1.1 > smaller than the one it is compiled with. While it can help, I'm not sure if it's a good solution.
> Otherwise the problem will reappear every time a new > version of fetchmail enters testing before the version of > openssl it is compiled with. This case is rare. If OpenSSL and fetchmail are uploaded at the same time, they should migrate to testing together. If OpenSSL uploaded a day or more earlier, then it should be in testing sooner than fetchmail. If it's fetchmail that is uploaded sooner, then it will be built with an earlier OpenSSL version. Such a problem only happens if OpenSSL is stuck in Sid which should not happen as it breaks all packages that compiled with that version and can migrate to testing on its own. That is, OpenSSL should be maintained properly. However it's missing manpower for one and half decades [1]. :( Cheers, Laszlo/GCS [1] https://bugs.debian.org/332498
