Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 23840 - output is too wordy when running emerge sync as normal user
Summary: output is too wordy when running emerge sync as normal user
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2003-07-01 17:35 UTC by David Grant
Modified: 2004-02-08 17:55 UTC (History)
0 users

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


Attachments
patch to fix this bug (emerge.patch,523 bytes, patch)
2004-01-06 16:09 UTC, David Grant
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David Grant 2003-07-01 17:35:57 UTC
The first small this is that if I run "emerge sync" as a normal user I get:

david@sidicpc21 david $ emerge sync
myaction sync
myopts []
emerge: root access required.

It really should just return "emerge: root access required".  I think the "my
action sync\nmyopts []" is unecessary.  Very small complaint indeed.

Reproducible: Always
Steps to Reproduce:
Comment 1 Michael Ihde 2003-07-28 19:12:07 UTC
On a similar note, when running emerge sync as a regular user you get the message

*** Please add this user to the portage group if you wish to use portage.

However a user probably would not be able to add themselves to the portage group.  Perhaps it should read

*** Please ask the system administrator to add you to the portage group if you wish to use portage.

 
Comment 2 David Grant 2003-10-21 12:36:00 UTC
Can we get this bug finished up?  It shouldn't be too difficult.
Comment 3 David Grant 2004-01-06 16:09:48 UTC
Created attachment 23269 [details, diff]
patch to fix this bug
Comment 4 Masatomo Nakano (RETIRED) gentoo-dev 2004-01-19 17:56:46 UTC
Fixed in CVS
Comment 5 Marius Mauch (RETIRED) gentoo-dev 2004-02-08 17:55:06 UTC
supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.