First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 127144
Alias:
Product:
Component:
Status: RESOLVED
Resolution: NEEDINFO
Assigned To: Gentoo Web Application Packages Maintainers <web-apps@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Michael Stewart (vericgar) (RETIRED) <vericgar@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 127144 depends on: 124440 Show dependency tree
Bug 127144 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-03-21 20:49 0000 
webapp-config conflicts with a new feature of portage: EMERGE_DEFAULT_OPTS

I have added --ask to this variable, and so every emerge acts like "--ask" is
passed to this. During certain steps, webapp-config calls emerge, and it seems
to hang because emerge is waiting for input.

Perhaps the IO could be handled in a way to display the emerge output and pass
the input back to it?

As a side note, typing "Yes" and hitting enter got to portage, so the action
continued. It just took me a bit to figure out what was going on.

------- Comment #1 From Gunnar Wrobel 2006-04-20 16:03:55 0000 ------- 

*** This bug has been marked as a duplicate of 124440 ***

------- Comment #2 From Michael Stewart (vericgar) (RETIRED) 2006-04-21 17:44:57 0000 ------- 
I do not believe this is a duplicate bug.

webapp-config is a seperate application from the eclass. Unless the application
itself is not going to call emerge, then this issue will not be fixed by
removing the emerge calls from the eclass.

------- Comment #3 From Gunnar Wrobel 2006-04-23 01:26:29 0000 ------- 
Hm, webapp-config never directly calls emerge. It imports portage though. It
does that in order to access portage.settings. I don't see how that could
trigger --ask. The webapp.eclass on the other hand contains a direct "emerge"
call that we still need to replace.

The portage version I have currently installed (2.0.54) does not provide the
EMERGE_DEFAULT_OPTS feature. So I guess I should upgrade to unstable for a
test. Which version features this new variable?

Can you give an example under which conditions webapp-config hangs? Does it
hang while you install/clean/upgrade and does it provide any output before it
stalls?

------- Comment #4 From Jakub Moc (RETIRED) 2006-10-25 12:04:53 0000 ------- 
vericgar, please reply to comment #3, thanks.
First Last Prev Next    No search results available      Search page      Enter new bug