MIME-Version: 1.0
References: <20190502081103.wfiglbuj7trtackz@aurora.visucore.com>
In-Reply-To: <20190502081103.wfiglbuj7trtackz@aurora.visucore.com>
From: Marco Falke <falke.marco@gmail.com>
Date: Thu, 2 May 2019 12:16:08 -0400
Message-ID: <CAK51vgD+NOScgv9vRW6SnFGFxXLW0rxEqREBMqxWj+bBcVPzUA@mail.gmail.com>
To: Bitcoin Core Discussion <bitcoin-core-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [bitcoin-core-dev] Bitcoin Core 0.18.0 released
Precedence: list

Two addenda from me:

* Beginning with Bitcoin Core 0.18.0, Windows builds for 32-bit
Windows will no longer be provided. Please let us know if and why you
can not use the 64-bit build.
* There is an experimental Bitcoin Core snap package in the snap
store. There should be a "track" for the latest release and a track
for each major version branch that is not yet EOL. While the snap
package uses the signed release binaries, I am not aware of a way to
generate the hash of binaries in an installed snap that works on any
Linux distribution. (On some distributions, a call to `sha256sum
/var/lib/snapd/snap/bitcoin-core/current/{bin/*,snap/snapcraft.yaml}`
generates the hashes that you can then compare to the signed ones as
usual)

Marco