Hello,
I would like to hear about the community opinion on this.
The pipeline delivery team currently installs a number of packages in some
of their pipeline tasks, this package list (package + package version) is
stored in a file and that file gets updated when a new version of a listed
package is around in Koji.
The problem is that Koji is being used to check for new package versions
but that doesn't mean a compose was run which can lead to a situation where
mirrors do not have that "latest" package version that was built on koji
(a compose is run weekly).
To illustrate things in a practical way:
- A new version (1.34.0) of NetworkManager was built in koji:
https://koji.mbox.centos.org/koji/packageinfo?packageID=1433;
- The package is not available in centos mirrors (yet):
http://mirror.centos.org/centos/8-stream/BaseOS/aarch64/os/Packages/ ;
- The package gets updated in this file:
https://gitlab.com/redhat/edge/ci-cd/manifests/-/blob/update-package-Networ…
;
- The pipeline job fails because yum can't find that version of the
package in the BaseOS repository.
I know that we can download those RPMs directly from Koji but I was
wondering if this is where the SIG could/should step in and make the user
experience a bit better by providing a single source of truth, be it a
repository or some tooling, to retrieve package info and show where they
stand.
Any thoughts on this?
Thanks!
--
Leonardo Rossetti
Red Hat <https://www.redhat.com>
lrossett(a)redhat.com
<https://www.redhat.com>
Hi all - here is a link to the video recording from yesterday's call
https://www.youtube.com/watch?v=b0pUDb_BWSQ
I will be putting together a poll to make sure the meeting time works for
most people going forward, and will also put together an Office Hours in
about 2 weeks. hope to see you there!
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
I'd like to personally invite you to the upcoming CentOS Automotive SIG
meeting, which will happen this upcoming Thursday. I'd also like to
personally apologize for the connectivity problems we had during the
initial meeting. We will have a better solution this time using Bluejeans.
In addition, we will start the actual meeting 5 minutes after the hour so I
can help people join as needed.
date: Sept 16
time: 8am PDT / 11am EDT / 5pm CEST
conf: https://bluejeans.com/870492784
agenda:
https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings/2021-09
We will go over the goals and details about the SIG at the beginning for
those who missed it last time, and will set some time aside to talk about
the ongoing infrastructure status. I'd also like to have some time to talk
about what people want to see in this SIG in terms of content, and if we
are able, to outline the steps needed to get to a release of the Automotive
variant.
I'm also planning to announce a monthly Office Hours informal meeting that
will happen between the standard formal meetings, in the same time slot.
This will simply be an hour for interested parties to drop in and talk shop
about automotive software.
Thanks & I hope to see you there on Thursday! Let me know if you have any
questions.
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive