Enable copr builds and add packit config#236
Conversation
|
Can one of the admins verify this patch? |
|
@openscap-ci test this please |
|
@dhodovsk I have pushed to your branch, could you please take a look whether it looks OK to you? |
|
There was an error while running a copr build: You can re-trigger copr build by adding a comment ( |
- Use fedora-all instead of hardcoding version numbers. - Get spec file from downstream, don't put it to the repo. - Enable release-time downstream Fedora release.
matejak
force-pushed
the
packit-onboard-w-copr
branch
from
ca1ef78 to
9947e41
Compare
|
Observation: Some builds have failed (for legitimate reasons), but it shows "Pending" long afterwards. |
|
Please add the .spec file back so that we comply with the upstream first policy. In addition, most the upstream RH projects have the spec file in them. |
|
@redhatrises When this discussion has been asked on the scap-security-guide mailing list, nobody was able to provide an example of what added value would the synchronization of Rawhide spec file provide. As Packit support touches all of our projects, let's discuss things there on one place - preferably that ML. |
4 participants
Let us introduce packit service to you - the automation to integrate upstream open source projects into Fedora operating system.
After merging this PR, you are just a few steps away from RPM builds being automatically triggered on your PR's.
It means, that you'll be able to try and play with your change, packaged as an RPM.
But there is more. By using packit, you can for example enable adding new releases into Fedora Rawhide.
What are the next steps?
For more info, please:
The spec you see in this PR was fetched from your package's Fedora dist-git.