On Thu, 2022-04-21 at 17:21 +0200, Julian Sikorski wrote:
> Hello,
> 
> I have recently created 3 updates to goffice and gnumeric:
> 
> - https://bodhi.fedoraproject.org/updates/FEDORA-2022-a7a300f5b1
> - https://bodhi.fedoraproject.org/updates/FEDORA-2022-9a07603dd6
> - https://bodhi.fedoraproject.org/updates/FEDORA-2022-ab9857bfaf
> 
> Despite putting the gnome-chemistry-utils update into the same batch, 3 
> FailsToInstall bugs were filed:
> 
> - https://bugzilla.redhat.com/show_bug.cgi?id=2077398
> - https://bugzilla.redhat.com/show_bug.cgi?id=2077400
> - https://bugzilla.redhat.com/show_bug.cgi?id=2077401
> 
> Am I doing something wrong?

The bug text states:

"The data was generated solely from koji buildroot, so it might be
newer than the latest compose or the content on mirrors"

This sounds like Miro's tool just uses whatever is currently in the
buildroot - it is not working on the contents of updates or anything
like that.

If you handled this by submitting a buildroot override for
goffice/gnumeric and then building gnome-chemistry-utils , then I
imagine what happened is that Miro's tool ran these build tests against
the current stable g-c-u with the goffice/gnumeric from the buildroot
override, and so they failed.

The bug text does suggest a way you can avoid this: instead of using
buildroot overrides, use side tags. If you had created a side tag and
built goffice/gnumeric in it, then built g-c-u in it, then created an
update from it, then you should not get a bug filed. It's also a nicer
experience than using buildroot overrides once you're used to the
process, and it avoids the problem of something else unexpectedly
getting built against the buildroot override while it's active (which I
brought up a few weeks ago on this list).
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to