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
Keep .spec in git #1016
Keep .spec in git #1016
Conversation
packit srpm failed with this:
It already failed the same way in my previous attempt when I dropped @lachmanfrantisek, @TomasTomecek : What am I doing wrong here? This PR is actually meaning to go towards the approach that packit wants, i.e. we want to reduce our packit.yaml. I.e. I'm happy to structure this otherwise, in some "that's the standard way". Thank you in advance! |
I changed the approach to not leave the generated .spec file in the tree, it might confuse packit. |
Nope, still won't budge. Somehow packit really doesn't like a spec file which is not in the project root dir? |
@@ -1,14 +1,12 @@ | |||
upstream_project_url: https://github.com/cockpit-project/cockpit-podman | |||
# enable notification of failed downstream jobs as issues | |||
issue_repository: https://github.com/cockpit-project/cockpit-podman | |||
specfile_path: cockpit-podman.spec |
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.
See https://github.com/packit/packit-service/issues/1511 -- there's a bug that propose-downstream fails without an explicit specfile_path:
, so we'll most likely have to bring that back anyway (with a bug ref). That will surface when testing the releasing, but until then we first need to sort out the packit srpm
build.
Same issue in cockpit-project/cockpit#17450. I can reproduce this locally with |
@lachmanfrantisek, @TomasTomecek : Isolated, reproduced, filed packit/packit#1621 about it. |
Still fails srpm build, I followed up to packit/packit#1621 |
The packit issue was fixed, so let's try this again. |
Argh, this is still broken. I can reproduce this locally:
So it seems that once again violates the "Else recursively search the tree and use the first spec file found." documentation.
|
b859ffa
to
5dbb437
Compare
Give up on .spec.in and directly keep the .spec in git. This aligns a lot better with what packit wants to do, and avoids having explicit `post-upstream-clone:` actions. We still want to build tarballs with a correct .spec (for using with `rpmbuild -tb` and VM image preparation), so make sure that they get a patched file with correct Version:.
Not important, and not worth the hassle. |
Give up on .spec.in and directly keep the .spec in git. This aligns a
lot better with what packit wants to do, and avoids having explicit
post-upstream-clone:
actions.We still want to build tarballs with a correct .spec (for using with
rpmbuild -bb
and VM image preparation), so make sure that they get thepatched file.
create-archive:
action packit/packit#1621