The `nmu` boolean in the upload_history table is never set: 0 of 997,602
rows are TRUE, while 38,052 uploads in the same table carry NMU version
conventions in their version string (+nmuN or the non-maintainer
revision form -z.N, Dev-Ref 5.11.2). The upload_history_nmus view
aggregates this same always-FALSE column, so it reports no NMUs anywhere.

Tools that try to identify non-maintainer uploads via upload_history.nmu
therefore silently get zero results. We currently detect NMUs from the
version string instead.

Suggested resolution: either populate `nmu` (e.g. from the version-string
conventions above), or document the column as unmaintained/deprecated and
note the version-string approach so downstream users don't rely on it.

Reproduction (against the public mirror):
  SELECT count(*) FILTER (WHERE nmu),
         count(*) FILTER (WHERE version ~ '\+nmu[0-9]+$'
                             OR version ~ '-[0-9]+\.[0-9]+$')
  FROM upload_history;

Hello,

Bug #1140965 in qa.debian.org reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/qa/udd/-/commit/2c452857557e541c16402d4678f339be9f9ff547

------------------------------------------------------------------------
upload-history: preserve NMU flag from extractor instead of forcing false

rimporters/upload_history.rb unconditionally set current['NMU'] = false
after parsing, discarding the True/False value computed by
scripts/upload_history_extractor.py (version + changelog heuristics).
As a result upload_history.nmu was always FALSE and the
upload_history_nmus view was always empty. Parse the extractor value
instead so NMUs are recorded.

Closes: #1140965

AI-assisted: yes, opencode + muse-spark-1.3-contributor
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1140965