Watching Linux distros (and yes, it is usually Debian packagers who act the most sanctimonious) shoot themselves in the face and then insult upstream AND the users of a popular package under the delusion that only the distro's self-declared experts are capable of making decisions is always a good reminder as to why you will never be able to waterboard me into using Linux as my primary desktop. Very sorry this is happening Team KeePassXC. https://fosstodon.org/@keepassxc/112417353193348720
Team KeePassXC (@[email protected])

Debian Users - Be aware the maintainer of the KeePassXC package for Debian has unilaterally decided to remove ALL features from it. You will need to switch to `keepassxc-full` to maintain capabilities once this lands outside of testing/sid.

Fosstodon
The KeePassXC GitHub repo where Debian users are filing bugs (b/c people by default blame upstream, in part b/c the distros love to blame upstream for everything, even when the changes are clearly the packagers fault) and the Debian packager responds by calling the software crap is my favorite part. https://github.com/keepassxreboot/keepassxc/issues/10725
Debian No-Feature KeePassXC Package · Issue #10725 · keepassxreboot/keepassxc

Overview I'm using the Brave and Firefox browsers under Ubuntu testing using keepassxc version 2.7.7, suddenly the browser integration doesn't work anymore. So I went into the settings menu to enab...

GitHub

@film_girl

my favorite part was the call back to the xscreensaver fracas from days long gone by

part of the answer is the same now as then: The bugs from Debian users belong in Debian channels

(deleted & redrafted into the "my favorites" part of the thread)

@idlestate @film_girl but also that was the upstream dev being an ass hiding that time bomb message & generally sabotaging an orderly packaging process.
Other distros just patched that one out, while Debian tried to be nice and coordinate with upstream ...

This time, the Debian maintainer does seem kinda rude. And while I think the reasoning behind the change is sound, they're definitely late to the party and should really use a more delicate approach

On the other hand, this is what happens when you use the *testing* distribution.
I use stable because I don't want these kind of changes. In two years, I might have to switch a few packages around when I switch to the next stable. And that's fine, because before I make that decision, I won't.
@kgMadee2 the problem is unstable and testing find its way to downstream distros that have more normie users more quickly. And although I agree in theory that people who use unstable branches should read release notes, fundamentally breaking a package — which let’s be very clear here, is what this Debian packager did — for existing users and giving those users no info about that change, a change that includes removing a way some users might unlock the program (yubikey) in anti-user and bad.