BugFix: Error popup on insufficient permissions during memcard conversion

[thethunderturner]

Description of Changes

Added a permissions check during the conversion of a memory card. It occurred to me that if somehow the permissions change during the setup of the conversion, then it will finish successfully, but wont be copied over to the new directory.

Furthermore, I also made a slight modification to the build-dependencies.sh, as I had an error when using curl.
More specifically: curl: (33) HTTP server does not seem to support byte ranges. Cannot resume.

Rationale behind Changes

Its just a bug fix. Helps user understand what went wrong.

Suggested Testing Steps

• Have permissions to the memcard directory
• Select a memcard for conversion
• When the popup is displayed, change permissions of the directory to nobody (sudo chmod 000 ./memory_save)
• Start conversion

This time you should get an error popup.

[github-actions]

Thank you for submitting a contribution to PCSX2

As this is your first pull request, please be aware of the contributing guidelines.

Additionally, as per recent changes in GitHub Actions, your pull request will need to be approved by a maintainer before GitHub Actions can run against it. You can find more information about this change here.

Please be patient until this happens. In the meantime if you'd like to confirm the builds are passing, you have the option of opening a PR on your own fork, just make sure your fork's master branch is up to date!

[F0bes]

Thanks for doing the Windows side too.
You have a bunch of lines with spaces where tabs should be.
Could you also mark variables such as canRead or fileAttributes as const?

[F0bes]

Would you be able to squash the commits into two and prefix the resulting commit?

Using git CLI you can interactive rebase all of your commits and then force push the result back to this branch..

[thethunderturner]

Would you be able to squash the commits into two and prefix the resulting commit?

Using git CLI you can interactive rebase all of your commits and then force push the result back to this branch..

Hey, could you check if everything is ok now? Lemme know if I missed something.

[thethunderturner]

Hmm, I will check why its failing

[F0bes]

I've already taken care of it for you. I've just asked some people to test the Windows portion and it will be good to merge.

[thethunderturner]

I've already taken care of it for you. I've just asked some people to test the Windows portion and it will be good to merge.

It still failed. I just tested it locally with the new commit, and everythign should work.
Apologies

[thethunderturner]

Why is the #ifdef at 0 indentation? 🤔

[F0bes]

If you want to use an LLM to help you program, that's fine, it's another tool that can sometimes be valuable. Please don't blindly copy and paste from it though. I was suspicious before, but now I'm 90% confident. The pointless commenting, the completely busted formatting (that I just fixed for you). With all respect I don't want to review a machines code.

Why is the #ifdef at 0 indentation? 🤔

It's configured that way in our clang-format.

[F0bes]

I'll switch to windows and figure this out..

[F0bes]

There, tested on Windows and Linux and it works.