-
Notifications
You must be signed in to change notification settings - Fork 375
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
Packman setup for 5.3.0 broken after 5.3.1 release #231
Comments
Ah, I'm seeing this as well:
It seems like this file is out of date: |
Please update packman, and it'll work: #230 We are looking at auto-updating packman as part of the generate projects phase to avoid this in the future. |
Leaving this open for now because the discussion may not be as visible as it should be. |
Oh I see, completely forgot the discussions tab existed so I didn't think to check there |
With main branch of this repo, I've obtained error similar to : NVIDIA-Omniverse/PhysX#231 I resolved it by manually updtating pacman after cloning PhysX, what was proposed here NVIDIA-Omniverse/PhysX#230. Signed-off-by: Michał Pełka <[email protected]>
I'm facing the same issue on running generate_projects.sh : Is there any temporary fix for this? I need the physx SDK files for my project |
@gupta-ish yes please look at the discussion #230 mentioned above. |
Somehow, I'm still getting the same error : |
That's a different error that I have not seen before, and I cannot repro locally (with 5.3.0). |
@gupta-ish @preist-nvidia |
Yes, please see #230 |
@preist-nvidia Still I am unable to fetch dependencies due to invalid server certificate
|
@zemlifr - I cannot repro this on a machine on a public network. I use the same packman version. I assume you cannot download any of the packages? |
I tried from my side as well (and deleted any existing package so Packman is forced to pull it again) on a public network and it works just fine. |
Yes, I have tried public network as well and it works. So you are right it is something with our company network setting. I will ask our admins. |
@preist-nvidia Hello :) The same here. I've just downloaded 4.1 version and 5.4 version on the same PC and put their folders in the same directory, as a result generate_projects.bat creates projects on 4.1, but shows the same errors about VsWhere on 5.4. Upgrading packman doesn't fix this. It says that the version is already 7.23.1 |
Hello @kv1128 , |
Hi @ayoub-belarbi. I've edited logs a little bit in order to remove the actual paths that are not significant here. Well, the errors are a little bit different from the topic starter's, since there are some connection errors as well Running generate_projects.bat vc16win64 |
Thank you @kv1128 , |
No VPN and no firewall, at least on my PC |
Did you try to update to latest packman? |
Yes, I tried, but it doesn't seem to update anything Downloading from https://bootstrap.packman.nvidia.com/packman-command%407.last-known-good.txt (26.00 bytes) |
Getting some errors running our build script on a new computer using version 5.3.0:
The root cause seems to be that something is wrong with the PhysXGpu packman package downloaded before build. This didn't happen about a month ago (when I last tried clean setup).
Got it fixed by copying the packages folder from another computer, but probably something to look at.
The text was updated successfully, but these errors were encountered: