charliecloud: point Source0 at the published release asset - #2678
Conversation
📦 Package Count Analysis ResultsEnvironment: UBI 10 Container 🏭 Factory RepositoriesStatus: ✅ Factory repositories analysis completed successfully
Analysis performed by OpenHPC Package Count CI |
🚀 CCache Statistics
📊 Detailed StatisticsopenEuler (aarch64)openEuler (x86_64)RHEL (aarch64/gnu15)RHEL (x86_64/gnu15)RHEL (x86_64/intel)🤖 Generated from workflow run |
Test Results 30 files ± 0 30 suites ±0 53s ⏱️ +6s Results for commit caea254. ± Comparison against base commit b967bc8. This pull request removes 1 and adds 5 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
b198226 to
d37f837
Compare
|
Could you update it to 0.45.1 and also take a look at this: https://gitlab.com/charliecloud/charliecloud/-/releases#release-tarballs-now-have-usable-urls I mentioned it to the upstream developers that they do not have stable tar archive URLs and this seems to have changed with newer releases. |
Source0 pointed at a GitLab upload path that carries an opaque hash. The hash
changes with every release, so the URL cannot be derived from the version and
needs hand editing each time.
Charliecloud now publishes release tarballs under a stable path. Source0 uses
that path and follows %{version}. The name fragment is no longer needed,
because the URL already ends in the tarball name.
Signed-off-by: Vinícius Ferrão <ferrao@versatushpc.com.br>
d37f837 to
caea254
Compare
It is done. |
The package_files URL returns 404. Use the release asset URL for 0.44 and
drop the now unused package_file_id macro.