Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 256583 - sys-apps/portage: make.globals ELOG_* variables are not visible to emerge environment
Summary: sys-apps/portage: make.globals ELOG_* variables are not visible to emerge env...
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - External Interaction (show other bugs)
Hardware: All Linux
: High minor
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-28 01:39 UTC by Boney McCracker
Modified: 2009-01-28 03:06 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boney McCracker 2009-01-28 01:39:19 UTC
make.globals contains default values for many make.conf variables

Default values for ELOG_* variables are specified there, but they don't seem to make it into the portage environment.

The result is that users must specify each variable in make.conf.  This in itself is not a problem, but the presence of the ELOG_* variables in the make.globals files is misleading, given that the values do not appear in the portage environment unless specified in make.conf.




Reproducible: Always

Steps to Reproduce:
1.  With no ELOG_* variable assignments in /etc/make.conf, emerge a package.

2.  With ELOG_* variable assignments present in /etc/make.conf, repeat (1) above.

Actual Results:  
1. No ELOG output is captured or handled. (I only tested for email, which was not generated.)

2. The variables are visible in 'emerge --info' output, and the ELOG output is captured and handled as expected.

Expected Results:  
ELOG output should be captured and handled in accordance with the ELOG_* variable assignments made in /etc/make.globals.

Alternatively, if the variable assignments made in make.globals have no effect, they should be removed to avoid confusion.

# $ emerge --info
Password: 
Portage 2.1.6.7 (default/linux/x86/2008.0/desktop, gcc-4.3.2, glibc-2.9_p20081201-r1, 2.6.28-gentoo-r1 i686)
=================================================================
System uname: Linux-2.6.28-gentoo-r1-i686-Pentium_III_-Coppermine-with-glibc2.0
Timestamp of tree: Tue, 27 Jan 2009 07:45:02 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p48
dev-java/java-config: 1.3.7-r1, 2.1.7
dev-lang/python:     2.5.4-r2
dev-util/ccache:     2.4-r8
dev-util/cmake:      2.6.2
sys-apps/baselayout: 2.0.0
sys-apps/openrc:     0.4.2
sys-apps/sandbox:    1.3.2
sys-devel/autoconf:  2.13, 2.63
sys-devel/automake:  1.5, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.19
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.28-r1
ACCEPT_KEYWORDS="x86 ~x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="ftp://ftp.gtlib.gatech.edu/pub/gentoo http://gentoo.osuosl.org/ http://open-systems.ufl.edu/mirrors/gentoo "
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
LDFLAGS="-Wl,-O1,--hash-style=gnu"
LINGUAS="en_US en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X a52 acl acpi alsa berkdb bzip2 cairo caps cdr cli cracklib crypt cups dbus dri dvd dvdread eds encode esd evo exif ffmpeg flac fortran gdbm gif gnome gnome-keyring gpm gstreamer gtk hal iconv ieee1394 imagemagick java jpeg libnotify logrotate mad midi mmx mp3 mpeg mudflap nautilus ncurses nls nptl nptlonly nsplugin ogg opengl openmp pam pcre pdf perl png ppds python quicktime readline reflection samba sdl session spell spl sse ssl startup-notification svg sysfs threads tiff truetype unicode usb userlocales vorbis win32codecs x86 xml xorg xulrunner xv zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse joystick" KERNEL="linux" LINGUAS="en_US en" USERLAND="GNU" VIDEO_CARDS="nv"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 Marius Mauch (RETIRED) gentoo-dev 2009-01-28 02:08:35 UTC
Just to be sure: You know that the variables are PORTAGE_ELOG_*, not ELOG_*, right?
Also, do the variables from make.gobals show up in `emerge --info -v | grep PORTAGE_ELOG`?
If they do then something else is going on. If you could provide an actual example where things don't work as expected it might help to isolate the problem.
Comment 2 Boney McCracker 2009-01-28 02:43:01 UTC
(In reply to comment #1)
> Just to be sure: You know that the variables are PORTAGE_ELOG_*, not ELOG_*,
> right?

Yes, I am referring specifically to the following variables in make.globals (and make.conf):

PORTAGE_ELOG_CLASSES
PORTAGE_ELOG_SYSTEM
PORTAGE_ELOG_MAILURI
PORTAGE_ELOG_MAILSUBJECT
PORTAGE_ELOG_MAILFROM

> Also, do the variables from make.gobals show up in `emerge --info -v | grep
> PORTAGE_ELOG`?

No they don't; but they don't show up there in any case.  To be clear, those variables show up in 'emerge --info' output neither in case (1) above (i.e. with no PORTAGE_ELOG* variables in /etc/make.conf), nor in case (2) (i.e. with all PORTAGE_ELOG* variables explicitly assigned in /etc/make.conf).

> If they do then something else is going on. If you could provide an actual
> example where things don't work as expected it might help to isolate the
> problem.

Well, I'm not sure how that would help.  The actual "not expected" consequences of this are the following:

If the user does not explicitly make all PORTAGE_ELOG* variable assignments in /etc/make.conf, then elog does absolutely nothing.  The user has no visibility of the processing of the make.globals file.

One additional thing.  The observations I have provided are consistent across four machines I have checked (all fully updated):

i686 running gentoo-sources with ACCEPT_KEYWORDS="~x86"
i686 running hardened with ACCEPT_KEYWORDS="~x86"
i686 running hardened with ACCEPT_KEYWORDS="x86"
ppc running gentoo-sources with ACCEPT_KEYWORDS="ppc"
Comment 3 Boney McCracker 2009-01-28 03:06:31 UTC
CORRECTION

> > Also, do the variables from make.gobals show up in `emerge --info -v | grep
> > PORTAGE_ELOG`?

I didn't use "-v".  The variables DO show up.

This bug is invalid.

I believe my problem is that the mailer I use requires the custom PORTAGE_ELOG_MAILURI value I have in make.conf, and it fails silently when the default variable is inherited.

My apologies for being ignorant of the "-v" option there and wasting your time, and thank you for diagnosing this for me.