Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch build from createrepo-c to createrepo #3609

Merged
merged 1 commit into from
Jul 21, 2022

Conversation

HebaruSan
Copy link
Member

Problem

After #3605, the build failed:

screenshot

Cause

Ubuntu and Debian have createrepo-c for generating RPM repos. I hoped that mono:latest would be the same 🤞, but it was not to be.

$ docker run -it --entrypoint sh mono:latest

# apt-cache search createrepo
createrepo - tool to generate the metadata for a yum repository

Changes

  • The deploy.yml file is updated to install createrepo instead of createrepo-c
  • The RPM Makefile now uses createrepo if you have it, or createrepo_c if you don't, so local dev will still work

I'll merge this shortly.

@HebaruSan HebaruSan added Bug Easy This is easy to fix Pull request Build Issues affecting the build system Linux Issues specific for Linux Package: rpm Issues affecting RPM packaging labels Jul 21, 2022
@HebaruSan HebaruSan merged commit 66c595b into KSP-CKAN:master Jul 21, 2022
@HebaruSan HebaruSan deleted the fix/rpm-createrepo branch July 21, 2022 18:14
@HebaruSan
Copy link
Member Author

That worked, but the nightly repo only has ckan-1.31.1-1.noarch, which lacks a daily incrementing version number part, so all the builds until the next release will share the same version number and RPM won't update them...

@HebaruSan
Copy link
Member Author

Updated release.yml in 5917e37.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Build Issues affecting the build system Easy This is easy to fix Linux Issues specific for Linux Package: rpm Issues affecting RPM packaging Pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant