Travis CI on Linux will be broken for the coming time:

http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html

:(

On Wednesday, 1 June 2016 at 20:21:36 UTC, Johan Engelen wrote:
> Travis CI on Linux will be broken for the coming time:
>
> http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html
>
> :(

can't you push the deb package in a Github repo (or somewhere else with free traffic) and download it from there?

On Wednesday, 1 June 2016 at 21:01:34 UTC, Seb wrote:
> On Wednesday, 1 June 2016 at 20:21:36 UTC, Johan Engelen wrote:
>> Travis CI on Linux will be broken for the coming time:
>>
>> http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html
>>
>> :(
>
> can't you push the deb package in a Github repo (or somewhere else with free traffic) and download it from there?

But who builds the packages?

(for Windows, we build our own LLVM trunk package (two needed), and for Mac we use Homebrew packages for LLVM3.8)

On Friday, 3 June 2016 at 17:47:09 UTC, Johan Engelen wrote:
> On Wednesday, 1 June 2016 at 21:01:34 UTC, Seb wrote:
>> On Wednesday, 1 June 2016 at 20:21:36 UTC, Johan Engelen wrote:
>>> Travis CI on Linux will be broken for the coming time:
>>>
>>> http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html
>>>
>>> :(
>>
>> can't you push the deb package in a Github repo (or somewhere else with free traffic) and download it from there?
>
> But who builds the packages?
>
> (for Windows, we build our own LLVM trunk package (two needed), and for Mac we use Homebrew packages for LLVM3.8)

The LLVM team?
Maybe a simple wget is enough:

http://llvm.org/releases/download.html


Otherwise as said if you still have the LLVM deb packages, you could mirror them somewhere.

On Saturday, 4 June 2016 at 03:47:45 UTC, Seb wrote:
> On Friday, 3 June 2016 at 17:47:09 UTC, Johan Engelen wrote:
>> On Wednesday, 1 June 2016 at 21:01:34 UTC, Seb wrote:
>>> On Wednesday, 1 June 2016 at 20:21:36 UTC, Johan Engelen wrote:
>>>> Travis CI on Linux will be broken for the coming time:
>>>>
>>>> http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html
>>>>
>>>> :(
>>>
>>> can't you push the deb package in a Github repo (or somewhere else with free traffic) and download it from there?
>>
>> But who builds the packages?
>>
>> (for Windows, we build our own LLVM trunk package (two needed), and for Mac we use Homebrew packages for LLVM3.8)
>
> The LLVM team?
> Maybe a simple wget is enough:
>
> http://llvm.org/releases/download.html

Huh? I thought those were Clang release-only packages, but I see that it contains development libraries too. We can trim down those packages (clang is not needed), put them somewhere for download, wget+unpack, and done.

thanks,
  Johan

On Saturday, 4 June 2016 at 07:41:33 UTC, Johan Engelen wrote:
> On Saturday, 4 June 2016 at 03:47:45 UTC, Seb wrote:
>>
>> The LLVM team?
>> Maybe a simple wget is enough:
>>
>> http://llvm.org/releases/download.html
>
> Huh? I thought those were Clang release-only packages, but I see that it contains development libraries too. We can trim down those packages (clang is not needed), put them somewhere for download, wget+unpack, and done.

CircleCI is back!
(LLVM 3.8.0 instead of 3.9trunk)
https://github.com/ldc-developers/ldc/pull/1541

Travis uses Ubuntu 12 for which I did not find packages on llvm.org... :(

On 3 Jun 2016, at 18:47, Johan Engelen via digitalmars-d-ldc wrote:
> But who builds the packages?

I think it would make sense to raise this point on the LLVM mailing list. Having APT packages available makes it easy for other projects to provide immediate feedback about the state of trunk, so I think it would be in the interest of the upstream devs to keep the packages available. Presumably, most of the traffic comes from CI systems, and there might be a simple solution to that.

 — David

On Saturday, 4 June 2016 at 20:32:50 UTC, David Nadlinger wrote:
> On 3 Jun 2016, at 18:47, Johan Engelen via digitalmars-d-ldc wrote:
>> But who builds the packages?
>
> I think it would make sense to raise this point on the LLVM mailing list. Having APT packages available makes it easy for other projects to provide immediate feedback about the state of trunk, so I think it would be in the interest of the upstream devs to keep the packages available. Presumably, most of the traffic comes from CI systems, and there might be a simple solution to that.

I am keeping an eye on the LLVM maillist discussion. Many people use the APT repos (hence the traffic ;)), and it seems LLVM wants to maintain something like it.

-Johan

On 4 Jun 2016, at 22:45, Johan Engelen via digitalmars-d-ldc wrote:
> I am keeping an eye on the LLVM maillist discussion. Many people use the APT repos (hence the traffic ;)), and it seems LLVM wants to maintain something like it.

Seems like there was a split in the thread archive, since I only found the first couple of posts. Thanks for keeping track of this!

 — David