Summary: | "Starting parallel fetch" message is displayed even when no fetching is needed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David <write2David> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | CC: | xmw |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 377365, 459934 |
Description
David
2011-05-22 02:05:47 UTC
Well, you can fetch no files in a parallel style. (In reply to comment #0) > Total: 13 packages (12 upgrades, 1 in new slot, 13 binaries), Size of > downloads: 0 kB The 0 kB display is only shown with the --verbose display code. While we could save this info and use it to avoid parallel-fetch in some cases, it makes little sense to do so. > > Would you like to merge these packages? [Yes/No] yes > > >>> Starting parallel fetch > > > ------------- > > Note especially the line "Size of downloads: 0 kB" > > (Yes, in the above example, I did also pre-build (but not install) these > packages, using 'emerge -B') > > Expected Results: > Since emerge knows it does *not* have to fetch any files, I'd expect that it > would not tell me that it *is* fetching files. What it will actually do in this case is, in parallel to and scheduled builds, got through the merge list and use the stat function to verify that all of the required files are the correct sizes. (In reply to comment #1) > Well, you can fetch no files in a parallel style. Ha ha. :-) Hey, myself and some others may not be able to provide lots of help on the technical side of Gentoo, but I'm trying to at least do what I can to help Gentoo and make some helpful comments on the UI stuff from the regular user's perspective (even if they are sometimes minor things). From a UI design perspective, I think it's probably better to show the "Starting parallel fetch" message every time regardless of the fetch state shown in the --verbose output. Otherwise, variance in behavior could be confusing since it could lead people to wonder why the output between two seemingly identical invocations is different (especially when --verbose is not enabled). I suppose that we could eliminate the "Starting parallel fetch" message entirely, since it's not really an essential notification. (In reply to comment #5) > I suppose that we could eliminate the "Starting parallel fetch" message > entirely, since it's not really an essential notification. I agree. To most people it gives the impression that fetching is occurring, even though it is not. 1.5 years later... Awaiting further comment? or perhaps this item is dead? (In reply to comment #5) > I suppose that we could eliminate the "Starting parallel fetch" message > entirely, since it's not really an essential notification. Done: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ff864a499160f3abda33e7247e0e457bd7ba4270 This is fixed in 2.1.11.53 and 2.2.0_alpha164. |