I installed Evolution 2.2 today (which is remarkably stable). Do I report bugs to Fedora, Ximian or both?
On Tue, Mar 08, 2005 at 11:06:54AM -0500, David Cary Hart wrote:
I installed Evolution 2.2 today (which is remarkably stable). Do I report bugs to Fedora, Ximian or both?
In general, report packaging/build problems to Fedora, and actual issues with the program upstream.
Hi.
Matthew Miller mattdm@mattdm.org 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).
On Tue, Mar 08, 2005 at 06:21:55PM +0100, Ralf Ertzinger wrote:
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).
A good point, and I'm sure part of the reason for Fedora's policy of tracking upstream as closely as possible with minimal patching.
Ralf Ertzinger wrote:
Hi.
Matthew Miller mattdm@mattdm.org 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.
On Tue, 08 Mar 2005 11:06:54 -0500, David Cary Hart Fedora@tqmcube.com wrote:
I installed Evolution 2.2 today (which is remarkably stable). Do I report bugs to Fedora, Ximian or both?
evolution 2.2 from where? I don't see evolution 2.2 in today's development tree. If you aren't using an evo package built by red hat for fedora core, I'm not sure wise it is to file bugs against fedora's bugzilla.
To generalize Matthew's advice a bit. In general, report packaging/build problems to the package vendor and actual program bugs upstream. If this evo 2.2 package is not built by red hat you'll need to use the appropriate package vendor's bugzilla for packaging issues.
-jef
On Tue, 2005-03-08 at 12:14 -0500, Jeff Spaleta wrote:
evolution 2.2 from where? I don't see evolution 2.2 in today's development tree. If you aren't using an evo package built by red hat for fedora core, I'm not sure wise it is to file bugs against fedora's bugzilla.
To generalize Matthew's advice a bit. In general, report packaging/build problems to the package vendor and actual program bugs upstream. If this evo 2.2 package is not built by red hat you'll need to use the appropriate package vendor's bugzilla for packaging issues.
This is a source build. Might bug reporting - possibly - be useful to the developers in advance of the Fedora build? Might this not - possibly - lead to patch development? Be assured that I am not asking rhetorically.
On Tue, 08 Mar 2005 12:29:35 -0500, David Cary Hart Fedora@tqmcube.com wrote:
This is a source build. Might bug reporting - possibly - be useful to the developers in advance of the Fedora build? Might this not - possibly
- lead to patch development? Be assured that I am not asking
rhetorically.
I think i can pretty savely say that pre-emptive bug reports which anticipate problems for packages that don't even exist yet are not something fedora developers are going to want want to see. If its a source build... file the problem upstream. Fedora developers 'should' be watching upstream. Patch development should happen upstream as much as possible and then back ported if needed at the distribution level when it comes time to package this source code up.
There is more than enough clutter in fedora's bugzilla right now to keep developers busy... pre-emptive bugs reports for issues that might not even exist in the upstream code by the time the codebase is packaged in fedora seems like a waste of everyone's time.
-jef
On Tue, 2005-03-08 at 11:06, David Cary Hart wrote:
I installed Evolution 2.2 today (which is remarkably stable). Do I report bugs to Fedora, Ximian or both?
It sounds like you built it yourself, in which case report bugs upstream to bugzilla.ximian.com (I built "official" evo 2.2 packages yesterday; they landed in Rawhide this morning).
Otherwise, if using a Fedora package, you have to make an judgement call as to whether the problem is specific to Fedora, or a general problem from upstream, and file accordingly.
Of course, this assumes you have a fair knowledge of the internals of the code/packaging process etc which many users won't have (and probably shouldn't be expected to). Ideally you should check both upstream and downstream bugzillas for duplicates.
When in doubt, file upstream (bugzilla.ximian.com for Evolution), and make it clear which distro the problem was seen on, and exactly which package. If it looks like I've messed up the build or there's some other Fedora-specific problem, then file in bugzilla.redhat.com - but we try to do as much as possible upstream.
And if a bug seems to us to be in the wrong bugzilla, we'll try to refile it.
Hope all that makes sense
Dave
On Wed, 2005-03-09 at 10:21 -0500, Dave Malcolm wrote:
On Tue, 2005-03-08 at 11:06, David Cary Hart wrote:
I installed Evolution 2.2 today (which is remarkably stable). Do I report bugs to Fedora, Ximian or both?
It sounds like you built it yourself, in which case report bugs upstream to bugzilla.ximian.com (I built "official" evo 2.2 packages yesterday; they landed in Rawhide this morning).
Thanks. I'm working on the compilations as I write.
- - - - <gratuitous snip>-----------
Hope all that makes sense
It does.