On Fri, 13 Jun 2008 16:27:46 -0400, Jesse Keating wrote:
1) It's a bug regarding a released version, so any changes would
require
bodhi updates
Plus:
- check other open bugs
- check whether there's a new upstream release
Else it would be a test update just for this fix, and possibly another one
right after that because the maintainer awakes and dislikes the small
fix-update that doesn't address other issues. It could even be that
additional problems are not covered in bugzilla. I wouldn't want to work
on this bug without talking to the package maintainer first.
2) it's essentially enabling a feature, that may or may not work
and one
would hope that if there was a reason this wasn't turned on, it would be
listed in the spec file.
For those reasons, I wouldn't be quick to jump in and try to fix it. It'd
be worth doing a scratch build just to see if it would compile, and maybe
work but I still wouldn't feel comfortable without talking to the maintainer
in question first.
And the maintainer already works with the next upstream release series [in
rawhide]. It would not be the first time that those packages are pushed to
the other branches. It has been done before with Audacious, even with
changes in the plugin ABI+API.