findmyvef.blogg.se

Sudo apt autoremove invalid operation
Sudo apt autoremove invalid operation









  1. #Sudo apt autoremove invalid operation install#
  2. #Sudo apt autoremove invalid operation 32 bit#
  3. #Sudo apt autoremove invalid operation upgrade#

#Sudo apt autoremove invalid operation 32 bit#

now those held packages have been installed and the cost was the elimination of unneeded ancillary 32 bit packages.

#Sudo apt autoremove invalid operation upgrade#

Since by doing some research I am OK doing this upgrade I say Y to above prompt. Libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386 libxxf86vm1:i386 zlib1g:i386Ģ upgraded, 0 newly installed, 47 to remove and 0 not upgraded.Īfter this operation, 525 MB disk space will be freed. The following package was automatically installed and is no longer required:

#Sudo apt autoremove invalid operation install#

However I am OK with going ahead and doing updates on those held packages so I run sudo apt-get install libc6 libc6-dbg The following packages have been kept back:Ġ upgraded, 0 newly installed, 0 to remove and 2 not upgraded. for example sudo apt-get -with-new-pkgs upgrade typically this will happen when the system knows by performing this install it will have to uninstall other packages. If you are certain you want this change to happen you can just sudo apt-get install xxxxx Because A only recommends B, you can manually remove B to get back to the initial situation.The message indicates a potentially unsafe condition When you remove pipelight-multi and run apt-get autoremove, B is marked as auto-removable and gets checked, but because A is still installed, B is kept, even though the package which caused it to be installed in the first place is gone. You install pipelight-multi which also recommends B given that you explicitly specified -install-recommends, we know B is then installed along with pipelight-multi. 2 Answers Sorted by: 15 This sudo apt-get cpufrequtils is missing a mandatory option. You already have some other package, A, installed this package recommends B but the latter isn't installed. I did so and then I realized that it also removed some of my desktop applications and the look of my desktop environment completely changed. Such packages are kept only as long as some other package depends on them, or recommends them (this is the default setting, it can be changed).Īll this would explain your situation as follows. After one of these install/remove commands, apt-get suggested to run apt-get autoremove command. When a package is flagged as auto-removable, either manually or automatically (in the latter case, because it's installed automatically to satisfy a dependency or recommendation), the auto-removal flag is the only information stored the system doesn't remember why a package was automatically installed. The mechanics behind this aren't necessarily intuitive. Since you've removed the packages manually it's hard to determine, but in future you can run aptitude why $ for each package you think should be auto-removed, and aptitude will tell you why it's being kept.

sudo apt autoremove invalid operation sudo apt autoremove invalid operation

My best guess is that the 40 packages were recommended by other packages you had already installed pipelight-multi along with the -install-recommends option caused them to be installed, but they were kept after its removal because of those recommendations. So after I removed Pipelight, why weren't all of its unneeded dependencies marked as auto-removable? Only about ten minutes passed between installing Pipelight and removing it. There were no unmet dependencies on my system before I installed Pipelight and I hadn't marked any packages as manually-installed, installed or removed anything else, or anything like that. So this left about 40 packages that weren't considered auto-removeable, and so weren't removed. There were exactly 100 of these (there were also exactly 100 packages in Synaptic Package Manager's 'Autoremovable' list). This command removed all auto-removeable packages.

sudo apt autoremove invalid operation

Pipelight subsequently didn't work, so I removed it: sudo apt-get purge pipelight-multi Therefore, about 140 new packages were installed. The installation command, sudo apt-get install -install-recommends pipelight-multi was for only one package, but it entailed downloading and installing about 180 dependency packages, about 40 of which were upgrades to currently-installed packages. I installed Pipelight from the PPA archive, according to these instructions.











Sudo apt autoremove invalid operation