C. Michael Pilato wrote:
> Branko Čibej wrote:
>
>> Hyrum K. Wright wrote:
>>
>>> We've run into a little bit of a problem with the 1.6.7 release. Just as I was preparing to roll the tarball this evening, Jack Repenning mailed me indicating there were problems with the Subversion instance on tigris.org. As a project, we've never used that instance, so normally this wouldn't be a problem. But in the wake of our migration to the ASF, we've co-opted the s.t.o Subversion instance to host our download tarballs. Since that instance is borked, we've got a problem.
>>>
>>> There is another upgrade to tigris.org which is supposed to roll out in January, which will fix these issues. I do not know if there is a temporary workaround or not, but Jack's suggestions were:
>>> - wait for the upgrade
>>> - use the Documents and files area for the actual file downloads, rather than Subversion commits to www/
>>> - find another download server
>>>
>>> Personally, I don't like any of them, and am hoping there is still some way of using Subversion commits to www/. Thoughts?
>>>
>>>
>> You can always point directly at the s.t.o repository for downloads, you
>> don't have to wait for the tarballs to appear (or not) in some other
>> place on tigris.org.
>>
>
> Nonono, don't do that! Apache will perform *much* better serving those
> files out of a working copy than directly from the repository.
>
Sure, but it's a stopgap that doesn't require a new download server. IMO
trying to get 1.6.7 on subverison.apache.org/dist is a lost cause, we'll
spend a month just bickering on general_at_incubator about whether all the
legalese is covered or not. (Sorry to any eavesdroppers but I was quite
unpleasantly surprised by some of the nonsense that passes as
"discussion" on that list.)
If the tigris.org issues are fixed, then of course we don't need to do that.
-- Brane
Received on 2009-12-22 21:23:37 CET