askell.org/cabal/release/
>>>
>>> (admins, note: I just changed the nginx.conf directly, we need to backport
>>> all our changes into the full deploy scripts…)
>>>
>>> —Gershom
>>>
>>> On March 15, 2015 at 3:18:52 AM, Miëtek Bak (mie..
t;>
>> (admins, note: I just changed the nginx.conf directly, we need to backport
>> all our changes into the full deploy scripts…)
>>
>> —Gershom
>>
>> On March 15, 2015 at 3:18:52 AM, Miëtek Bak (mie...@bak.io) wrote:
>>> There are at two problem
te: I just changed the nginx.conf directly, we need to backport
> all our changes into the full deploy scripts…)
>
> —Gershom
>
> On March 15, 2015 at 3:18:52 AM, Miëtek Bak (mie...@bak.io) wrote:
>> There are at two problems with the Cabal webpage on haskell.org:
>>
>>
are at two problems with the Cabal webpage on haskell.org:
>
>
> 1. The release directories are no longer browseable, as attempting to list
> their contents
> fails with 403 errors.
>
> Being able to browse these directories was probably the only way to locate
&g
Hi,
On 18 March 2015 at 22:55, Gershom B wrote:
> Mitek: Go ahead and send on a public ssh key to admin@ and we'll get
> you access to that portion of the site.
A better idea is to upload the website's source files to GitHub and
let people send us pull requests there. I can do that if someone gi
ing-a-release
Sound good?
Cheers,
Gershom
On Sun, Mar 15, 2015 at 3:18 AM, Miëtek Bak wrote:
> There are at two problems with the Cabal webpage on haskell.org:
>
>
> 1. The release directories are no longer browseable, as attempting to list
> their contents fails with 403 error
There are at two problems with the Cabal webpage on haskell.org:
1. The release directories are no longer browseable, as attempting to list
their contents fails with 403 errors.
Being able to browse these directories was probably the only way to locate
binary downloads for releases older
