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

Pulp - backward compatible repofiles #3504

Open
Tracked by #2533
FrostyX opened this issue Nov 1, 2024 · 4 comments
Open
Tracked by #2533

Pulp - backward compatible repofiles #3504

FrostyX opened this issue Nov 1, 2024 · 4 comments
Assignees
@FrostyX
Labels
pulp

Comments

@FrostyX
Copy link
Member

FrostyX commented Nov 1, 2024 •
edited
Loading

Fix repofiles to be backward compatible with old paths (so users don't need to re-enable copr projects)
@FrostyX FrostyX mentioned this issue Nov 1, 2024
Open
31 tasks
@github-project-automation github-project-automation bot moved this to Needs triage in CPT Kanban Nov 1, 2024
@FrostyX FrostyX changed the title fix repofiles to be backward compatible with old paths (so users don't need to re-enable copr projects) Pulp - backward compatible repofiles Nov 1, 2024
@FrostyX FrostyX added the pulp label Nov 1, 2024
@xsuchy xsuchy moved this from Needs triage to In 3 months in CPT Kanban Nov 4, 2024
@praiskup praiskup moved this from In 3 months to In Progress in CPT Kanban Jan 6, 2025
@praiskup
Copy link
Member

We had a meeting, and we have some plan (for possible experiments)

@FrostyX
Copy link
Member Author

FrostyX commented Jan 18, 2025

Ansible PR: https://pagure.io/fedora-infra/ansible/pull-request/2437

@FrostyX
Copy link
Member Author

FrostyX commented Feb 3, 2025

We don't want to redirect things from srpm-builds chroot but otherwise we can assume it is done.

@FrostyX
Copy link
Member Author

FrostyX commented Feb 6, 2025

Another PR: https://pagure.io/fedora-infra/ansible/pull-request/2453 (already merged)

FrostyX added a commit to FrostyX/copr that referenced this issue Feb 12, 2025
@FrostyX
backend, frontend: create HTTP redirects for migrated projects
937c1c3 
See fedora-copr#3504

At the same time, this allows us to run the migration only from this backend
script, and it will propagate to the frontend database from here. Probably
making the `copr-frontend change-storage` command obsolete.
@FrostyX FrostyX mentioned this issue Feb 12, 2025
Open
FrostyX added a commit to FrostyX/copr that referenced this issue Feb 12, 2025
@FrostyX
backend, frontend: create HTTP redirects for migrated projects
edf9928 
See fedora-copr#3504

At the same time, this allows us to run the migration only from this backend
script, and it will propagate to the frontend database from here. Probably
making the `copr-frontend change-storage` command obsolete.
FrostyX added a commit to FrostyX/copr that referenced this issue Feb 12, 2025
@FrostyX
backend, frontend: create HTTP redirects for migrated projects
e917c79 
See fedora-copr#3504

At the same time, this allows us to run the migration only from this backend
script, and it will propagate to the frontend database from here. Probably
making the `copr-frontend change-storage` command obsolete.
FrostyX added a commit to FrostyX/copr that referenced this issue Feb 12, 2025
@FrostyX
backend, frontend: create HTTP redirects for migrated projects
504e699 
See fedora-copr#3504

At the same time, this allows us to run the migration only from this backend
script, and it will propagate to the frontend database from here. Probably
making the `copr-frontend change-storage` command obsolete.
FrostyX added a commit to FrostyX/copr that referenced this issue Feb 13, 2025
@FrostyX
backend, frontend: create HTTP redirects for migrated projects
1434983 
See fedora-copr#3504

At the same time, this allows us to run the migration only from this backend
script, and it will propagate to the frontend database from here. Probably
making the `copr-frontend change-storage` command obsolete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FrostyX FrostyX

Labels
pulp
Projects
CPT Kanban
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FrostyX @praiskup