`EnvDeploy` script doesn't mount /dev/null and /dev/urandom which breaks build process
Because EnvDeploy didn't prepare dev environment correctly, I experience the following issue: https://github.com/SynologyOpenSource/pkgscripts-ng/issues/47
After I mounted those devices manually, I was able to build the example package as expected.
My VM uses Ubuntu 22.04 x64.
What do you mean "After I mounted those devices manually, I was able to build the example package as expected." Where did you do that and how?
What do you mean "After I mounted those devices manually, I was able to build the example package as expected." Where did you do that and how?
@pjdubya here you can find the details: https://stackoverflow.com/questions/78092696/execute-python-script-as-a-root-in-ubuntu-id-grep-uid-0-dev-null-throws/78094034#comment138110601_78094034
@usarskyy thanks. Took me a bit but I figured out finally where to add the changes to the right script. PR https://github.com/SynologyOpenSource/pkgscripts-ng/pull/50 ready for Synology to merge, or for others to use in the meantime to see what to modify on their own local repo.