[Rspamd-Users] update issue on Debian 10
martin at holub.co.at
Sun Mar 19 20:02:14 UTC 2023
According to https://wiki.debian.org/DebianReleases Debian 10 buster is
EOL as of Sept 10th 2022 (this was half a year ago), ~1 year after the
current stable Debian was released. One may discuss supporting it via
some LTS mechanism, but i get Vsevolods point by not supporting it
directly, but only stable releases. Maybe this policy could be outlined
somewhere on the rspamd.com website (i haven't found anything about
it?), but i totally understand that he has not the time to support the
"compiler hell". One Option to have newer rspamd on older system might
be switching to a dockerzized setup, maybe you want to look into that?
Am 19.03.23 um 20:02 schrieb Fred Zinsli via Users:
> So you have already stopped Debian 10 support in spite of the fact
> that official support stops 1 Aug 2022 and LTS support expires 2028.
> This means that you are supporting "forced" OS upgrades regardless of
> the users circumstances.
> If this is your position then you should be advising users of your
> position and when you intend to stop support for any given OS version.
> This is a position that should be reviewed.
> On 19/03/2023 21:13, Vsevolod Stakhov wrote:
>> On 19/03/2023 05:55, Miroslav Šebek via Users wrote:
>>> latest rspamd update from 3.4 to 3.5 on Debian 10 is causing package
>>> to be removed because it depends on packages libc++1-16,
>>> libc++abi1-16 and libunwind-16 which are all in experimental debian
>>> repos only.
>>> Right now staying on 3.4 but will there be some kind of solution for
>> Debian 10 is EOL. I'm not going to support updates for EOL
>> distributives. The debian packages for Rspamd 3.5 are still not in a
>> good shape but I will definitely drop support for Debian 10 (buster)
>> and Ubuntu Bionic as they are no longer supported. The burden to
>> support old compilers is too high...
More information about the Users