The CBS build for https://cbs.centos.org/koji/taskinfo?taskID=3111085 is continually failing due to not being able to find the code in lookaside cache to build the src.rpm. Initial research shows that the source code is in https://git.centos.org/sources/ostree-compliance-mode/ostree-compliance-mode-0.2.3.tar.gz/sha512/9ec3abea9fd6d3f32dbc2e662f93ed542d519562dadf3fdd0625be89f737a37f2731842e8f9cc8ff270f22a0e32509af4c895dad2e83c13cecd4c088ed0d383a/ostree-compliance-mode-0.2.3.tar.gz
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs
From that task, I see through root.log:
root.log
DEBUG util.py:446: + curl -L -H Pragma: -o ./ostree-compliance-mode-0.2.3.tar.gz -R -S --fail --retry 5 https://git.centos.org/sources/ostree-compliance-mode/ostree-compliance-mode-0.2.3.tar.gz/sha512/9ec3abea9fd6d3f32dbc2e662f93ed542d519562dadf3fdd0625be89f737a37f2731842e8f9cc8ff270f22a0e32509af4c895dad2e83c13cecd4c088ed0d383a/ostree-compliance-mode-0.2.3.tar.gz DEBUG util.py:444: % Total % Received % Xferd Average Speed Time Time Time Current DEBUG util.py:444: Dload Upload Total Spent Left Speed DEBUG util.py:444: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 9895 100 9895 0 0 185k 0 --:--:-- --:--:-- --:--:-- 185k DEBUG util.py:446: + break DEBUG util.py:446: + read -r _ filename _ hash DEBUG util.py:446: + [[ -n '' ]] DEBUG util.py:446: + sha512sum -c sources DEBUG util.py:446: ostree-compliance-mode-0.2.3.tar.gz: OK DEBUG util.py:598: Child return code was: 0
So it was able to get the correct source, but then in build.log :
build.log
error: Bad source: /builddir/build/SOURCES/ostree-compliance-mode-0.2.tar.gz: No such file or directory
Interesting to see the difference so can you check that it's all referencing correctly the correct version/source ?
the problem is in your .spec file : https://gitlab.com/CentOS/automotive/rpms/ostree-compliance-mode/-/blob/main/ostree-compliance-mode.spec#L8
It's referencing %{name}-%{version}.tar.gz expanded to 0.2 and not 0.2.3
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.