1 |
I'm really at a loss here. I did inspect the directories that were failing, |
2 |
and they don't look any different than ones that updated correctly. Just to |
3 |
be safe, I tried changing ownership and group of the directories failing, but |
4 |
it still fails. As for 'tar -p', I just used haubi's prefix-launcher, and |
5 |
I don't think it does that. |
6 |
|
7 |
The only other related thing to note is that on the directory in question |
8 |
that is my EPREFIX, it's group is not the same as my primary group. e.g., |
9 |
instead of being owned by "mdmcmull:mdmcmull" it is "mdmcmull:p/gnu/admin", |
10 |
which I am a member of. I'm not sure if that's affecting it... but if it |
11 |
was, I would think it would continue failing even after I remove the |
12 |
affected directories. |
13 |
|
14 |
The only other note I'd have is that there does seem to be a substantial |
15 |
lag in the file system in question. Not sure if that might be contributing. |
16 |
|
17 |
Anyhow, I've got a valid workaround, so I'm happy for now :-). |
18 |
|
19 |
----- Original Message ----- |
20 |
From: "Peter Ansell" <ansell.peter@×××××.com> |
21 |
To: gentoo-alt@l.g.o |
22 |
Sent: Wednesday, November 7, 2007 3:13:00 PM (GMT-0600) America/Chicago |
23 |
Subject: Re: [gentoo-alt] [AIX] subversion failures |
24 |
|
25 |
I suspect at least the cross-platform .svn directories issue is not to |
26 |
blame as it was able to update a file previous to that. The only place |
27 |
that I have heard of where .svn directories conflict with hosts in any |
28 |
way is with ASP.NET web applications, which makes TortoiseSvn on |
29 |
windows use _svn directories instead. Deleting subdirectories followed |
30 |
by updating using the current directories .svn directory as a basis is |
31 |
a common way to restore directories using svn and as such is expected |
32 |
to work if the subdirectory was broken but the parent was not. |
33 |
|
34 |
I wonder what ls -la on the files and files/.svn directories would |
35 |
have looked like previous to deleting them. :) |
36 |
|
37 |
I get issues like that if I accidently attempt to do svn update using |
38 |
a different user btw. Ie, if I am in a root shell and I do that I have |
39 |
to chown all the directories back to my normal user before svn update |
40 |
works again as the normal user. Did you use the tar -p option by |
41 |
accident? |
42 |
|
43 |
Peter |
44 |
|
45 |
On 08/11/2007, Fabian Groffen <grobian@g.o> wrote: |
46 |
> On 07-11-2007 20:48:07 +0000, Marshall McMullen wrote: |
47 |
> > WOW, that worked!! After removing the affected broken directory, I had to so |
48 |
> > an "svn cleanup" then a "svn update" and it recreated the valgrind directory. |
49 |
> > I then tried another svn update from the top-level directory, and it bailed |
50 |
> > on another directory. I repeated the process above, and now it seems like |
51 |
> > it's syncing up properly /* crosses fingers */ |
52 |
> |
53 |
> That leads me to the following thoughts: |
54 |
> - the snapshot you used is rotten |
55 |
> - the tar program you used to extract the snapshot is rotten |
56 |
> - your filesystem is rotten |
57 |
> - .svn dirs aren't as cross-platform as they look like. |
58 |
> ... eh? |
59 |
> |
60 |
> -- |
61 |
> Fabian Groffen |
62 |
> Gentoo on a different level |
63 |
> -- |
64 |
> gentoo-alt@g.o mailing list |
65 |
> |
66 |
> |
67 |
-- |
68 |
gentoo-alt@g.o mailing list |
69 |
|
70 |
|
71 |
-- |
72 |
gentoo-alt@g.o mailing list |