@Brian Once the archive is frozen this is not entirely trivial anymore as the command-not-found indexfile is stored in the now frozen archive mirror.
It seems the easiest way to fix is:
* uploading a higher version in the -updates pocket should fix the problem automatically, the database code (CommandNotFound/db/creator.py:_parse_single_commands_file()) should discard the content of older versions. There are some useful ways to control what commands are visible from the pkg, you could use "X-Cnf-Ignore-Commands: kms-universal-planes" on the "libdrm-tests" binary package stanza (see what-is-python for an example)
@Brian Once the archive is frozen this is not entirely trivial anymore as the command-not-found indexfile is stored in the now frozen archive mirror.
It seems the easiest way to fix is: d/db/creator. py:_parse_ single_ commands_ file()) should discard the content of older versions. There are some useful ways to control what commands are visible from the pkg, you could use "X-Cnf- Ignore- Commands: kms-universal- planes" on the "libdrm-tests" binary package stanza (see what-is-python for an example)
* uploading a higher version in the -updates pocket should fix the problem automatically, the database code (CommandNotFoun