Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[packit] Propose downstream failed for release 1.17 #1558

Closed
packit-as-a-service bot opened this issue Sep 9, 2024 · 6 comments · Fixed by #1559
Closed

[packit] Propose downstream failed for release 1.17 #1558

packit-as-a-service bot opened this issue Sep 9, 2024 · 6 comments · Fixed by #1559

Comments

@packit-as-a-service
Copy link

Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/crun.git):

dist-git branch error
f39 See https://dashboard.packit.dev/results/propose-downstream/10781
f40 See https://dashboard.packit.dev/results/propose-downstream/10782
f41 See https://dashboard.packit.dev/results/propose-downstream/10783
rawhide See https://dashboard.packit.dev/results/propose-downstream/10780

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

Copy link
Author

Packit failed on creating pull-requests in dist-git (https://gitlab.com/redhat/centos-stream/rpms/crun.git):

dist-git branch error
c10s See https://dashboard.packit.dev/results/propose-downstream/10784

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

@giuseppe
Copy link
Member

/packit propose-downstream

Copy link
Author

Packit failed on creating pull-requests in dist-git (https://gitlab.com/redhat/centos-stream/rpms/crun.git):

dist-git branch error
c10s See https://dashboard.packit.dev/results/propose-downstream/10803

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

Copy link
Author

Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/crun.git):

dist-git branch error
f39 See https://dashboard.packit.dev/results/propose-downstream/10799
f40 See https://dashboard.packit.dev/results/propose-downstream/10801
f41 See https://dashboard.packit.dev/results/propose-downstream/10802
rawhide See https://dashboard.packit.dev/results/propose-downstream/10800

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

@giuseppe
Copy link
Member

@lsm5 PTAL

@lsm5
Copy link
Member

lsm5 commented Sep 10, 2024

I'll bump this manually in Fedora and also PR to fix it upstream.

lsm5 added a commit to lsm5/crun that referenced this issue Sep 10, 2024
Packit's propose-downstream failed[0] for crun 1.17 because packit wasn't
able to create `tests/tmt` path structure in the downstream repo[1].
[0]: containers#1558
[1]: https://dashboard.packit.dev/jobs/propose-downstream/10800

Using `mkpath: true` will create missing path components if any.
Ref: https://packit.dev/docs/configuration#files_to_sync

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5 added a commit to lsm5/crun that referenced this issue Sep 10, 2024
Packit's propose-downstream failed[0] for crun 1.17 because packit wasn't
able to create `tests/tmt` path structure in the downstream repo[1].
[0]: containers#1558
[1]: https://dashboard.packit.dev/jobs/propose-downstream/10800

Using `mkpath: true` will create missing path components if any.
Ref: https://packit.dev/docs/configuration#files_to_sync

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5 added a commit to lsm5/crun that referenced this issue Sep 10, 2024
Packit's propose-downstream failed[0] for crun 1.17 because packit wasn't
able to create `tests/tmt` path structure in the downstream repo[1].
[0]: containers#1558
[1]: https://dashboard.packit.dev/jobs/propose-downstream/10800

Using `mkpath: true` will create missing path components if any.
Ref: https://packit.dev/docs/configuration#files_to_sync

Fixes: containers#1558

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
@lsm5 lsm5 linked a pull request Sep 10, 2024 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants