Hi Marcelo, On 06-03-2019 15:07, Marcelo Jorge Vieira wrote: > On Tue, 2019-03-05 at 15:51 +0100, Paul Gevers wrote: >> On 05-03-2019 15:44, Marcelo Jorge Vieira wrote: >>> Could you, please, unblock pyres and remotecv? >>> The new pyres version closes #917658. >> >> pyres is not in testing. Can you please elaborate why you think we >> should grant you an exception, assuming that we don't know what pyres >> is >> (which is true at least for me). > > Now pyres package is only in unstable, but it was in testing for more > than 440 days. It was removed last month from testing because of > #917658. > > http://bugs.debian.org/917658 > > > This is the lifetime of pyres package: > > [2019-03-04] Accepted pyres 1.5-2 (source all) into unstable > [2019-02-13] pyres REMOVED from testing > [2017-11-26] pyres 1.5-1 MIGRATED to testing > [2017-11-16] Accepted pyres 1.5-1 (source all) into unstable > > > IMHO, this is a good point to unblock pyres package. So you missed the soft freeze (like loads of other packages). The soft freeze is there for a reason, we try to prevent surprises while we are preparing for the release of buster. You didn't act on that FTBFS bug (or at least didn't show it) until two days ago. I am asking my question again, try to answer it differently this time: Can you please elaborate why you think we should grant your package an exception, assuming that we don't know what pyres is? Paul
Attachment:
signature.asc
Description: OpenPGP digital signature