-
Notifications
You must be signed in to change notification settings - Fork 202
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
[skip-ci] Packit/RPM: more fixes #2015
[skip-ci] Packit/RPM: more fixes #2015
Conversation
The |
9144bc1
to
332a7de
Compare
689910c
to
a623b64
Compare
a623b64
to
c3b98a8
Compare
@Luap99 @edsantiago @rhatdan @TomSweeneyRedHat @mheon PTAL. I have updated the containers-common rpm manually to the latest version. |
You can rebase to pick up the spelling fix: #2019 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I cannot claim I understand the spec files but your commit message explanation sounds good enough to me
Packit failed to trigger an automatic fedora package update on the upstream release v0.59.0 which brought to light further issues which this commit corrects. Packit doesn't honor a global `downstream_package_name` key when the upstream repo and downstream package name don't match. For this very repo, upstream repo is `common`, while downstream package is `containers-common`. For such cases, `downstream_package_name` should be specified at the package level. The `Source0` URL in rpm spec has also been corrected. This wasn't noticed in packit jobs on PRs because packit replaces Source0 with a locally created archive. The `mv` commands in rpm spec have also been replaced by `cp` so that consecutive `rpmbuild` runs will not complain about not finding the source files. The autosetup step in rpm spec has also been updated to the correct untarred archive name format. Misc cleanup includes removal of `update_release: false` from downstream jobs. It's meaningless in those jobs. Even for copr jobs, we should prefer packit's default behavior of `update_release: true`. Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
fc19a57
to
3c96617
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lsm5, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick v0.59 |
Packit failed to trigger an automatic fedora package update on the upstream release v0.59.0 which brought to light further issues which this commit corrects.
Packit doesn't honor a global
downstream_package_name
key when the upstream repo and downstream package name don't match. For this very repo, upstream repo iscommon
, while downstream package iscontainers-common
. For such cases,downstream_package_name
should be specified at the package level.The
Source0
URL in rpm spec has also been corrected. This wasn't noticed in packit jobs on PRs because packit replaces Source0 with a locally created archive.The
mv
commands in rpm spec have also been replaced bycp
so that consecutiverpmbuild
runs will not complain about not finding the source files.The autosetup step in rpm spec has also been updated to the correct untarred archive name format.