I decided to do a standard upgrade today and selected to mark all upgrades in Synaptic package manager. Once everything reloaded synaptic showed packages to be installed and packages to be upgraded as normal but a new package was to be installed that I do not want installed so I cancelled the upgrade and located the package that was to be installed and attempted to unmark it for installation but found the options to unmark the packaged was greyed out as well as the options to remove or completely remove the package. On further investigation I found other packages that those options were also greyed out. In all my years as a Linux and Debian based system user I have never been denied as the root user the ability to unmark a package for installation or the ability to remove any package from the system that I desired to remove even if it was an critical component of the system that would crash the works. I need to know if this is a bug in my system or something new that has been implemented in MX. Any clarification is most appreciated as it's a game changer for me as-is. Thank You, JBoman
Search the forum for how to pin packages in Synaptic, or just explore Synaptic's menus and you'll find it. After pinning yours at the current version you'll need to reload the available packages and check for upgrades again. Your package now shouldn't be listed among the upgrades.
Also you have Debian Backports permanently enabled. This could break your system. If you need packages from there, MX Package Installer is your friend. You also shouldn't have added the VirtualBox repo. VB is available in MX's own repositories including 6.1.10 in the MX Test Repo if you want a newer version for some reason.
Thank you, the suggestions and recommendations to insure stability in my system are appreciated, however, I still need to know why the package control options are greyed out in synaptic.
http://patentabsurdity.com/
AMD 64x2 2.6GHz 4GB ram MX-18.1 KDE regular updates
"beware a frequent flirt with potential disaster"
I had considered backports as a possible reason for the disabled options so I disabled backports, reloaded package list, and marked upgrades again only to find the same package trying to install and the same greyed out options. The persistent package trying to install I first noticed that I didn't want was youtube-dl.
http://patentabsurdity.com/
AMD 64x2 2.6GHz 4GB ram MX-18.1 KDE regular updates
"beware a frequent flirt with potential disaster"
Since SMPlayer now requires youtube-dl for its Youtube playback feature, I made it a dependency of that program. Synaptic should let you know it's removing SMPlayer if you have both installed, like apt on the command line:
$ sudo apt remove youtube-dl
[sudo] password for steve:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libigdgmm5 liblept5 libllvm9 libllvm9:i386 libtesseract4 libvapoursynth libvapoursynth-script0
libzimg2 mpv vapoursynth-python3 xsel
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
smplayer smplayer-l10n smplayer-themes youtube-dl
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 25.9 MB disk space will be freed.
Do you want to continue? [Y/n] n
JayM wrote: Fri Jul 10, 2020 11:51 pm
Search the forum for how to pin packages in Synaptic, or just explore Synaptic's menus and you'll find it. After pinning yours at the current version you'll need to reload the available packages and check for upgrades again. Your package now shouldn't be listed among the upgrades.
Also you have Debian Backports permanently enabled. This could break your system.
As long as you do not change the MX Linux default repo priorities that will not happen, you need to force version to install or upgrade anything from backports.
The test repo or virtual box repo is a different matter.
Or leaving the Debian Backports repo enabled while doing updates may have broken something, possibly Synaptic. Many of MX's packages and libraries are actually newer or different than the ones in Debian including their backports and updating everything available in Backports may have overwritten things such as system files and libraries with different versions. See Don't Break Debian and How To Break Your System in my signature.
Yes was a dependency issue. Thanks for all the help and thanks Stevo for the verification of why. Backports and VB are disabled now and thanks for that as I never intended to have left backports enabled and and had not paid any attention to repos until this happened. Great Community, Thanks again, Jerry
http://patentabsurdity.com/
AMD 64x2 2.6GHz 4GB ram MX-18.1 KDE regular updates
"beware a frequent flirt with potential disaster"