package to install depends on old kernels that were removed
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I removed old kernels (with dpkg -P), and now many packages that
I try to install complain that the miss the old (removed) kernels
as dependencies
If I do a "apt-get install -f" as suggested, my old kernels get
reinstalled....
sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
synaptic is already the newest version (0.83).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-extra-4.10.0-28-generic : Depends: linux-image-4.10.0-28-generic but it is not going to be installed
linux-image-extra-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic but it is not going to be installed
linux-image-extra-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic but it is not going to be installed
linux-signed-image-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic (= 4.10.0-35.39~16.04.1) but it is not going to be installed
linux-signed-image-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic (= 4.10.0-37.41~16.04.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
apt package-management kernel dpkg dependencies
asked Mar 22 at 14:27
Max L.
1253
add a comment |Â
up vote
0
down vote
favorite
I removed old kernels (with dpkg -P), and now many packages that
I try to install complain that the miss the old (removed) kernels
as dependencies
If I do a "apt-get install -f" as suggested, my old kernels get
reinstalled....
sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
synaptic is already the newest version (0.83).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-extra-4.10.0-28-generic : Depends: linux-image-4.10.0-28-generic but it is not going to be installed
linux-image-extra-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic but it is not going to be installed
linux-image-extra-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic but it is not going to be installed
linux-signed-image-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic (= 4.10.0-35.39~16.04.1) but it is not going to be installed
linux-signed-image-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic (= 4.10.0-37.41~16.04.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
apt package-management kernel dpkg dependencies
asked Mar 22 at 14:27
Max L.
1253
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest usingsudo apt install -fto reinstall the missing kernels, and then runningsudo apt autoremove
– Charles Green
Mar 22 at 14:31
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I removed old kernels (with dpkg -P), and now many packages that
I try to install complain that the miss the old (removed) kernels
as dependencies
If I do a "apt-get install -f" as suggested, my old kernels get
reinstalled....
sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
synaptic is already the newest version (0.83).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-extra-4.10.0-28-generic : Depends: linux-image-4.10.0-28-generic but it is not going to be installed
linux-image-extra-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic but it is not going to be installed
linux-image-extra-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic but it is not going to be installed
linux-signed-image-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic (= 4.10.0-35.39~16.04.1) but it is not going to be installed
linux-signed-image-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic (= 4.10.0-37.41~16.04.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
apt package-management kernel dpkg dependencies
asked Mar 22 at 14:27
Max L.
1253
I removed old kernels (with dpkg -P), and now many packages that
I try to install complain that the miss the old (removed) kernels
as dependencies
If I do a "apt-get install -f" as suggested, my old kernels get
reinstalled....
sudo apt-get install synaptic
Reading package lists... Done
Building dependency tree
Reading state information... Done
synaptic is already the newest version (0.83).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-extra-4.10.0-28-generic : Depends: linux-image-4.10.0-28-generic but it is not going to be installed
linux-image-extra-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic but it is not going to be installed
linux-image-extra-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic but it is not going to be installed
linux-signed-image-4.10.0-35-generic : Depends: linux-image-4.10.0-35-generic (= 4.10.0-35.39~16.04.1) but it is not going to be installed
linux-signed-image-4.10.0-37-generic : Depends: linux-image-4.10.0-37-generic (= 4.10.0-37.41~16.04.1) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
apt package-management kernel dpkg dependencies
apt package-management kernel dpkg dependencies
asked Mar 22 at 14:27
Max L.
1253
asked Mar 22 at 14:27
Max L.
1253
asked Mar 22 at 14:27
Max L.
1253
asked Mar 22 at 14:27
Max L.
1253
asked Mar 22 at 14:27
Max L.
1253
1253
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest usingsudo apt install -fto reinstall the missing kernels, and then runningsudo apt autoremove
– Charles Green
Mar 22 at 14:31
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49
add a comment |Â
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest usingsudo apt install -fto reinstall the missing kernels, and then runningsudo apt autoremove
– Charles Green
Mar 22 at 14:31
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest using
sudo apt install -f to reinstall the missing kernels, and then running sudo apt autoremove– Charles Green
Mar 22 at 14:31
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest using
sudo apt install -f to reinstall the missing kernels, and then running sudo apt autoremove– Charles Green
Mar 22 at 14:31
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
If package A (here, linux-image-extra-*** and linux-signed-image-***) depends on package B (here, linux-image-***), it is a problem if package A is installed while package B is not. There are two ways to solve this problem: install package B, or remove package A.
apt-get install -f tries to do the former, but here, it is clear that what you want to do is remove the unwanted packages, so just do it™:
sudo apt remove linux-image-extra-4.10.0-28-generic linux-image-extra-4.10.0-35-generic linux-image-extra-4.10.0-37-generic linux-signed-image-4.10.0-35-generic linux-signed-image-4.10.0-37-generic
Yes, all in one command, not separately. And in the future, please always remove package with Apt, not dpkg.
answered Mar 22 at 15:55
fkraiem
8,46121727
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
If package A (here, linux-image-extra-*** and linux-signed-image-***) depends on package B (here, linux-image-***), it is a problem if package A is installed while package B is not. There are two ways to solve this problem: install package B, or remove package A.
apt-get install -f tries to do the former, but here, it is clear that what you want to do is remove the unwanted packages, so just do it™:
sudo apt remove linux-image-extra-4.10.0-28-generic linux-image-extra-4.10.0-35-generic linux-image-extra-4.10.0-37-generic linux-signed-image-4.10.0-35-generic linux-signed-image-4.10.0-37-generic
Yes, all in one command, not separately. And in the future, please always remove package with Apt, not dpkg.
answered Mar 22 at 15:55
fkraiem
8,46121727
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
add a comment |Â
up vote
3
down vote
accepted
If package A (here, linux-image-extra-*** and linux-signed-image-***) depends on package B (here, linux-image-***), it is a problem if package A is installed while package B is not. There are two ways to solve this problem: install package B, or remove package A.
apt-get install -f tries to do the former, but here, it is clear that what you want to do is remove the unwanted packages, so just do it™:
sudo apt remove linux-image-extra-4.10.0-28-generic linux-image-extra-4.10.0-35-generic linux-image-extra-4.10.0-37-generic linux-signed-image-4.10.0-35-generic linux-signed-image-4.10.0-37-generic
Yes, all in one command, not separately. And in the future, please always remove package with Apt, not dpkg.
answered Mar 22 at 15:55
fkraiem
8,46121727
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
If package A (here, linux-image-extra-*** and linux-signed-image-***) depends on package B (here, linux-image-***), it is a problem if package A is installed while package B is not. There are two ways to solve this problem: install package B, or remove package A.
apt-get install -f tries to do the former, but here, it is clear that what you want to do is remove the unwanted packages, so just do it™:
sudo apt remove linux-image-extra-4.10.0-28-generic linux-image-extra-4.10.0-35-generic linux-image-extra-4.10.0-37-generic linux-signed-image-4.10.0-35-generic linux-signed-image-4.10.0-37-generic
Yes, all in one command, not separately. And in the future, please always remove package with Apt, not dpkg.
answered Mar 22 at 15:55
fkraiem
8,46121727
If package A (here, linux-image-extra-*** and linux-signed-image-***) depends on package B (here, linux-image-***), it is a problem if package A is installed while package B is not. There are two ways to solve this problem: install package B, or remove package A.
apt-get install -f tries to do the former, but here, it is clear that what you want to do is remove the unwanted packages, so just do it™:
sudo apt remove linux-image-extra-4.10.0-28-generic linux-image-extra-4.10.0-35-generic linux-image-extra-4.10.0-37-generic linux-signed-image-4.10.0-35-generic linux-signed-image-4.10.0-37-generic
Yes, all in one command, not separately. And in the future, please always remove package with Apt, not dpkg.
answered Mar 22 at 15:55
fkraiem
8,46121727
answered Mar 22 at 15:55
fkraiem
8,46121727
answered Mar 22 at 15:55
fkraiem
8,46121727
answered Mar 22 at 15:55
fkraiem
8,46121727
8,46121727
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
add a comment |Â
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
@fkraim that worked ! Wish there was a command to remove all unmet dependencies !
– Max L.
Mar 23 at 21:02
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1018272%2fpackage-to-install-depends-on-old-kernels-that-were-removed%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Your chosen method of removing the older kernels may not be the best method of removing these. You are, apparently, removing the primary bit of the kernel, but not removing the additional kernel packages - I would suggest using
sudo apt install -fto reinstall the missing kernels, and then runningsudo apt autoremove– Charles Green
Mar 22 at 14:31
There are two excellent kernel cleanup scripts available. here and here.
– Doug Smythies
Mar 22 at 15:12
@CharlesGreen, I cannot install the old kernels because my /boot becomes full, that puts me in a catch 22 situation !
– Max L.
Mar 22 at 15:24
Ah! - that sheds new light on the situation. As mentioned by Doug Smythies, there are a couple of very good scripts for removing old kernels. You might also review https://askubuntu.com/questions/2793/how-do-i-remove-old-kernel-versions-to-clean-up-the-boot-menu and also https://askubuntu.com/questions/89710/how-do-i-free-up-more-space-in-boot
– Charles Green
Mar 22 at 15:31
I've tried various methods of removing old kernel, then when I want to add other packages, they complain about dependencies to these old (and removed) kernels
– Max L.
Mar 22 at 15:49