Re: [PATCH 5/5] gnu: Add emacs-mmm-mode

[Federico Beffa <beffa@ieee.org>]

On Thu, Jul 9, 2015 at 1:19 AM, Mark H Weaver <mhw@netris.org> wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> Ludovic Courtès (2015-07-04 18:16 +0300) wrote:
>>
>>> Alex Kost <alezost@gmail.com> skribis:
>>>
>>>> I think I've found a problem with downloading packages from melpa-stable
>>>> (probably the same will be with 'melpa', but I don't know).  I tried to
>>>> build this 'emacs-mmm-mode' package but it failed because
>>>> <http://stable.melpa.org/packages/mmm-mode-0.5.2.tar> does not exist
>>>> anymore (because the current version is 0.5.4).
>>>
>>> If tarball deletion or renaming is common on MELPA, then maybe we could
>>> address it by providing an additional alternate URL, as is done for
>>> ‘lftp’ and other packages.  WDYT?
>>
>> If I understand correctly, there is no alternative URL.  Only URL for a
>> latest version.  (but I may be wrong)
>
> emacs-mmm-mode is failing to build on hydra, because the downloaded
> tarball doesn't match the expected hash:
>
> http://hydra.gnu.org/build/563640/nixlog/1/tail-reload
>
> --8<---------------cut here---------------start------------->8---
> starting download of `/gnu/store/gdwf9rsqvvqqb77qkgpp94w8k8z1i6wf-mmm-mode-0.5.4.tar' from `http://stable.melpa.org/packages/mmm-mode-0.5.4.tar'...
>
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar    0.0% of 300.0 KiB (0. KiB/s)
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar   21.3% of 300.0 KiB (405. KiB/s)
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar   42.7% of 300.0 KiB (372. KiB/s)
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar   64.0% of 300.0 KiB (439. KiB/s)
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar   85.3% of 300.0 KiB (411. KiB/s)
> http://stable.melpa.org/.../mmm-mode-0.5.4.tar  100.0% of 300.0 KiB (419. KiB/s)
> output path `/gnu/store/gdwf9rsqvvqqb77qkgpp94w8k8z1i6wf-mmm-mode-0.5.4.tar' should have sha256 hash `1llkzb6d978ym3zv3yfzwj0w5zzmmj3ksrm5swrx1papxcnqnkb9', instead has `1kjc41nlsf7qxmmy9mrzk6myinjvc550zl5ia0ivvdz945x39yay'
> --8<---------------cut here---------------end--------------->8---
>
> What went wrong here?

That's not a good sign. I still have in the store the tar file with
the hash indicated in the package and it builds fine. However, if I
'guix download ...' the file again I get a hash which is different
from the one in the package and also from the one in the hydra log.

I can imagine that melpa is building the tar file on the fly. Is guix
taking the time stamp as an input to determine the hash?

Fede