Hans de Goede wrote:
> Well, that is a fix, but the real problem is that either the new libglvnd
> enabled mesa should not be in updates-stable and thus not in the
> buildroot; or both the new libglvnd enabled mesa and the new libglvnd
> should be in updates-stable.
This is the result of 4 very poor decisions, by different people/groups:
1. the decision to enable libglvnd in an update to a stable release. IMHO,
such a change is totally unsuitable for a stable release update and
should have been done in Rawhide only.
2. the decision to block Bodhi pushes on ostree failures. Without that,
Bodhi would not have been stuck for days with all updates locked and this
fiasco might possibly have been avoided. If the ostree compose fails, the
Bodhi push should just proceed with an empty or old ostree directory
(whatever is easier to implement). Rarely used experimental delivery
methods should not hold the entire distribution hostage.
3. the decision to use autokarma. This is just yet another broken update
that went stable due to autokarma. Autokarma is an absolutely
unacceptable practice and should not be allowed. All push requests should
be issued by a human after reviewing the status.
4. the decision to disallow direct stable pushes. The right way to fix the
issue quickly, limiting the damage once done, would have been to push
libglvnd directly to stable. But Bodhi won't allow that. Direct stable
pushes are an essential mechanism to fix regressions and to limit the
number of affected users by minimizing the exposure time to the
regression.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
