tibbs added a new comment to an issue you are following:
Yes, of course, if what you say was actually possible then I certainly would have done it
and not bothered with worrying about untagging the bad build. But there is a class of
errors which prevent you from doing a new build. Perhaps gcc is broken and now cannot
rebuild itself. Or perhaps there is an error in a dependency which prevents one of the
buildroot packages from being installed. In these cases, you need to be able to tag and
Certainly more careful testing would help here, but this is rendered more difficult when
rawhide as a whole has other issues or hasn't composed in a long time.
In any case, there was a workaround (tagging an old version of the package into f28-build
in order to build a new version of the package). I am not sure if that workaround is
blessed by releng as a proper way to deal with this, and I'm also not sure what
permissions are needed to tag into each of the various tags.
To reply, visit the link below or just reply to this email