Rich Freeman schrieb:
If the user recognizes this as a critical package, then they can do the
research before deciding on whether to use the package as is, attempt to
downgrade, or wait until a fix is released.
But, you've ALREADY overwritten the previous version of the package
that presumably didn't have this problem. What if downgrading doesn't
cause the problem to go away? What if it is due to some dependency or
toolchain change? Users would presumably want to roll back to the
binaries that were working just a few minutes ago, not build new ones
that might or might not have the same issue.
Users could weigh their options and then decide on how to best proceed. In
case of zfs, they still have time until next reboot to fix this.
Or the maintainer can set PROPERTIES="interactive" in anticipation of such a
situation and ask "Are you sure you want to install this [y/N]?".
Best regards,
Chí-Thanh Christopher Nguyễn
