Summary: | sys-apps/portage (2.1 and 2.2 branches) : emerge should warn that there are ewarns/errors to read | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DEMAINE Benoît-Pierre, aka DoubleHP <dhp_gentoo> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | gentoo-bugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
DEMAINE Benoît-Pierre, aka DoubleHP
2009-07-04 16:52:40 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. 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. 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): PORT_LOGDIR=/var/log/portage PORTAGE_ELOG_CLASSES="warn error log" PORTAGE_ELOG_MAILURI="root /usr/sbin/sendmail" PORTAGE_ELOG_MAILSUBJECT="[lister ELOG] package \${PACKAGE}" PORTAGE_ELOG_SYSTEM="save mail" 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. I am testing this again. It works with your params, when adding: PORTAGE_ELOG_MAILFROM="mysource@foobar.com" *** Still: - 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 ?) console: 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: * ebuild.sh, 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'. * email: LOG: setup Compiling support for device userspace Compiling support for device usbirboy Setting default lirc-device to /dev/usbirboy 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: '/var/log/portage/x11-plugins:gkrellmbups-2.0.2-r1:20090704-215245.log' press enter, wait for compilation => [...] >>> Emerging (1 of 1) x11-plugins/gkrellmbups-2.0.2-r1 >>> Downloading 'http://ftp.vectranet.pl/gentoo/distfiles/gkrellmbups-2.0.2.tar.gz' --2009-07-04 23:56:37-- http://ftp.vectranet.pl/gentoo/distfiles/gkrellmbups-2.0.2.tar.gz Resolving ftp.vectranet.pl... 88.156.78.16 Connecting to ftp.vectranet.pl|88.156.78.16|: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. Personally: http://members.dslextreme.com/users/billw/gkrellm/Plugins.html => http://www.cryptofreak.org/projects/gkrellmgimps/ => 404 ... All this is just strange and full of contradictions. NB: I am not surprised by the fact itself that it tried to download it, consuidering that I am using the parallel fetch feature. 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. |