Thank you very much for all the explanations :)
Gesendet: Samstag, 4. April 2026 um 18:38
Von: "Sebastiaan Couwenberg" <[email protected]>
An: "Bob Ansay" <[email protected]>, [email protected]
Betreff: Re: keepassxc: cannot install keepassxc on debian 12.8 due to libbotan-2-19 and libqt5concurrent5 not found
> I have the three sources with "codenames" in my sources list, but with some differences:
> no trailing backslash
The trailing backslash shouldn't matter.
> "non-free" missing
This shouldn't matter either, keepassxc is in main which cannot depend on packages in non-free.
> I changed to match yours, but the two libs still were not found
Try a different mirror then, I use the mirror in my country on most systems (ftp.nl.debian.org):
https://www.debian.org/mirror/list
And don't forget to run `apt update` after making sources.list changes and before installing packages to update the repository data.
> only after adding the "oldstable" sources keepassxc installed properly.
>
> In a quest to understand, I then deleted files from /var/lib/apt/lists (googled that it should purge the sources cache), removed keepassxc and apt-autoremov'ed the libs in question.
`apt clean` should suffice.
> But from that point on, I could never get keepassxc to not install
>
> somehow the libs, or the sources to them are now magically present somewhere on my system?
There is no magic, only apt.
> My linux/debian knowledge is not very profound - I don't even get what you told me about the codenames in the sources.list
That's one of the fields in the package repository metadata:
Suite: oldstable
Version: 12.13
Codename: bookworm
https://ftp.debian.org/debian/dists/bookworm/Release
Using the codename puts you in charge when your systems undergo major version upgrades.
From the release-notes:
"
A release can often be referred to both by its codename (e.g. “bookworm”, “trixie”) and by its status name (i.e. “oldstable”, “stable”, “testing”, “unstable”). Referring to a release by its codename has the advantage that you will never be surprised by a new release and for this reason is the approach taken here. It does of course mean that you will have to watch out for release announcements yourself. If you use the status name instead, you will just see loads of updates for packages available as soon as a release has happened.
"
https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#preparing-apt-sources-files
> is oldstable the same as bookworm?
At time of writing it is, when forky is released as stable bookworm will become oldoldstable and trixie will become oldstable.
> I am on bookworm, this is why it is kind of irritating for me
Consider upgrading the forky, the current stable release.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
