Skip to content

Conversation

@NelsonGaldeman
Copy link
Contributor

When previous releases are fetched and the specified version wasn't added to the checksum list we used to get a "Checksum did not match" which isn't true (bitcoin-core/bitcoincore.org#753 (comment)).

If the specified version number is not on the list, it now logs cannot do the comparison instead.

@theStack
Copy link
Contributor

Concept ACK, will test later

Copy link
Contributor

@rajarshimaitra rajarshimaitra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK with an error message comment.

@NelsonGaldeman NelsonGaldeman force-pushed the improves-error-message-on-utils branch from 179f1b4 to e217dca Compare July 19, 2021 12:21
Copy link
Contributor

@theStack theStack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left two possible improvements that came up while reviewing the code. Couldn't test yet (the machine I am using right now is running OpenBSD, where the script doesn't work; even if the platform is overrided to e.g. 'x86_64-linux-gnu', the tar command fails), but will do tomorrow on a Linux machine.

@fanquake
Copy link
Member

even if the platform is overrided to e.g. 'x86_64-linux-gnu', the tar command fails),

That sounds like something we should be able to fixup.

If a requested version doesn't exist on our list of checksums it says it cannot do a checksum comparision instead of saying it did not match
@NelsonGaldeman NelsonGaldeman force-pushed the improves-error-message-on-utils branch from e217dca to 179a051 Compare July 20, 2021 08:51
Copy link
Contributor

@theStack theStack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK 179a051, tested on Debian bullseye/sid

master branch:

$ ./test/get_previous_releases.py -b v0.21.0
Releases directory: releases
Fetching: https://bitcoincore.org/bin/bitcoin-core-0.21.0/bitcoin-0.21.0-x86_64-linux-gnu.tar.gz
[ ... ]
Checksum did not match
$ echo $?
1

PR branch:

$ ./test/get_previous_releases.py -b v0.21.0
Releases directory: releases
Fetching: https://bitcoincore.org/bin/bitcoin-core-0.21.0/bitcoin-0.21.0-x86_64-linux-gnu.tar.gz
[ ... ]
Checksum for given version doesn't exist
$ echo $?
1

By the way, welcome as a new contributor NelsonGaldeman! 🎉

even if the platform is overrided to e.g. 'x86_64-linux-gnu', the tar command fails),

That sounds like something we should be able to fixup.

Yes, will take a look into that.

@practicalswift
Copy link
Contributor

cr ACK 179a051

Warm welcome as a new contributor @NelsonGaldeman! 🥇

@maflcko maflcko merged commit 8bc4a11 into bitcoin:master Jul 25, 2021
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Jul 28, 2021
…leases script

179a051 util: improves error messages on get_previous_releases script (Nelson Galdeman)

Pull request description:

  When previous releases are fetched and the specified version wasn't added to the checksum list we used to get a "Checksum did not match" which isn't true (bitcoin-core/bitcoincore.org#753 (comment)).

  If the specified version number is not on the list, it now logs cannot do the comparison instead.

ACKs for top commit:
  practicalswift:
    cr ACK 179a051
  theStack:
    tACK 179a051, tested on Debian bullseye/sid

Tree-SHA512: 2a07ce75232f853fd311c43581f8faf12d423668946ae6ad784feece5b4d0edd57fc018ba1f0c5a73bfaccb326e0df9a643580d16bf427c1ec3ff34a9cdbc80c
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants