.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "Config::Model::models::Dpkg::BugFiles::Control 3pm" .TH Config::Model::models::Dpkg::BugFiles::Control 3pm 2024-03-03 "perl v5.38.2" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME Config::Model::models::Dpkg::BugFiles::Control \- Configuration class Dpkg::BugFiles::Control .SH DESCRIPTION .IX Header "DESCRIPTION" Configuration classes used by Config::Model .SH Elements .IX Header "Elements" .SS report-with .IX Subsection "report-with" Often programs are distributed across several different packages, for example an upstream package 'foo' may be packaged in Debian as foo, libfoo, foo-common and foo-data. In such cases it can be useful to include related package information in bugreports, to minimise the need for 'moreinfo' requests to the submitter :) This is done by adding a "report-with" header to the control file:: .PP .Vb 1 \& report\-with: foo libfoo foo\-common foo\-data .Ve .PP Package information will be added to the bug report for each extra package listed. .PP See README.developers for details. \fI Optional. Type uniline. \fR .SS package-status .IX Subsection "package-status" request that the status information for other packages (that are not dependencies or recommendations) be included with the report. .PP See README.developers for details. \fI Optional. Type uniline. \fR .SS Submit-As .IX Subsection "Submit-As" The package maintainer can control to which packages bug reports are submitted, by setting the Package: field of the bug report. This will be mainly used to redirect bugs in packages coming from a single source to where the maintainer likes to have them. See README.developers for details. \fI Optional. Type uniline. \fR .SS Send-To .IX Subsection "Send-To" Packages not distributed by Debian can take advantage of reportbug utility too with this parameter. For instance: .PP .Vb 1 \& Send\-To: bugs.myproject.com .Ve .PP ``reportbug`` will add ``submit@` ``quiet@`` or ``maintonly@`` to form the address the bug report mail is send to. .PP (Note: you probably should use dpkg's support for Origin and Bugs tags in lieu of this support.) .PP See README.developers for details. \&\fI Optional. Type uniline. \fR .SH "SEE ALSO" .IX Header "SEE ALSO" .IP \(bu 4 cme