|
On 11/08/2019 9:05, Shlomo Solomon
wrote:
I'll do my best to defend.Let me start by saying that I'm not looking for a solution - I solved my problem. I'm just angry and letting off some steam. binations of commands such as:sudo apt-get --fix-broken install sudo apt autoremove sudo dpkg -P mono-complete sudo dpkg --remove --force-remove-reinstreq mono-complete sudo apt-get clean sudo apt-get autoclean sudo apt-get -u dist-upgrade sudo apt-get -o Dpkg::Options::="--force-overwrite" upgrade sudo apt-get -o Dpkg::Options::="--force-overwrite" -f install sudo dpkg -P --force-all mono-complete sudo dpkg --configure -a Or just use aptitude.
It allows you to schedule as many dpkg operations as you need to get things working, including multiple suggestions how to automatically fix your problem, allowing you to choose between them. I discovered that there were some post removal scripts that were crashing dpkg and the solution was to manually remove several files from /var/lib/dpkg/info. WOW - isn't that a "pretty" way to go. It is not.
In Linux's (Debian's, in this case) defense, a bug in the installation script is never easy to recover from. On Windows, you'd be in much worse a state under similar circumstances.
Shachar |
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
