Enable copr builds and add packit config

[dhodovsk]

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

[psss]

/packit copr-build

[packit-as-a-service]

There was an error while running a copr build:

Request is not in JSON format, there is probably a bug in the API code.

You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.

[TomasTomecek]

^ that error is actually coming from kubernetes and the original cause is something like gateway error, whatever that means -_-

[TomasTomecek]

/packit build

[packit-as-a-service]

Congratulations! The build has finished successfully. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/psss-edd-10
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[TomasTomecek]

\o/

[packit-as-a-service]

There was an error while running a copr build:

The create-archive action did not output a path to the generated archive. Please make sure that an absolute path to the archive is printed.

You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.

[packit-as-a-service]

There was an error while running a copr build:

The create-archive action did not output a path to the generated archive. Please make sure that an absolute path to the archive is printed.

You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.

[psss]

Pushed further simplification which we've agreed on today's meeting. @lachmanfrantisek, please review if everything's as expected and let me know when the updated code is in production. Thanks.

[packit-as-a-service]

There was an error while creating a SRPM. You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.

Output:

make: *** No rule to make target 'packit-tarball'.  Stop.

Return code: 2

[packit-as-a-service]

There was an error while running a copr build:

The create-archive action did not output a path to the generated archive. Please make sure that an absolute path to the archive is printed.

You can re-trigger copr build by adding a comment (/packit copr-build) into this pull request.

[lachmanfrantisek]

Works for me locally on the packit master. Let's wait for the redeploy.

[psss]

Nice! Looking forward :)

[lachmanfrantisek]

/packit build

[TomasTomecek]

:/

[lachmanfrantisek]

:/

I'll take a look on the paths for sandcastle (our sandboxing system) -- it's probably different than the local build.

[lachmanfrantisek]

A little out-of-the topic info:

• Dominika is working on removing unnecessary packit/rpm-build failed status:

• I am going to fix this one (error in the status instead of the comment, pending builds) (Fixed in Better SRPM exception messages packit/packit#653 and Comment on the SRPM error packit/packit-service#317)

[psss]

/packit build

[TomasTomecek]

I think the problem here is that the path is absolute - it should ideally be relative within the project

[psss]

I guess this the same issue as teemtee/tmt/pull/249. I've tried relative path there as well but it did not help.