-
Notifications
You must be signed in to change notification settings - Fork 56
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
Issue with copr git #3266
Comments
The same for all recent builds. |
Thank you for the report @andersrh and @samoht0, It was caused by a
I think we should configure our servers to not run automatic security upgrades on weekends ... Not sure what is the problem with the new git, so I only did
as a workaround until somebody can investigate the issue properly. |
Hi @FrostyX Thanks a lot :) it seems to be working now :) |
Yeah, working fine again. Thanks for the quick solution. |
Red Hat Copr fix needed. |
@FrostyX claims we should check if we can configure dnf-automatic for non-weekend times |
The mentioned git update is now available It didn't help but I can finally see the errors in the httpd log:
This is probably caused by the fact that the directory is owned by the
works and makes it possible to clone the repository. For the record, I don't know what The problem is that it is not possible to configure The only thing that works is
which completely disables the feature. Per man git-config:
Which isn't ideal but may be fine in our situation? |
I am keeping this open because I still want to send a message to git mailing list. But I deployed the fix and we are now running the up-to-date version of git, so technically, the issue is fixed. |
Hi.
I have tried to make a build this morning for our project because a new linux kernel release came out.
When I start the build I get 500 error from the copr git repo and the build fails.
log can be found here:
https://download.copr.fedorainfracloud.org/results/bieszczaders/kernel-cachyos-dev/fedora-39-x86_64/07456843-kernel-cachyos-lts/builder-live.log.gz
The text was updated successfully, but these errors were encountered: