rpms/bitcoin-core
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The bitcoin-core package
38 commits 17 branches 0 tags 362 KiB
Find a file
Exact
Simone Caronni 4163348106 Update to 29.0
2025-04-16 12:45:18 +02:00
.gitignore Update .gitignore 2025-01-11 12:24:04 +01:00
bitcoin-0.18.0-unicode.patch First import 2022-04-05 13:29:07 +02:00
bitcoin-core.spec Update to 29.0 2025-04-16 12:45:18 +02:00
bitcoin-gpg.sh Update sources and delete old keyrings 2023-05-30 15:10:49 +02:00
bitcoin-offline-pubring.gpg Update to 29.0 2025-04-16 12:45:18 +02:00
bitcoin-qt.desktop First import 2022-04-05 13:29:07 +02:00
bitcoin-qt.metainfo.xml Add AppData file 2022-04-07 16:45:01 +02:00
bitcoin-qt.protocol First import 2022-04-05 13:29:07 +02:00
bitcoin-tmpfiles.conf First import 2022-04-05 13:29:07 +02:00
bitcoin-verify-offline.patch Update to 28.0 2024-10-08 14:53:48 +02:00
bitcoin.conf.example First import 2022-04-05 13:29:07 +02:00
bitcoin.service.system First import 2022-04-05 13:29:07 +02:00
bitcoin.service.user First import 2022-04-05 13:29:07 +02:00
bitcoin.sysconfig First import 2022-04-05 13:29:07 +02:00
db-4.8.30.NC-configure-c99.patch Port bundled Berkeley DB 4.8 configure script to C99 (#2179373) 2023-03-17 15:37:43 +01:00
db-4.8.30.NC-format-security.patch First import 2022-04-05 13:29:07 +02:00
README.gui.redhat First import 2022-04-05 13:29:07 +02:00
README.md Update to 29.0 2025-04-16 12:45:18 +02:00
README.server.redhat First import 2022-04-05 13:29:07 +02:00
README.utils.redhat First import 2022-04-05 13:29:07 +02:00
sources Update to 29.0 2025-04-16 12:45:18 +02:00

README.md

bitcoin-core

The bitcoin-core package.

Preparing a new update

Perform the following steps to prepare the update to a new version. The sample commands below are performed with version 29.0.

Generic package update steps:

$ rm -f bitcoin-*.tar.gz SHA256SUMS*

$ rpmdev-bumpspec -D -c "Update to 29.0." -n 29.0 bitcoin-core.spec

$ spectool -g bitcoin-core.spec
Downloading: https://bitcoincore.org/bin/bitcoin-core-29.0/bitcoin-29.0.tar.gz
100% of  10.9 MiB |#######################################################| Elapsed Time: 0:00:01 Time:  0:00:01
Downloaded: bitcoin-29.0.tar.gz
Downloading: https://bitcoincore.org/bin/bitcoin-core-29.0/SHA256SUMS.asc
100% of  10.3 KiB |#######################################################| Elapsed Time: 0:00:00 Time:  0:00:00
Downloaded: SHA256SUMS.asc
Downloading: https://bitcoincore.org/bin/bitcoin-core-29.0/SHA256SUMS
100% of   2.8 KiB |#######################################################| Elapsed Time: 0:00:00 Time:  0:00:00
Downloaded: SHA256SUMS
Downloading: https://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
File '/home/slaanesh/workspace/fedora/bitcoin-core/db-4.8.30.NC.tar.gz' already present.

When uploading sources, make sure the DB tarball is included even if it has not changed as otherwise will not be available in the Koji build root:

$ fedpkg new-sources bitcoin-29.0.tar.gz SHA256SUMS SHA256SUMS.asc db-4.8.30.NC.tar.gz
File already uploaded: db-4.8.30.NC.tar.gz
Uploading: bitcoin-29.0.tar.gz
######################################################################## 100.0%
Uploading: SHA256SUMS
######################################################################## 100.0%
Uploading: SHA256SUMS.asc
######################################################################## 100.0%
Source upload succeeded. Don't forget to commit the sources file

After this, based on the list of keys that have signed the release and that are listed in SHA25SUM.asc, download the available ones and assemble an offline GPG keyring:

$ ./bitcoin-gpg.sh
Prepare official script to verify releases to work offline... done.
Creating GPG keyring with public keys that have signed release 29.0... done.

After this, it's time to commit and build:

$ git add bitcoin-offline-pubring.gpg
$ git commit -a -m "Update to 29.0"
$ git push
$ fedpkg build --nowait