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.

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

GA rebase checklist should handle "manual cherry-picks" into Pungi compose #1602

Closed
jlebon opened this issue Nov 1, 2023 · 2 comments · Fixed by #1604
Closed

GA rebase checklist should handle "manual cherry-picks" into Pungi compose #1602

jlebon opened this issue Nov 1, 2023 · 2 comments · Fixed by #1604

Comments

@jlebon
Copy link
Member

jlebon commented Nov 1, 2023

See e.g. coreos/fedora-coreos-config#2692 in which we manually fast-tracked a package to match the compose.

Maybe we just need another GitHub Action that we can manually run for that period of time which just ensures our lockfiles match the latest compose output?

dustymabe added a commit to dustymabe/fedora-coreos-config that referenced this issue Nov 2, 2023
This patch adds a repo definition for the latest candidate compose
for a given Fedora release. This is only relevant in the lead up to
Beta and GA for a given Fedora release where packages in the candidate
compose can lead the Fedora stable repos. For our `next` stream we want
to pick up the packages quickly, so using the candidate compose as input
makes sense.

Using this repo in the `next*` streams should address
coreos/fedora-coreos-tracker#1602
dustymabe added a commit to dustymabe/fedora-coreos-config that referenced this issue Nov 2, 2023
This patch adds a repo definition for the latest candidate compose
for a given Fedora release. This is only relevant in the lead up to
Beta and GA for a given Fedora release where packages in the candidate
compose can lead the Fedora stable repos. For our `next` stream we want
to pick up the packages quickly, so using the candidate compose as input
makes sense.

Using this repo in the `next*` streams should address
coreos/fedora-coreos-tracker#1602
jlebon pushed a commit to coreos/fedora-coreos-config that referenced this issue Nov 2, 2023
This patch adds a repo definition for the latest candidate compose
for a given Fedora release. This is only relevant in the lead up to
Beta and GA for a given Fedora release where packages in the candidate
compose can lead the Fedora stable repos. For our `next` stream we want
to pick up the packages quickly, so using the candidate compose as input
makes sense.

Using this repo in the `next*` streams should address
coreos/fedora-coreos-tracker#1602
@dustymabe
Copy link
Member

With coreos/fedora-coreos-config#2705 and coreos/fedora-coreos-config#2706 should we close this?

jlebon added a commit to jlebon/fedora-coreos-tracker that referenced this issue Nov 3, 2023
… repo

This is a repo that we only want during the Beta period. Make sure we
remove it otherwise.

Closes: coreos#1602
@jlebon
Copy link
Member Author

jlebon commented Nov 3, 2023

I opened #1604 which will close this.

jlebon added a commit that referenced this issue Nov 3, 2023
… repo

This is a repo that we only want during the Beta period. Make sure we
remove it otherwise.

Closes: #1602
aaradhak pushed a commit to aaradhak/fedora-coreos-config that referenced this issue Mar 18, 2024
This patch adds a repo definition for the latest candidate compose
for a given Fedora release. This is only relevant in the lead up to
Beta and GA for a given Fedora release where packages in the candidate
compose can lead the Fedora stable repos. For our `next` stream we want
to pick up the packages quickly, so using the candidate compose as input
makes sense.

Using this repo in the `next*` streams should address
coreos/fedora-coreos-tracker#1602
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants