LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   Apt: The following packages have been kept back: linux-image-amd64 (https://www.linuxquestions.org/questions/debian-26/apt-the-following-packages-have-been-kept-back-linux-image-amd64-4175686018/)

platypo 11-30-2020 08:42 AM
Apt: The following packages have been kept back: linux-image-amd64
 
Hello!

For serveral months now i have had the message
Code:
The following packages have been kept back:
  linux-image-amd64
when running apt-get upgrade in debian buster.
Same goes for my intel machine:
Code:
The following packages have been kept back:
  linux-image-686-pae
I have found serveral workarounds wich i can't remember and never fully understood but after some updates the error allways came back.

I am currently a bit short on time to invest in this, so can someone explain to me in simple words what's happening here, wheter or not this might be unprofitable for the system and if so, how to persistently fix it for good?

TIA

shruggy 11-30-2020 08:49 AM
Code:
sudo apt full-upgrade
From the apt(8) manpage:
Quote:
upgrade (apt-get(8))
upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for a package requires the removal of an installed package the upgrade for this package isn't performed.
full-upgrade (apt-get(8))
full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole.

Brains 11-30-2020 09:37 PM
My guess...
You have repositories of more than one Debian/Debian derivative, some packages cannot be upgraded because of version dependency issues.

cynwulf 12-01-2020 11:47 AM
The answer is in post no. 2. Being "short on time", not being willing to set aside time to learn, means that you should consider paid support.

platypo 12-02-2020 11:15 AM
Quote:
Originally Posted by Brains (Post 6190467)
My guess...
You have repositories of more than one Debian/Debian derivative, some packages cannot be upgraded because of version dependency issues.
I remember now that the error correlates with the installation of brave browser. I completely lost track of this issue over the past few weeks, i'm sorry. I will try to pursue this as soon i have more time.
Quote:
Originally Posted by cynwulf (Post 6190661)
The answer is in post no. 2. Being "short on time", not being willing to set aside time to learn, means that you should consider paid support.
I guess i can't contradict this i was a bit quick to ask here. In my defense, i'm not permanently unwilling to work/learn but especially when it comes to updates/package distribution i know from experience that i am very happy to be able to consult interactive platforms like LQ in addition to available documentation.

shruggy 12-02-2020 11:32 AM
So? Did apt full-upgrade resolve it? Then mark the thread [SOLVED].

platypo 12-02-2020 11:38 AM
Quote:
Originally Posted by shruggy (Post 6191026)
So? Did apt full-upgrade resolve it? Then mark the thread [SOLVED].
I will try this as soon as i have some more time but i won't forget to mark this thread solved. Certainly thanks for the support so far.

cynwulf 12-02-2020 06:20 PM
Quote:
Originally Posted by platypo (Post 6191016)
I remember now that the error correlates with the installation of brave browser.
Though 3rd party repositories are often discouraged, and for good reason, this is unrelated.

platypo 12-12-2020 05:26 AM
After investigating a bit i got a little clairity over what i did. The error seems to have occured due to an attempt to install an application from sid via apt and then trying to switch back to upgrading from stable wich obviously didn't work out well. The reason i opened this thread is that the same issue appeared on my i686 machine where i haven't found any manipulations in the sources. I don't know exactly why the conflict appeared there but it's still possible that it's something similar. Thanks for your support i hope next time i won't have to ask for help anymore.

ondoho 12-12-2020 12:05 PM
Maybe I'm stating the obvious here, but:
https://wiki.debian.org/DontBreakDebian

sgosnell 12-12-2020 02:22 PM
It doesn't seem to be obvious to many people. Else we wouldn't have the number of people who come here with the same issue.


All times are GMT -5. The time now is 02:56 AM.