Bug 253336 – portage-2.1.6.4: ebuild ....ebuild merge misses output

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Peter Volkov (RETIRED) 2009-01-01 09:29:08 UTC]

Please, take a look at the following output:

localhost libnotify # ebuild libnotify-0.4.5.ebuild merge
Disabling noauto in features... merge disables it. (qmerge doesn't)
[snipping checksums since they are [ ok ] ]
>>> Checking libnotify-0.4.5.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that 'libnotify-0.4.5' is already compiled; skipping.
>>> Remove '/vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/.compiled' to force compilation.
>>> Test phase [not enabled]: x11-libs/libnotify-0.4.5

>>> Install libnotify-0.4.5 into /vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/image/ category x11-libs
[snip useful output]
>>> Completed installing libnotify-0.4.5 into /vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/image/

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment
   usr/bin/notify-send
   usr/lib64/libnotify.so.1.1.3
   usr/lib64/libnotify.a
removing executable bit: usr/lib64/libnotify.la
localhost libnotify #

Between "removing executable bit: usr/lib64/libnotify.la" and shell "localhost libnotify # " there is no output although package was installed.

[Comment 1 Serkan Kaba (RETIRED) 2009-01-01 10:08:16 UTC]

I thought this was a feature.

[Comment 2 Zac Medico 2009-01-01 10:16:46 UTC]

Since bug #186842, the previous "quiet" behavior is default. The emerge --verbose option triggers the verbose output. The ebuild command does not currently have such an option, but we can add it.

[Comment 3 Peter Volkov (RETIRED) 2009-01-01 10:44:34 UTC]

Probably another way to solve this bug is to enable verbose for ebuild command always. I think if user uses ebuild command he already touches enough low level to see everything happening there.

[Comment 4 Zac Medico 2009-01-03 01:20:32 UTC]

Created attachment 177175 [details, diff]
display files during merge by default

(In reply to comment #3)
> Probably another way to solve this bug is to enable verbose for ebuild command
> always. I think if user uses ebuild command he already touches enough low level
> to see everything happening there.

Seems reasonable. Serkan, do you want a --quiet option to disable this?

[Comment 5 Serkan Kaba (RETIRED) 2009-01-03 07:08:33 UTC]

(In reply to comment #4)
> Created an attachment (id=177175) [edit]
> display files during merge by default
> 
> (In reply to comment #3)
> > Probably another way to solve this bug is to enable verbose for ebuild command
> > always. I think if user uses ebuild command he already touches enough low level
> > to see everything happening there.
> 
> Seems reasonable. Serkan, do you want a --quiet option to disable this?
> 

I have no preference. Thanks.

[Comment 6 Zac Medico 2009-01-12 20:14:18 UTC]

This is fixed in 2.1.6.5 and 2.2_rc21.