How do I get back the packages I removed?












1














Someone asked me, on an issue I'd reported on Github, to remove a couple of packages and test it without them. I'm sure the implicit request was for me to do it safely!



Anyway, I removed the packages (in this case, libicu52 and libssl1.0.0), planning to get them back afterwards. It turns out both of these packages were dependencies of, respectively, libpsl0 and spotify-client, which were also removed. As you might expect, reinstalling each did not go as planned:



$ sudo apt install libicu52
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu52 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu52' has no installation candidate


Same is true for libssl1.0.0 and the depending packagelibpsl0.



If I try to install the depending package spotify-client, I am seeing the following:



$ sudo apt install spotify-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
spotify-client : Depends: libssl1.0.0 but it is not installable
Recommends: libavcodec54 but it is not installable or
libavcodec-extra-54 but it is not installable
Recommends: libavformat54 but it is not installable
E: Unable to correct problems, you have held broken packages.


You can see the results from the end of my dpkg.log:



2017-12-05 23:30:49 startup packages remove
2017-12-05 23:30:49 status installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 remove libpsl0:amd64 0.5.1-1 <none>
2017-12-05 23:30:49 status half-configured libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status half-installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 remove libicu52:amd64 52.1-8+deb8u5 <none>
2017-12-05 23:30:49 status half-configured libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status half-installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 startup packages configure
2017-12-05 23:31:01 startup packages remove
2017-12-05 23:31:01 status installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 remove spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26 <none>
2017-12-05 23:31:01 status half-configured spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status half-installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status not-installed spotify-client:amd64 <none>
2017-12-05 23:31:01 status installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 remove libssl1.0.0:amd64 1.0.1t-1+deb8u7 <none>
2017-12-05 23:31:01 status half-configured libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status half-installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:02 startup packages configure


Should I be worried? Should I try to get my packages back? How should I go about that?










share|improve this question
























  • Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
    – Patrick Mevzek
    Dec 6 '17 at 17:22










  • @PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
    – Brandon Arnold
    Dec 6 '17 at 17:35










  • Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
    – Patrick Mevzek
    Dec 6 '17 at 17:38












  • @PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
    – Brandon Arnold
    Dec 6 '17 at 17:48










  • Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
    – Arrow
    Dec 6 '17 at 17:52


















1














Someone asked me, on an issue I'd reported on Github, to remove a couple of packages and test it without them. I'm sure the implicit request was for me to do it safely!



Anyway, I removed the packages (in this case, libicu52 and libssl1.0.0), planning to get them back afterwards. It turns out both of these packages were dependencies of, respectively, libpsl0 and spotify-client, which were also removed. As you might expect, reinstalling each did not go as planned:



$ sudo apt install libicu52
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu52 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu52' has no installation candidate


Same is true for libssl1.0.0 and the depending packagelibpsl0.



If I try to install the depending package spotify-client, I am seeing the following:



$ sudo apt install spotify-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
spotify-client : Depends: libssl1.0.0 but it is not installable
Recommends: libavcodec54 but it is not installable or
libavcodec-extra-54 but it is not installable
Recommends: libavformat54 but it is not installable
E: Unable to correct problems, you have held broken packages.


You can see the results from the end of my dpkg.log:



2017-12-05 23:30:49 startup packages remove
2017-12-05 23:30:49 status installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 remove libpsl0:amd64 0.5.1-1 <none>
2017-12-05 23:30:49 status half-configured libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status half-installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 remove libicu52:amd64 52.1-8+deb8u5 <none>
2017-12-05 23:30:49 status half-configured libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status half-installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 startup packages configure
2017-12-05 23:31:01 startup packages remove
2017-12-05 23:31:01 status installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 remove spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26 <none>
2017-12-05 23:31:01 status half-configured spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status half-installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status not-installed spotify-client:amd64 <none>
2017-12-05 23:31:01 status installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 remove libssl1.0.0:amd64 1.0.1t-1+deb8u7 <none>
2017-12-05 23:31:01 status half-configured libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status half-installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:02 startup packages configure


Should I be worried? Should I try to get my packages back? How should I go about that?










share|improve this question
























  • Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
    – Patrick Mevzek
    Dec 6 '17 at 17:22










  • @PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
    – Brandon Arnold
    Dec 6 '17 at 17:35










  • Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
    – Patrick Mevzek
    Dec 6 '17 at 17:38












  • @PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
    – Brandon Arnold
    Dec 6 '17 at 17:48










  • Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
    – Arrow
    Dec 6 '17 at 17:52
















1












1








1







Someone asked me, on an issue I'd reported on Github, to remove a couple of packages and test it without them. I'm sure the implicit request was for me to do it safely!



Anyway, I removed the packages (in this case, libicu52 and libssl1.0.0), planning to get them back afterwards. It turns out both of these packages were dependencies of, respectively, libpsl0 and spotify-client, which were also removed. As you might expect, reinstalling each did not go as planned:



$ sudo apt install libicu52
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu52 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu52' has no installation candidate


Same is true for libssl1.0.0 and the depending packagelibpsl0.



If I try to install the depending package spotify-client, I am seeing the following:



$ sudo apt install spotify-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
spotify-client : Depends: libssl1.0.0 but it is not installable
Recommends: libavcodec54 but it is not installable or
libavcodec-extra-54 but it is not installable
Recommends: libavformat54 but it is not installable
E: Unable to correct problems, you have held broken packages.


You can see the results from the end of my dpkg.log:



