I'll start by stating, I'm pretty sure this is a unique mess of my own design, but I hope someone encountered this and might be able to help.
My laptop runs Pop!_OS 22.04 (Based on Ubuntu Jammy). I really like the xscreensaver packages, but the Debian/Ubuntu/Pop!_OS release repos contain an outdated version, and only sid (aka Unstable) contains the updated package*.
No fret, that's why pinning exists, and so this is how I have it setup:
Package: * Pin: release a=unstable Pin-Priority: 200
Package: xscreensaver* Pin: release a=unstable Pin-Priority: 2000
deb [arch=amd64] http://http.us.debian.org/debian sid main contrib non-free
This actually works, at this point running
sudo apt install xscreensaver installs the updated versions.
However, there is a strange side-effect.
When I run
sudo apt update followed by
sudo apt upgrade, I get the following output:
This also throws off Pop!_OS Shop's update count, with these packages showing as pending Operating System Updates.
Some data I collected while attempting to troubleshoot this.
/etc/apt/sources.list.d/debian.sid.list and running
sudo apt update resolves the issue, so I know it's just a miscalculation/flawed logic somewhere.
Focusing on the the first package in the list
Although I know the error is completely superficial, at first I thought
apt somehow tracks where (which repo) the package came from, so I removed, cleaned-up, then reinstalled the package. Didn't make a difference.
sudo apt remove alsa-topology-conf sudo apt clean sudo apt update sudo apt install alsa-topology-conf
apt policy alsa-topology-conf, the results are:
alsa-topology-conf: Installed: 220.127.116.11-2 Candidate: 18.104.22.168-2 Version table: *** 22.214.171.124-2 200 200 http://http.us.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status 126.96.36.199-2 501 501 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 501 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
It seems that both
jammy have the exact same version, and for some reason,
apt matches the package to the
200 priority, instead of the
501 priority entry.
/etc/apt/sources.list.d/debian.sid.list removed, the output looks like this:
alsa-topology-conf: Installed: 188.8.131.52-2 Candidate: 184.108.40.206-2 Version table: *** 220.127.116.11-2 501 501 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 501 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status
The following are related questions with similar situations but none of the answers there helped me understand or resolve this.
- apt pinning priority restricted
- Debian 10: Why some SSL packages will be downgraded?
- How to get rid of "Packages were downgraded and -y was used without --allow-downgrades" apt message
I've tried all of the answers in the above questions, but none seems to either be relevant or work out.
Does anyone have any suggestion on how to reconcile this so that the system will not constantly think that these packages need to be DOWNGRADED ?
apt policyseems to show that you're mixing Debian and Ubuntu repositories. I wouldn't recommend that. Can you show the set of repositories you've got configured?