The Target Path needs to be entered in a strict and specific format that uses system properties to define where the artifact will be stored and its specific layout as follows:
Target Path Format
[path];deb.distribution=[distribution];deb.component=[component];deb.architecture=[architecture]
Property | Description |
|---|---|
path | The repository path where the package should be stored. Artifactory supports storing Debian packages anywhere within the repository. The examples on this page show Debian packages stored under the pool folder in accordance with the Debian convention. |
distribution | The value to assign to the |
component | The value to assign to the |
architecture | The value to assign to the |
Adding Architecture Independent Packages
Uploading a Debian package with deb.architecture=all will cause it to appear in the Packages index of all the other architectures under the same Distribution and Component, as well as under a new index branch called binary-all which holds all Debian packages that are marked as "all'. Removing an "all" Debian package will also remove it from all other indexes under the same Distribution and Component. When the last Debian package in an architecture is removed but the Packages index still contains an "all" Debian package, it is preserved in the index. If you want such an architecture index removed you may do so via the UI or using Calculate Debian Repository Metadata in the REST API, which cleans up orphaned package files from the index.