First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 99079
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Karol Wojtaszek (RETIRED) <sekretarz@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Fabian Groffen <grobian@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
firebird-1.5.1.ebuild.patch small patch made to the ebuild patch Fabian Groffen 2005-07-15 00:50 0000 456 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

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

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







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

Description:   Opened: 2005-07-15 00:47 0000 
When emerging dev-db/firebird-1.5.1 before the install phase many sed errors
appear.  These are caused by a sed attempting to read a directory.  This can
easily be solved to make a cleaner (e)build output.

Reproducible: Always
Steps to Reproduce:
1. emerge "=dev-db/firefird-1.5.1"
2. watch the ebuild doing it's work, especially right after the install phase
has started
3.

Actual Results:  
many sed errors

Expected Results:  
be a little more cautious with what sed to feed and avoid those errors

------- Comment #1 From Fabian Groffen 2005-07-15 00:50:10 0000 ------- 
Created an attachment (id=63446) [edit]
small patch made to the ebuild

by telling find only to look for files, sed does not have to try to operate on
directories, which it doesn't know how to operate on.

------- Comment #2 From Karol Wojtaszek (RETIRED) 2005-07-31 11:43:09 0000 ------- 
Fixed in portage, thanks for help.
First Last Prev Next    No search results available      Search page      Enter new bug