You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Artifactory to host an internal caching remote for the cuda debian repository.
But we run into an issue while actually trying to get a package.
Another developer has also ran into the same issue, and his finding suggest the actual main cause is the incorrect use of relative urls inside the Packages file
The text was updated successfully, but these errors were encountered:
Hmmm, I would think this syntax is compliant with the Debian repository specifications.
While we rolled out a custom implementation (see repo-debian.sh in this repository) in 2020 for generating this metadata, it was designed to be a drop-in replacement for the previous mechanism apt-ftparchive.
Looking at older releases, I see the same relative path format in the meta-data to the *.deb packages
CUDA 9.0 local installer for Ubuntu 16.04: Packages.gz
Filename: ./cuda_9.0.176-1_amd64.deb
Taking a look at a Debian repo maintained within Artifactory's implementation I see relative paths without the ./ prefix
We are using Artifactory to host an internal caching remote for the cuda debian repository.
But we run into an issue while actually trying to get a package.
We created an initial issue here:
https://jfrog.atlassian.net/browse/RTFACT-24926
Another developer has also ran into the same issue, and his finding suggest the actual main cause is the incorrect use of relative urls inside the Packages file
The text was updated successfully, but these errors were encountered: