Bug#613522: [akregator] Please use upstream metakit
n Tue, Feb 15, 2011 at 8:39 PM, Modestas Vainius <modax@debian.org> wrote:
> severity 613522 wishlist
> tags 613522 wontfix
> unblock 590147 by 613522
> thanks
>
> Hello,
>
> On antradienis 15 Vasaris 2011 15:11:24 Bastien ROUCARIES wrote:
>> Package: akregator
>> Version: 4:4.4.7-3
>> Severity: serious
>>
>> Please use separate source for metakit. Serious because it is code
>> duplication, lead to dataloss and moreover package is outdated.
>
> Your reasons for serious are just wrong. There is NO metakit source package in
> Debian so there is NO dublication. What is more, metakit library is hopelessly
> outdated upstream (2007 is the latest release date) and there is no proof that
> new version would fix current akregator problems. Actually, the metakit lib
> that is currently embedded in the akregator (2.4.9.5), has no interesting
> changes in comparison with the current metakit stable release (2.4.9.7) (yes,
> I have actually checked). So please do not exagerate bug severities based on
> pure guesses. You could have saved some valuable time for everybody.
>
> Future is akonadi-based akregator and, obviously, we are not interested in
> maintaining a dead library just for the sake of it.
I will maintain it, I have taken ownership of metakit and intent to
package. I will also investigate how to avoid segv.
When metakit will hit unstable are you willing to use the .so lib ?
> Moreover, unless you can actually confirm the fix for 590147, do not add false
> information to the BTS.
> P.S. Users should never set serious severity unless they can pin point Debian
> policy violation. You obviously failed to do so in this case.
Reply to: