standard-test-roles

#325 On-board on packit
Opened by ttomecek. Modified
ttomecek/standard-test-roles on-board-on-packit  into  master

Download 325.patch

This pull requests enables upstream STR to use packit.

I have tested these three packit commands:

  • packit propose-update to create a dist-git PR with the latest upstream release, documentation
  • packit srpm creates a new SRPM out of the current state of the upstream repository (using git describe for version), documentation
  • packit sync-from-downstream --no-pr to pull content from the downstream repo back to upstream (e.g. when rel-eng does mass rebuild) documentation
    • packit does not support creating pull requests on pagure.io, yet

I was running packit from git: I needed this PR. We will release packit 0.3.0 later this week and the release should include the PR.

Why should you care about this? I took a look at package_howto.md and with packit, you can remove like half of the steps now. Once we implement more in packit, the expectation is that you'll have to do very little to bring new upstream releases to Fedora.

@ttomecek HI!

  1. There is a .spec file in this PR. To facilitate user experience please add a line to PR doc: ".spec file in this PR should stay always compatible with Fedora Rawhide". So upstream knows .spec target.

  2. We build STR as a module. 1 MBS build produces 3 MBS builds. And, as you know MBS creates independent buildroot for each module. Is this supported by packit ?

Packit does not support module builds right now. We can (and should) add that to our Flock 2019 goal. You can propose pull requests using packit to any branches though.

Once the module builds are done, are you able to attach them to a bodhi update afterwards?

I'm sorry but what's a PR doc?

@ttomecek I think .spec file in dist-git and here will be out of sync.
Could you please update PR and remove change log in .spec?
Then ACK to merge.

@ttomecek I think .spec file in dist-git and here will be out of sync.

That is a valid concern. This is one of the goals of packit to prevent this situation. Right now we have two commands which help you keep the spec file in sync (propose-update to create a PR in dist-git using the upstream spec, sync-from-downstream to update spec file in the upstream repo from dist-git). Once we have packit service in-place, the PRs will be filed automatically.

Could you please update PR and remove change log in .spec?

Since packit copies the upstream spec file downstream, the removed changelog will be propagated downstream: not sure if this is something you want.

In the long run, we would love to integrate with some templating system so that changelog is populated automatically.

Then ACK to merge.
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.