Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 76178
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Ahlberg (RETIRED) <aliz@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: David Ripton <dripton@ripton.net>
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 76178 depends on: Show dependency tree
Bug 76178 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: 2004-12-30 15:20 0000 
I did an emerge -e world, and it blocked on app-misc/dnetc-2.9008.490, waiting
for me to supply interactive configuration input.  (It wanted me to enter my
email address, as if I'd typed "dnetc -config")  This cost me a few hours of
compiling time.

Of course, Gentoo ebuilds are not supposed to do that.  A long emerge should be
able to run to error or completion unattended.

My email address was already in /etc/conf.d/dnetc, anyway.

I think the pkg_preinst step that calls "/opt/distributed.net/dnetc -quiet
-flush" is the problem.  dnetc is being too "smart" and implicitly doing
-config even though that option wasn't given.  Maybe this step should be
removed, and a comment asking the user to do it himself added?

------- Comment #1 From Daniel Ahlberg (RETIRED) 2005-01-01 06:21:23 0000 ------- 
I've made some modifications so it uses the same configuration as the
initscript. Please test the new 2.9009.494 version.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug