Subject: bug#30109: closed (Re: bug#30109: [PATCH] gnu: shishi: Make shishi keys and database administrator-modifiable.)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 20 Apr 2019 15:20:02 +0000

Your bug report

#30109: [core-updates] shishi 1.0.2 not reproducible

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
30109: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30109
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#30109: [PATCH] gnu: shishi: Make shishi keys and database administrator-modifiable.
From: Danny Milosavljevic <[email-masked]>
To: Maxim Cournoyer <[email-masked]>
Cc: [email-masked]
Date: Sat, 20 Apr 2019 17:19:31 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi Maxim,

> I've applied and tried your proposed fix, and it made shishi
> reproducible; so LGTM!  Could you apply your fix to core-updates?

Thanks for the test!

I've pushed the fix to core-updates.

Subject: [core-updates] shishi 1.0.2 not reproducible
From: Gábor Boskovits <[email-masked]>
To: [email-masked]
Date: Sun, 14 Jan 2018 12:29:33 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

It seems, that the shishi build generates keys which end up in the store,
making the build unreproducible. Can the key generation be extracted from
the build?

If yes, then are we able to do the following: use a reproducible substitute
without the key, generate the key afterwards, and store it somewhere else.

diffoscope output attached.