Recently, emerge --depclean decided to unmerge sys-auth/policykit and gnome-extra/policykit-gnome. However, even though policykit-gnome DEPENDs on policykit, policykit was unmerged first. This causes issues with the binary dependency hack: * pre_pkg_prerm: bindepcheck.sh ... * Binary object libpolkit.so.2.0.0 will be removed, checking for dependencies: * (none) * Binary object libpolkit.so.2 will be removed, checking for dependencies: * gnome-extra/policykit-gnome-0.7_pre20071106 * Binary object libpolkit.so will be removed, checking for dependencies: * (none) * Binary object libpolkit-dbus.so.2.0.0 will be removed, checking for dependencies: * (none) * Binary object libpolkit-dbus.so.2 will be removed, checking for dependencies: * gnome-extra/policykit-gnome-0.7_pre20071106 * Binary object libpolkit-dbus.so will be removed, checking for dependencies: * (none) * Binary object libpolkit-grant.so.2.0.0 will be removed, checking for dependencies: * (none) * Binary object libpolkit-grant.so.2 will be removed, checking for dependencies: * gnome-extra/policykit-gnome-0.7_pre20071106 * Binary object libpolkit-grant.so will be removed, checking for dependencies: * (none) * Removing policykit-0.7_pre20071101 will break binary dependencies of the above listed * packages. Remerging the above packages may prevent this. * * ERROR: sys-auth/policykit-0.7_pre20071101 failed. * Call stack: * ebuild.sh, line 1741: Called qa_call 'pre_pkg_prerm' * ebuild.sh, line 35: Called pre_pkg_prerm * 10phase_hooks.sh, line 20: Called source '/etc/portage/phase_hooks.d/pre_pkg_prerm/bindepcheck.sh' * bindepcheck.sh, line 86: Called bindep_removed_objs * bindepcheck.sh, line 81: Called die * The specific snippet of code: * die "bindep" * The die message: * bindep * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/sys-auth:policykit-0.7_pre20071101:20071117-012745.log'. * emerge --unmerge gnome-extra/policykit-gnome sys-auth/policykit has the same issue; in both cases the unmerge list appears to be coming from arbitrary-order traversal of a dict (unlike merging, where dependencies are respected). This has a pretty trivial workaround (emerge --unmerge gnome-extra/policykit-gnome && emerge --unmerge sys-auth/policykit), but it'd still be useful, esp. as depclean already has a full dependency tree calculated. Perhaps it'd be enough for emerge --unmerge to respect the command-line order?
(In reply to comment #0) > Recently, emerge --depclean decided to unmerge sys-auth/policykit and > gnome-extra/policykit-gnome. However, even though policykit-gnome DEPENDs on > policykit, policykit was unmerged first. Technically, it's the RDEPEND and PDEPEND (runtime deps) that should matter here. The DEPEND is supposed to be completely optional at this stage. The digraph that depclean currently creates does not include any information about dependency priority. It needs to be more like the one that depgraph creates for installation actions, which places DepPriority objects in the digraph.
This is fixed in 2.2_pre3.
This is supposed to be fixed in portage-2.2_pre5 or earlier.
*** Bug 233261 has been marked as a duplicate of this bug. ***
