Hello Hervé,
> Hi,
>
> On 07/30/2017 03:28 AM, Janssen-10, R.R.E. wrote:
>> Hello,
>>
>> So, are you absolutely sure nothing has changed in this package?
>
> All I'm saying it that version 1.4.0 of this package has not changed
> since it was first made on May 13, 2014. Before version 1.4.0, we ha
Hi,
On 07/30/2017 03:28 AM, Janssen-10, R.R.E. wrote:
Hello,
So, are you absolutely sure nothing has changed in this package?
All I'm saying it that version 1.4.0 of this package has not changed
since it was first made on May 13, 2014. Before version 1.4.0, we had
version 1.3.1000. Of course
Hi,
Hi,
any suggestions or better diagnostics that could help us
fixing this, in case it really is something in xcms ?
There were a few earlier reports with similar messages,
back in 2013, slightly hinting at virus scanners:
http://r.789695.n4.nabble.com/quot-Failed-to-locate-the-texi2pdf-
Hello,
So, are you absolutely sure nothing has changed in this package?
I can still reproduce the hash mismatch.
In GNU Guix, the SHA256 hash is computed when the tarball is downloaded by the
person who adds or changes the package. So at some point, the tarball was
different (at least to to pac
