llvm dev - Jun 2016 - [llvm-foundation] apt repositories back!

Le 23/06/2016 à 19:13, Renato Golin a écrit :
> On 23 June 2016 at 17:56, Sylvestre Ledru via llvm-foundation
> <llvm-foundation at lists.llvm.org> wrote:
>> Thanks to the LLVM Foundation and Tanya, the apt repository is now
back:
>>
>> http://apt.llvm.org/
> Nice! Thanks everyone!
>
> Are we filtering multiple hits, or are we just assuming people will be
> using local caches?
What are you thinking about?
For now, the current configuration is a stupid apache serving the deb files.

Sylvestre

On 24 June 2016 at 13:36, Sylvestre Ledru <sylvestre at debian.org>
wrote:
> What are you thinking about?
> For now, the current configuration is a stupid apache serving the deb
files.
In the other thread, I think it was reported that the problem is too
many connections and people weren't using local cache, even though
they're mostly getting the same files on build systems.

Putting up another server up, unless it's bigger than the previous
one, won't hold for the same reason.

I suggested something like mod_evasive in a very friendly mode could
at least hold off the worst "offenders" and not break repo for
everyone else. Those offenders could them install / configure a local
cache.

But it was just a suggestion, if you don't think it's needed, that's
fine.

cheers,
--renato

I'm getting this warning on Ubuntu 16.04 about apt.llvm.org repo:

W: The repository 'http://apt.llvm.org/xenial llvm-toolchain-xenial
Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration
details.

On Fri, Jun 24, 2016 at 2:51 PM Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 24 June 2016 at 13:36, Sylvestre Ledru <sylvestre at debian.org>
wrote:
> > What are you thinking about?
> > For now, the current configuration is a stupid apache serving the deb
> files.
>
> In the other thread, I think it was reported that the problem is too
> many connections and people weren't using local cache, even though
> they're mostly getting the same files on build systems.
>
> Putting up another server up, unless it's bigger than the previous
> one, won't hold for the same reason.
>
> I suggested something like mod_evasive in a very friendly mode could
> at least hold off the worst "offenders" and not break repo for
> everyone else. Those offenders could them install / configure a local
> cache.
>
> But it was just a suggestion, if you don't think it's needed,
that's fine.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160704/e3159176/attachment.html>