Package: bugs.debian.org Severity: wishlist X-Debbugs-Cc: debbug.deb...@sideload.33mail.com
When composing a bug report where another package is affected by the bug, there is no way to express that because the control command makes bug number a required field: http://5ekxbftvqg26oir5wle3p27ax3wksbxcecnm6oemju7bjra2pn26s3qd.onion/Bugs/server-control#affects So you cannot write the header: control: affects $bugNumber $otherPkg because you don’t yet have a bug# for the report you are writing. The workaround is cumbersome: You must submit the bug report and wait for a bug# to be generated. Then you must compose a separate control msg that references the new bug number. It shouldn’t be that tedious because you know at the time of composition what other pkgs are affected. I can see 3 possible solutions: 1) introduce a new pseudo-header “Affects” and/or 2) make the <bug number> field optional so that it defaults to the bug number being processed and/or 3) add support for a placeholder bug number like “-1” (similar to how the clone command works)
