Miro Hrončok wrote:
> Because if we don't, people just gonna ignore FTBFS forever.
And this would be a problem why exactly?
Packages built for older Fedora releases tend to run on newer Fedora
releases just fine. If the package:
* has no broken dependencies, and
* is not reported as completely broken in Bugzilla,
it should be assumed to be working by default.
If you encounter a package that does not actually work, it is your job as a
user to report it. This can happen independently of whether the package
still compiles or not. It can even still be broken after a successful
rebuild.
So why are we wasting packagers' time on fixing FTBFS issues (which are
typically NOT caused by their package, but by changes in dependencies such
as your python-unversioned-command change, or such as yet another
incompatible change in GCC for the sake of compliance with some obscure
subparagraph of a language standard, etc.) when not actually needed? I
actually NEED to fix the FTBFS if the package has broken dependencies or if
I need to make some other change to it. Otherwise, the FTBFS fix is just
churn that Fedora forces me to waste my time on.
Kevin Kofler
_______________________________________________
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
