On Saturday 25 March 2017 10:46 PM, Ivo De Decker wrote:
> Hi,
> 
> On Fri, Mar 24, 2017 at 10:52:44AM +0530, Pirate Praveen wrote:
>> I don't understand why diaspora-installer was removed from testing. #858521 
>> was
>> only affecting unstable.
> 
> There are serious doubts whether this package is suitable for a stable
> release. The version that was in testing clearly wasn't (#856720 was the
> trigger for the original request in this unblock bug). Previous attempts to
> fix the issues weren't successful, and a review of the latest changes,
> combined with the filing of #858521 (which was found by piuparts testing),
> raises serious concerns about the quality of the package. For it to be allowed
> back into testing, a thorough review of the entire packaging would be needed,
> and I don't know it that's realistic for stretch.

I believe this is arbitrary, unfair and de-motivating. I can understand
packages getting removed when it has long standing rc bugs and there was
no activity from the maintainer. Here I have always responded quickly to
any rc bugs and currently it has no pending rc bugs.

#856720 caused marking for auto-removal, but it was already fixed (its
auto removal date was not reached). #858521 was also fixed quickly. I
agree it was a big mistake, it happened because I was focusing on
diaspora-installer binary package for testing and purging of
diaspora-common binary was slipped. It was indeed a regression, but
having a single critical regression which was fixed soon does not
qualify (is not enough) for a removal.

I hope you'll reconsider your decision.

> Cheers,
> 
> Ivo
> 
> 


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to