Removing dependencies that are not needed.

Cossty

I tried it again with installing lutris. After I uninstalled it and put sudo eopkg rmo into terminal, I got “No packages to remove” even though I can see in software center that all dependencies are still installed and number of packages in neofetch is reduced only by 1.

algent

Cossty I never seen this kind of issue. You can try to run sudo eopkg rdb to rebuild database.

WetGeek

algent You can try to run sudo eopkg rdb to rebuild database.

Excellent suggestion. I didn't know of any orphans, and I had run eopkg rmo fairly often, as part of my normal system maintenance. After reading your post, I ran eopkg rdb, followed by eopkg rmo, and two orphaned dependencies of Audacious (which I'd previously removed) were finally removed.

It seems that eopkg rmo might just need eopkg rdb run first, in order for it to do its job well. My next alias?

Cossty

algent nope didn't help
idk what could fix this.
One thing to add. I'm using VM. I want to switch from Manjaro to Solus, so I have been playing with it in VM for a couple of days. Maybe it's VM issue?? IDK why that would be the case. Maybe I will try to install Solus on some old laptop I have lying around and see if that will fix it.

algent

Cossty Maybe it's VM issue??

I don't think it is a VM issue. I tried this on Virtual Box and eopkg rmo is working fine.

Cossty

I installed Solus on my unused pc, but the problem remains

algent

Cossty Well we have two common things here, same ISO file and same user 😛.
My guess is that something should be Broken in the ISO file.
What edition of Solus are you using?
You can try to re-donwload the ISO and check SHA256SUMS to make sure that the ISO file isn't damaged or try another edition.

Cossty

algent In VM I have Solus Budgie and on my old pc I have Solus Gnome, so I don't think it is problem with iso, but just to be sure, how do I check if iso is good?
When I was trying to fix it, at first I was doing this:
opened neofetch to see how many packages is installed
Installed lutris with software center
uninstalled lutris with sc
put sudo eopkg rdb and after that sudo eopkg rmo into the terminal
close sc, open sc
check if dependencies are still there
check how many packakes is neofetch saying that I have

After that tried everything with terminal
sudo eopkg it lutris
sudo eopkg rm lutris
sudo eopkg rdb
sudo eopkg rmo

mangohud is still installed, even though it wasn't before I installed lutris

WetGeek

Cossty mangohud is still installed, even though it wasn't before I installed lutris

Sometimes a work-around can be a good option when a solution isn't apparent. A backup is a good way to return to an earlier condition if that turns out to be desirable. Perhaps you'll consider that in the future? If so, search the forum for "restic" to see a concise way to set up and perform backups.

With the VM it's even simpler. Just a couple clicks of the mouse are all that's needed to create a "snapshot" of the current state, and it's just as easy to revert to that state later, if desired. So before you install something you might later regret, just take a snapshot. Then if it turns out that you do regret installing it, you can uninstall it and all its dependencies with virtually a click of the mouse.

I realize that these suggestions are not solutions to your present problem. Since a solution seems still to be elusive, though, they might be a good second choice. Nobody ever regretted having a backup when something went wrong.

Cossty

WetGeek I guess that's the only option for now.
thx

WetGeek

Cossty I guess that's the only option for now.

Even after you discover the solution to the present problem, regular backups are still a good idea. I backup all of my computers and my wife's just before every weekly update. If anything were to go wrong with the update, or if I did something stupid myself during the week and caused a problem, I could immediately return the system to a state that was working fine.

I'm not alone in doing regular backups. And if you have anything at all business-related on those computers, that's even more reason to make regular backups a habit.

kyrios

Could you paste here the output of the lasts operations from eopkg history ?

Cossty

kyrios Operation #27: remove
Date: 2021-09-09 18:28

* mangohud 0.6.5-6-1-x86_64 is removed.

Operation #26: remove
Date: 2021-09-09 18:27

* lutris 0.5.8.4-61-1-x86_64 is removed.

Operation #25: install
Date: 2021-09-09 18:27

* lutris 0.5.8.4-61-1-x86_64 is installed.

Operation #24: remove
Date: 2021-09-09 17:04

* lutris 0.5.8.4-61-1-x86_64 is removed.

Operation #23: install
Date: 2021-09-09 17:03

* lutris 0.5.8.4-61-1-x86_64 is installed.

Operation #22: remove
Date: 2021-09-09 17:02

* lutris 0.5.8.4-61-1-x86_64 is removed.

Operation #21: install
Date: 2021-09-09 16:59

* libgcc-32bit 11.2.0-58-1-x86_64 is installed.
* pyyaml 5.1.2-11-1-x86_64 is installed.
* cabextract 1.9.1-3-1-x86_64 is installed.
* glibc-32bit 2.33-67-1-x86_64 is installed.
* libgpg-error-32bit 1.39-19-1-x86_64 is installed.
* libgcrypt-32bit 1.8.7-24-1-x86_64 is installed.
* python-evdev 1.1.2-6-1-x86_64 is installed.
* libgnome-keyring 3.12.0-16-1-x86_64 is installed.
* systemd-32bit 247.8-97-1-x86_64 is installed.
* inih 53-3-1-x86_64 is installed.
* gamemode 1.6.1-9-1-x86_64 is installed.
* libstdc++-32bit 11.2.0-58-1-x86_64 is installed.
* mangohud 0.6.5-6-1-x86_64 is installed.
* dbus-32bit 1.12.20-32-1-x86_64 is installed.
* gamemode-32bit 1.6.1-9-1-x86_64 is installed.
* python-lxml 4.2.4-11-1-x86_64 is installed.
* python-pillow 6.2.2-25-1-x86_64 is installed.
* lutris 0.5.8.4-61-1-x86_64 is installed.

Operation 27 where mangohud is removed, that's me manually removing it.

Staudey

Maybe it would be wise to first do a full system update and then test again.

Cossty

Staudey System is up-to-date.

Staudey

Cossty How can the system be up-to-date when installing lutris pulls in the glibc update? Obviously it's not up-to-date, or at least wasn't when the log was created.

DataDrake Yes, I thought it might have to do something with automatically pulled-in required updates and that messing with the orphan system. Who knows? (without a deep dive into the code 🙂 )

DataDrake

Guys, it's probably a bug in how manually installed packages are marked or how orphaned packages are calculated. That was a late stage add-on for eopkg and I'm not sure that it's 100% reliable.

Cossty

DataDrake Can I do something about it, or should I wait for a fix?

DataDrake

Cossty There isn't going to be a fix. eopkg is in maintenance mode and we'd rather not break it further. If someone manages to track down the cause, I'm amenable to a PR for it, but Josh and I have much bigger fish to fry.

Cossty

Staudey I uninstalled almost every application that came with Solus and some unneeded dependencies too. It might have been one of those. Lutris installed glibc 32bit. I don't think that package is necessary for Solus to run. After your message, I checked glibc 64bit and software center didn't let me remove it. I might be wrong, though. You probably know more about Linux than me.
I'm pretty sure that system was updated before I started removing and installing packages.

Cossty

DataDrake I'm not going to pretend that I know more than you, but wouldn't it unnecessarily bloat Solus after a couple of months/years if dependencies are not removed correctly? You probably have more important things to worry about, as you said, and this currently isn't that big of an issue. I'm just curious.

Girtablulu

DataDrake Could it be a "chain dependency" issue? like breeze pulls in needed deps to run and these deps pull in some other etc etc, does eopkg handle such cases nicely?