Bug 245491 – app-portage/eix - eix-sync -q isn't quiet enough

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Clemente Aguiar 2008-11-04 08:58:01 UTC]

I run "eix-sync -q" daily on my boxes on a cron job, and I always get some output, and consequently I get emailed the output.

On my amd64 boxes I get the following output:

q: Updating ebuild cache ... 
q: Finished 25554 entries in 0.291096 seconds
real 175.08
user 16.99
sys 6.78

On my x86 boxes I only get the following output.

real 175.08
user 16.99
sys 6.78

So, basically, the -q option is not 100% quiet.
I actually think that the "culprit" app is "emerge", namely "emerge --sync -q" which is called from "eix-sync -q".

Reproducible: Always

[Comment 1 Jeroen Roovers (RETIRED) 2008-11-04 19:55:04 UTC]

I would say the problem should be put firmly to the app-portage/eix developers - it is their -q option that promises quietness.

The "culprit" so to speak is very likely /etc/portage/postsync.d/q-reinitialize from the app-portage/portage-utils package, and eix-sync should probably redirect the output appropriately to make true its promise of quietness. From the output of app-portage/portage-utils:

 * //etc/portage/postsync.d/q-reinitialize has been installed for convenience
 * If you wish for it to be automatically run at the end of every --sync simply chmod +x //etc/portage/postsync.d/q-reinitialize
 * Normally this should only take a few seconds to run but file systems such as ext3 can take a lot longer.
 * If ever you find this to be an inconvenience simply chmod -x //etc/portage/postsync.d/q-reinitialize

To wit:

elmer ~ # /etc/portage/postsync.d/q-reinitialize
q: Updating ebuild cache ...
q: Finished 25556 entries in 16.955048 seconds

[Comment 2 Clemente Aguiar 2008-11-05 09:57:22 UTC]

You are right, there are actually two "culprits".

On the amd64 bit there is "problem" with emerge, or maybe more specifically as you mentioned with /etc/portage/postsync.d/q-reinitialize:
$ emerge --sync -q
q: Updating ebuild cache ... 
q: Finished 25555 entries in 0.290815 seconds

On the x86 and amd64 there is a problem with eix-sync:
$ eix-sync -q
real 1.32
user 0.46
sys 0.06

[Comment 3 Jeroen Roovers (RETIRED) 2008-11-05 18:30:02 UTC]

Looks like two bugs to me. Could you focus on one issue here ("app-portage/eix - eix-sync -q isn't quiet enough") and open a new bug for the other ("app-portage/portage-utils - /etc/portage/postsync.d/q-reinitialize isn't quiet enough"), please?

[Comment 4 Clemente Aguiar 2008-11-05 19:42:37 UTC]

Done. Bug opened n. 245739.

[Comment 5 Jeroen Roovers (RETIRED) 2008-11-05 19:51:15 UTC]

Nothing to do with emerge - something out there is running `time emerge --sync`.

[Comment 6 Jeremy Olexa (darkside) (RETIRED) 2008-11-05 20:09:31 UTC]

The POSIX time command output to stdout, we can't fix that.

[Comment 7 Jeremy Olexa (darkside) (RETIRED) 2008-11-05 20:10:37 UTC]

*** This bug has been marked as a duplicate of bug 235269 ***

[Comment 8 Jeremy Olexa (darkside) (RETIRED) 2008-11-05 20:15:35 UTC]

(In reply to comment #6)
> The POSIX time command output to stdout, we can't fix that.
> 

typo: s/stdout/stderr/

[Comment 9 Mattias Merilai 2010-09-03 10:42:25 UTC]

(In reply to comment #8)
> (In reply to comment #6)
> > The POSIX time command output to stdout, we can't fix that.
> > 
> 
> typo: s/stdout/stderr/
> 

but can you do something like 'time foo &> /dev/null || echo fail'?

[Comment 10 Martin Väth 2010-09-03 12:57:07 UTC]

(In reply to comment #9)
> but can you do something like 'time foo &> /dev/null || echo fail'?

It should not be the purpose of -q to suppress clear error messages.

Anyway, the whole bug should no longer be an issue (it is almost 2 years old):
Current versions of eix-sync measure time using date and calculate the
difference manually.