https://socially.drinkingatmy.computer/objects/4df5b6b4-102f-4854-8721-480d56380e0c
I use debian btw 🙈
I like debians dad bud 😻
https://socially.drinkingatmy.computer/objects/4df5b6b4-102f-4854-8721-480d56380e0c
I use debian btw 🙈
I like debians dad bud 😻
What about their handling didn’t you like?
It sounded like they were put in a pretty crappy position by the upstream adding a grumpy warning message. It’s also not like they were shipping a dangerous vulnerable old version or something, they backported security fixes into the stable version like with every other package, it just didn’t have new features and improvements and the dev was sick of being asked by users to support the old versions.
Patching out the message (which was effectively PUP malware) on testing and then porting that to stable and shifting the default to LightDM and LightLocker in future releases seems like a good solution. I probably would have dropped xscreensaver altogether in future versions (which is what the author suggested) for being malicious, but at the time there weren’t a lot of reliable alternatives and it was better for users to still have the option.
I think they should have either dropped the package or at the very least renamed it so people stop bothering jwz. Making the upstream developers deal with LTS versions they never intended to support is incredibly disrespectful.
Frankly Debian should have dropped it. If you create a situation where your users are annoying the fuck out of the author then your at fault.
Debian really did not handle the situation well. But it’s the same sort of attitude I see from shitty mod pack authors in modding communities.
They ship outdated versions and back port patches, then get pissy or don’t comply with the authors of the software they are shipping when the author rightfully gets upset at being bothered to support out dated shit.
It’s not the first nor will it be the last time a out dated distro causes this issue.