https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sci-electronics/bluespec-2025.01.1 fetches file(s) that do not match recorded size. Discovered on: amd64 (internal ref: guru_ci) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0018
Created attachment 925988 [details] build.log build log and emerge --info
Error(s) that match a know pattern: !!! Fetched file: bluespec-2025.01.1.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size
This checksum change is harmless, it is because the export-subst command causes the export to be related to the git state, causing inconsistencies. https://github.com/B-Lang-org/bsc/blob/2025.01.1/.gitattributes#L14C33-L14C46 # Tell Linguist not to include the following code # in statistics about this repo # src/Parsec/** linguist-vendored src/vendor/stp/src/** linguist-vendored testsuite/** linguist-vendored doc/** linguist-documentation # Scripts that query git for commit info will not work # if the source is not in a git repo, so when exporting # (via 'git archive') substitute patterns in these files # with the info they need # src/comp/update-build-version.sh export-subst I carefully checked the upstream changes and found them to be harmless. The detailed reproducible process is as follows: I carefully checked the upstream changes and found them to be harmless. The detailed reproducible process is as follows: ```bash $ b2sum *.tar.gz efc39090de2052cd8f3957265d5b1e24c468648b84339206736d9ef47ea3966eff26ef18fb676fca4d6411d7d609e86a08c28afb52e8cfd7120aaa4238d880eb a_bluespec-2025.01.1.tar.gz 4f0c67de78bf37f9de894ad544430613491de3a97d7f2a00767adf12ccd527146af1d55cd90fdaa25441611fb18f9755a847bf7d7cb89db350eac92b914348e1 b_bluespec-2025.01.1.tar.gz $ sha512sum *.tar.gz c922240ede92e0a448d3602bef71990467b5106b921c70b6a7e003df7930582fa0ecbd615918e6c3f56ab9c8bbb9cc4b3a38840f64feafd88fa4fd44dcbeff9a a_bluespec-2025.01.1.tar.gz d1d9fc149da0b793cf9158bf72219942cd11bef8b0e8ddce51a22de591cbad07cce367bb72e3c718bca1e81d3768a298b4f3e61cbb5b4b3cc04cf1cc7796908a b_bluespec-2025.01.1.tar.gz $ mkdir a b && tar -zxvf a_bluespec-2025.01.1.tar.gz -C a/ && tar -zxvf b_bluespec-2025.01.1.tar.gz -C b/ $ diff -bur a/bsc-2025.01.1 b/bsc-2025.01.1 diff --color -bur a/bsc-2025.01.1/src/comp/update-build-version.sh b/bsc-2025.01.1/src/comp/update-build-version.sh --- a/bsc-2025.01.1/src/comp/update-build-version.sh 2025-03-06 10:52:16.000000000 +0800 +++ b/bsc-2025.01.1/src/comp/update-build-version.sh 2025-03-06 10:52:16.000000000 +0800 @@ -48,7 +48,7 @@ # If the source was exported (via 'git archive') if [[ '%' == "%" ]]; then GITCOMMIT='65e3a87a1' - if [[ 'HEAD -> main, tag: 2025.01.1' =~ tag:\ ([^ ]+) ]]; then + if [[ 'tag: 2025.01.1' =~ tag:\ ([^ ]+) ]]; then GITDESCR="${BASH_REMATCH[1]}" else GITDESCR="archive-g${GITCOMMIT}" ``` Which form ``https://github.com/B-Lang-org/bsc/blob/2025.01.1/src/comp/update-build-version.sh#L49-L56`` This code is related to the status of git archive at the moment, resulting in two possibilities: 1. At the moment of archive, when ``HEAD`` is at ``2025.01.1``, result ``a`` will be obtained. 2. At the moment of archive, when ``HEAD`` is newer than ``2025.01.1``, result ``b`` will be obtained. Therefore, this result is caused by the uncertainty caused by the status of git archive at the moment. If you want to reproduce this yourself using the original files, or want to see the detailed discussion, you can visit the following links. https://github.com/gentoo/guru/commit/38220093772cc634c361b8604a8003b2ef1573af
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=38220093772cc634c361b8604a8003b2ef1573af commit 38220093772cc634c361b8604a8003b2ef1573af Author: Huang Rui <vowstar@gmail.com> AuthorDate: 2025-04-27 07:58:10 +0000 Commit: Huang Rui <vowstar@gmail.com> CommitDate: 2025-04-27 08:02:31 +0000 sci-electronics/bluespec: update Manifest Closes: https://bugs.gentoo.org/954336 Signed-off-by: Huang Rui <vowstar@gmail.com> sci-electronics/bluespec/Manifest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
