-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add Packit Integration #274
base: main
Are you sure you want to change the base?
Add Packit Integration #274
Conversation
/packit copr-build |
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 2 |
ce227f7
to
b8d6b82
Compare
There was a problem in the environment the service is running in:
You can re-trigger copr build by adding a comment ( Please, contact @packit-service/the-packit-team if the re-trigger did not help. |
b8d6b82
to
6d92aa5
Compare
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 1 |
6d92aa5
to
18d6527
Compare
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 1 |
/packit copr-build |
18d6527
to
5e52448
Compare
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 1 |
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 1 |
/packit build |
new sandbox image with json-c should be up, let's see |
There was an error while creating a SRPM. You can re-trigger copr build by adding a comment ( Output:
Return code: 1 |
I wonder, should it be json-c or json-c-devel? |
@TomasTomecek My mistake, it should be json-c-devel, systemd-devel, and libcurl-devel. |
Finally got back to this after the winter holidays. I added the -devel packages to our sandbox - the changes should be live on Monday. |
Signed-off-by: Tomas Tomecek <[email protected]>
packit: use actions to make the build work
There was an error while creating SRPM. You can re-trigger build by adding a comment ( Output:
|
The issue is:
|
@dhodovsk Hello, in the tlog master github repo should return '7'
And in the packet configuration we have:
Could you help me understand if I am missing something here? |
I actually have the same problem as Justin: it works for me locally with packit CLI, but in the service we have the problem which Dominika described. |
So I've tried it again and it seems the tag is only in https://github.com/justin-stephenson/tlog fork:
But in Scribery:
When packit checks out the PR to make changes, it only does the alternative of @TomasTomecek is this expected or should we do something about it in packit? |
I'd say that we should definitely fetch tags in packit. Shall we open an issue for that? |
Add basic setup for https://packit.dev/ triggering RPM builds in pull requests, tests to be added later.