On Wed, Jul 12, 2023 at 1:01 PM Mikel Olasagasti <[email protected]> wrote:
>
> Hau idatzi du Fabio Valentini ([email protected]) erabiltzaileak
> (2023 uzt. 12(a), az. (11:53)):
> >
> > On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti <[email protected]> 
> > wrote:
> > >
> >
> > (snip)
> >
> > >
> > > > golang-github-moby-spdystream            go-sig, mikelo2
> > >
> > > Builds fine in Koschei and no BZ
> > >
> > > > golang-github-openapi-validate           alexsaezm, go-sig
> > >
> > > Builds fine in Koschei and no BZ
> >
> > This is usually an indication that the package fails to even produce a
> > valid SRPM file (i.e. "fedpkg srpm" fails).
> > In this case, mass rebuild will skip it, no FTBFS bug will be filed,
> > and koschei will keep using the last "known good" SRPM from koji.
>
> Both packages work for me. I'm doing the following:
>
> $ fedpkg clone golang-github-moby-spdystream
> $ cd golang-github-moby-spdystream
> $ fedpkg srpm
> $ mock -r fedora-rawhide-x86_64
> /tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm

If that is indeed the case, then the missing f38 build was likely
caused by a hiccup during the f38 mass rebuild.
To get the package off the "long term FTBFS retirements" list, all
that would be needed is to run "fedpkg build".

Fabio
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to