Bugzilla Bug 234301

I tried to install nmrpipe which has a fetch restiction. With emerge --jobs=4
-v sci-chemistry/nmrpipe the einfo from pkg_nofetch() isn't shown. As a result
the sense of this is lost. W/o --jobs everything works like expected.

This will be handled a little better in 2.2_rc7 by automatically displaying the
content of /var/log/emerge-fetch.log in cases like this.

In a later version I plan to add support for a temp directory during fetch, for
holding elog messages from pkg_nofetch or whatnot.

Not that with --verbose enabled you can see a summary of fetch restrictions at
the bottom of the merge list display and in any case you can see the
pkg_nofetch output in /var/log/emerge-fetch.log.

> Not that with --verbose enabled you can see a summary of fetch restrictions at
> the bottom of the merge list display 
I don't see any einfo from pkg_nofetch at the bottom. All other einfos are
shown except that one.
Isn't that problem to take a quick look into the ebuild to find the packages to
fetch, but I was sure to have them fetched and was confused that the fetch
restriction is still not full filled. 

(In reply to comment #2)
> > Not that with --verbose enabled you can see a summary of fetch restrictions at
> > the bottom of the merge list display 
> I don't see any einfo from pkg_nofetch at the bottom. All other einfos are
> shown except that one.

Right, with <2.2_rc7 you won't see the einfo unless you look in
/var/log/emerge-fetch.log. In 2.2_rc7 it will display the fetch log
automatically if that's the only thing that failed.

For normal elog support in pkg_nofetch, we need to allocate a temporary for the
ebuild to store elog messages in. This will not be fixed until after 2.2_rc7
has been released.

(In reply to comment #3)
> Right, with <2.2_rc7 you won't see the einfo unless you look in
> /var/log/emerge-fetch.log. In 2.2_rc7 it will display the fetch log
> automatically if that's the only thing that failed.
Perhaps it would be better only show the failed fetch and not the whole log. I
was I little stunned as this whole bunch of fetches scrolls down in front of
me.

I suppose we can take the output from a failed fetch and use it to generate an
elog message. Then it can easily be displayed, similar to how die messages are
displayed.

In svn r11686 is fixed to generate an eerror message that includes the path of
the fetch log.

This is fixed in 2.2_rc13.