Bug#952645: Please clarify the status of ublock-origin in NEW

2020-07-15 Thread Sean Whitton
Hello, On Wed 15 Jul 2020 at 05:19PM +02, Markus Koschany wrote: > Thanks for your reply. I'm glad that ublock-origin hasn't been simply > forgotten. However I'd like to suggest to implement a strict FIFO queue > because now it is more like FILO. This would automatically reduce > support

Bug#952645: Please clarify the status of ublock-origin in NEW

2020-07-15 Thread Markus Koschany
Hello, Am 14.07.20 um 17:22 schrieb Sean Whitton: [...] >> Please clarify the status of ublock-origin and why it is still in the >> NEW queue. > > Simply that we do not have enough active FTP team members. > > Just to note that being in binary-NEW makes no difference; it gets a > full check as

Bug#952645: Please clarify the status of ublock-origin in NEW

2020-07-14 Thread Sean Whitton
Hello, On Tue 14 Jul 2020 at 10:19AM +02, Markus Koschany wrote: > I am reaching out to you because the Firefox/Chromium addon > ublock-origin is still in the NEW queue despite being uploaded four > months ago. The package is not really new in Debian and it is quite > unusual that a binary-new

Bug#952645: Please clarify the status of ublock-origin in NEW

2020-07-14 Thread Markus Koschany
Dear ftp team, I am reaching out to you because the Firefox/Chromium addon ublock-origin is still in the NEW queue despite being uploaded four months ago. The package is not really new in Debian and it is quite unusual that a binary-new package has been stuck in the queue for such a long time.