2017-12-05 23:30:49 startup packages remove
2017-12-05 23:30:49 status installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 remove libpsl0:amd64 0.5.1-1 <none>
2017-12-05 23:30:49 status half-configured libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status half-installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 remove libicu52:amd64 52.1-8+deb8u5 <none>
2017-12-05 23:30:49 status half-configured libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status half-installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 startup packages configure
2017-12-05 23:31:01 startup packages remove
2017-12-05 23:31:01 status installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 remove spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26 <none>
2017-12-05 23:31:01 status half-configured spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status half-installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status not-installed spotify-client:amd64 <none>
2017-12-05 23:31:01 status installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 remove libssl1.0.0:amd64 1.0.1t-1+deb8u7 <none>
2017-12-05 23:31:01 status half-configured libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status half-installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:02 startup packages configure


Should I be worried? Should I try to get my packages back? How should I go about that?










share|improve this question















Someone asked me, on an issue I'd reported on Github, to remove a couple of packages and test it without them. I'm sure the implicit request was for me to do it safely!



Anyway, I removed the packages (in this case, libicu52 and libssl1.0.0), planning to get them back afterwards. It turns out both of these packages were dependencies of, respectively, libpsl0 and spotify-client, which were also removed. As you might expect, reinstalling each did not go as planned:



$ sudo apt install libicu52
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libicu52 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libicu52' has no installation candidate


Same is true for libssl1.0.0 and the depending packagelibpsl0.



If I try to install the depending package spotify-client, I am seeing the following:



$ sudo apt install spotify-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
spotify-client : Depends: libssl1.0.0 but it is not installable
Recommends: libavcodec54 but it is not installable or
libavcodec-extra-54 but it is not installable
Recommends: libavformat54 but it is not installable
E: Unable to correct problems, you have held broken packages.


You can see the results from the end of my dpkg.log:



2017-12-05 23:30:49 startup packages remove
2017-12-05 23:30:49 status installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 remove libpsl0:amd64 0.5.1-1 <none>
2017-12-05 23:30:49 status half-configured libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status half-installed libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status config-files libpsl0:amd64 0.5.1-1
2017-12-05 23:30:49 status installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 remove libicu52:amd64 52.1-8+deb8u5 <none>
2017-12-05 23:30:49 status half-configured libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status half-installed libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 status config-files libicu52:amd64 52.1-8+deb8u5
2017-12-05 23:30:49 startup packages configure
2017-12-05 23:31:01 startup packages remove
2017-12-05 23:31:01 status installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 remove spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26 <none>
2017-12-05 23:31:01 status half-configured spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status half-installed spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status config-files spotify-client:amd64 1:1.0.64.407.g9bd02c2d-26
2017-12-05 23:31:01 status not-installed spotify-client:amd64 <none>
2017-12-05 23:31:01 status installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 remove libssl1.0.0:amd64 1.0.1t-1+deb8u7 <none>
2017-12-05 23:31:01 status half-configured libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status half-installed libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:01 status config-files libssl1.0.0:amd64 1.0.1t-1+deb8u7
2017-12-05 23:31:02 startup packages configure


Should I be worried? Should I try to get my packages back? How should I go about that?







debian apt dpkg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 51 mins ago









Rui F Ribeiro

39.2k1479130




39.2k1479130










asked Dec 6 '17 at 17:17









Brandon Arnold

1307




1307












  • Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
    – Patrick Mevzek
    Dec 6 '17 at 17:22










  • @PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
    – Brandon Arnold
    Dec 6 '17 at 17:35










  • Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
    – Patrick Mevzek
    Dec 6 '17 at 17:38












  • @PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
    – Brandon Arnold
    Dec 6 '17 at 17:48










  • Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
    – Arrow
    Dec 6 '17 at 17:52




















  • Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
    – Patrick Mevzek
    Dec 6 '17 at 17:22










  • @PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
    – Brandon Arnold
    Dec 6 '17 at 17:35










  • Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
    – Patrick Mevzek
    Dec 6 '17 at 17:38












  • @PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
    – Brandon Arnold
    Dec 6 '17 at 17:48










  • Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
    – Arrow
    Dec 6 '17 at 17:52


















Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
– Patrick Mevzek
Dec 6 '17 at 17:22




Versions may have changed (and they are kind of hardcoded in the package name). Do a apt-cache search libicu and apt-cache search libssl to find the current ones and try installing these.
– Patrick Mevzek
Dec 6 '17 at 17:22












@PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
– Brandon Arnold
Dec 6 '17 at 17:35




@PatrickMevzek I've done it, and I've also verified that these are installed via apt list | grep libicu and apt list | grep libssl. Should I remove and reinstall these packages?
– Brandon Arnold
Dec 6 '17 at 17:35












Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
– Patrick Mevzek
Dec 6 '17 at 17:38






Try just reinstalling spotify-client and libpsl0, they should then automatically bring the dependencies they need.
– Patrick Mevzek
Dec 6 '17 at 17:38














@PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
– Brandon Arnold
Dec 6 '17 at 17:48




@PatrickMevzek There are problems. libpsl0 is the same (no installation candidate) and as for spotify-client, please see my update to my answer.
– Brandon Arnold
Dec 6 '17 at 17:48












Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
– Arrow
Dec 6 '17 at 17:52






Have you seen the message: you have held broken packages. Do an apt-get --fix-broken install before trying anything else.
– Arrow
Dec 6 '17 at 17:52












0






active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f409260%2fhow-do-i-get-back-the-packages-i-removed%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f409260%2fhow-do-i-get-back-the-packages-i-removed%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

宮崎県

濃尾地震

シテ島