rigo nuked my system! reverse dependency! [Solved]

[gowger]

after the latest upgrade I had a few things that were suggested to be removed. None of them seemed particularly relevant to my usage so I went ahead and allowed them to be removed.

I was surfing the web while it was working in the background so I didn't pay too much attention. When I went bac and check the logs though it had done a reverse dependency search and removed something like 1040 packages!! Kde had completely been removed as well as all the kde applications and lots and lots more!

How could this be allowed to happen? it seems like the reverse dependency got recursively carried away somehow and I feel like I should never remove any package again if this can happen!

[lxnay]

Rigo tells you what it is about to do. I am afraid to say that this is your fault.

[cl00t]

I had 5 items I think to remove after todays update, which I always do like:

Code: Select all

equo remove package1 package2 package3 package4 package5 --nodeps --configfiles --ask


Personally I never use rigo for anything.

[gowger]

that looks like a good idea, with the no deps flag. Will use that in future thanks

[Provia]

Rigo tells you what it is about to do. I am afraid to say that this is your fault.

A question: If i remove a package rigo ask me if i want to remove it and related packages. So if related packages have dependencies too then rigo will ask me if remove them(dependencies of dependencies)?
Maybe it's a stupid question but i'm now a little afraid about removing with rigo

[lxnay]

Of course it does.

[Provia]

Of course it does.

Ok, thank you

[gowger]

I believe it would be a good idea to allow a nodeps option to be chosen when this happens, because the implications are a bit too extreme. I didn't see (or refused to see) the full list of implied reverse dependencies when this happened, and trusted it blindly.

I like the sense of humour of course the way it does tell you it's breaking stuff sometimes.

Well I have a cleaner system now in any case!

[micia]

I believe it would be a good idea to allow a nodeps option to be chosen when this happens [...]

This isn't possible, using nodeps wouldn't fix anything, it would simply break the packages that did rely on the packages you are trying to remove.
This isn't an entropy (rigo or equo) exclusive, it is the way any package manager that handles dependencies behaves.

The only solution to this is always check what package you are going to remove, it happens often that you try to remove a package that looks useless but it is not, always take a look to the remove queue after dependency calculations.

[Matte88]

I can't understand how a package manager could broke your system if the same tells you which packages will be removed (if there are deps) or blocks itself when recognize vital packages to be removed. Maybe I totally misunderstood the thread.