5 ms·

Well no, what the user is actually being given is a completely different application than the original one they downloaded, which is now increasing the maintena

by worble 2y ago

Well no, what the user is actually being given is a completely different application than the original one they downloaded, which is now increasing the maintenance burden upstream because THEY are they one getting all the bug reports because Debian decided to swap the packages out from underneath their users: https://github.com/keepassxreboot/keepassxc/issues/10725#issuecomment-2104381335 https://github.com/keepassxreboot/keepassxc/issues/10725#iss... > This is now our fourth bug report because of the decision to neuter the base KeePassXC package in Debian

cjk2 2y ago
It's not completely different. They patched stuff out. And I, as an end user, am absolutely fine with that, as a user of vim-nox package etc etc...
- riedel 2y ago
  I thought from reading the bug report is that they only changed the default of a supported cmake build flag. I think that a keepass-nonet would have be a wiser choice, but I do not blame Debian people to be opinionated towards the more secure choice.
- alyandon 2y ago
  vim-nox is pretty much full-featured vim without x11 stuff. Do you have a non-trivial .vimrc/.vim directory? Would you be accepting of the maintainer disabling a bunch of features and pushing those changes out under the main vim-nox package such that it breaks your existing install? Would it be reasonable to expect you as the end user to figure out what has happened and that you need to uninstall vim-nox and and install vim-nox-full?
  - cjk2 2y ago
    My .vimrc is 8 lines. I learned not take the kitchen sink with me on holiday.
- yjftsjthsd-h 2y ago
  But vim-nox is a separate package with a clear name saying that it's got X removed; I don't think this would be nearly as controversial if they'd shipped a keepassxc-nonetwork package.
  - joeyh 2y ago
    vim-tiny is installed by default on debian (providing a vim command), and also has X removed.
    - yjftsjthsd-h 2y ago
      Okay? Calling it keepassxc-tiny would also be fine. I think it's relevant that `apt install vim` does not give you vim-tiny.
    - naniwaduni 2y ago
      Yeah, I hated that too.
Arnavion 2y ago
Users should ideally report bugs to their distribution, not to upstream. The distribution package maintainer then does triage to determine if the issue is specific to the distribution package or should be forwarded upstream. That's how it used to be in the past (and still is for enterprise distros because you might as well use the support contract you paid for). But lately users have gotten more savvy about talking to upstream directly, especially since more and more upstreams are now on easy-to-use websites like GitHub instead of mailing lists. That's still fine if users do their own diligence to ensure the issue is with upstream and not with the distribution package, but alas they don't all do that, leading to these spurious reports.
- cqqxo4zV46cp 2y ago
  What’s your point? We all know why it’s happening. The reality is that it’s not to user expectations, which is bad.

by worble 2y ago

cjk2 2y ago

It's not completely different. They patched stuff out. And I, as an end user, am absolutely fine with that, as a user of vim-nox package etc etc...

riedel 2y ago
I thought from reading the bug report is that they only changed the default of a supported cmake build flag. I think that a keepass-nonet would have be a wiser choice, but I do not blame Debian people to be opinionated towards the more secure choice.
alyandon 2y ago
vim-nox is pretty much full-featured vim without x11 stuff. Do you have a non-trivial .vimrc/.vim directory? Would you be accepting of the maintainer disabling a bunch of features and pushing those changes out under the main vim-nox package such that it breaks your existing install? Would it be reasonable to expect you as the end user to figure out what has happened and that you need to uninstall vim-nox and and install vim-nox-full?
- cjk2 2y ago
  My .vimrc is 8 lines. I learned not take the kitchen sink with me on holiday.
yjftsjthsd-h 2y ago
But vim-nox is a separate package with a clear name saying that it's got X removed; I don't think this would be nearly as controversial if they'd shipped a keepassxc-nonetwork package.
- joeyh 2y ago
  vim-tiny is installed by default on debian (providing a vim command), and also has X removed.
  - yjftsjthsd-h 2y ago
    Okay? Calling it keepassxc-tiny would also be fine. I think it's relevant that `apt install vim` does not give you vim-tiny.
  - naniwaduni 2y ago
    Yeah, I hated that too.

Arnavion 2y ago

Users should ideally report bugs to their distribution, not to upstream. The distribution package maintainer then does triage to determine if the issue is specific to the distribution package or should be forwarded upstream. That's how it used to be in the past (and still is for enterprise distros because you might as well use the support contract you paid for). But lately users have gotten more savvy about talking to upstream directly, especially since more and more upstreams are now on easy-to-use websites like GitHub instead of mailing lists. That's still fine if users do their own diligence to ensure the issue is with upstream and not with the distribution package, but alas they don't all do that, leading to these spurious reports.

cqqxo4zV46cp 2y ago
What’s your point? We all know why it’s happening. The reality is that it’s not to user expectations, which is bad.