Open iieklund opened 2 years ago
Hello @iieklund , Reason to not have "architectures" as an option in API Client is that the AptlyAPI server is not supporting such:
`func apiReposCreate(c *gin.Context) {
var b struct {
Name string `binding:"required"`
Comment string
DefaultDistribution string
DefaultComponent string
}`
I'm not even sure if "architectures" flag in CMD (example that you have posted) have any effect on newly created repository. On the other hand "architectures" may have significant effect when publishing a repository. So I believe that what you are trying to achieve should be done when publishing a repository, as you already did!
Hi,
If looking at the Aptly itself it supports the following:
$ aptly repo add -architectures="amd64" <search dir for amd64 .deb packages>
$ aptly repo add -architectures="arm64" <search dir for arm64 .deb packages>
There is no such option available when using e.g. this flow:
The publish api does provive the "architectures" support:
Does it achieve the same result if I'm adding both amd64 and arm64 .deb packages via "aptly.files.upload" and "aptly.repos.add_uploaded_file" and upon publishing a snapshot I pass "architectures=['amd64', 'arm64']" ?