digitalmars.D - ./install.sh dmd broken?
- Jean-Louis Leroy (8/8) Aug 10 2018 jll@euclid:~/dlang$ ./install.sh dmd
- bachmeier (3/11) Aug 10 2018 It may be this:
- Jean-Louis Leroy (3/16) Aug 10 2018 Probably not. I am trying to install dmd on a new machine I got
- Seb (15/21) Aug 10 2018 Is there anything specific about your machine?
- Jonathan Marler (14/22) Aug 13 2018 Seb and I found the issue (TLDR: fix here:
- Seb (2/10) Aug 13 2018 The respective hotfix PR is merged and deployed now ;-)
- Jean-Louis Leroy (2/8) Aug 21 2018 Spot on! Thanks...
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 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.
Aug 10 2018
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
Aug 10 2018
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:Probably not. I am trying to install dmd on a new machine I got in June.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
Aug 10 2018
On Friday, 10 August 2018 at 13:19:21 UTC, Jean-Louis Leroy wrote:jll euclid:~/dlang$ ./install.sh dmdIs 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-keysYou should see a similar output as on https://dlang.org/gpg_keys.html Also:sha256sum ~/dlang/d-keyring.gpg4de1bb6028bb1e3d4eefd9e1a1651ad6c372ead0482b63e3aafdfdc0fbb48dbd /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 ;-)
Aug 10 2018
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.
Aug 13 2018
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 ;-)
Aug 13 2018
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...
Aug 21 2018