| Summary: | emerge-webrsync does not give any error message when dns fails | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | maximilian haeussler <maximilianh> |
| Component: | Tools | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
maximilian haeussler
2004-10-05 03:25:48 UTC
when a newbie-user follows the installation instructions but forgets to copy over resolv.conf and has a firewall which does not allow rsync to pass, he will run emerge-webrsync, as instructed by the manual. It will not work, of course, as there is no dns server. but the emerge-webrsync will silently fail, not outputting any message and a new user won´t notice, as he does not know anything about the portage tree. so he will continue with the installation manual, where from now on everything involving emerge will fail. very frustrating. Reproducible: Always Steps to Reproduce: install gentoo, forget to copy resolv.conf Expected Results: I suggest motifyfing the emerge-webrsync script somehow to report "hey, no dns you foolish idiot!", I just don´t know how, as I myself am this newbie user... Discovering that from a script is not particularly easy. The failure message is the FETCHCOMMAND's business... not portage. |
