1 |
On Tue, 2005-10-18 at 16:50 -0400, Dave Nebinger wrote: |
2 |
> On Tuesday 18 October 2005 04:34 pm, Holly Bostick wrote: |
3 |
> > > For Holly's case, I'm wondering if she's syncing against a system |
4 |
> > > that doesn't mirror that file from upstream? Just a guess. |
5 |
> > |
6 |
> > I sync against the Netherlands rsync pool, |
7 |
> > SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage". |
8 |
> > |
9 |
> > I suppose what you say is possible, but does not seem to be the case. |
10 |
> |
11 |
> I figured you sync'd daily Holly; I wouldn't have expected any less. ;-) |
12 |
> |
13 |
> The question is, however, if you and I both sync daily and, although file |
14 |
> times suggest they have been updated, but the file contents are different, |
15 |
> where would the problem lie? |
16 |
> |
17 |
> The only guess I could come up with is the upstream mirror. I sync against |
18 |
> http://gentoo.osuosl.org/, and you're syncing against the netherlands pool. |
19 |
> Either one themselves could be sync'd against another mirror which is sync'd |
20 |
> against another mirror... |
21 |
> |
22 |
> Somewhere along the line I'm guessing that perhaps this particular file is not |
23 |
> fetched/updated for some reason which would leave one of us with an outdated |
24 |
> copy. |
25 |
> |
26 |
> I know mine comes out of CVS with the header |
27 |
> $Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1502 2005/10/18 |
28 |
> 00:03:00 vapier Exp $, so I'm guessing that I have the later file. |
29 |
> |
30 |
spider@Darkmere> cvs up use.local.desc ; grep vim-with-x use.local.desc |
31 |
|
32 |
app-editors/vim:vim-with-x - Linking console vim against X11 libraries |
33 |
to enable title and clipboard features in xterm |
34 |
|
35 |
|
36 |
spider@Darkmere> head -n 4 use.local.desc |tail -n 2 |
37 |
# $Header: /var/cvsroot/gentoo-x86/profiles/use.local.desc,v 1.1505 |
38 |
2005/10/18 20:18:45 agriffis Exp $ |
39 |
|
40 |
|
41 |
//Spider |
42 |
|
43 |
-- |
44 |
begin .signature |
45 |
Tortured users / Laughing in pain |
46 |
See Microsoft KB Article Q265230 for more information. |
47 |
end |