Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 131344 - sys-apps/portage-2.1_pre9-r4 and etc-update
Summary: sys-apps/portage-2.1_pre9-r4 and etc-update
Status: RESOLVED DUPLICATE of bug 130982
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-26 07:45 UTC by toto
Modified: 2006-04-29 02:22 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description toto 2006-04-26 07:45:21 UTC
After update sys-libs/glibc  to stable:
darkstar ~ # etc-update
Scanning Configuration files...
The following is the list of files which need updating, each
configuration file is followed by a list of possible replacement files.
1) /etc/host.conf (1)
Please select a file to edit by entering the corresponding number.
              (don't use -3 or -5 if you're unsure what to do)
              (-1 to exit) (-3 to auto merge all remaining files)
                           (-5 to auto-merge AND not use 'mv -i'):
/usr/sbin/etc-update: line 145: ((: == -5 : syntax error: operand expected (error token is "== -5 ")
/usr/sbin/etc-update: line 149: ((: == -3 : syntax error: operand expected (error token is "== -3 ")
/usr/sbin/etc-update: line 154: ((: == 0 : syntax error: operand expected (error token is "== 0 ")
/usr/sbin/etc-update: line 105: [: ==: unary operator expected
/usr/sbin/etc-update: line 105: [: ==: unary operator expected
The following is the list of files which need updating, each
configuration file is followed by a list of possible replacement files.

whith stable portage all ok
Comment 1 SpanKY gentoo-dev 2006-04-26 16:39:59 UTC

*** This bug has been marked as a duplicate of 130982 ***
Comment 2 Renato Caldas 2006-04-29 02:22:34 UTC
As a side note, please don't use something like "sys-apps/portage-2.1_pre9-r4 and etc-update" as a summary. A summary shouldn't be just the name of the components where the problem exists. It should be a _description_ of the problem.

Also, you should always post your "emerge --info" output.

Please read the bug posting FAQ before posting bug reports.