I wanted to try @Aravisian 's recommendation first because it appeared that should be done 1st. But maybe not. But I just now tried your suggestion and deleted both "linuxmint-daily-build-team" from stacer. And this is now what I get below when I try to install Nemo:
The following packages have unmet dependencies:
nemo : Depends: libnemo-extension1 (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Depends: nemo-data (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Recommends: nemo-fileroller (>= 4.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
In the other Folders You should look if there are Files that are related to that. Maybe with an similar File Names.
And then is there the File /etc/apt/sources.list which You should open with the Text Editor to look if there is this linuxmint-daily-build Repo listed.
# deb cdrom:[Zorin-OS 16.2 Core 64bit]/ focal main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ focal main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ focal-updates main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ focal universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal universe
deb http://us.archive.ubuntu.com/ubuntu/ focal-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ focal multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal multiverse
deb http://us.archive.ubuntu.com/ubuntu/ focal-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu focal partner
# deb-src http://archive.canonical.com/ubuntu focal partner
deb http://security.ubuntu.com/ubuntu focal-security main restricted
# deb-src http://security.ubuntu.com/ubuntu focal-security main restricted
deb http://security.ubuntu.com/ubuntu focal-security universe
# deb-src http://security.ubuntu.com/ubuntu focal-security universe
deb http://security.ubuntu.com/ubuntu focal-security multiverse
# deb-src http://security.ubuntu.com/ubuntu focal-security multiverse
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
# deb-src https://dl.winehq.org/wine-builds/ubuntu/ focal main
The following packages have unmet dependencies:
nemo : Depends: libnemo-extension1 (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Depends: nemo-data (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Recommends: nemo-fileroller (>= 4.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Okay, thank You. Like @Aravisian wrote is the linuxmint-daily-build Repo still there. So, You have to remove them manually. If You shouldn't know how to do that, I write You the Commands for the Terminal:
@Aravisian , i just did all that, including "sudo apt --fix-broken install" and still get:
The following packages have unmet dependencies:
nemo : Depends: libnemo-extension1 (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Depends: nemo-data (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Recommends: nemo-fileroller (>= 4.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
In this, no.
The programs apt and apt-get are two different pieces of software included in Debian and Ubuntu and derivatives of the above two distros to access APT (Advanced Package Tool) through the terminal.
So you can use apt or apt-get for most basic functions without noticing any difference.
The apt software is newer than apt-get and as such, offers more comprehensive dependency resolution and better user-friendliness than apt-get. You will usually not notice a difference until you run advanced commands are are running advanced package troubleshooting.
If you still had the LinuxMint Daily Builds repository added... and you had previously run system upgrades - then it likely added a Mint Specific Source file to your computer.
This is why I warn users that if they add another Distros repository solely for the purpose of installing one piece of software, that they immediately remove that repo once that software is installed.
You might search your computer for the mintsources file. With Nemo lacking, you may need to use a different search application to make that easier.
If you find it - or are uncertain if it is present or not... You can try running (For FOCAL):
So, did You delete the Files? Without that it will not get Process.
The Difference between apt and apt-get is: apt has a wider range of Operations. apt-get is more specific. It is more a Difference in Details. But sometimes it all depends on the Details. And it seems that we now have this Case.
When You have deleted the Files, try it please with sudo apt update and after that with sudo apt install nemo
It is necessary to remove any changes made by system software (like software-properties-gtk) by the mintsources package.
If everything is as it should be, then the commands will not harm the existing O.S. software. We differentiate software because none of the commands posted will harm the computer, in any way.
But there is always an element of risk on any OS when a user replaces packages.
Right now, your best bet is to face that minimal risk to correct the packaging issue.
The other option is to re-install your Operating system, restore any personal file back-ups - then install Nemo.
@Ponce-De-Leon , I did delete all the files in those folders. And then i did: sudo apt update and after that with sudo apt install nemo
And this i what i got:
The following packages have unmet dependencies:
nemo : Depends: libnemo-extension1 (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Depends: nemo-data (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Recommends: nemo-fileroller (>= 4.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
@Aravisian , I did everything exactly as you said, I do want to point out a few things, your 5 commands didnt include "sudo apt-get update", maybe that was your intention though.
And 2.) Noteworthily when i did sudo apt --fix-broken install
Results were:
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
And at the end of all 5 of your commands this is the result:
The following packages have unmet dependencies:
nemo : Depends: libnemo-extension1 (= 4.4.2-2ubuntu2) but 5.8.4-unstable-202308021446~ubuntu20.04.1 is to be installed
Recommends: cinnamon-l10n (>= 4.4) but it is not going to be installed
Recommends: nemo-fileroller (>= 4.4) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
That is pretty weird ... did You controled that they are deleted? Please don't understand me wrong: I am now on a Point where I can't help You anymore because I have no Idea's anymore. To delete the Sources File and the Key and then a sudo apt update should make it work again. In preferences.d isn't a File so there it couldn't be, too.
The only Thing that I could suggest You would be to save Your Data and make a fresh Install. But You have the Suggestion from @Aravisian. I hope this will help You.
What did the terminal print out as a result of this command?
What I am seeing here is:
The dependency set by the package contained within your repos is for 4.4.2, yet, the source is trying to install 5.8.4 unstable.
This clearly indicates that you have a source directing to that later package.
We need to really know if the mintsources package was added due to retention of the Mint Daily Builds repo.
The MintSources package is a bit pernicious...
YUP, there's your problem. The repo was retained - which the daily builds notates that that repo is for the Latest Builds and Packages - which resulted in it installing the MintSources packages for Mint, not your existing Operating System, creating package conflict.
You can try ensuring any existing Nemo files or packages are purged... You might use Synaptic to seek and destroy all Mint, Cinnamon and Nemo files and packages. Once everything is purged, then try reinstalling from the Main Universe Repo that came default with your installed O.S.
Other than that... I can only recommend reinstalling the O.S. as lesson learned that when using another distros specific repo to install a package, to never forget to remove that repo before running system upgrades.
And for the record, I have made this mistake, myself. It is how I know about the MintSources fiasco that gets its tendrils deeply embedded in the system. I successfully removed it at that time...
