Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 276481 - sys-apps/portage (2.1 and 2.2 branches) : emerge should warn that there are ewarns/errors to read
Summary: sys-apps/portage (2.1 and 2.2 branches) : emerge should warn that there are e...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
Depends on:
Reported: 2009-07-04 16:52 UTC by DEMAINE Benoît-Pierre, aka DoubleHP
Modified: 2020-01-06 18:08 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description DEMAINE Benoît-Pierre, aka DoubleHP 2009-07-04 16:52:40 UTC
ATM i am using sys-apps/portage-2.2_rc33 . I think that the two branches of portage (2.1 and 2.2) should include an improovement, in the behaviour of emerge. There are many applications to read emessages; I still use the deprecated enotice; but there are other officially maintained projects: elogv elogviewer kelogviewer ...

On forums and IRC, I see a lot of people asking things because they do not read their emessages, or installed their machine by reading a guide that does not even mention to read them, or not how, and how often.

I think that, the same way portage 2.2 tells about messages (and says to see "eselect news), and preserved rebuild ... portage should also say that there are messages to read ... and how

- a variable in make.conf to set the level of alter (for example, a value of 2 would only mention ewarnings and errors)
- it could mention the application to install (elogv, elogview, eselect-foobar [see below] ... )
- it should of course only consider unreaded messages, and shut up about readed emssages, or messages with low priority (below the threasold)
- it could also be implement through eselect (instead of make conf). Eselec could be a new way to read about emessages
- as in debian an cron, messages above the threashold should possible to send by email (this would of course depend on an MTA), or stored in a dedicated log file (like an mbox), or log dir (like a maildir)
- some kind of package like eselect-foobar could provide required some features

Special should be taken about the readed messages, and the way to index them. I am using entice since 2006; and my actual set up is nearly 2y old; with time, and growing quantity of messages, enotice takes more and more time to find out the new ones, or just say there are no new one. Indexation may help a lot.

This is important to me, because I see too many people asking trivial question that have answers in the emessages they do not read.
Comment 1 Allen Brooker (AllenJB) 2009-07-04 17:04:55 UTC
The storage / email options you talk about are already available. See the PORTAGE_ELOG_* options in "man make.conf"

Personally I think the way things are done now is fine. By default you're shown the messages at the end of the emerge process and the important ones appear with red or yellow highlights.

There are some things a lot of people just will not do when it comes to computers, and reading messages shown to them is one of them.
Comment 2 DEMAINE Benoît-Pierre, aka DoubleHP 2009-07-04 17:12:17 UTC
I configured mail, and it does not work. I configured to get messages at end of compile; and it does not work properly: get only ewarns for the merges that suceeded; if an emerge fails, you get only the last error, and never the ewarns of previously suceeded ones.

The way things are done now ... does not work properly, and needs to be redesigned.
Comment 3 Allen Brooker (AllenJB) 2009-07-04 17:43:12 UTC
The following is my configuration. While I only use this with a local-only Postfix setup, it works perfectly for me, sending an email for every package including failed packages (portage 2.2_rc33):
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_MAILURI="root /usr/sbin/sendmail"

I also had it working perfectly using ssmtp to send to my external mail account, altho I don't have the exact configuration available any more (but I'm pretty sure it was very similar to the examples given in the documentation).

I recommend you retest your mail setup, starting with testing sending a mail directly through your MTA (eg. ssmtp / postfix / sendmail), then working back from there. Don't forget to check your MTA logs for errors if it still appears to not work.
Comment 4 DEMAINE Benoît-Pierre, aka DoubleHP 2009-07-04 20:05:56 UTC
I am testing this again. It works with your params, when adding:


- a new system could be set to use eselect, as for news.
- default settings are not verbose enough: beginers, and users who read quick tutos may not know they have to do this. An explicit message should be prompted in all configurations, whatever is stated in make.conf, for everybody, when there are unreaded messages
- received emails are not really explanatory (I have an error with lirc, see below the difference between the console, and the mail - unless there is again a param I am not aware of ?)

hw_ftdi.c:54:18: error: ftdi.h: No such file or directory
hw_ftdi.c: In function âchild_processâ:
hw_ftdi.c:112: error: storage size of âftdicâ isnât known
make[3]: *** [hw_ftdi.o] Error 1
make[3]: Leaving directory `/var/tmp/portage/app-misc/lirc-0.8.5/work/lirc-0.8.5/daemons'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/app-misc/lirc-0.8.5/work/lirc-0.8.5/daemons'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-misc/lirc-0.8.5/work/lirc-0.8.5'
make: *** [all] Error 2
 * ERROR: app-misc/lirc-0.8.5 failed.
 * Call stack:
 *     , line   49:  Called src_compile
 *             environment, line 4255:  Called linux-mod_src_compile
 *             environment, line 3319:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"                                               CROSS_COMPILE=${CHOST}-         LDFLAGS=\"$(get_abi_LDFLAGS)\"                                                 ${BUILD_FIXES}                                          ${BUILD_PARAMS}                                                ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 *  The die message:
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=   all
 * 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/app-misc:lirc-0.8.5:20090704-200339.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-misc/lirc-0.8.5/temp/environment'.

LOG: setup
Compiling support for device userspace
Compiling support for device usbirboy
Setting default lirc-device to /dev/usbirboy
Comment 5 DEMAINE Benoît-Pierre, aka DoubleHP 2009-07-04 22:17:46 UTC
plus email system sends unrevealant messages; just now, in order:

type this:
USE="nut" emerge -va x11-plugins/gkrellmbups

receive this mail:

ERROR: unpack
Fetch failed for 'x11-plugins/gkrellmbups-2.0.2-r1', Log file:

press enter, wait for compilation =>

>>> Emerging (1 of 1) x11-plugins/gkrellmbups-2.0.2-r1
>>> Downloading ''
--2009-07-04 23:56:37--
Connecting to||:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 74807 (73K) [application/x-gzip]
Saving to: `/mnt/DHP_1T/distfiles/gkrellmbups-2.0.2.tar.gz'

100%[======================================>] 74,807       154K/s   in 0.5s

2009-07-04 23:56:38 (154 KB/s) - `/mnt/DHP_1T/distfiles/gkrellmbups-2.0.2.tar.gz' saved [74807/74807]

 * gkrellmbups-2.0.2.tar.gz RMD160 SHA1 SHA256 size ;-) ...              [ ok ]
>>> Installing (1 of 1) x11-plugins/gkrellmbups-2.0.2-r1
>>> Recording x11-plugins/gkrellmbups in "world" favorites file...

and after the end of this, emerge does not show me any warning or error message (I usually get them, when there are some, with the condictions i already spoke about)

So, in the end, why was this email send ? I just do not "officially" undderstand.

=> 404 ...

All this is just strange and full of contradictions.
Comment 6 DEMAINE Benoît-Pierre, aka DoubleHP 2009-07-04 22:18:58 UTC
NB: I am not surprised by the fact itself that it tried to download it, consuidering that I am using the parallel fetch feature.
Comment 7 Christohper Harrington 2020-01-06 18:08:07 UTC
Is there still something to do here? It's not clear if there is actually a problem or if this was just a configuration issue.