Ralf Ertzinger wrote:
Hi.
Matthew Miller <mattdm@xxxxxxxxxx> wrote:
In general, report packaging/build problems to Fedora, and actual issues
with the program upstream.
This may be tricky since the casual user has absolutely no clue what patches RH applied to the packages (and upstream does not know that, either).
About the only way around that is to follow the age-old advice of downloading, building and installing the latest (reads: CVS) version from the original developer of the program in question to see if the bug is still present, and report it only if it is. At that point, you would know if it were a problem with a Fedora patch or not. Otherwise, best practice is exactly as stated above. Just make sure that you let the upstream team know that you are testing on a Fedora system.
Additionally, if the problem does not exist upstream, you might be able to create a patch that fixes the problem downstream and submit it as an interim fix until the new version makes it downstream.
