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
When I run a scan_packages() or an update_repository() I get a Packages and a Packages.gz file that contain a "Filename" field for each package in the repo; however, the field only contains the name of the file and not the path to the file. If I manually run a dpkg-scanpackages -m ${dir} | gzip -9c > ${dir}/Packages.gz on the repo the Packages.gz that it creates has a relative path to the .deb file in the "Filename" field. Is there support already for creating Packages files that contain relative paths to the archives in their repos?
The text was updated successfully, but these errors were encountered:
When I run a
scan_packages()
or anupdate_repository()
I get a Packages and a Packages.gz file that contain a "Filename" field for each package in the repo; however, the field only contains the name of the file and not the path to the file. If I manually run adpkg-scanpackages -m ${dir} | gzip -9c > ${dir}/Packages.gz
on the repo the Packages.gz that it creates has a relative path to the .deb file in the "Filename" field. Is there support already for creating Packages files that contain relative paths to the archives in their repos?The text was updated successfully, but these errors were encountered: