jll@euclid:~/dlang$ ./install.sh dmd
Downloading and unpacking http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz
######################################################################### 100.0%
Invalid signature http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz.sig

Same problem with 'install update'. But not when installing ldc or gdc.

On Friday, 10 August 2018 at 13:19:21 UTC, Jean-Louis Leroy wrote:
> jll@euclid:~/dlang$ ./install.sh dmd
> Downloading and unpacking http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz
> ######################################################################### 100.0%
> Invalid signature http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz.sig
>
> Same problem with 'install update'. But not when installing ldc or gdc.

It may be this:
https://issues.dlang.org/show_bug.cgi?id=19100

On Friday, 10 August 2018 at 13:52:19 UTC, bachmeier wrote:
> On Friday, 10 August 2018 at 13:19:21 UTC, Jean-Louis Leroy wrote:
>> jll@euclid:~/dlang$ ./install.sh dmd
>> Downloading and unpacking http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz
>> ######################################################################### 100.0%
>> Invalid signature http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz.sig
>>
>> Same problem with 'install update'. But not when installing ldc or gdc.
>
> It may be this:
> https://issues.dlang.org/show_bug.cgi?id=19100

Probably not. I am trying to install dmd on a new machine I got in June.

On Friday, 10 August 2018 at 13:19:21 UTC, Jean-Louis Leroy wrote:
> jll@euclid:~/dlang$ ./install.sh dmd

Is there anything specific about your machine?
We ship our own keyring on the first usage of the install.sh script, which will get stored to ~/dlang/d-keyring.gpg

You can do the following to check the current keyring:

> gpg --no-default-keyring --keyring ~/dlang/d-keyring.gpg --list-keys

You should see a similar output as on https://dlang.org/gpg_keys.html
Also:

> sha256sum ~/dlang/d-keyring.gpg
4de1bb6028bb1e3d4eefd9e1a1651ad6c372ead0482b63e3aafdfdc0fbb48dbd  /home/seb/dlang/d-keyring.gpg

However, if this is really the issue I don't know how you could have ended up with an old keyring on a new machine. So please provide all the input and information about your machine that could be relevant. Thanks!


> Same problem with 'install update'. But not when installing ldc or gdc.

That's because they don't ship signed binaries ;-)

On Friday, 10 August 2018 at 13:19:21 UTC, Jean-Louis Leroy wrote:
> jll@euclid:~/dlang$ ./install.sh dmd
> Downloading and unpacking http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz
> ######################################################################### 100.0%
> Invalid signature http://downloads.dlang.org/releases/2.x/2.081.1/dmd.2.081.1.linux.tar.xz.sig
>
> Same problem with 'install update'. But not when installing ldc or gdc.

Seb and I found the issue (TLDR: fix here: https://github.com/dlang/installer/pull/338)

The problem is downloading "install.sh" directly to "~/dlang/install.sh".  This causes the install script to think that it has already downloaded the "d-keyring.gpg" so it never downloads it, causing the "invalid signature" error.  The fix is to download "install.sh" if the d-keyring is not downloaded, even if install.sh already is.

What made it more confusing is that if it doesn't download d-keyring.gpg, then it will create a default one...making you think it was downloaded but it actually wasn't...odd.  In your case you'll want to manually remove "~/dlang/d-keyring.gpg" and use the new "install.sh" script after PR 338 is merged/deployed.

On Monday, 13 August 2018 at 17:10:13 UTC, Jonathan Marler wrote:
> Seb and I found the issue (TLDR: fix here: https://github.com/dlang/installer/pull/338)
>
> ...
> What made it more confusing is that if it doesn't download d-keyring.gpg, then it will create a default one...making you think it was downloaded but it actually wasn't...odd.  In your case you'll want to manually remove "~/dlang/d-keyring.gpg" and use the new "install.sh" script after PR 338 is merged/deployed.

The respective hotfix PR is merged and deployed now ;-)

On Monday, 13 August 2018 at 17:10:13 UTC, Jonathan Marler wrote:
> The problem is downloading "install.sh" directly to "~/dlang/install.sh".  This causes the install script to think that it has already downloaded the "d-keyring.gpg" so it never downloads it, causing the "invalid signature" error.  The fix is to download "install.sh" if the d-keyring is not downloaded, even if install.sh already is.

Spot on! Thanks...