Re: Packit service not submitting builds or updates for branched / F38

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 1, 2023 at 5:34 PM Matej Focko <mfocko@xxxxxxxxxx> 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
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux