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
The Nexus Repo generated Packages file does not follow the DebianRepository spec in regard to the Filename: field.
The Filename: field that Nexus Repo generates contains a leading /, this is in direct violation of the spec which requires it to be a relative path (source). The UNIX spec defines a relative path as a path without a leading slash (source).
This creates issues with some apt utilities such as deb-mirror which will always clone the repo to the root dir /pool instead of the correct relative location.
The Nexus Repo generated
Packages
file does not follow the DebianRepository spec in regard to theFilename:
field.The
Filename:
field that Nexus Repo generates contains a leading/
, this is in direct violation of the spec which requires it to be a relative path (source). The UNIX spec defines a relative path as a path without a leading slash (source).This creates issues with some apt utilities such as
deb-mirror
which will always clone the repo to the root dir/pool
instead of the correct relative location.Proxied APT repos do not have this issue.
Example Nexus-Generated
Packages
file:Note the leading slash at the start of the
Filename:
field.For comparison, here is the head of the Ubuntu Jammy repo's
Packages
file (from a Nexus Proxy APT repo)Note how the
Filename:
field does not contain a leading slash.The text was updated successfully, but these errors were encountered: