update available or not?
D. R. Evans
doc.evans at gmail.com
Fri Dec 8 15:56:38 GMT 2006
On 05/12/06, Tez <binary_y2k2 at blueyonder.co.uk> wrote:
> D. R. Evans wrote:
> > More update weirdness... (Why is it that update issues seem to consume
> > so much reflector bandwidth? Or is it just me imagining it?)
> > So...
> > 0. Using dapper.
> > 1. I am running amarok 1.4.3.
> > 2. Adept Notifier tells me that there are three updates available [is
> > there some way to discover from which apt source it thinks they are
> > available??]
> > 3. The three packages to be updated are all amarok related
> > 4. For example, current amarok package is: 18.104.22.168-0ubuntu8~dapper1
> > and the candidate updtae package is: 22.214.171.124-0kubuntu2
> > 5. Open synaptic to perform the update
> > 6. Execute "Mark all upgrades"
> > 7.The status bar of synaptic says: 18509 packages listed, 1416
> > installed, 0 broken, 0 to install/upgrade. 0 to remove
> > 8. If I select "amarok" and check its properties, synaptic says that
> > it's installed and upgradeable.
> > What's going on? Can anyone please explain in plain English?
> Ff you run the command:
> apt-cache policy [package]
> (no need for sudo) it will tell you the current installed version, the
> latest version available and what versions are available from which source.
[H:~] apt-cache policy amarok
500 http://archive.czessi.net dapper/main Packages
*** 2:1.4.3-0ubuntu8~dapper1 0
500 http://us.archive.ubuntu.com dapper-backports/main Packages
500 http://us.archive.ubuntu.com dapper/main Packages
500 http://archive.ubuntu.com dapper/main Packages
> You can also try doing the update from the command line to see if there
> are actually any updates:
> sudo apt-get upgrade
[H:~] sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
The following packages have been kept back:
amarok amarok-engines amarok-xine
So on the one hand it seems to be telling me that updates are
available, but when I try to install them, it refuses to do so
(without telling me why).
So I am afraid that I'm no closer to understanding what's going on
than I was when the GUI tools behaved essentially the same way :-(
(although I do at least know now where the packages are that are
causing the trouble -- but I still don't know why apt won't install
More information about the kubuntu-users