Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 390965 - sys-apps/portage-2.1.10.37 elog syslog module produces one-character messages
Summary: sys-apps/portage-2.1.10.37 elog syslog module produces one-character messages
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks: 381649
  Show dependency tree
 
Reported: 2011-11-18 23:24 UTC by Navid Zamani
Modified: 2011-11-26 04:02 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Zamani 2011-11-18 23:24:38 UTC 
Hello, this turned up a couple of versions ago on my hardened x86 system.
I have portage configured to log to syslog via
  PORTAGE_ELOG_CLASSES="warn error log"
  PORTAGE_ELOG_SYSTEM="mail_summary syslog"
  …
in /etc/make.conf.
My log daemon is app-admin/metalog-2, but I doubt that makes a difference
I get log output as shown below.

Reproducible: Always

Steps to Reproduce:
1. Set portage to log to syslog as shown above. (You can remove the "mail_summary".)
2. emerge any package you want, provided it has some elog output.
3. When done, look at your system log file for that output.
Actual Results:  
It should look something like this:

Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: N
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: O
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: T
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: E
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: :
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst:  
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: B
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: e
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: g
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: i
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: n
                - Last output repeated twice -
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: i
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: n
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: g
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst:  
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: w
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: i
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: t
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst: h
Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: postinst:  

… and so on for hundreds or thousands of lines.

Expected Results:  
Obviously, the output should be in one line, not one character per line. :)

I have not seen such behavior on my ~amd64 desktop system.
Comment 1 Zac Medico gentoo-dev 2011-11-18 23:34:46 UTC 
This is fixed since 2.1.10.31 and 2.2.0_alpha71 by the following commit:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=12cb62465b130c21080281d78f7bfac077c17dfb
Comment 2 Navid Zamani 2011-11-19 00:38:03 UTC 
Ok, sorry but the title of my bug had the wrong version. As you can see in my bug report / first comment, the log output actually shows:

Nov 18 23:30:39 [portage] sys-apps/portage-2.1.10.35: …

So it was 2.1.10.35.

Sorry for the mistake. I fixed the bug title. But I will verify that it still happens with 2.1.10.35, as it clearly shouldn’t happen anymore, before changing the status back from “RESOLVED”.
Comment 3 Zac Medico gentoo-dev 2011-11-19 00:49:10 UTC 
I've tested here with the latest version and it worked fine.
Comment 4 Navid Zamani 2011-11-19 01:18:46 UTC 
Ok, thanks. We’ll keep it closed unless I see it again in my log file, even with the current version…
Comment 5 Navid Zamani 2011-11-25 19:11:02 UTC 
Ok, I just got the behavior again. With sys-apps/portage-2.1.10.37.
(In case it's relevant: I'm using app-admin/metalog-2 and hardened-sources-3.0.4-r4.)

Example from a couple of minutes ago:

Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: r
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: o
                - Last output repeated twice -
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: t
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: :
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: n
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: a
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: m
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: e
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: d
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst:  
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: /
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: {
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: e
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: t
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: c
Nov 25 19:50:51 [portage] net-dns/bind-9.7.4_p1: postinst: ,
…
Comment 6 Navid Zamani 2011-11-25 19:12:34 UTC 
Correction: I’m not getting it “again”, but “still”.
Comment 8 Navid Zamani 2011-11-25 20:46:14 UTC 
Ah, nice! Thanks, man!
Comment 9 Zac Medico gentoo-dev 2011-11-26 04:02:12 UTC 
This is fixed in 2.1.10.38 and 2.2.0_alpha78.