Hi all,
$SUBJECT is now happening for (at least) the second time with F38. It looks like the packit service is mis-configured and does not submit any builds updates for "branched":
https://bodhi.fedoraproject.org/updates/?user=packit
Having updates in Fedora 37 (stable branch) and Rawhide (development branch), and in some cases even Fedora 36 (oldstable branch), but *not* in the branch for the next release is really bad.
Can we get this fixed please? Errors like these really do make me not trust packit with any of my packages.
It would be great if $PACKIT_ADMIN would go through the updates that were filed by packit since the F38 branch point and submit missing builds and updates? Preferably before the F38 final freeze? ...
Fabio
Hi,
we have already been informed about the issue and fix for the issue is ready (will be deployed to production next Tuesday, unless we hit any issues in the staging instance)
https://github.com/packit/packit/pull/1863
This issue has been hit after a change in the Bodhi API that introduced a new state for releases that are in a “frozen” state (see the release schedule for Fedora 38, we have entered the Beta Freeze on February 20; also last F38 Bodhi update from Packit has been created on February 22, which is 15 days after branching and 2 days after the Beta Freeze, therefore there was no reason to suspect any issues being present).
On the other hand, if I didn't know about the merged PR, I wouldn't be able to provide you help in any way, since you haven't provided any additional details that would allow me to assess your issue appropriately (no exceptions have been caught and furthermore I don't know what package we are talking about).
In case you hit any issue in the future, feel free to reach out for help on any of the following platforms:
* #packit:fedora.im on Matrix * #packit on libera.chat * hello@packit.dev
You can also file an issue with details (project, trigger, steps to reproduce, etc.) at https://github.com/packit/packit-service/issues/new if you hit a bug. We do not consider this mailing list as a way to submit bug reports as it would create too much noise and also spam other people, thanks for understanding.
Thanks for using Packit :)
On behalf of Packit Team Matej
On 3/1/23 15:31, Fabio Valentini wrote:
Hi all,
$SUBJECT is now happening for (at least) the second time with F38. It looks like the packit service is mis-configured and does not submit any builds updates for "branched":
https://bodhi.fedoraproject.org/updates/?user=packit
Having updates in Fedora 37 (stable branch) and Rawhide (development branch), and in some cases even Fedora 36 (oldstable branch), but *not* in the branch for the next release is really bad.
Can we get this fixed please? Errors like these really do make me not trust packit with any of my packages.
It would be great if $PACKIT_ADMIN would go through the updates that were filed by packit since the F38 branch point and submit missing builds and updates? Preferably before the F38 final freeze? ...
Fabio _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
Hi,
we have already been informed about the issue and fix for the issue is ready (will be deployed to production next Tuesday, unless we hit any issues in the staging instance)
https://github.com/packit/packit/pull/1863
This issue has been hit after a change in the Bodhi API that introduced a new state for releases that are in a “frozen” state (see the release schedule for Fedora 38, we have entered the Beta Freeze on February 20; also last F38 Bodhi update from Packit has been created on February 22, which is 15 days after branching and 2 days after the Beta Freeze, therefore there was no reason to suspect any issues being present).
Sorry about that, I assumed it was the same problem as during the F37 development cycle, and not a new bug :)
On the other hand, if I didn't know about the merged PR, I wouldn't be able to provide you help in any way, since you haven't provided any additional details that would allow me to assess your issue appropriately (no exceptions have been caught and furthermore I don't know what package we are talking about).
I included a link to the updates that have been submitted by packit, where you can see that for the last 1-2 weeks, F38 updates have been missing, but I can list them manually, if it helps ...
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38 - osbuild-composer v75: submitted to F39, F37, F36, but not F38 - cockpit-composer v44: submitted to F39, F37, F36, but not F38 - gpxsee v12.1: submitted to F39, F37, F36, but not F38 - osbuild v81: submitted to F37, F36, but not F39 or F38 (?) - mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38 - osbuild-composer v76: submitted to F39, F37, F36, but not F38
It appears that some packages are more badly affected than others, so it might have to do with how they configure packit (listing branches manually or just saying "all fedora branches"?) ..
You can also file an issue with details (project, trigger, steps to reproduce, etc.) at https://github.com/packit/packit-service/issues/new if you hit a bug. We do not consider this mailing list as a way to submit bug reports as it would create too much noise and also spam other people, thanks for understanding.
I understand. I did not want to report a bug with packit. I wanted to point out that there are updates missing from Fedora 38, which will impact upgrade path from Fedora 37, which is why I thought the devel list was appropriate.
Whatever the reason, what should be done about the missing updates? I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
Fabio
Hi Fabio, answers inline below.
On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini decathorpe@gmail.com wrote:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
- osbuild-composer v75: submitted to F39, F37, F36, but not F38
- cockpit-composer v44: submitted to F39, F37, F36, but not F38
- gpxsee v12.1: submitted to F39, F37, F36, but not F38
- osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
- mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
- osbuild-composer v76: submitted to F39, F37, F36, but not F38
Thank you for the list, once we get guidance on how to proceed (see below), we will create those missing updates.
Whatever the reason, what should be done about the missing updates?
I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
We as Packit have honestly the same question: what does this freeze exactly mean? Should we continue creating bodhi updates?
CCing Ben to give us guidance. https://pagure.io/fedora-infrastructure/new_issue
Tomas
On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek ttomecek@redhat.com wrote:
Hi Fabio, answers inline below.
On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini decathorpe@gmail.com wrote:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
- osbuild-composer v75: submitted to F39, F37, F36, but not F38
- cockpit-composer v44: submitted to F39, F37, F36, but not F38
- gpxsee v12.1: submitted to F39, F37, F36, but not F38
- osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
- mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
- osbuild-composer v76: submitted to F39, F37, F36, but not F38
Thank you for the list, once we get guidance on how to proceed (see below), we will create those missing updates.
Whatever the reason, what should be done about the missing updates? I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
We as Packit have honestly the same question: what does this freeze exactly mean? Should we continue creating bodhi updates?
CCing Ben to give us guidance.
The fact that a release is currently "frozen" should not affect submission of updates at all. The only difference there is how updates are pushed from "testing" to "stable" state: Updates will not be submitted to "stable" repos automatically after a few days, but only after the freeze is officially lifted.
Since packager's cannot "mess this up" (it is enforced by update infrastructure), there is no reason to not build + submit updates for releases that are currently in a "freeze", especially if you are also submitting the updates to stable branches of Fedora.
Fabio
On 02. 03. 23 16:06, Fabio Valentini wrote:
On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek ttomecek@redhat.com wrote:
Hi Fabio, answers inline below.
On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini decathorpe@gmail.com wrote:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
- osbuild-composer v75: submitted to F39, F37, F36, but not F38
- cockpit-composer v44: submitted to F39, F37, F36, but not F38
- gpxsee v12.1: submitted to F39, F37, F36, but not F38
- osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
- mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
- osbuild-composer v76: submitted to F39, F37, F36, but not F38
Thank you for the list, once we get guidance on how to proceed (see below), we will create those missing updates.
Whatever the reason, what should be done about the missing updates? I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
We as Packit have honestly the same question: what does this freeze exactly mean? Should we continue creating bodhi updates?
CCing Ben to give us guidance.
The fact that a release is currently "frozen" should not affect submission of updates at all. The only difference there is how updates are pushed from "testing" to "stable" state: Updates will not be submitted to "stable" repos automatically after a few days, but only after the freeze is officially lifted.
Since packager's cannot "mess this up" (it is enforced by update infrastructure), there is no reason to not build + submit updates for releases that are currently in a "freeze", especially if you are also submitting the updates to stable branches of Fedora.
In other words: It depends. Same as with updates to stable releases.
I'd say that if you are creating the update in stable releases, you should also create it in frozen/branched. Not doing it creates mess.
However, whether or not an update is suitable for a stable release or for a post-Beta branched release must always be decided by the packager and never by a service.
On Thu, Mar 2, 2023 at 4:48 PM Miro Hrončok mhroncok@redhat.com wrote:
On 02. 03. 23 16:06, Fabio Valentini wrote:
On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek ttomecek@redhat.com
wrote:
Hi Fabio, answers inline below.
On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini decathorpe@gmail.com
wrote:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
- osbuild-composer v75: submitted to F39, F37, F36, but not F38
- cockpit-composer v44: submitted to F39, F37, F36, but not F38
- gpxsee v12.1: submitted to F39, F37, F36, but not F38
- osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
- mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
- osbuild-composer v76: submitted to F39, F37, F36, but not F38
Thank you for the list, once we get guidance on how to proceed (see
below), we will create those missing updates.
Whatever the reason, what should be done about the missing updates? I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
We as Packit have honestly the same question: what does this freeze
exactly mean? Should we continue creating bodhi updates?
CCing Ben to give us guidance.
The fact that a release is currently "frozen" should not affect submission of updates at all. The only difference there is how updates are pushed from "testing" to "stable" state: Updates will not be submitted to "stable" repos automatically after a few days, but only after the freeze is officially lifted.
Since packager's cannot "mess this up" (it is enforced by update infrastructure), there is no reason to not build + submit updates for releases that are currently in a "freeze", especially if you are also submitting the updates to stable branches of Fedora.
In other words: It depends. Same as with updates to stable releases.
I'd say that if you are creating the update in stable releases, you should also create it in frozen/branched. Not doing it creates mess.
However, whether or not an update is suitable for a stable release or for a post-Beta branched release must always be decided by the packager and never by a service.
Perfect, thanks for the explanation, Fabio and Miro.
We will create the missing updates.
We have already fixed this and it will be rolled out to production on Tue, 7th.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hello, just a small update. We have verified recently that Packit staging correctly creates F38 updates now: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b3613064bf
This will land in production tomorrow, so as of March 7th, Packit will correctly create F38 dist-git PRs and everything else.
Fabio, thank you for giving us a list of missing updates.
Maintainers in CC, please update your f38 dist-git branches & provide bodhi updates before the final freeze, Tue 2023-04-04, so that you have up to date versions in Fedora 38 before the release.
In my former email, I thought that only bodhi updates are missing. That was incorrect, f38 dist-git branch needs to be updated as well.
Tomas
On Thu, Mar 2, 2023 at 8:23 PM Tomas Tomecek ttomecek@redhat.com wrote:
On Thu, Mar 2, 2023 at 4:48 PM Miro Hrončok mhroncok@redhat.com wrote:
On 02. 03. 23 16:06, Fabio Valentini wrote:
On Thu, Mar 2, 2023 at 3:47 PM Tomas Tomecek ttomecek@redhat.com
wrote:
Hi Fabio, answers inline below.
On Wed, Mar 1, 2023 at 5:50 PM Fabio Valentini decathorpe@gmail.com
wrote:
On Wed, Mar 1, 2023 at 5:34 PM Matej Focko mfocko@redhat.com wrote:
- linux-system-roles v1.35.1: submitted to F39, F37, F36, but not F38
- osbuild-composer v75: submitted to F39, F37, F36, but not F38
- cockpit-composer v44: submitted to F39, F37, F36, but not F38
- gpxsee v12.1: submitted to F39, F37, F36, but not F38
- osbuild v81: submitted to F37, F36, but not F39 or F38 (?)
- mrack v1.13.3: submitted to F39, F37, F36, EPEL9, EPEL8, but not F38
- osbuild-composer v76: submitted to F39, F37, F36, but not F38
Thank you for the list, once we get guidance on how to proceed (see
below), we will create those missing updates.
Whatever the reason, what should be done about the missing updates? I'll be publishing my "builds + updates missing from Fedora Branched report" soon anyway, so the packages will show up there either way ...
We as Packit have honestly the same question: what does this freeze
exactly mean? Should we continue creating bodhi updates?
CCing Ben to give us guidance.
The fact that a release is currently "frozen" should not affect submission of updates at all. The only difference there is how updates are pushed from "testing" to "stable" state: Updates will not be submitted to "stable" repos automatically after a few days, but only after the freeze is officially lifted.
Since packager's cannot "mess this up" (it is enforced by update infrastructure), there is no reason to not build + submit updates for releases that are currently in a "freeze", especially if you are also submitting the updates to stable branches of Fedora.
In other words: It depends. Same as with updates to stable releases.
I'd say that if you are creating the update in stable releases, you should also create it in frozen/branched. Not doing it creates mess.
However, whether or not an update is suitable for a stable release or for a post-Beta branched release must always be decided by the packager and never by a service.
Perfect, thanks for the explanation, Fabio and Miro.
We will create the missing updates.
We have already fixed this and it will be rolled out to production on Tue, 7th.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue