"curl: option : blank argument where content is expected" while building
hello, i started getting an issue recently after doing the
/etc/ migration where for some reason curl stopped working my script. here's the part where it errors in the github action, and here's the part of the script where i believe it begins to error out. no idea whats happening since this worked fine before, and maybe also if someone could suggest a better way of doing this instead of. however i'm doing it.GitHub
chore(wuzetka): curl command fixes · sernik-tech/member-images@230d...
Custom Universal Blue-powered images made with BlueBuild for and by Sernik members - chore(wuzetka): curl command fixes · sernik-tech/member-images@230dc37
GitHub
member-images/files/scripts/system-wuzetka.sh at main · sernik-tech...
Custom Universal Blue-powered images made with BlueBuild for and by Sernik members - sernik-tech/member-images
8 Replies
The problem appears to be at line 50 when you're trying to read Thorium's version. You can see the exact commands that are run by calling
set -x and then turn it off with set +x.
Yes the -/+ are in the right order, that's just bashhmm okay
i'll poke at it later then, still no idea whats happening here
Solution
Yeah
set -x is your friend when it comes to debugging a bash scriptoh. funny
i added that to the script and for some reason it now seems to be Perfectly Fine
guess i'll mark as solved, idk what was happening then for it to act like that
this seems to be happening again despite nothing changing and it seemingly being happy before
i'm not completely sure if perhaps the way i'm doing this is just weird (i should find a better way but not entirely sure how) or if curl is just bugged
Try
echoing the values you get back from curl to see if you're getting the right json you're expecting. This is unfortunately not a bluebuild specific issue so it's not something on our side we can fix. This will just require time debugging ityou could also try wget, if that's more reliable for you
nevermind . the issue doesn't seem to be curl or anything at fault here - rather, the github repository it fetches releases from marks its beta builds as "latest" so it fails because it tries to grab a specific rpm that doesn't exist for those beta builds . probably should have checked that first