| Summary: | Fetching seems to be stopped | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Dennis Winter <d.w.79> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | Keywords: | InVCS |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 216231 | ||
(In reply to comment #0) > During fetching I get the following message and it seems to be stopped: > > >>> Emerging (2 of 4) sys-apps/usermode-utilities-20040406-r1 to / > Downloading 'uml_utilities_20040406.tar.bz2'... see /var/log/emerge-fetch.log > for details. > ^C Did you look in /var/log/emerge-fetch.log to see if it appeared to be fetching? If it's fetching correctly then there's no need to press ^C. If you don't like parallel-fetch the you can add FEATURES="-parallel-fetch" to /etc/make.conf. It's been enabled by default in portage-2.1.5 since most people seem to like it. If this is about parallel fetching, than this is indeed neither a bug nor a problem, but it would be nice to have a short note in the error message, that would clearify it. And yes, it seems to be fetching, since after a restart the new fetching process starts higher than 0%. Maybe something like this be more clear: Downloading 'uml_utilities_20040406.tar.bz2' in a background process. See /var/log/emerge-fetch.log for details. Here's what the new message will look like: * Fetching 'uml_utilities_20040406.tar.bz2' in the background. To * view fetch progress, run `tail -f /var/log/emerge-fetch.log` in * another terminal. This is fixed in 2.1.5_rc3. |
During fetching I get the following message and it seems to be stopped: >>> Emerging (2 of 4) sys-apps/usermode-utilities-20040406-r1 to / Downloading 'uml_utilities_20040406.tar.bz2'... see /var/log/emerge-fetch.log for details. ^C ##### * This problem is not limited to this particular ebuild, but a general problem. * The problem occurs only if you emerge more than 1 ebuilds and never with the first ebuild * Thus a restart resolves the problem BUT actually after the restart it "resumes" the fetching process, therfore it is most probably not a problem in the actual fetching process but in the feedback to the user. In any case it is a little bit distracting. Reproducible: Sometimes Steps to Reproduce: It just happens from time to time