search

mvo5 / synaptic

The synaptic package manager
GNU General Public License v2.0
154 stars 55 forks source link

Mixed Repositories Issue #118

Closed 0A7V9A closed 9 months ago

0A7V9A commented 9 months ago

I got mixed versions of packages in linux because I added "debian backports" (as far as i can remember it was "debian backports") repo before but then removed later. Anyhow the packages were already installed by those versions from "debian backports". For example: a random package version like "1:3.0.18-dmo9" stays on top and considered "higher or latest" version than "3.0.19" from "kali-rolling" repo, that's why I want to [force] reinstall ALL (or at least the ones which has issues like that ) packages to "kali-rolling" versions, and it's creating big issues like removing a lot of softwares and other packages. Are there any easy and safe ways (maybe using apt pinning) to do this in synaptic manager or aptitude or etc?

Here you can see that "1:3.0.18-dmo9" is considered latest and forcing version to "3.0.19" from (kali-rolling repo) is considered as DOWNGRADING Screenshot_2023-10-22_13-28-29

Here i selectively forced verions for vlc packages: Screenshot_2023-10-22_13-39-37 Screenshot_2023-10-22_13-34-30

No broken packages but look at this: Screenshot_2023-10-22_17-22-28

trebmuh commented 9 months ago

"1:3.0.18-dmo9" is considered latest and forcing version to "3.0.19"

This is expected as the epoch number is set to "1" in the dmo9 version. You can see the Debian manual for more information about this (tips: search for "epoch" in the page).

0A7V9A commented 9 months ago

Somehow i was able to "resolve" this issue by manually installing/removing a bunch of local, obsolete packages. Closing this now