Bug 336595 – sys-apps/portage: With --quiet, don't display "Global Updates" message

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Jeremy Olexa (darkside) (RETIRED) 2010-09-09 13:44:25 UTC]

It is cluttering up my cron email. Please consider, thanks. Specifically, this message:

"Performing Global Updates: /home/prefix/www/htdocs/gentoo-portage-prefix/profiles/updates/3Q-2010
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
........."

[Comment 1 Zac Medico 2010-09-09 14:16:52 UTC]

It might be confusing about what's going on if we make it totally silent. Maybe a good compromise would be to omit everything except these parts:

Performing Global Updates:
/home/prefix/www/htdocs/gentoo-portage-prefix/profiles/updates/3Q-2010

[Comment 2 Jeremy Olexa (darkside) (RETIRED) 2010-09-09 16:12:45 UTC]

It is a delicate balance of quiet vs verbose and we have both --quiet and --verbose. I don't see how it would be confusing because most people assume that updates are being applied and don't need to see confirmation. Can you even turn updates off?

[Comment 3 Zac Medico 2010-09-09 16:51:39 UTC]

Well FEATURES=fixpackages can be toggled. There's also a --package-moves=n emerge option that was added recently.

My problem with making it dead silent is that it can be time consuming and I don't want people confused what's happening during that time.

If you don't want to see it in your cron logs, why don't you send stdout to /dev/null? That way you'll still have stderr in case there are any relevant error messages.

[Comment 4 Sebastian Luther (few) 2010-09-09 17:12:54 UTC]

What it prints there is imo useless information for almost all users. What about this:

with -q:
Performing Global Updates

without -q:
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)

with --debug:
<the current output>

[Comment 5 Jeremy Olexa (darkside) (RETIRED) 2010-09-09 18:02:40 UTC]

(In reply to comment #3)
> Well FEATURES=fixpackages can be toggled. There's also a --package-moves=n
> emerge option that was added recently.

ah, didn't realize this new(to me) option.
 
> My problem with making it dead silent is that it can be time consuming and I
> don't want people confused what's happening during that time.

understood.
 
> If you don't want to see it in your cron logs, why don't you send stdout to
> /dev/null? That way you'll still have stderr in case there are any relevant
> error messages.

I don't care to see the useless (to me) message about global updates but want to see everything else that -q outputs.


(In reply to comment #4)
> What it prints there is imo useless information for almost all users. What
> about this:

my point. :)
 
> with -q:
> Performing Global Updates
> 
> without -q:
> Performing Global Updates
> (Could take a couple of minutes if you have a lot of binary packages.)
> 
> with --debug:
> <the current output>

Acceptable. But can it be made to say "Performing Global Updates" only once instead of N times (where N is the number of files in $PORTDIR/profiles/updates/)? On a new install (or in my case, a nightly bootstrapping email) this takes up lots of room and is redundant.

[Comment 6 Zac Medico 2010-09-10 00:03:54 UTC]

(In reply to comment #4)
Sounds good.

For some extra friendliness, we might show a special message for each package from the world set that's been moved.

[Comment 7 Zac Medico 2010-09-10 00:05:25 UTC]

(In reply to comment #5)
> Acceptable. But can it be made to say "Performing Global Updates" only once
> instead of N times (where N is the number of files in
> $PORTDIR/profiles/updates/)?

Certainly. It's ridiculous as it is. :)

[Comment 8 Sebastian Luther (few) 2010-09-10 10:24:03 UTC]

I proposed a patch that does the following:

$ emerge --ignore-default-opts -1p portage 

Performing Global Updates:
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
/var/lib/layman/sage-on-gentoo/profiles/updates/3Q-2010.
/usr/portage/profiles/updates/1Q-2004.........................................
/usr/portage/profiles/updates/2Q-2004................................................................................................................
/usr/portage/profiles/updates/3Q-2004...............................................................................................................................................................................................
[...]


$ emerge --ignore-default-opts -1pq portage 

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)

[Comment 9 Zac Medico 2010-09-10 14:52:57 UTC]

This should be fixed by these two commits:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7eb3f27caee118d3452ac8670b6de9067ff3557c
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=465e8facba7deffea50d76e8be03badc14927fb3

[Comment 10 Zac Medico 2010-09-10 20:29:38 UTC]

This is fixed in 2.1.9.3 and 2.2_rc79.