On Fri, 2020-04-10 at 12:42 -0400, Alexei Podtelezhnikov wrote:
> On Fri, Apr 10, 2020 at 11:14 AM Olivier Fourdan <ofour...@redhat.com> wrote:
> > On Fri, Apr 10, 2020 at 4:38 PM Adam Jackson <a...@redhat.com> wrote:
> > > On Fri, 2020-04-10 at 15:35 +0200, Olivier Fourdan wrote:
> > > > [...]
> > > > Adam, want me to launch an official build, just to rebuild?
> > > 
> > > Yes, please!
> > 
> > Oops, looks like I've been presumptuous on that one, I don't have the 
> > rights.
> 
> xorg-x11-drv-intel has very extensive set of BuildRequires, which
> seems rather large for a driver. I presume koji satisfies those and
> your test builds do indeed match the official ones.

There *is* a difference between most mock builds and koji builds, FWIW.
They do not use exactly the same buildroot, especially not for Branched
and Rawhide. The buildroot in Koji is re-generated with all packages
tagged 'stable' quite often, and includes buildroot overrides. mock
builds, if you just use the 'normal' targets like fedora-32-x86_64 or
fedora-rawhide-x86_64, use the current official stable repo contents as
the buildroot. This is usually somewhat "behind" the buildroot koji
uses, because it's only updated from successful daily composes, and
doesn't include buildroot overrides.

The mock target with -koji on the end - like fedora-32-x86_64-koji -
have the koji buildroot repo added alongside the 'fedora' repo, so if
you use those targets, the builds should more closely match koji
builds.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://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

Reply via email to