Some of my scripts have recently started spitting out this error:
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 kB
!!! The following update(s) have been skipped due to unsatisfied dependencies
!!! triggered by backtracking:
Nothing to merge; quitting.
pentoo/pentoo is a custom metapackage which controls which packages go on my livecd, so in this case it's basically a package with a few dozen deps. Clearly something went wrong when calculating the deps, and as such, portage aborted instead of doing what I asked (in this case updating world, where pentoo/pentoo is in the world file).
I find this inappropriate for two reasons:
1.) The error is useless, it tells me nothing about the dep error other than "unsatisfied".
2.) It exits with code 0 indicating success. I said update world, it didn't update everything in world, I don't believe this was as success at all.
All my scripts are set to trap errors using the return code and drop me to a shell so I can fix it, but in this case, portage returns success and keeps going which is obviously wrong since it didn't succeed.
Please consider changing the return code, and if possible, adding some useful output (although I'm happy with fixing the return code).
please show the exact command line you used
(In reply to Rick Farina (Zero_Chaos) from comment #0)
> !!! The following update(s) have been skipped due to unsatisfied dependencies
> !!! triggered by backtracking:
A missed update is not the same as being "unsatisfied". In this case, it's possible for emerge to update some other packages while skipping that update.
We should make it display precisely which broken dependencies caused the update to be skipped. We could add an option to make missed updates fatal.