Missing pkgs in testing

Dasc · 11-11-2005, 04:20 PM

These days I started experiencing a problem: some packages I need disappeared from testing pkgs lists (mainly kdevelop3) and this is causing some troubles with synaptic updates
it seems the problem is that kdevelop needs kdelibs4 but the actual pkg changed to kdelibs4c2. so when I try a smart upgrade it marks the old kdelibs4 for uninstall thus trying to remove kdevelop3 too
While next versions of kdevelop (actually present in unstable) require this kdelibs4c2 testing version does not so I'm forced to delay sys updates

I've googled a bit and amongst the few infos i've found someone suggested to add stable repositories to sources.list
but i've also read of the troubles coming from mixed system
is this the case or is it meant to work that way?

should I just wait for a kdevelop pkg upgrade or i'm intended to add stable to my sources?

for completeness here is my sources.list
# deb file:///cdrom/ sarge main

deb http://ftp.it.debian.org/debian/ testing main
deb-src http://ftp.it.debian.org/debian/ testing main
deb http://security.debian.org/ stable/updates main
deb http://ftp.it.debian.org/debian/ testing non-free
deb http://ftp.it.debian.org/debian/ testing contrib

deb http://www.stanchina.net/~flavio/debian-fglrx-modules/ ./
deb http://www.stanchina.net/~flavio/debian-fglrx-xfree86/ ./

deb http://www.tux.org/pub/java/debian/ testing non-free

# deb http://wine.sourceforge.net/apt/ binary/
# deb-src http://wine.sourceforge.net/apt/ source/

zero79 · 11-11-2005, 05:14 PM

this happens from time to time as new packages are merged into testing. if you add a line

Code:

deb http://ftp.it.debian.org/debian/ sarge main

to your /etc/apt/sources.list and

Code:

Package: *
Pin: release a=stable
Pin-Priority: 550

Package: *
Pin: release a=testing
Pin-Priority: 600

to an /etc/apt/preferences file, you will be able to install the stable version of kdevelop with

Code:

# apt-get update
apt-get install -t stable kdevelop3

good luck

Dasc · 11-14-2005, 06:58 PM

sorry for the delay and thanks for your answer

but does this method solve the lib conflict problem?
I mean, the issue was not exactly trying to install kdevelop3 (wich i have already installd) but avoid it to be uninstalled due to other pkgs update (kdelibs4c2 replaces kdelibs4 and as a consequence kdevelop3 is removed)

about the config thing, is it completely release-safe and something that i should do anyway?

zero79 · 11-24-2005, 02:01 PM

most advanced users set up apt as i've described. it's safe. using the '-t stable' apt option will get the libs and packages from stable, and will probably revert the entirety of kde to the stable version.

good luck.