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 <quote> 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@). </quote> I'm closing this bug as the requested feature already exists. Regards, Adam