However, only the repositories which are still configured are ever taken into account.The Advanced package tool, commonly known as APT, is a application which allows for the management, installation and removal of software packages on Debian-based Linux distributions such as Ubuntu. In summary: if you’ve restored your /etc/apt/sources.list configuration to its previous values and run apt update since then, nothing will have changed, and you should be able to install keepassxc without needing the Sid repositories.Īs far as undoing an apt update command goes, you can’t ever fully undo it unless you have a backup of /var/lib/apt/lists, because the information from the repositories which are still configured has been updated. Your initial problem is surprising, since keepassxc is available in Bullseye and has been continuously ever since Bullseye has existed. A subsequent apt upgrade won’t know about packages (and versions) in Sid. Removing the Sid entries and running apt update again will result in the Sid information being forgotten (or rather, no longer taken into account). So apt update on its own, after adding entries for Sid, will only retrieve the repository information, it won’t upgrade anything to Sid. It doesn’t cause any packages to be upgraded, or anything to be restarted or ask to be restarted.Īpt upgrade upgrades the system’s installed packages so that they match the latest available versions, adjusted according to “pin priorities” if necessary (and the default release, if configured, which is a sort of pin priority). I’m somewhat surprised that apt update would request “2 restarts of programs”.Īpt update retrieves the repository information for all the repositories configured in /etc/apt/sources.list and files in /etc/apt/. Package files: 100 /var/lib/dpkg/status release a=now 500 stretch/non-free amd64 Packages release v=9.13,o=Debian,a=oldstable,n=stretch,l=Debian,c=non-free,b=amd64 origin 500 stretch/contrib amd64 Packages release v=9.13,o=Debian,a=oldstable,n=stretch,l=Debian,c=contrib,b=amd64 origin 500 stretch/main amd64 Packages release v=9.13,o=Debian,a=oldstable,n=stretch,l=Debian,c=main,b=amd64 origin 500 stretch/updates/main amd64 Packages release v=9,o=Debian,a=oldstable,n=stretch,l=Debian-Security,c=main,b=amd64 origin 500 stretch/main amd64 Packages release v=9.13,o=Debian,a=oldstable,n=stretch,l=Debian,c=main,b=amd64 origin Pinned packages: Has my dependency tree been irrevocably messed up? If I run a sudo apt upgrade, would this pull in changes from the sid release? I don't totally understand the difference between update and upgrade, so this could be a non-issue.Īny help would be greatly appreciated. I then ran a sudo apt autoremove, which removed 3 packages. I then commented out the line in the sources.list file and ran sudo apt update again, the output of which said there were no updates. It was running for a while at that point and even had requested 2 restarts of programs. After realizing that this was probably a bad idea, I did a keyboard interrupt (Ctrl-C) as the update was running. I added a line for a sid mirror to /etc/apt/sources.list and then ran sudo apt update. I tried running sudo apt install keepassxc but it turns out keepassxc is not apart of the bullseye release. I'm running Debian bullseye and wanted to install KeepassXC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |