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

Re: Unable to complete package upgrade in jessie

On 04/27/2015 at 07:15 PM, Bill Baker wrote:

> On 04/27/2015 07:05 PM, The Wanderer wrote:
>> A few thoughts:
>> 1. Is there a reason why you need 'apt-get -f install packagename'?
>> Does it error out if you just run 'apt-get install packagename'?
> I used -f because the output suggested I use it.

The output was suggesting 'apt-get -f install' as a standalone complete
command, to let apt-get calculate a fix for the dependency situation on
its own. If you're trying to specify a solution in any way, I think it's
generally best to omit that option.

>> 2. What happens if you try to install linux-image-586 instead, or
>> even the specific-kernel-version package which it depends on
>> (linux-image-3.16.0-4-586)? linux-image-486 is just a dummy
>> package depending on the -586 package anyway. Even if it still
>> fails, you may get a more helpful error message.
> Here is the output from sudo apt-get install linux-image-586:
> Reading package lists... Done
> Building dependency tree      
> Reading state information... Done
> You might want to run 'apt-get -f install' to correct these:
> The following packages have unmet dependencies:
>  consolekit : Breaks: udev (< 204-1) but 175-7.2 is to be installed
>  linux-image-586 : Depends: linux-image-3.16.0-4-586 but it is not going
> to be installed
> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
> specify a solution).

So it doesn't help anything; the broken package dependencies are
overriding everything else.

In that case, I think I see two possible avenues forward (short of
reinstalling the entire system, or doing complex gymnastics with a
rescue environment):

1. Downgrade the packages which are leading to the broken-dependencies
situation, so that you can upgrade the kernel package manually. This may
be only consolekit, or it may extend to other packages as well. This
could be very complicated, but it might work.

2. Download the .deb for a sufficiently-new kernel version, install it
directly with dpkg rather than indirectly with apt-get, and proceed from

I would recommend starting with approach 2. You should be able to get
the needed .deb file from the 'security.debian.org' link here:


Download it locally, install it with 'dpkg -i
linux-image-3.16.0-4-586_3.16.7-ckt9-3~deb8u1_i386.deb', reboot into the
new kernel, and run 'apt-get -f install'. (Yes, the filename is
complicated.) That should get things moving again.

If it doesn't, or if you have any problems along the way, report back
and I'll see what else I can suggest.

   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: