| 1 |
Mark Knecht wrote: |
| 2 |
> Right. I misspoke. New use flags, not new a package. |
| 3 |
> |
| 4 |
> However the outcome is consistent. It says it's 'fetching' because |
| 5 |
> it's responding to the idea that there's a new use flag, but then |
| 6 |
> fetches nothing because the file is already here and builds nothing |
| 7 |
> because it's already been built. |
| 8 |
> |
| 9 |
> It's not a big deal. The machine is fine. Everything is consistent as |
| 10 |
> far as I know. However some portion of the download logic in emerge is |
| 11 |
> confused. |
| 12 |
> |
| 13 |
> I've seen this sort of thing a few times in the past but it's always |
| 14 |
> cleared up in a day or two. This one has gone on for weeks. |
| 15 |
> |
| 16 |
> Note that I do use ~amd64 on portage& eix. Maybe it's a bug that |
| 17 |
> hasn't been cleaned up yet. |
| 18 |
> |
| 19 |
> So, following through, there does appear to be a new flag setting |
| 20 |
> (-gdu) however it's not triggered emerging @world even though packages |
| 21 |
> on the system require gvfs according to equery. |
| 22 |
> |
| 23 |
> Somethings inconsistent. (Possibly my brain!) |
| 24 |
> |
| 25 |
> Cheers, |
| 26 |
> Mark |
| 27 |
> |
| 28 |
> c2stable ~ # emerge -pvDuN gvfs |
| 29 |
> |
| 30 |
> These are the packages that would be merged, in order: |
| 31 |
> |
| 32 |
> Calculating dependencies... done! |
| 33 |
> [ebuild R ] gnome-base/gvfs-1.4.3-r1 USE="gnome http udev |
| 34 |
> -archive -avahi -bash-completion -bluetooth -cdda -doc -fuse -gdu* |
| 35 |
> -gnome-keyring -gphoto2 -hal -samba" 0 kB |
| 36 |
> |
| 37 |
> Total: 1 package (1 reinstall), Size of downloads: 0 kB |
| 38 |
> c2stable ~ # emerge -pvDuN @world |
| 39 |
> |
| 40 |
> These are the packages that would be merged, in order: |
| 41 |
> |
| 42 |
> Calculating dependencies... done! |
| 43 |
> |
| 44 |
> Total: 0 packages, Size of downloads: 0 kB |
| 45 |
> c2stable ~ # equery depends gvfs |
| 46 |
> * These packages depend on gvfs: |
| 47 |
> app-cdr/brasero-2.28.3 (gnome-base/gvfs) |
| 48 |
> gnome-base/gnome-2.28.2 (>=gnome-base/gvfs-1.4.3[gdu]) |
| 49 |
> gnome-base/libgnome-2.28.0 (gnome-base/gvfs) |
| 50 |
> gnome-base/nautilus-2.28.4-r1 (>=gnome-base/gvfs-0.1.2) |
| 51 |
> c2stable ~ # |
| 52 |
> |
| 53 |
> |
| 54 |
> Just curious. |
| 55 |
> |
| 56 |
> Cheers, |
| 57 |
> Mark |
| 58 |
> |
| 59 |
> |
| 60 |
|
| 61 |
What does it do when you run: |
| 62 |
|
| 63 |
emerge -vDuN gvfs |
| 64 |
|
| 65 |
It should start to compile the package. Keep in mind, if you use the -f |
| 66 |
option, it will fetch but not compile or anything else. I used to use |
| 67 |
that back when I was on dial-up, which sucked by the way. Even this |
| 68 |
slow DSL is about 30 times faster than my old dial-up. lol It *should* |
| 69 |
only fetch it once tho unless it fails the checksum thingy. Portage |
| 70 |
should give you a error message tho. |
| 71 |
|
| 72 |
Dale |
| 73 |
|
| 74 |
:-) :-) |
Archives