| Summary: | portage-2.1.4.4 - nvidia.eclass ewarns not logged by elog | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | DEMAINE Benoît-Pierre, aka DoubleHP <dhp_gentoo> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | 2.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge--info
/etc/portage/profile/profile.bashrc |
||
|
Description
DEMAINE Benoît-Pierre, aka DoubleHP
2008-02-26 17:16:53 UTC
Created attachment 144686 [details]
emerge--info
Is it logged in /var/log/portage/elog/ ? moon_gen_3 ~ # grep -nri "Add the following" /var/log/portage/elog/ /var/log/portage/elog/app-shells:bash-completion-20050121-r10:20080224-005331.log:2:Add the following to your ~/.bashrc to enable completion support. /var/log/portage/elog/sys-fs:cryptsetup-1.0.5-r1:20080224-122017.log:9:after 10 seconds add the following to your bootloader config: moon_gen_3 ~ # same problem with /var/log/portage/dev-libs\:libmix-2.05\:20080227-122234.log I heard beeps, switched to emerging console, did not see any message. I ran enotice to check messages, no notice to show. Went into emergelog, checked recently emerged things, and found this: /var/log/portage/dev-libs\:libmix-2.05\:20080227-122234.log contains yellow warnings: * QA Notice: The following shared libraries lack a SONAME * /var/tmp/portage/dev-libs/libmix-2.05/image/usr/lib/libmix++.so /var/tmp/portage/dev-libs/libmix-2.05/image/usr/lib/libmix.so * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * misc/misc.c:212: warning: null argument where non-null required (argument 1) * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: http://mixter.void.ru/ but, they are not reported by enotice. Following Marius' recent question, I give this: moon_gen_3 ~ # grep -nri "QA Notice: Package" /var/log/portage/elog/ moon_gen_3 ~ # As I thought, but did not mentioned in first report, it seems to me that all ewarns that are printed by inherited bits of code (for example by including eclasses) lead to logging failures. Assigners of this bug: please consider to change the name of the bug, to something like: ebuild/emerge warnings and errors are not logged when produced by inherited scripts The reasons I am complaining for are: - enotice/elogs are designed to archive messages; here, we have messages that are not logged - logging system have been set up so that "root" can consult messages long time after installation, without having to re-emerge - logging principle is based on the idea we cant stare at compiling console for hours, and that when we emerge sth that have a dep, last ebuilds flodding the console make previous logs croll up ... so that we visualy loose them. => logs are here to allow us to catch back lost messages => in present cases, there are logs that tend to alert $root of potential problems, and those logs are lost because log system fails. I report for the principle that messages to be logged are lost. I understand this may not be important for most people, and be eventually very difficult to fix. Please keep this bug open, so that we can list here cases where messages are lost. different problem (maybe you will think this point is not related to this bug): at end of emerging mpg123, I say a red aloert about collision detection. Enotice still dont have anything to say about it: moon_gen_3 ~ # enotice No notices found. moon_gen_3 ~ # but here, elog does: moon_gen_3 ~ # grep -nri "file collision" /var/log/portage/elog/ /var/log/portage/elog/media-sound:mpg123-1.2.0:20080227-134219.log:17:Detected file collision(s): /var/log/portage/elog/x11-drivers:nvidia-drivers-100.14.19:20080226-141033.log:17:Detected file collision(s): /var/log/portage/elog/media-libs:svgalib-1.9.25:20080226-140927.log:17:Detected file collision(s): moon_gen_3 ~ # since enotice is not really part of portage, I think you will reject this point, as elog has traces of this error message. Still, it'd be nice to point me to a solution. *** *** *** I am trying elogv: as expected, it shows a 2 line message about mpg123 collision (but only 2 or 3 lines, instead of the >12 red ones I have seen in console); and does not say anything about the nvidia warnings ... and absolutely nothing about libmix. => problem reproduced: elogv behaves the same way as enotice in regard to this bug about nvidia and libmix. In regard to what's in elog, they seem different. Please attach /etc/portage/bashrc and /etc/portage/profile/profile.bashrc (if existant). Created attachment 144753 [details]
/etc/portage/profile/profile.bashrc
moon_gen_3 ~ # ls -l /etc/portage/profile/profile.bashrc
-rw-r--r-- 1 root root 811 2004-11-10 22:15 /etc/portage/profile/profile.bashrc
moon_gen_3 ~ # ls -l /etc/portage/bashrc
ls: cannot access /etc/portage/bashrc: No such file or directory
moon_gen_3 ~ #
Ok, so enotice still hijacks elog functions, meaning it's incompatible. If you want to use elog remove your profile.bashrc and use another reader tool, if you want to continue to use enotice you'll have to talk to its authors, as it is (and always was) completely unsupported by us. |
