Bug#1018218: bugs.debian.org: Pseudo-header needed for “affects” relationship
> Yes, you can, because this: > > > 3) add support for a placeholder bug number like “-1” (similar to how > > the clone command works) > > is an intrinsic part of how the "Control" pseudo-header works. Somehow I missed that, even though I was looking. There are several docs on the bug tracker and the doc I found seemed to only indicate that -1 was used in the cloning context. Sorry for the trouble.
Bug#1018218: bugs.debian.org: Pseudo-header needed for “affects” relationship
On Sat, 2022-08-27 at 10:40 +0200, debbug.deb...@sideload.33mail.com wrote: > 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 > Yes, you can, because this: > 3) add support for a placeholder bug number like “-1” (similar to how > the clone command works) is an intrinsic part of how the "Control" pseudo-header works. Quoting https://www.debian.org/Bugs/Reporting#pseudoheader Control Commands Control: control commands Allows for any of the commands which must be sent to cont...@bugs.debian.org to work when sent to sub...@bugs.debian.org or n...@bugs.debian.org. -1 initially refers to the current bug (that is, the bug created by a mail to submit@ or the bug messaged with nnn@). I'm closing this bug as the requested feature already exists. Regards, Adam
Bug#1018218: bugs.debian.org: Pseudo-header needed for “affects” relationship
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 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)
