-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update SABnzbd to 4.3.2 #6107
Update SABnzbd to 4.3.2 #6107
Conversation
@th0ma7 I was a bit surprised it tries to build Python for |
Actually there's two totally different problems:
|
Nice catch! Indeed in Further looking at the code the That should be relatively easy to do. I can try to create a quick PR for testing. EDIT: Testing a potential begining of a fix in PR #6108 |
Well, ARM v5 won't work for Sab anyway because unrar doesn't support it anymore. It needs C++11 minimum. |
Indeed but ideally we can still resolve the py311 build issue for it so
checks are all green. My new pr should solve that hopefully.
Le jeu. 30 mai 2024, 07 h 27, Safihre ***@***.***> a écrit :
… Well, ARM v5 won't work for Sab anyway because unrar doesn't support it
anymore. It needs C++11 minimum.
—
Reply to this email directly, view it on GitHub
<#6107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECZA2SKXAX6CNT5RWKVZCLZE4EKFAVCNFSM6AAAAABIPTMCCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGM2DQOBXG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Safihre would you mind rebasing against master now that my PR python311 fix is merged for armv5 no-atomic? much thnx in advance. |
@th0ma7 worked! |
Strange, when I rand the build to publish it suddenly failed for |
Sometimes it is just because it completed at the same time as another one and parallel uploading fails on our package server. Just re-run failed ones. |
@th0ma7 I don't think the issue is the same as a failed upload. The build fails to complete in the first place:
Based on the logs I see this:
I don't know if this is a setup issue but it would be useful @Safihre to re-run this failed job to see if a second run has the same issue. |
This is odd, further as it worked initially on two pr. @Safihre can you re-run failed build? |
Unfortunately, same result |
I'll try to have a look at it over the weekend. |
This is odd, looking at the github-action build logs, this should normally be the trigger for
When this is seen normally shortly thereafter it should trigger the dependency processing for the toolchain such as:
But that is entirely skipped somehow... I will have to figure out how to replicated this. @hgy59 I'm running LXC/LXD on my end, are you runing docker and may be able to replicated this? which may be, again, related to the EDIT: I may have found where the issue may be ... IF the
|
related to #6054 ? |
@hgy59 yup, i believe this is the case... |
Worked! Thanks a lot for your help every time! 👍👍 |
Awesome! 🚀 Now let's hope it suffice for all github-action caching scenarios... |
@Safihre will you be publishing the |
Oh thought it was an unsupported arch 😱 |
Oh now that I trigger a build with publishing it failed again: |
@Safihre, I've triggered a run on your behalf and it built and published successfully: https://github.com/mreid-tt/spksrc/actions/runs/9381360715/job/25830726706 |
That's something to keep an eye on wetter it fixes things for good or not for qoriq building. Ping me if you notice this again. |
Sounds like a cache problem. Thanks! |
Description
Update SABnzbd to 4.3.2
Checklist
all-supported
completed successfullyType of change