On Wed, Oct 02, 2019 at 10:13:43AM -0600, Jerry James wrote: > I just received the email below. I built ntl-11.3.4-1.fc32 on > September 24. Later that day, upstream released version 11.4.0, so I > built ntl-11.4.0-1.fc32 the next day, September 25. Why has the > previous build suddenly come back from the dead? Having it go stable > now is going to break all of the ntl-using packages that I built > against 11.4.0 last week. > > Can somebody please do whatever is necessary to have the 11.4.0 build > be the one that is current in Rawhide? Thank you. So, this is my 'fault' I guess. There were some builds stuck in the signing tag in rawhide, so I retagged them to get them signed and in. In this case it made an 'older' build show up. ;( I'll check f32 for older builds and fix them all. The cause of some builds not being signed seems to be fas throwing 500 errors sporadically. We are trying to track down the cause of that now. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
