Can not upload apt package to a component other than main

sonatype / nexus-public

Sonatype Nexus Repository Open-source codebase mirror

https://www.sonatype.com/products/repository-oss-download

Eclipse Public License 1.0

1.94k stars 572 forks source link

Can not upload apt package to a component other than main #223

Open ghost opened 1 year ago

ghost commented 1 year ago

What problem are you trying to solve? Controlling development and release cycles for our debian packages
Do you have a workaround you are using at present? No
What feature or behavior is this required for? Releasing debian packages to non-main components
How could we solve this issue? (Not knowing is okay!) Provide a way to specify which component a debian package is to be uploaded, instead of assuming 'main'
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using? Sonatype Nexus Repository OSS 3.58.1-02

ghost commented 1 year ago

Note: the lack of this functionality was captured in the final comment almost exactly a year ago here: https://blog.sonatype.com/nexus-repo-supports-apt

Unfortunately the JIRA tickets referenced are not viewable, or closed so I can not tell what became of them.

ghost commented 1 year ago

Note2: It is clear that nexus can support multiple apt components because this works with apt-proxy repos. The ability to specify any component when uploading is just not present today (or I am unable to find it documented).

nblair commented 1 year ago

Hi @sillydino thanks for opening an issue. Your request sounds remarkably similar to what the Staging capability in our Pro product offers, have you considered that option?

If Pro and staging is not an option, we can leave this issue open to gauge demand from the community for this feature.

ghost commented 1 year ago

Hi @nblair thank you for the info. In our case we just need the basic ability to write to the component field for apt artifacts. No need for higher-level-integration for deployments (as in the Pro product). Even with Pro there doesn't exist an API for writing the component name, and this is a basic convention of APT.

Again, because Nexus can already handle multiple components in terms of storage (in the case of apt-proxies), it shouldn't be a heavy lift to expose that field for uploads to apt-hosted repos right?

liachini commented 10 months ago

@nblair so you confirm that in oss versione of nexus it’s impossible to’ upload deb packaging in different directory otterrai then main? So we can’t use Components like apt repo should provide?

thank you