Re: [gentoo-dev] Re: [IDEA] Enumerate solutions for blockers, to avoid tedious manual work.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 04 Nov 2013 10:20:24 -0500 Ian Stakenvicius 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-
Re: [gentoo-dev] Re: [IDEA] Enumerate solutions for blockers, to avoid tedious manual work.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/11/13 10:07 AM, Pacho Ramos wrote: > El lun, 04-11-2013 a las 10:01 -0500, Ian Stakenvicius escribió: >> On 03/11/13 07:10 AM, Tom Wijsman wrote: >>> On Sun, 03 Nov 2013 10:53:13 +0200 Alan McKinnon >>> wrote: >>> On 02/11/2013 17:03, Michał Górny wrote: Sadly, it's somewhat common for (newish) users to not know what to do with that. Blocker output can be quite daunting in the beginning, especially if it's in the middle of 20 other things portage is also updating. >>> >>> +1 I agree, we should look into having errors not only tell >>> what we should not do, but also tell what we could do; every >>> time I see a blocker it is annoying that I have to go manually >>> search the solution. >>> >> >> This sounds like a great idea. >> >> However, let's first get Portage to stop dumping out massive >> amounts of useless and/or meaningless slot collision messages >> first, seemingly *whenever* there is some other random and >> unrelated blockage triggered. Dropping the extra noise will help >> a lot I think to make things more clear. >> > > I agree, but I think a bug was already opened due that and wasn't > so easy to solve :( (not sure if Zac will read this to clarify). I > think it was a problem due backtracking code > > 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. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlJ3uzgACgkQ2ugaI38ACPCGWQEAnIq5wGnsInGVH0j/yE8wY/ln uHkCGQOF3NSKb4zMvVEA/jkBKcA8nvnzepFlkQO1TEzzTlRhOJP82WXcbNS5K2KF =nNGm -END PGP SIGNATURE-
Re: [gentoo-dev] Re: [IDEA] Enumerate solutions for blockers, to avoid tedious manual work.
El lun, 04-11-2013 a las 10:01 -0500, Ian Stakenvicius escribió: > On 03/11/13 07:10 AM, Tom Wijsman wrote: > > On Sun, 03 Nov 2013 10:53:13 +0200 Alan McKinnon > > wrote: > > > >> On 02/11/2013 17:03, Michał Górny wrote: Sadly, it's somewhat > >> common for (newish) users to not know what to do with that. > >> Blocker output can be quite daunting in the beginning, especially > >> if it's in the middle of 20 other things portage is also > >> updating. > > > > +1 I agree, we should look into having errors not only tell what > > we should not do, but also tell what we could do; every time I see > > a blocker it is annoying that I have to go manually search the > > solution. > > > > This sounds like a great idea. > > However, let's first get Portage to stop dumping out massive amounts > of useless and/or meaningless slot collision messages first, seemingly > *whenever* there is some other random and unrelated blockage > triggered. Dropping the extra noise will help a lot I think to make > things more clear. > I agree, but I think a bug was already opened due that and wasn't so easy to solve :( (not sure if Zac will read this to clarify). I think it was a problem due backtracking code
[gentoo-dev] Re: [IDEA] Enumerate solutions for blockers, to avoid tedious manual work.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/11/13 07:10 AM, Tom Wijsman wrote: > On Sun, 03 Nov 2013 10:53:13 +0200 Alan McKinnon > wrote: > >> On 02/11/2013 17:03, Michał Górny wrote: Sadly, it's somewhat >> common for (newish) users to not know what to do with that. >> Blocker output can be quite daunting in the beginning, especially >> if it's in the middle of 20 other things portage is also >> updating. > > +1 I agree, we should look into having errors not only tell what > we should not do, but also tell what we could do; every time I see > a blocker it is annoying that I have to go manually search the > solution. > This sounds like a great idea. However, let's first get Portage to stop dumping out massive amounts of useless and/or meaningless slot collision messages first, seemingly *whenever* there is some other random and unrelated blockage triggered. Dropping the extra noise will help a lot I think to make things more clear. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlJ3trcACgkQ2ugaI38ACPB+nAD5AXdXTR3Aw3M0hSsneq0kz0A4 qD4R255jipGDETA2NOEA/jGc33K60gquaMd0ByyFkN3+qpUBGvCTVRWrQKqUDyPW =FpuT -END PGP SIGNATURE-
