Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=546169 --- Comment #7 from Ralf Corsepius <[email protected]> 2009-12-11 01:25:04 EDT --- (In reply to comment #6) > Upstream, does not have time to maintain this anymore. OK, then my impression was right, it's a private fork. > There are patches lined up for months now sp the ones related to memory leak. Well, this is nothing unusual. IMO, the appropriate approach to this would be to either "patch the original package" or to make your "private fork" a "public fork"/"official project". Private forks don't help anybody - How do other distros handle this issue in this particular case? > I will bump the release next time :) TIA. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list [email protected] http://www.redhat.com/mailman/listinfo/fedora-package-review
