DFSG NEW Queue

Frequently Asked Questions

Answers to the questions maintainers most often ask about this dashboard. If your package was rejected, see also the Reject FAQ.

How soon after I upload will my package appear here?

Usually a little more than an hour. The archive software (dak) processes uploads once an hour and then refreshes ftp-master's NEW page. This site looks at the NEW queue several times an hour, so a package normally shows up at quarter past or half past the hour following that run.

How do I know the dashboard is up to date?

The dashboard shows when the NEW queue was last checked. That time moves on with every check, including the many checks that find nothing new. If it is later than the hourly archive run that followed your upload and your package is still missing, see the next question.

The dashboard has been updated but my upload is not on it. Why?

Only uploads that are waiting in the NEW queue are listed. An upload that did not need NEW processing, or that the archive refused before it reached NEW, never appears here.
Only uploads targeting unstable or experimental are reviewed through this site. Uploads to other distributions are not shown.
If a newer version of the same source package is also in NEW, the dashboard lists the newest one. Earlier versions are still reachable from its review page.

Where can I see the state of my package's review?

Go to /reviews/source for the highest version of your source package that we know about, with any review and public notes. Use /reviews/source/version for a specific version. If you log in with Salsa, My Packages lists your own uploads.

In what order are packages reviewed?

The dashboard is sorted by a priority score, though reviewers are free to pick any package. The score grows with the time spent in the queue. It is higher for packages that block other bugs (most of all release-critical ones) and for packages that are already installed by users. It is lower when the upload closes no bug or the package has no Vcs-* fields. Binary-NEW uploads of sources already in the archive are prioritised, and so are uploads that only rename a source package already in the archive.

My upload was rejected. What do I do now?

We treat a rejection as a request for changes to that upload. The rejection email and the review page give the reasons, and the Reject FAQ lists the common ones. Fix them and upload again in the usual way. If you think the decision is wrong, reply to the rejection email; the About page describes how disputes are resolved.

How is a new upload of a rejected package handled?

Where it goes in the queue: the priority score of the rejected upload is not carried over. However, a new upload of a previously reviewed package is highlighted to its reviewer, and it will normally jump to the front of that reviewer's own queue.
Who reviews it: typically the same reviewer, unless they have asked for someone else to handle it.
Where to explain what changed: the changelog is the best place to say what has been fixed since the rejected upload.

My package has been waiting a long time, or is urgent. Who do I contact?

The About page describes how to ping the team and what to do for an urgent fix.

My question is not answered here.

Ask on Matrix at #debian-dfsg:matrix.debian.social or by email to dfsg-team@debian.org. Problems with this site itself can be reported at its issue tracker on Salsa.