Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Install *-distro-aliases using pip #2746

Open
nforro opened this issue Mar 11, 2025 · 2 comments
Open

Install *-distro-aliases using pip #2746

nforro opened this issue Mar 11, 2025 · 2 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@nforro
Copy link
Member

nforro commented Mar 11, 2025

Currently, an updated version doesn't get into the images until Fedora 41 Bodhi update for a new upstream release reaches stable. We could do what we do with requre and install the packages using pip from a git clone, or we could at least install from PyPI to avoid the Fedora updates testing phase.
@lbarcziova lbarcziova added area/general Related to whole service, not a specific part/integration. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. complexity/single-task Regular task, should be done within days. labels Mar 11, 2025
@lbarcziova lbarcziova moved this from new to priority-backlog in Packit Kanban Board Mar 11, 2025
@lbarcziova
Copy link
Member

We discussed on standup, and would probably rather go directly with installing from Copr: https://copr.fedorainfracloud.org/coprs/g/rpm-software-management/fedora-distro-aliases/builds/, which will make it possible to get the new versions faster.

@nforro
Copy link
Member Author

nforro commented Mar 11, 2025

Then we should onboard opensuse-distro-aliases to Packit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: priority-backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nforro @lbarcziova