acompneu ~ # emerge --keep-going @preserved-rebuild * IMPORTANT: 2 news items need reading for repository 'gentoo'. * Use eselect news to read news items. Calculating dependencies ... done! emerge: there are no ebuilds to satisfy "kde-misc/kdnssd-avahi:3.5". * IMPORTANT: 2 news items need reading for repository 'gentoo'. * Use eselect news to read news items.
(In reply to comment #0) > emerge: there are no ebuilds to satisfy "kde-misc/kdnssd-avahi:3.5". The --keep-going option currently does not drop unsatisfied dependencies. I suppose we could add an additional option for that. Anyway, kde-misc/kdnssd-avahi:3.5 looks like it's been removed from the tree, so if you are still using kde3 then you may want to use this overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/kde-sunset.git
Yes, I know that the package is not existing anymore. Is there any easy way to strip out (or ignore) all non-existing packages out of the @preserved-rebuild? Or in most cases I probably also want to delete such packages from my system.
The closest thing I can think of is to use `emerge -C @unavailable` to remove any packages that don't have ebuilds in the tree.
Ah, thanks for that hint, didn't know that set. :) I guess this will solve the problem for me then. But a --keep-going (or sth similar) could anyway be nice for unsatisfied dependencies. For example revdep-rebuild usage is pretty annoying with it (and as in this bug report, also @preserved-rebuild).
Possible duplicates: bug #263630, bug #312467, bug #312789, bug #340287, bug #342713, bug #362355
Please have a look at the possible duplicates bug #263630, bug #312467, bug #312789, bug #340287, bug #342713, bug #362355, and then raise the priority of the appropriate bugs. This issue is really annoying me by now, because it prevents a proper update of @world since months.
(In reply to comment #5) > Possible duplicates: bug #263630, bug #312467, bug #312789, bug #340287, bug > #342713, bug #362355 No, the @preserved-rebuild thing is different from all the others.
As part of the process of migrating to the 17.0 profile we were asked to emerge -e @world. I did so with a -k in the mix, but found the build exit really early, namely after fakechroot failed to build. Is that the same issue (i.e. is @world expected to behave like @preserved-rebuild in this regard) or something else?
(In reply to Martin von Gagern from comment #8) > As part of the process of migrating to the 17.0 profile we were asked to > emerge -e @world. I did so with a -k in the mix, but found the build exit > really early, namely after fakechroot failed to build. Is that the same > issue (i.e. is @world expected to behave like @preserved-rebuild in this > regard) or something else? Comment #0 is about a failure that occurs before anything is built. When it fails after things have started building that's a different class of issue (there are several issues in that class which block bug 373807).
