* [gentoo-dev] Who hacked this terrible debug output into emerge ?
@ 2004-07-28 19:16 Jörg Schaible
2004-07-28 20:00 ` Tom Wesley
0 siblings, 1 reply; 3+ messages in thread
From: Jörg Schaible @ 2004-07-28 19:16 UTC (permalink / raw
To: gentoo-dev
Hi gang,
after syncing today I have a *lot* of debug output. Look at this below, if
any user can really tell you what the original developer of the gaim ebuild
try to say to him with the ewarns, you'll be lucky. IMHO this makes the
system quite useless.
Rgerads,
Jörg
======= %< ===========
>>> /usr/bin/gaim-remote
+ pkg_postinst
+ print_gaim_warning
+ ewarn
+ '[' no = yes ']'
+ echo -e ' * '
*
+ esyslog daemon.warning rc-scripts ''
+ return 0
+ return 0
+ ewarn 'If you are merging gaim-0.80 from an earlier version, you will
need'
+ '[' no = yes ']'
+ echo -e ' * If you are merging gaim-0.80 from an earlier version, you will
need'
* If you are merging gaim-0.80 from an earlier version, you will need
+ esyslog daemon.warning rc-scripts 'If you are merging gaim-0.80 from an
earlier version, you will need'
+ return 0
+ return 0
+ ewarn 'to re-merge any plugins like gaim-encryption or gaim-snpp.'
+ '[' no = yes ']'
+ echo -e ' * to re-merge any plugins like gaim-encryption or gaim-snpp.'
* to re-merge any plugins like gaim-encryption or gaim-snpp.
+ esyslog daemon.warning rc-scripts 'to re-merge any plugins like
gaim-encryption or gaim-snpp.'
+ return 0
+ return 0
+ ewarn
+ '[' no = yes ']'
+ echo -e ' * '
*
+ esyslog daemon.warning rc-scripts ''
+ return 0
+ return 0
+ ewarn 'If you experience problems with gaim, file them as bugs with'
+ '[' no = yes ']'
+ echo -e ' * If you experience problems with gaim, file them as bugs with'
* If you experience problems with gaim, file them as bugs with
+ esyslog daemon.warning rc-scripts 'If you experience problems with gaim,
file them as bugs with'
+ return 0
+ return 0
+ ewarn 'Gentoo'\''s bugzilla, http://bugs.gentoo.org. DO NOT report them'
+ '[' no = yes ']'
+ echo -e ' * Gentoo'\''s bugzilla, http://bugs.gentoo.org. DO NOT report
them'
* Gentoo's bugzilla, http://bugs.gentoo.org. DO NOT report them
+ esyslog daemon.warning rc-scripts 'Gentoo'\''s bugzilla,
http://bugs.gentoo.org. DO NOT report them'
+ return 0
+ return 0
+ ewarn 'as bugs with gaim'\''s sourceforge tracker, and by all means DO
NOT'
+ '[' no = yes ']'
+ echo -e ' * as bugs with gaim'\''s sourceforge tracker, and by all means
DO NOT'
* as bugs with gaim's sourceforge tracker, and by all means DO NOT
+ esyslog daemon.warning rc-scripts 'as bugs with gaim'\''s sourceforge
tracker, and by all means DO NOT'
+ return 0
+ return 0
+ ewarn 'seek help in #gaim.'
+ '[' no = yes ']'
+ echo -e ' * seek help in #gaim.'
* seek help in #gaim.
+ esyslog daemon.warning rc-scripts 'seek help in #gaim.'
+ return 0
+ return 0
+ ewarn
+ '[' no = yes ']'
+ echo -e ' * '
*
+ esyslog daemon.warning rc-scripts ''
+ return 0
+ return 0
+ ewarn 'Be sure to USE="debug" and include a backtrace for any seg'
+ '[' no = yes ']'
+ echo -e ' * Be sure to USE="debug" and include a backtrace for any seg'
* Be sure to USE="debug" and include a backtrace for any seg
+ esyslog daemon.warning rc-scripts 'Be sure to USE="debug" and include a
backtrace for any seg'
+ return 0
+ return 0
+ ewarn 'faults, see http://gaim.sourceforge.net/gdb.php for details on'
+ '[' no = yes ']'
+ echo -e ' * faults, see http://gaim.sourceforge.net/gdb.php for details
on'
* faults, see http://gaim.sourceforge.net/gdb.php for details on
+ esyslog daemon.warning rc-scripts 'faults, see
http://gaim.sourceforge.net/gdb.php for details on'
+ return 0
+ return 0
+ ewarn backtraces.
+ '[' no = yes ']'
+ echo -e ' * backtraces.'
* backtraces.
+ esyslog daemon.warning rc-scripts backtraces.
+ return 0
+ return 0
+ ewarn
+ '[' no = yes ']'
+ echo -e ' * '
*
+ esyslog daemon.warning rc-scripts ''
+ return 0
+ return 0
+ ewarn 'Please read the gaim FAQ at http://gaim.sourceforge.net/faq.php'
+ '[' no = yes ']'
+ echo -e ' * Please read the gaim FAQ at
http://gaim.sourceforge.net/faq.php'
* Please read the gaim FAQ at http://gaim.sourceforge.net/faq.php
+ esyslog daemon.warning rc-scripts 'Please read the gaim FAQ at
http://gaim.sourceforge.net/faq.php'
+ return 0
+ return 0
+ ewarn
+ '[' no = yes ']'
+ echo -e ' * '
*
+ esyslog daemon.warning rc-scripts ''
+ return 0
+ return 0
+ einfo
+ '[' no '!=' yes ']'
+ echo -e ' * '
*
+ return 0
+ einfo 'Note that we are now filtering all unstable flags in C[XX]FLAGS.'
+ '[' no '!=' yes ']'
+ echo -e ' * Note that we are now filtering all unstable flags in
C[XX]FLAGS.'
* Note that we are now filtering all unstable flags in C[XX]FLAGS.
+ return 0
+ einfo
+ '[' no '!=' yes ']'
+ echo -e ' * '
*
+ return 0
+ echo -ne '\a'
+ sleep 0.1
+ sleep 0,1
+ echo -ne '\a'
+ sleep 1
+ echo -ne '\a'
+ sleep 0.1
+ sleep 0,1
+ echo -ne '\a'
+ sleep 1
+ echo -ne '\a'
+ sleep 0.1
+ sleep 0,1
+ echo -ne '\a'
+ sleep 1
+ echo -ne '\a'
+ sleep 0.1
+ sleep 0,1
+ echo -ne '\a'
+ sleep 1
+ echo -ne '\a'
+ sleep 0.1
+ sleep 0,1
+ echo -ne '\a'
+ sleep 1
+ sleep 3
+ set +x
>>> Regenerating /etc/ld.so.cache...
============== %< ============
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] Who hacked this terrible debug output into emerge ?
2004-07-28 19:16 [gentoo-dev] Who hacked this terrible debug output into emerge ? Jörg Schaible
@ 2004-07-28 20:00 ` Tom Wesley
2004-07-28 21:08 ` [gentoo-dev] " Jörg Schaible
0 siblings, 1 reply; 3+ messages in thread
From: Tom Wesley @ 2004-07-28 20:00 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Wed, 2004-07-28 at 21:16 +0200, Jörg Schaible wrote:
> Hi gang,
>
> after syncing today I have a *lot* of debug output. Look at this below, if
> any user can really tell you what the original developer of the gaim ebuild
> try to say to him with the ewarns, you'll be lucky. IMHO this makes the
> system quite useless.
>
> Rgerads,
> Jörg
>
>
I only get this output with emerge -d gaim-remote, without the -d all
looks good.
From man emerge:
--debug (-d)
Tells emerge to run the emerge command in --debug mode. In this
mode the bash build environment will run with the -x option, causing it
to output verbose debug information to stdout. --debug is great for
finding bash syntax errors.
--
Tom Wesley <tom@tomaw.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-dev] Re: Who hacked this terrible debug output into emerge ?
2004-07-28 20:00 ` Tom Wesley
@ 2004-07-28 21:08 ` Jörg Schaible
0 siblings, 0 replies; 3+ messages in thread
From: Jörg Schaible @ 2004-07-28 21:08 UTC (permalink / raw
To: gentoo-dev
Tom Wesley wrote:
> I only get this output with emerge -d gaim-remote, without the -d all
> looks good.
>
> From man emerge:
> --debug (-d)
> Tells emerge to run the emerge command in --debug mode. In this
> mode the bash build environment will run with the -x option, causing it
> to output verbose debug information to stdout. --debug is great for
> finding bash syntax errors.
Hi Tom,
you're right, I looked into my bash history and I mistyped 'd' instead of
'D' as usual. So, sorry for the noise.
-- Jörg
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-07-28 21:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-28 19:16 [gentoo-dev] Who hacked this terrible debug output into emerge ? Jörg Schaible
2004-07-28 20:00 ` Tom Wesley
2004-07-28 21:08 ` [gentoo-dev] " Jörg Schaible
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox