On 02/02/11 22:57, Peter Hercek wrote:
> On 02/02/2011 11:26 PM, Magnus Therning wrote:
>>
>>> A way to mitigate this would be to either keep at kill list of files
>>> to remove and when and/or having a separate repo for these archives.
>> Are there any tools that would make it easier to maintain s
On 02/02/2011 11:26 PM, Magnus Therning wrote:
A way to mitigate this would be to either keep at kill list of files
to remove and when and/or having a separate repo for these archives.
Are there any tools that would make it easier to maintain such a kill
list?
How about keeping the last two
On 02/02/11 22:16, Nicolas Pouillard wrote:
> On Wed, 02 Feb 2011 18:50:16 +0100, Peter Simons wrote:
>> Hi guys,
>>
>> yesterday, I tried to install "haskell-pandoc" on a Linux/i686 machine,
>> but Pacman was unable to download that binary package, because the file
>>
>> haskell-pandoc-1.6.0.1-
On Wed, 02 Feb 2011 18:50:16 +0100, Peter Simons wrote:
> Hi guys,
>
> yesterday, I tried to install "haskell-pandoc" on a Linux/i686 machine,
> but Pacman was unable to download that binary package, because the file
>
> haskell-pandoc-1.6.0.1-2-i686.pkg.tar.xz
>
> had been deleted from the s
Hi guys,
yesterday, I tried to install "haskell-pandoc" on a Linux/i686 machine,
but Pacman was unable to download that binary package, because the file
haskell-pandoc-1.6.0.1-2-i686.pkg.tar.xz
had been deleted from the server, probably because an update to version
1.8.0.1-1 had become availab
http://www.haskell.org/pipermail/haskell-cafe/2011-February/088829.html
Looks like they're still cleaning up after the attack.
On Tue, Feb 1, 2011 at 3:37 AM, Magnus Therning wrote:
> I used to be able to log in to community.haskell.org with an SSH key
> (I don't think I was ever given a passwor
