Create deb and rpm packages with each conda release

[marcoesters]

Checklist

• I added a descriptive title
• I searched open issues and couldn't find a duplicate

What?

Anaconda produces deb and rpm packages with each conda release. They are currently available in the following repositories:

• deb: https://repo.anaconda.com/pkgs/misc/debrepo/
• rpm: https://repo.anaconda.com/pkgs/misc/rpmrepo/

This is currently accomplished by installing conda into a new environment and packaging the directory into a deb and an rpm package. These packages are then indexed and uploaded to the repositories mentioned above.

These repositories are maintained and controlled by Anaconda. conda is, however, an open-source project and should thus be the entity creating these packages.

Why?

The current deb and rpm releases for conda are built in a private repository by Anaconda. conda, however, is an open source product and should thus be the entity producing these artifacts and managing the repositories.

Integrating this process into the release process ensures that these package formats are available with each conda release. This can potentially be expanded to other package formats.

User impact

conda gains control over all conda-related artifacts. This consolidates the codebase and facilitates bug reports. It also provides the opportunity to build other package formats with a new repository.

Goals

• Create a repository for deb and rpm packages owned and controlled by conda.
• Incorporate the generation of these packages into the release process.

Tasks

• Create repositories on a conda-owned domain for deb and rpm packages
• Generate a GPG key to sign the packages
• Create conda and upload conda packages with each release
• Create workflow to build deb and rpm packages on release and upload to repository

This epic is blocked by:

No response

This epic blocks:

No response