Community
Participate
Working Groups
We've discussed this before ... maybe email? ... but I can't find it now. In short, I need directories on 'archive' to put released repos. Or, part of them, actually. Some details are documented in bug 330134. I need (write access to) .../releases/helios and .../releases/indigo (at least to start with). There is a 'releases' on archives, already, and I would create them myself ... but ... drwxr-s--- 4 root root 1K 2010-11-15 13:30 releases/ Thanks,
I've made you the owner of releases: drwxr-s--- 4 david_williams root 96 Nov 15 13:30 releases The way it's set up now, our web servers cannot access that directory nor its contents. Although I don't know why it's like that, I can't help but think we did that on purpose. Do you know?
(In reply to comment #1) > > The way it's set up now, our web servers cannot access that directory nor its > contents. Although I don't know why it's like that, I can't help but think we > did that on purpose. Do you know? No. No reason I can think of. And seems like we would want them to be able to ... well ... that is, if we want to put old released repos there. And, some of those old ones, based on old update manager, might not be as easy to "move". The p2 based one should be more easily "movable". Separate issue, but can we leave old ones like Europa and Ganymede in place, and just exclude from mirroring? Back to this issue ... are you saying they are "not accessible" based on no "other" permissions? There as been a quirk, in the past, that cvs subdirectories won't "replicate" to web servers unless there are literally files in parent directory ... but, not sure that's relevant here ... just in case.
(In reply to comment #2) > Back to this issue ... are you saying they are "not accessible" based on no > "other" permissions? Yes, since the Apache user is in the "other" group. At any rate, I think we're done here?
> > At any rate, I think we're done here? Probably. I have, just now, changed 'releases' to o=rx. I still can't "read" a file from there via http, but assume it just takes a while for that permission change to "take effect". My test case is http://archive.eclipse.org/releases/indigo/201012170900/aggregate/artifacts.jar I'll re-open if I can't access it later today. Thanks so much.
> > I still can't "read" a file from there via http, but assume it just takes a > while for that permission change to "take effect". My test case is > > http://archive.eclipse.org/releases/indigo/201012170900/aggregate/artifacts.jar > I can read it now.
