On Mon, 27 Feb 2023 at 03:03, Petr Pisar <ppisar@xxxxxxxxxx> wrote:
V Sat, Feb 25, 2023 at 09:52:03PM -0800, Gordon Messmer napsal(a):
> On 2023-02-22 02:47, Petr Pisar wrote:
> > V Mon, Feb 20, 2023 at 11:48:26AM -0800, Gordon Messmer napsal(a):
> > >
> > > First, the bug. From these results, it looks like rpminspect is only
> > > comparing the primary package to the old build. I do see a result for the
> > > package "nghttp2", but I don't see an rpminspect result for "libnghttp2".
> > > Are sub-packages not tested, or are the results simply not exposed? (Or am
> > > I simply missing the path to find them?)
> > >
> > > ...
> > >
> > > Should I report those in bugzilla, and if so, against what component?
> > I think David prefers <https://github.com/rpminspect/rpminspect/issues/>.
>
>
> Thanks. I'll file the RFE there. But, with regard to the bug: offhand, if
> this is a bug, it seems like a bug in the koji CI scripts and not in
> rpminspect, doesn't it?
It's not Koji CI. The CI is more bound to Bodhi than to Koji. Though CI people
would probably argue that it's a completely independnent beast.
This is a general problem I see with many discussions in infrastructure. Developers shorthand a LOT of the parts of how a build occurs as 'koji' when it can be many of a lot of components inside or related partially to the build system:
- koji (tool which runs the builders)
- src.fedoraproject.org (pkgs)
- bodhi (Business logic system for artifacts)
- pdc (Product Definition Center?)
- zuul (not run by Fedora Infrastructure but called by parts)
- openqa
- koschei (system which rebuilds packages regularly for testing)
- pungi/compose
- builders talked to by koji
- sign-vault/sign-bridge/autosign
- mbs (module build system)
- kojipkgs
- oci (open container index)
- odcs (?)
- osbs (open shift build system)
- debuginfod
- fedimg (seems to push ami images?)
- download servers (mainly when a packager can't find something they built)
- various parts in openshift I am not sure of (would be good to get a list).
> Where would I find the definition of the
> "fedora-ci.koji-build.rpminspect.static-analysis" stage for review?
I know about <https://pagure.io/fedora-ci/general/issues/> which I use for
reporting issues in Fedora CI. There are more CI trackers on Pagure in
fedora-ci name space, but I don't understand the CI internals to give you
a more focused answer.
-- Petr
_______________________________________________
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
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren_______________________________________________ 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
