apt-get - autoremove wants to uninstall Gnome
As empathy 2.30 in Debian Wheezy didn't meet all my preferences I tried out empathy 3.1 from experimental, using the command:
apt-get -t experimental install empathy
I had to find out, this version of empathy doesn't work well in Gnome 2.x. Therefore I mentioned:
apt-get purge empathy
apt-get install empathy
Hoping, that this will reinstall the "standard" version of empathy again.
So far, everything worked well.
But now:
apt-get autoremove
wants to delete Gnome as a whole.
How can I calm down apt-get autoremove
?
debian apt
add a comment |
As empathy 2.30 in Debian Wheezy didn't meet all my preferences I tried out empathy 3.1 from experimental, using the command:
apt-get -t experimental install empathy
I had to find out, this version of empathy doesn't work well in Gnome 2.x. Therefore I mentioned:
apt-get purge empathy
apt-get install empathy
Hoping, that this will reinstall the "standard" version of empathy again.
So far, everything worked well.
But now:
apt-get autoremove
wants to delete Gnome as a whole.
How can I calm down apt-get autoremove
?
debian apt
add a comment |
As empathy 2.30 in Debian Wheezy didn't meet all my preferences I tried out empathy 3.1 from experimental, using the command:
apt-get -t experimental install empathy
I had to find out, this version of empathy doesn't work well in Gnome 2.x. Therefore I mentioned:
apt-get purge empathy
apt-get install empathy
Hoping, that this will reinstall the "standard" version of empathy again.
So far, everything worked well.
But now:
apt-get autoremove
wants to delete Gnome as a whole.
How can I calm down apt-get autoremove
?
debian apt
As empathy 2.30 in Debian Wheezy didn't meet all my preferences I tried out empathy 3.1 from experimental, using the command:
apt-get -t experimental install empathy
I had to find out, this version of empathy doesn't work well in Gnome 2.x. Therefore I mentioned:
apt-get purge empathy
apt-get install empathy
Hoping, that this will reinstall the "standard" version of empathy again.
So far, everything worked well.
But now:
apt-get autoremove
wants to delete Gnome as a whole.
How can I calm down apt-get autoremove
?
debian apt
debian apt
edited Jun 3 '11 at 12:30
Gilles
529k12810601586
529k12810601586
asked Jun 3 '11 at 8:20
Marcel
6071823
6071823
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
APT maintains an indicator for each package, telling it whether the package is manually installed (installed because the user/administrator wanted it) or automatically installed (installed only because it's a dependency of some other package). That's what apt-get autoremove
uses to determine what to remove: it removes packages that are marked as automatically installed, but that no currently installed package requires.
You need to mark the gnome
package, or whatever Gnome package corresponds to the bits you want to keep, as manually installed. It's easiest to do this in an interactive tool with access to the automatically-installed setting:
- On the command line, call
aptitude unmarkauto PACKAGENAME
to mark PACKAGENAME as manually installed, ormarkauto
to mark it as automatically installed. - In Aptitude, move to the line corresponding to a package, then press
m
to mark it as manually installed, orM
to mark it as automatically installed. - In Synaptic, move to the line corresponding to a package, then toggle “Automatically installed” in the “Package” menu.
Note that (at least as of squeeze, I haven't checked wheezy) gnome-desktop-environment
depends on all of the official Gnome components, including empathy. I suspect you had gnome-desktop-environment
installed, and removing the empathy
package had to remove it because of the dependency. If this is the case you should now reinstall gnome-desktop-environment
. (If you don't remember, you can find a history of what APT-based package managers did in /var/log/apt
.)
Instead of purging and installing empathy
, you could have just done apt-get -t wheezy empathy
to install the wheezy version.
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but thegnome-desktop-environment
package depends onempathy
, so you must have removed that, and probably want to reinstall it.
– Gilles
Jun 5 '11 at 10:23
add a comment |
You can apt-get install
some gnome package (which is already installed) to set it as manually selected (installed). This should introduce the needed dependencies such that autoremove does not want to remove the gnome packages anymore.
I am not using gnome, but probably there is some gnome-desktop package or something like that which pulls in all the main gnome stuff.
For example the output on my system for a non-gnome package:
# apt-get install libsource-highlight3
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsource-highlight3 is already the newest version.
libsource-highlight3 set to manually installed.
libsource-highlight3
was automatically installed as dependency of source-highlight
. After the remove of source-highlight
, apt-get autoremove
would not remove the libsource-highlight3
package, because it is set to manually installed now.
Thank you! I followed your suggestion and mentionedapt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.
– Marcel
Jun 3 '11 at 9:04
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to doapt-get install gnome
. @maxshekepzig was suggestingapt-get install
for some package you already have installed.
– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for agnome-desktop
package (in the meantime I think it's calledgnome-core
).
– Marcel
Jun 5 '11 at 8:19
add a comment |
Another solution would be to completelly switch off autoremove with these options (in /etc/apt/apt.conf orn in file in /etc/apt/apt.conf.d/ directory):
APT::Get::AutomaticRemove "0";
APT::Get::HideAutoRemove "1";
add a comment |
Just copy the list of packages apt is wanting to autoremove (use a text editor to remove trailing whitespace). Then sudo apt install <paste list of packages>
fixed this issue for me on numerous occasions. Its simply a difference of packages being manually installed (apt thinks you must need these as you installed them) vs. packages being automatically installed (apt installed these so it assumes it can do what it wants with them). By doing th above you tell apt that they are all mannually installed. FYI - I sometimes have to do this twice as it will continue to suggest further autoremoves.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f14310%2fapt-get-autoremove-wants-to-uninstall-gnome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
APT maintains an indicator for each package, telling it whether the package is manually installed (installed because the user/administrator wanted it) or automatically installed (installed only because it's a dependency of some other package). That's what apt-get autoremove
uses to determine what to remove: it removes packages that are marked as automatically installed, but that no currently installed package requires.
You need to mark the gnome
package, or whatever Gnome package corresponds to the bits you want to keep, as manually installed. It's easiest to do this in an interactive tool with access to the automatically-installed setting:
- On the command line, call
aptitude unmarkauto PACKAGENAME
to mark PACKAGENAME as manually installed, ormarkauto
to mark it as automatically installed. - In Aptitude, move to the line corresponding to a package, then press
m
to mark it as manually installed, orM
to mark it as automatically installed. - In Synaptic, move to the line corresponding to a package, then toggle “Automatically installed” in the “Package” menu.
Note that (at least as of squeeze, I haven't checked wheezy) gnome-desktop-environment
depends on all of the official Gnome components, including empathy. I suspect you had gnome-desktop-environment
installed, and removing the empathy
package had to remove it because of the dependency. If this is the case you should now reinstall gnome-desktop-environment
. (If you don't remember, you can find a history of what APT-based package managers did in /var/log/apt
.)
Instead of purging and installing empathy
, you could have just done apt-get -t wheezy empathy
to install the wheezy version.
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but thegnome-desktop-environment
package depends onempathy
, so you must have removed that, and probably want to reinstall it.
– Gilles
Jun 5 '11 at 10:23
add a comment |
APT maintains an indicator for each package, telling it whether the package is manually installed (installed because the user/administrator wanted it) or automatically installed (installed only because it's a dependency of some other package). That's what apt-get autoremove
uses to determine what to remove: it removes packages that are marked as automatically installed, but that no currently installed package requires.
You need to mark the gnome
package, or whatever Gnome package corresponds to the bits you want to keep, as manually installed. It's easiest to do this in an interactive tool with access to the automatically-installed setting:
- On the command line, call
aptitude unmarkauto PACKAGENAME
to mark PACKAGENAME as manually installed, ormarkauto
to mark it as automatically installed. - In Aptitude, move to the line corresponding to a package, then press
m
to mark it as manually installed, orM
to mark it as automatically installed. - In Synaptic, move to the line corresponding to a package, then toggle “Automatically installed” in the “Package” menu.
Note that (at least as of squeeze, I haven't checked wheezy) gnome-desktop-environment
depends on all of the official Gnome components, including empathy. I suspect you had gnome-desktop-environment
installed, and removing the empathy
package had to remove it because of the dependency. If this is the case you should now reinstall gnome-desktop-environment
. (If you don't remember, you can find a history of what APT-based package managers did in /var/log/apt
.)
Instead of purging and installing empathy
, you could have just done apt-get -t wheezy empathy
to install the wheezy version.
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but thegnome-desktop-environment
package depends onempathy
, so you must have removed that, and probably want to reinstall it.
– Gilles
Jun 5 '11 at 10:23
add a comment |
APT maintains an indicator for each package, telling it whether the package is manually installed (installed because the user/administrator wanted it) or automatically installed (installed only because it's a dependency of some other package). That's what apt-get autoremove
uses to determine what to remove: it removes packages that are marked as automatically installed, but that no currently installed package requires.
You need to mark the gnome
package, or whatever Gnome package corresponds to the bits you want to keep, as manually installed. It's easiest to do this in an interactive tool with access to the automatically-installed setting:
- On the command line, call
aptitude unmarkauto PACKAGENAME
to mark PACKAGENAME as manually installed, ormarkauto
to mark it as automatically installed. - In Aptitude, move to the line corresponding to a package, then press
m
to mark it as manually installed, orM
to mark it as automatically installed. - In Synaptic, move to the line corresponding to a package, then toggle “Automatically installed” in the “Package” menu.
Note that (at least as of squeeze, I haven't checked wheezy) gnome-desktop-environment
depends on all of the official Gnome components, including empathy. I suspect you had gnome-desktop-environment
installed, and removing the empathy
package had to remove it because of the dependency. If this is the case you should now reinstall gnome-desktop-environment
. (If you don't remember, you can find a history of what APT-based package managers did in /var/log/apt
.)
Instead of purging and installing empathy
, you could have just done apt-get -t wheezy empathy
to install the wheezy version.
APT maintains an indicator for each package, telling it whether the package is manually installed (installed because the user/administrator wanted it) or automatically installed (installed only because it's a dependency of some other package). That's what apt-get autoremove
uses to determine what to remove: it removes packages that are marked as automatically installed, but that no currently installed package requires.
You need to mark the gnome
package, or whatever Gnome package corresponds to the bits you want to keep, as manually installed. It's easiest to do this in an interactive tool with access to the automatically-installed setting:
- On the command line, call
aptitude unmarkauto PACKAGENAME
to mark PACKAGENAME as manually installed, ormarkauto
to mark it as automatically installed. - In Aptitude, move to the line corresponding to a package, then press
m
to mark it as manually installed, orM
to mark it as automatically installed. - In Synaptic, move to the line corresponding to a package, then toggle “Automatically installed” in the “Package” menu.
Note that (at least as of squeeze, I haven't checked wheezy) gnome-desktop-environment
depends on all of the official Gnome components, including empathy. I suspect you had gnome-desktop-environment
installed, and removing the empathy
package had to remove it because of the dependency. If this is the case you should now reinstall gnome-desktop-environment
. (If you don't remember, you can find a history of what APT-based package managers did in /var/log/apt
.)
Instead of purging and installing empathy
, you could have just done apt-get -t wheezy empathy
to install the wheezy version.
edited Jun 5 '11 at 10:22
answered Jun 3 '11 at 12:29
Gilles
529k12810601586
529k12810601586
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but thegnome-desktop-environment
package depends onempathy
, so you must have removed that, and probably want to reinstall it.
– Gilles
Jun 5 '11 at 10:23
add a comment |
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but thegnome-desktop-environment
package depends onempathy
, so you must have removed that, and probably want to reinstall it.
– Gilles
Jun 5 '11 at 10:23
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
cool! Using this "trick" one could remove Empathy without removing Gnome, right?
– Marcel
Jun 5 '11 at 8:20
@Marcel: You can remove Empathy without removing other Gnome components, but the
gnome-desktop-environment
package depends on empathy
, so you must have removed that, and probably want to reinstall it.– Gilles
Jun 5 '11 at 10:23
@Marcel: You can remove Empathy without removing other Gnome components, but the
gnome-desktop-environment
package depends on empathy
, so you must have removed that, and probably want to reinstall it.– Gilles
Jun 5 '11 at 10:23
add a comment |
You can apt-get install
some gnome package (which is already installed) to set it as manually selected (installed). This should introduce the needed dependencies such that autoremove does not want to remove the gnome packages anymore.
I am not using gnome, but probably there is some gnome-desktop package or something like that which pulls in all the main gnome stuff.
For example the output on my system for a non-gnome package:
# apt-get install libsource-highlight3
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsource-highlight3 is already the newest version.
libsource-highlight3 set to manually installed.
libsource-highlight3
was automatically installed as dependency of source-highlight
. After the remove of source-highlight
, apt-get autoremove
would not remove the libsource-highlight3
package, because it is set to manually installed now.
Thank you! I followed your suggestion and mentionedapt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.
– Marcel
Jun 3 '11 at 9:04
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to doapt-get install gnome
. @maxshekepzig was suggestingapt-get install
for some package you already have installed.
– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for agnome-desktop
package (in the meantime I think it's calledgnome-core
).
– Marcel
Jun 5 '11 at 8:19
add a comment |
You can apt-get install
some gnome package (which is already installed) to set it as manually selected (installed). This should introduce the needed dependencies such that autoremove does not want to remove the gnome packages anymore.
I am not using gnome, but probably there is some gnome-desktop package or something like that which pulls in all the main gnome stuff.
For example the output on my system for a non-gnome package:
# apt-get install libsource-highlight3
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsource-highlight3 is already the newest version.
libsource-highlight3 set to manually installed.
libsource-highlight3
was automatically installed as dependency of source-highlight
. After the remove of source-highlight
, apt-get autoremove
would not remove the libsource-highlight3
package, because it is set to manually installed now.
Thank you! I followed your suggestion and mentionedapt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.
– Marcel
Jun 3 '11 at 9:04
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to doapt-get install gnome
. @maxshekepzig was suggestingapt-get install
for some package you already have installed.
– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for agnome-desktop
package (in the meantime I think it's calledgnome-core
).
– Marcel
Jun 5 '11 at 8:19
add a comment |
You can apt-get install
some gnome package (which is already installed) to set it as manually selected (installed). This should introduce the needed dependencies such that autoremove does not want to remove the gnome packages anymore.
I am not using gnome, but probably there is some gnome-desktop package or something like that which pulls in all the main gnome stuff.
For example the output on my system for a non-gnome package:
# apt-get install libsource-highlight3
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsource-highlight3 is already the newest version.
libsource-highlight3 set to manually installed.
libsource-highlight3
was automatically installed as dependency of source-highlight
. After the remove of source-highlight
, apt-get autoremove
would not remove the libsource-highlight3
package, because it is set to manually installed now.
You can apt-get install
some gnome package (which is already installed) to set it as manually selected (installed). This should introduce the needed dependencies such that autoremove does not want to remove the gnome packages anymore.
I am not using gnome, but probably there is some gnome-desktop package or something like that which pulls in all the main gnome stuff.
For example the output on my system for a non-gnome package:
# apt-get install libsource-highlight3
Reading package lists... Done
Building dependency tree
Reading state information... Done
libsource-highlight3 is already the newest version.
libsource-highlight3 set to manually installed.
libsource-highlight3
was automatically installed as dependency of source-highlight
. After the remove of source-highlight
, apt-get autoremove
would not remove the libsource-highlight3
package, because it is set to manually installed now.
edited Jun 3 '11 at 9:03
answered Jun 3 '11 at 8:56
maxschlepzig
33.5k32135211
33.5k32135211
Thank you! I followed your suggestion and mentionedapt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.
– Marcel
Jun 3 '11 at 9:04
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to doapt-get install gnome
. @maxshekepzig was suggestingapt-get install
for some package you already have installed.
– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for agnome-desktop
package (in the meantime I think it's calledgnome-core
).
– Marcel
Jun 5 '11 at 8:19
add a comment |
Thank you! I followed your suggestion and mentionedapt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.
– Marcel
Jun 3 '11 at 9:04
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to doapt-get install gnome
. @maxshekepzig was suggestingapt-get install
for some package you already have installed.
– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for agnome-desktop
package (in the meantime I think it's calledgnome-core
).
– Marcel
Jun 5 '11 at 8:19
Thank you! I followed your suggestion and mentioned
apt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.– Marcel
Jun 3 '11 at 9:04
Thank you! I followed your suggestion and mentioned
apt-get install gnome
in the command line. Debian now wants to use 200MB additional diskspace, which I find kind of strange - however, I hope that works.– Marcel
Jun 3 '11 at 9:04
1
1
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel, this should be ok - probably the application package or packages (which pulled your current gnome packaged as dependencies (e.g. empathy) and were later removed) just don't need all of gnome - a main gnome package on the other hand wants to provide the whole gnome desktop, i.e. it depends on all gnome packages which are considered as the default gnome experience.
– maxschlepzig
Jun 3 '11 at 9:12
@Marcel: you don't need to do
apt-get install gnome
. @maxshekepzig was suggesting apt-get install
for some package you already have installed.– Faheem Mitha
Jun 3 '11 at 11:02
@Marcel: you don't need to do
apt-get install gnome
. @maxshekepzig was suggesting apt-get install
for some package you already have installed.– Faheem Mitha
Jun 3 '11 at 11:02
@Faheem you are right.
apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for a gnome-desktop
package (in the meantime I think it's called gnome-core
).– Marcel
Jun 5 '11 at 8:19
@Faheem you are right.
apt-get install gnome
would pull all those other packages. Therefore I didn't need to search for a gnome-desktop
package (in the meantime I think it's called gnome-core
).– Marcel
Jun 5 '11 at 8:19
add a comment |
Another solution would be to completelly switch off autoremove with these options (in /etc/apt/apt.conf orn in file in /etc/apt/apt.conf.d/ directory):
APT::Get::AutomaticRemove "0";
APT::Get::HideAutoRemove "1";
add a comment |
Another solution would be to completelly switch off autoremove with these options (in /etc/apt/apt.conf orn in file in /etc/apt/apt.conf.d/ directory):
APT::Get::AutomaticRemove "0";
APT::Get::HideAutoRemove "1";
add a comment |
Another solution would be to completelly switch off autoremove with these options (in /etc/apt/apt.conf orn in file in /etc/apt/apt.conf.d/ directory):
APT::Get::AutomaticRemove "0";
APT::Get::HideAutoRemove "1";
Another solution would be to completelly switch off autoremove with these options (in /etc/apt/apt.conf orn in file in /etc/apt/apt.conf.d/ directory):
APT::Get::AutomaticRemove "0";
APT::Get::HideAutoRemove "1";
answered Dec 11 '12 at 22:30
pevik
598414
598414
add a comment |
add a comment |
Just copy the list of packages apt is wanting to autoremove (use a text editor to remove trailing whitespace). Then sudo apt install <paste list of packages>
fixed this issue for me on numerous occasions. Its simply a difference of packages being manually installed (apt thinks you must need these as you installed them) vs. packages being automatically installed (apt installed these so it assumes it can do what it wants with them). By doing th above you tell apt that they are all mannually installed. FYI - I sometimes have to do this twice as it will continue to suggest further autoremoves.
add a comment |
Just copy the list of packages apt is wanting to autoremove (use a text editor to remove trailing whitespace). Then sudo apt install <paste list of packages>
fixed this issue for me on numerous occasions. Its simply a difference of packages being manually installed (apt thinks you must need these as you installed them) vs. packages being automatically installed (apt installed these so it assumes it can do what it wants with them). By doing th above you tell apt that they are all mannually installed. FYI - I sometimes have to do this twice as it will continue to suggest further autoremoves.
add a comment |
Just copy the list of packages apt is wanting to autoremove (use a text editor to remove trailing whitespace). Then sudo apt install <paste list of packages>
fixed this issue for me on numerous occasions. Its simply a difference of packages being manually installed (apt thinks you must need these as you installed them) vs. packages being automatically installed (apt installed these so it assumes it can do what it wants with them). By doing th above you tell apt that they are all mannually installed. FYI - I sometimes have to do this twice as it will continue to suggest further autoremoves.
Just copy the list of packages apt is wanting to autoremove (use a text editor to remove trailing whitespace). Then sudo apt install <paste list of packages>
fixed this issue for me on numerous occasions. Its simply a difference of packages being manually installed (apt thinks you must need these as you installed them) vs. packages being automatically installed (apt installed these so it assumes it can do what it wants with them). By doing th above you tell apt that they are all mannually installed. FYI - I sometimes have to do this twice as it will continue to suggest further autoremoves.
answered Dec 25 '18 at 2:54
Jamie Lindsey
765
765
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f14310%2fapt-get-autoremove-wants-to-uninstall-gnome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown