[vox-tech] aptitude problems after a couple dist-upgrades

[Richard Harke]

You probably have a mismatch between distribution versions.
There are two ways to name debian releases and they move
with respect to each other whenever a new version is released.
i.e., at some point sarge was testing and later it became stable
But the install likely set up your sources.list to point at unstable
rather than explicitly pointing to sarge. So when you did a
apt-get dist-upgrade, you were actually trying to jump a whole
release. This has been known to create the crap you are seeing.
I'm not sure how to fix this except to start over and before you
do the dist-upgrade, be sure your sources.list is pointing
explicitly to sarge. Once you have the latest sarge, you can change
your sources.list and move to etch, if you want to. You could
of course just stay with sarge.
Richard

On Wed September 20 2006 10:40, Dylan Beaudette wrote:
> Hi everyone,
>
> just installed Debian Sarge from some old install media, and performed a
> dist-upgrade twice to get to the unstable distribution.
>
> however, i am not able to install a couple of new packages, namely kde:
>
> #apti   tude install kde
>
> [....]
>
> The following packages are BROKEN:
>   kcontrol kdepim-kfile-plugins kpilot
>
> [....]
>
> The following packages have unmet dependencies:
>   kdepim-kfile-plugins: Depends: libpisock8 but it is not installable
>   kcontrol: Depends: libraw1394-5 but it is not installable
>   kpilot: Depends: libpisock8 but it is not installable
> Resolving dependencies...
> The following actions will resolve these dependencies:
>
> Keep the following packages at their current version:
> blinken [Not Installed]
> kcontrol [Not Installed]
> kde [Not Installed]
> kde-amusements [Not Installed]
> kde-core [Not Installed]
> kdeaddons [Not Installed]
> kdeadmin [Not Installed]
> kdebase [Not Installed]
> kdeedu [Not Installed]
> kdepim [Not Installed]
> kdepim-kfile-plugins [Not Installed]
> konq-plugins [Not Installed]
> konqueror [Not Installed]
> kpilot [Not Installed]
> lilo-config [Not Installed]
>
>
> any ideas on how to fix this?
>
> also i noticed that this machine calls itself 'debian testing/unstable' --
> what exactly does this mean?
>
> thanks!