Lis code of va
#Lis code of va update
sudo apt update & sudo apt upgrade -y & sudo apt autoremove My issue was trying to chain the update command together like this. I just ran into the same issue with Ubuntu Mate and I found this thread. Then run sudo apt update to refresh the list of available software. The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. A standard Ubuntu sources.list file looks like the sources.list files in this answer. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error.
#Lis code of va software
The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. Run the following command: sudo dpkg -remove -force-remove-reinstreq Sudo mv /var/lib/dpkg/info/.* /tmp/new-package-location/ cd /tmp & sudo mkdir new-package-location Move the package folder to another location.
Run the following commands: sudo apt updateįind your package in /var/lib/dpkg/info ls -l /var/lib/dpkg/info | grep If you get this error message: Try 'apt-get -f install' with no packages (or specify a solution) Usually this means fixing a broken package by downgrading that package to an older version. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. Select a broken package, and then open the terminal and run apt policy. Select the broken packages one at a time. In the center pane will be listed any broken packages that still need to be repaired. From the list in the top left corner select Broken. In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
#Lis code of va install
Run the following commands to install Synaptic. Select the Fix Broken Packages option in Synaptic package manager. If you find any incorrect release lines in sources.list, open the sources.list file with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages. Open your sources.list file in /etc/apt/sources.list and check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. These are some fast and easy ways to fix the you have held broken packages error. I haven't taken the time to investigate how it would help in the above scenario, but it's worth using. It is still not the Swiss army knife that aptitude is, but it's a bit more human-oriented than apt-get. Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead: sudo aptitude -f install Įdit: this is an old answer, and since it was written a newer APT front end, simply titled apt, has become the preferred command line APT interface for end-users. It may give you more explanation of the problem and options for fixing it.
#Lis code of va full
Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.Īnother method of troubleshooting may be to use aptitude rather than apt-get to try to install your package: sudo aptitude install Īptitude will give up less easily and will attempt to find solutions that may involve modifying other packages.
If there are none, or none look related, then it's probably something else.
You can get a list of actual held packages with: dpkg -get-selections | grep hold That particular error message may indicate that you have held packages, but it may also indicate a different problem.