Mastodawn

The attitude shown by the #Debian packager who insists on going against the will of @keepassxc devs, in this comment: https://github.com/keepassxreboot/keepassxc/issues/10725#issuecomment-2104401817 is… wow 🤦

This "packagers thinking they know better than the developers, and unilaterally patching things" mentality, along with distros often shipping outdated versions, is why many upstream software developers dislike dealing with Debian (& any LTS distro), and now ask users to test/run #Flatpak versions of their applications first and foremost.

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

How unexpected for debian to screw up with packaging an app and doubling down when confronted

Show thread

Matthias Klumpp May 11, 2024

@nekohayo @keepassxc Honestly, that sounds like a reasonable take, especially considering the reply of the former maintainer below.
Still, a compromise in providing both the full and a hardened minimal version could surely be done to make everyone happy with it, that's what is done with Nginx and many other packages as well.

Show thread

Alex L 🕊 🇵🇸May 11, 2024

@nekohayo @keepassxc

Flatpak *is* indeed a platform for third-party apps while distros never were, they are called "distributions" for a reason. Distros' packages serve a different purpose that is: reconfiguring an OS (sometimes to include more apps) so of course a distro modifies upstream projects to integrate them.

That said, does Flatpak platform already provide the API needed by those KeepassXC features? When the needed API are (yet) not available the distro's manual integration is needed