On Mon, Oct 30, 2017 at 9:45 PM, Nicolas Braud-Santoni wrote:

> This RFS is a pretty good example: there was no new upstream version, and
> no review (or any sort of activity on the RFS) since June, while the timeout
> on mentors.debian.net is only 20 days.

The best you can do in that situation is bump the changelog date and reupload.

> I appreciate that Bart was likely trying to triage RFSes, but closing it
> rather than asking to reupload to mentors.d.n feels somewhat unfriendly,
> especially when the packaging repo is available, and up-to-date, on alioth.

That is a cron job that syncs the state of RFSes with the archive and
mentors. The maintainer of the cron job is fairly MIA, so I'm not sure
it will change any time soon.

> Note that I'm not mentionning that to complain or vent, but to report a
> problem that I'm encountering, as a non-DD contributor, in the hopes that
> it might be possible to fix it rather than let it affect other people.

Given the current general package sponsorship resources don't appear
to be increasing much year on year, I doubt it will ever be possible
for Debian to accept all proposed packages in a timely manner, sorry.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Reply via email to