On Sat, 17 Oct 2020 22:49:09 -0700 "Mike C." <[email protected]> dijo:
>Looking through the command output it doesn't look like you ever ran >the "sudo apt-ge autoremove" command? > >The general first steps advice when dealing w. a bad package state is >to run the auto-remove command and then attempt to fix any missing >and/or broken pkgs w. the "sudo apt-get install -f " command > >If you still run into problems, then you can try the below command. >Reference - https://linuxhint.com/apt_get_fix_missing_broken_packages/ > >sudo dpkg --remove -force --force-remove-reinstreq Package_Name I finally found how to remove the original package: sudo apt purge oscar And the instructions followed with your 'dpkg --remove -force <etc>' command in case the apt purge command failed. I never figured out why apt-get remove didn't do the job or why the 1.0.1 package was stuck in Synaptic. And once I got 1.0.1 removed I was able to install the .deb file for 1.2.0, and that is all that is now listed in Synaptic. Problem solved. But I still have something wonky with my sources list. If I do sudo apt-get update the command ends with about 20 lines of error messages, all of which look like: W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list:37 Each line refers to list:4 and to list:37. I take it that '4' and '37' are the line numbers in /etc/apt/sources.list, but when I looked at the file it looked perfectly normal and without any duplications. Everything is working fine. I just like to keep things neat and tidy if I can, so I want to figure out what is generating these error messages. _______________________________________________ PLUG: https://pdxlinux.org PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
