On Sun, Nov 1, 2020 at 1:06 AM Bill Wohler <woh...@newt.com> wrote: > Same here. > > Will you be able to fix this now so that everyone using fetchmail can > get mail without having to jump through hoops like building fetchmail or > finding the previous package? You can fetch the previous package version and its binaries[1] if you would like to. You can also enable the Sid repository, upgrade _only_ libssl1.1 from there then disable it. I will not be able to fix this due to how the packaging system works. When a Debian maintainer releases a new package version, s/he builds and tests it with the Sid/unstable repository. Buildd machines do very similar: build the package if the specified build dependencies and those minimal versions are met. Basically after some days the package migrates to testing / Bullseye if the following are true: the package built on all primary architectures it supports, doesn't have a serious bug reported against, its dependencies are in testing (or can migrate at the same time) and the package self-tests are successful. It was true for fetchmail but the new OpenSSL package (possibly due to upstream change) breaks other packages and can't migrate as is. But compiled code in fetchmail checks if the OpenSSL library is at least that version which was used for compilation. This is not true and it refuses to work. It will be solved by itself as soon as the OpenSSL package is fixed - unfortunately I don't see any steps toward this. Until then you can grab the previous fetchmail package version or upgrade to the newer OpenSSL package in Sid (which may break other packages using that).
Regards, Laszlo/GCS [1] http://snapshot.debian.org/package/fetchmail/6.4.12-1/
