scap-workbench
scap-workbench copied to clipboard
OpenSCAP
Enable copr builds and add packit config
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?
- Install Packit-as-a-Service github application in your repo
- In case you are first user, wait for account approval
- Enjoy the built RPMs!
For more info, please:
- check out the documentation: https://packit.dev/docs/
- contact @packit-service
The spec you see in this PR was fetched from your package's Fedora dist-git.
@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:
Failed to parse SPEC file: error: line 2: Unknown tag: <!DOCTYPE html>
You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.
![packit-as-a-service[bot] avatar](https://avatars.githubusercontent.com/in/29076?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.