Hi Paul, The usual stuff: real life. In any case I am not using esajpip much these days. So let's finally kill it. I'll file a RM bug report ASAP.
Thanks On Mon, Mar 11, 2019 at 7:47 PM Paul Gevers <[email protected]> wrote: > > Hi Mathieu, > > On 11-03-2019 18:41, Mathieu Malaterre wrote: > > Could someone please clarify the status of esajpip package. A bug with > > severity serious was set to the package and the package was > > 'autoremoved'. Since the serious bug was caused by a build-dep (at > > some point back in time), do I need to do anything for esajpip to > > migrate back to testing (921780 is closed) ? > > > > Thanks > > > > ---------- Forwarded message --------- > > From: Santiago Vila <[email protected]> > > Date: Mon, Mar 11, 2019 at 6:00 PM > > Subject: Re: Bug#921780: esajpip: FTBFS (LaTeX error) > > > > I would hope so, as this was definitely not the package's fault, but I > > guess you will have to ask for it explicitly because of the freeze. > > Your package was removed from testing because you didn't respond for a > month to a serious bug against your package. Your package will not > migrate back to testing before the release of buster unless you can > convince us why it should be part of the release. If you follow that > route, please use an unblock bug to communicate about it, and please > answer the question below in it. > > Why didn't you take action on the autoremoval mails that you should have > received? It would have been so much easier. > > Paul >
