#8601 Packages that fail to build SRPM are not reported during the mass rebuild bugzillas
Opened 3 years ago by churchyard. Modified 7 months ago

See for example: https://bugzilla.redhat.com/show_bug.cgi?id=1739634

The package cannot create SRPM:

$ fedpkg srpm 


error: Bad source: .../python-chm/pychm-0.8.4.1.tar.gz: No such file or directory
Could not execute srpm: Failed to execute command.

And hence it was not rebuilt since Fedora 29:

https://koji.fedoraproject.org/koji/packageinfo?packageID=3571

But no FTBFS bug was reported.


Yeah, this is because koji doesn't even send the 'start' fedmsg until after this, so there's not an indication a build was attempted.

Perhaps we could add in another set of messages there before/after srpm creation?

not sure how else to detect them. ;(

Well we do attempt to build them, so a check after the mass rebuild for packages we never heard back from would do.

Not entirely the same failure but it seems tcl wasn't bumped at all.

Metadata Update from @humaton:
- Issue tagged with: mini-initiative

2 years ago

Metadata Update from @mohanboddu:
- Issue tagged with: backlog

2 years ago

@humaton Just FYI, this is related to the MLT rebuild we have discussed via IRC

This could be solved by not only reporting bugzillas for packages listed in 37-failures.html, but also the remaining packages listed only in f37-need-rebuild.html. The bugzillas could be slightly different (they could say: "Your package was not rebuilt in the mass rebuild, investigate why"). That could also help discover packages like https://pagure.io/releng/issue/10920

Login to comment on this ticket.

Metadata
Boards 2
Mini Initiative Status: Backlog
mini-initative Status: Backlog