On Sat, Oct 30, 2021 at 7:45 AM lejeczek via CentOS-devel <centos-devel at centos.org> wrote: > > > > On 28/10/2021 13:30, Neal Gompa wrote: > > On Thu, Oct 28, 2021 at 7:30 AM lejeczek via CentOS-devel > > <centos-devel at centos.org> wrote: > >> > >> > >> On 27/10/2021 16:23, Sergio Correia wrote: > >>> On Wed, Oct 27, 2021 at 12:13 PM lejeczek via CentOS-devel > >>> <centos-devel at centos.org> wrote: > >>>> > >>>> On 27/10/2021 12:43, lejeczek via CentOS-devel wrote: > >>> [snip] > >>> > >>>>>>>> _______________________________________________ > >>>>>>>> > >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=2017541 > >>>>> > >>>> ps. at the moment Stream 9 is kind of tpm2-fcuked, for > >>>> clevis too do not do tpm2 :) > >>>> > >>> Actually clevis should be working again, with tpm2-tools-5.0-10.el9, > >>> which was built yesterday. > >>> > >> Great that the problem is fixed "somewhere" but, do those > >> fixes go, as updates, straight into the repos? > > When builds are made, they get tagged for c9s-gate, which is where > > they sit until they pass through automated and manual validation. > > After that's complete, they move from c9s-gate to c9s, where they get > > published and released in the next compose. Composes typically happen > > multiple times a day. > > > And how long before those should be in yum/dnf repos? A compose *includes* RPM repositories, so once a compose is released, the repositories are updated with the contents of the new compose. -- 真実はいつも一つ！/ Always, there's only one truth!