Maintenance: updating ElectrsNow and then it makes sense to update the server, since fixes and improvements are being added to the newer versions.
The details for updating are pretty much described at:
https://github.com/romanz/electrs/blob/master/doc/upgrading.md still, I thought it won't hurt to have also a newbie friendly one here, focused on what we've installed.
VersionIf you start your local electrs it will show its version. Mine is now 0.9.3 (yeah, I've done at some point in the past another/newer install).
In any git page of the project (like
https://github.com/romanz/electrs ) there's a combobox telling "master". If you click it, and click tags, you'll see all the versions; more important, you'll see which is the latest one. In my case it's 0.9.6, so I'll update to that.
Update OSWell, this should be run more often than updaing electrs, however, here we are:
sudo apt update
sudo apt upgrade
Optional prerequisitesAlthough it's not a required step to verify the signature, I will do that.
However, for that to work, we have to make sure our pgp "knows" the signature of the developer.
curl https://romanzey.de/pgp.txt
curl -o romanz.pgp https://romanzey.de/pgp.txt
gpg --import romanz.pgp
It should tell: "imported: 1".
Update ElectrsSince we have manual install, that path is what I'll follow.
Keep in mind that this code is for version 0.9.6; if you'll find newer versions on git, please adapt to that one.
cd ~
cd electrs
git checkout master
git pull
Now there's the optional step of verifying what we get. If you didn't import the pgp key, you will probably also skip this.
It should tell things like "good signature" and "Primary key fingerprint: 15C8 C357 4AE4 F1E2 5F3F 35C5 87CA E5FA 4691 7CBB"
It may also give a warning that it's not the most trusted signature, but it's fine.
Let's proceed:
git checkout v0.9.6
ROCKSDB_INCLUDE_DIR=/usr/include ROCKSDB_LIB_DIR=/usr/lib cargo build --locked --release
If, back at install time, your install of librocksdb-dev has failed and have used a workaround, you'll have to
look in git and adapt this last command (probably go for static linked path).
And we're done! If you also have the sh file
I've created here, then: