-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 04 Nov 2013 10:20:24 -0500 Ian Stakenvicius <a...@gentoo.org> wrote:
> Oh absolutely -- i figured this isn't a trivial issue. :) > > But it does seem like something we will need to fix (that is, ensuring > that blocker or conflict messages shown are -only- the ones that are > actually relevant) before being able to make the messages themselves > more user friendly and instructive. Heh, seems the ML overwrote my Reply-To header (infra bug? it is correct in Sent); as we're not supposed to be discussing this here. Yeah, I've asked about "pulled in by (no parents that aren't satisfied by other packages in this slot)" on #gentoo-portage and it is a weird state in the backtrack code; it was said by dwfreed there to intentionally not remove the orphans until it finds a solution, since it doesn't find one it outputs them. So, we just would need to remove faux orphans as well when we reach a blocker we can't solve... Anyhow, it is not a topic for the gentoo-dev ML, but thanks for mentioning your opinions; I'll be trying to look into this with them. - -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJSd74JAAoJEJWyH81tNOV9U24IAL4Ijx8p9HvAuc7GyGC14TM8 0gjPdrIC8GVXl96f8I9SQ5L07S76ccda4FRohWuUHP6+cAicvpT5t9UJDfANhDCH J12vU2Gyq4nUQ0fWxN0hPyKxy96r+UYYjSuEvZyfErr1mZ2QAS2qoTUXCtbUOSNb NH98FBUIuzdSRiwEQKBsWIaxk3Bt8mHt3Bjd8FrgzhMVXtP0g3eTbtJPAPkjlRzb Smutg3v1FazxRf5WahTpM6mqYZEmQnkxq/J0HgQKJrb8gAtTSRJQD1re0K5iQiZ8 lluWbdTBOmc+FFlcnQJHDyq22fC5yHpG94VFu/70AVMY/AuB3PDKyvxGjgNsMjI= =2zZx -----END PGP SIGNATURE-----
