Bug 16466 – empty ewarn/eerror hang ebuild

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Eloi Granado 2003-02-27 06:47:34 UTC]

In the sys-devel/perl-5.8.0-r9 ebuild there are some "empty string" ewarns and 
eerrors. When ebuild reaches those ones, it "hangs" (stop doing anything). Removing 
the empty ewarns solves the problem. I'm using sys-apps/portage-2.0.47-r6. Don't 
know if it happens in other messages (einfo...) or portage versions. 

Reproducible: Always
Steps to Reproduce:
1. Emerge sys-apps/portage-2.0.47-r6 
2. Try to emerge sys-devel/perl-5.8.0-r9 
3. 
Actual Results:  
Ebuild prints the empty warning/error, but hangs just after it. 

Expected Results:  
Continue installing the package

[Comment 1 Seemant Kulleen (RETIRED) 2003-02-27 06:53:13 UTC]

known issue.  if you remerge portage, you'll find it's been solved.

[Comment 2 SpanKY 2003-02-27 13:51:18 UTC]

*** Bug 16491 has been marked as a duplicate of this bug. ***

[Comment 3 SpanKY 2003-02-27 22:23:30 UTC]

*** Bug 16502 has been marked as a duplicate of this bug. ***

[Comment 4 SpanKY 2003-02-27 22:24:10 UTC]

not fixed quite yet

[Comment 5 Alexander Holler 2003-03-01 05:38:02 UTC]

This bug renders automated build scripts useless. 
 
Here is a fix for /sbin/functions.sh so that logger will not called without a message 
(and then waits for something on stdin): 
 
--- functions.sh.old    2003-02-03 10:34:15.000000000 +0100 
+++ functions.sh        2003-03-01 11:35:08.000000000 +0100 
@@ -80,7 +80,9 @@ 
                pri="$1" 
                tag="$2" 
                shift 2 
-               /usr/bin/logger -p ${pri} -t ${tag} -- $* 
+               if [ $1 ]; then 
+                   /usr/bin/logger -p ${pri} -t ${tag} -- $* 
+               fi 
        fi 
 } 
 

[Comment 6 Martin Schlemmer (RETIRED) 2003-03-01 10:46:01 UTC]

I fixed this a long time ago already by adding a dummy function for esyslog()
in ebuild.sh just after functions.sh gets sourced.  Nick moved the sourcing
of functions.sh to the bottom of the file, but not the 'dummy' esyslog(), so
functions.sh gets sourced *after* the 'dummy' esyslog() gets defined.

He did mail me earlier this week, and I told him what the issue is, but not
sure when he fixed it again.  No need thus for patching functions.sh.

[Comment 7 SpanKY 2003-03-01 13:09:19 UTC]

even if ebuild.sh 'fixes' this by adding in a dummy esyslog func, it still doesnt
fix rc-scripts/init.d scripts that have `ewarn ""` or `eerror ""` ...

also, it just seems like ignoring the fact that if you call ewarn/eerror in this
manner that it doesnt function properly ...

i like to use functions.sh in my scripts, and this would cause issues there too ...

[Comment 8 SpanKY 2003-03-01 20:42:20 UTC]

*** Bug 16633 has been marked as a duplicate of this bug. ***

[Comment 9 Matthew Humphrey 2003-03-01 20:47:13 UTC]

I don't think this is fixed because I ran into this with a brand new install off of 1.4 RC3, followed by an emerge sync and an emerge -u world. After doing that I eventually tried to install gentoo-sources and ran into this bug (see bug #16633).

[Comment 10 Matthew Humphrey 2003-03-02 09:32:34 UTC]

For what it's worth, I went ahead and rebuilt my system from scratch using the
1.4 RC3 livecd, a stage 1 install, and the instructions in the installation 
guide. The exact same problem occurred, fixed by re-emerging portage (and this
time I made sure to back up and restore my make.conf before/after doing this).

[Comment 11 SpanKY 2003-03-02 14:55:21 UTC]

*** Bug 16654 has been marked as a duplicate of this bug. ***

[Comment 12 SpanKY 2003-03-03 08:24:16 UTC]

*** Bug 16716 has been marked as a duplicate of this bug. ***

[Comment 13 SpanKY 2003-03-03 13:56:53 UTC]

*** Bug 16750 has been marked as a duplicate of this bug. ***

[Comment 14 SpanKY 2003-03-04 04:54:42 UTC]

*** Bug 16799 has been marked as a duplicate of this bug. ***

[Comment 15 Martin Schlemmer (RETIRED) 2003-04-06 11:07:30 UTC]

This has been fixed both portage and baselayout side.