> Not yet, I'll post again when its finished.
Okay okay. Thanks for that work :-/
> There is no script that is in a shape that would be useful to anybody else,
> for starters you need to know about cases where it doesn't work correctly
> etc.
Yep.. I read some of the website's scripts, I think I
On Tuesday, September 1, 2015 at 10:42:20 AM UTC-4, Nathann Cohen wrote:
>
> Some time ago you sent a link toward a new webpage interface to upload
> tarballs. Is it what we should be using now? Should we update the
> developer's manual in any way?
>
Not yet, I'll post again when its finished.
> This is precisely why we need a self-service solution to managing tarballs,
> which is what I've been working on.
Some time ago you sent a link toward a new webpage interface to upload
tarballs. Is it what we should be using now? Should we update the
developer's manual in any way?
> like in the
OK I've updated the packages.
This is precisely why we need a self-service solution to managing tarballs,
which is what I've been working on. I for one don't have time to read 5
paragraphs of prose describing how to download and rename upstream tarballs
like in the linked ticket. And the chance
I can only confirm that the files aren't on the server. Volker has a
script for uploading them, so I'll assume he handles that. I'm not
100% sure how to do this (I'm guessing it's a matter of stuffing the
files in the correct repositories)
On Tue, Sep 1, 2015 at 10:44 AM, Michele Borassi
wrote:
Helloo!
Sorry, David already told me about this issue, but I forgot to tell you.
The problem is that, probably, the packages should be uploaded on the
servers. You can find the correct versions here:
igraph:
https://drive.google.com/file/d/0B5D_YOccuV6xNFFUYnZFYzg0bkk/view?usp=sharing
pyt
