[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Not sure I get this unmet dependency



On Sat, Dec 09, 2006 at 11:45:03 -0800, Bill Moseley wrote:
> Sometimes I get confused by what the package system is telling me.
> I'm not sure what's happening below.
> 
> On Sid trying to update Gaim:
> 
>     $ apt-cache policy gaim     
>     gaim:
>       Installed: 1:2.0.0+beta5-3
>       Candidate: 1:2.0.0+beta5-6
> 
> Ok, trying to upgrade:
> 
> 
>     $ sudo apt-get install gaim          
>     The following packages have unmet dependencies:
>       gaim: Depends: gaim-data (= 1:2.0.0+beta5-6) but 1:2.0.0+beta5-3 is to be installed
>     E: Broken packages
> 
> 
> Looks like I could update gaim-data:
> 
> 
>     $ apt-cache policy gaim-data
>     gaim:
>       Installed: 1:2.0.0+beta5-3
>       Candidate: 1:2.0.0+beta5-6
>       Version table:
>          1:2.0.0+beta5-6 0
>             500 http://http.us.debian.org unstable/main Packages
>      *** 1:2.0.0+beta5-3 0
>             100 /var/lib/dpkg/status
> 
> But if I try it wants to remove gaim.
> 
>     $ sudo apt-get install gaim-data
>     Reading package lists... Done
>     Building dependency tree... Done
>     The following packages will be REMOVED:
>       gaim
>     The following packages will be upgraded:
>       gaim-data
>     1 upgraded, 0 newly installed, 1 to remove and 160 not upgraded.
>     Need to get 5153kB of archives.
>     After unpacking 4620kB disk space will be freed.
>     Do you want to continue [Y/n]? n
>     Abort.

gaim is currently not installable for me since it is still at version
1:2.0.0+beta5-6 while gaim-data is already at 1:2.0.0+beta5-7. (I use
ftp.nl.debian.org.)

My guess is: You did not run "apt-get update" recently enough so your
database of available packages is outdated. Even though apt thinks that
gaim-data 1:2.0.0+beta5-6 is still on the mirror, it probably finds
1:2.0.0+beta5-7 when it tries to actually download the package. It
cannot do anything with that until the gaim package catches up (which
will probably happen tomorrow).

-- 
Regards,
          Florian



Reply to: