[debbugs-tracker] bug#30109: closed ([core-updates] shishi 1.0.2 not reproducible)

[GNU bug Tracking System]

Your message dated Sat, 20 Apr 2019 17:19:31 +0200
with message-id <address@hidden>
and subject line Re: bug#30109: [PATCH] gnu: shishi: Make shishi keys and 
database administrator-modifiable.
has caused the debbugs.gnu.org bug report #30109,
regarding [core-updates] shishi 1.0.2 not reproducible
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30109: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30109
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [core-updates] shishi 1.0.2 not reproducible Date: Sun, 14 Jan 2018 12:29:33 +0100

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.

diffoscope-shishi
Description: Binary data

--- End Message ---

--- Begin Message --- Subject: Re: bug#30109: [PATCH] gnu: shishi: Make shishi keys and database administrator-modifiable. Date: Sat, 20 Apr 2019 17:19:31 +0200

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.

pgpi9OgEm6p7A.pgp
Description: OpenPGP digital signature

--- End Message ---