First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 151086
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Harald van Dijk <truedfx@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dustin Polke <gentoobugs.20.dsurawicz@spamgourmet.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
make.conf.diff Diff of make.conf with working and not working line text/plain Dustin Polke 2006-10-12 16:33 0000 508 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 151086 depends on: Show dependency tree
Show dependency graph
Bug 151086 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-10-12 16:29 0000 
Ufed fails to parse make.conf if a comment in make.conf begins directly after
quotation mark. For example, see attached diff file.

Error message:

solaris dustin # ufed
Parse error in /etc/make.conf
Compilation failed in require at /usr/sbin/ufed line 9.
BEGIN failed--compilation aborted at /usr/sbin/ufed line 9.

------- Comment #1 From Dustin Polke 2006-10-12 16:33:01 0000 ------- 
Created an attachment (id=99488) [edit]
Diff of make.conf with working and not working line

------- Comment #2 From Dustin Polke 2006-10-13 01:13:04 0000 ------- 
Maybe I should mention that this is 0.40-r1.

------- Comment #3 From Harald van Dijk 2006-10-13 13:56:17 0000 ------- 
Thanks for the report, fixed in 0.40-r3 (without a revbump). I'm pretty sure
portage only treats # that way by accident or chance though: bash behaves as
ufed did. :)
First Last Prev Next    No search results available      Search page      Enter new bug