diff options
Diffstat (limited to 'includes/squeeze/common')
29 files changed, 548 insertions, 1094 deletions
diff --git a/includes/squeeze/common/doc/FAQ/debian-faq.en.html.tar.gz b/includes/squeeze/common/doc/FAQ/debian-faq.en.html.tar.gz Binary files differindex a1eb63445..abee0f971 100644 --- a/includes/squeeze/common/doc/FAQ/debian-faq.en.html.tar.gz +++ b/includes/squeeze/common/doc/FAQ/debian-faq.en.html.tar.gz diff --git a/includes/squeeze/common/doc/FAQ/debian-faq.en.pdf.gz b/includes/squeeze/common/doc/FAQ/debian-faq.en.pdf.gz Binary files differindex e7c835a02..3b428a113 100644 --- a/includes/squeeze/common/doc/FAQ/debian-faq.en.pdf.gz +++ b/includes/squeeze/common/doc/FAQ/debian-faq.en.pdf.gz diff --git a/includes/squeeze/common/doc/FAQ/debian-faq.en.ps.gz b/includes/squeeze/common/doc/FAQ/debian-faq.en.ps.gz Binary files differindex 6d744f7b0..0ff09491e 100644 --- a/includes/squeeze/common/doc/FAQ/debian-faq.en.ps.gz +++ b/includes/squeeze/common/doc/FAQ/debian-faq.en.ps.gz diff --git a/includes/squeeze/common/doc/FAQ/debian-faq.en.txt.gz b/includes/squeeze/common/doc/FAQ/debian-faq.en.txt.gz Binary files differindex 87b535cb6..aeaaa4122 100644 --- a/includes/squeeze/common/doc/FAQ/debian-faq.en.txt.gz +++ b/includes/squeeze/common/doc/FAQ/debian-faq.en.txt.gz diff --git a/includes/squeeze/common/doc/FAQ/html/ch-basic_defs.en.html b/includes/squeeze/common/doc/FAQ/html/ch-basic_defs.en.html index 5d0babb9c..cc5565314 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-basic_defs.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-basic_defs.en.html @@ -597,7 +597,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-choosing.en.html b/includes/squeeze/common/doc/FAQ/html/ch-choosing.en.html index af1f232ae..e0403cc09 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-choosing.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-choosing.en.html @@ -948,7 +948,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-compat.en.html b/includes/squeeze/common/doc/FAQ/html/ch-compat.en.html index 7d9ea1562..375bff45d 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-compat.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-compat.en.html @@ -541,7 +541,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-contributing.en.html b/includes/squeeze/common/doc/FAQ/html/ch-contributing.en.html index 607a72bbd..db2d6e329 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-contributing.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-contributing.en.html @@ -357,7 +357,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-customizing.en.html b/includes/squeeze/common/doc/FAQ/html/ch-customizing.en.html index e112c5386..94671123b 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-customizing.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-customizing.en.html @@ -703,7 +703,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-faqinfo.en.html b/includes/squeeze/common/doc/FAQ/html/ch-faqinfo.en.html index 5349d74f2..9edac2076 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-faqinfo.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-faqinfo.en.html @@ -394,7 +394,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-ftparchives.en.html b/includes/squeeze/common/doc/FAQ/html/ch-ftparchives.en.html index 71b92a5dd..0efd28ab9 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-ftparchives.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-ftparchives.en.html @@ -743,7 +743,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-getting.en.html b/includes/squeeze/common/doc/FAQ/html/ch-getting.en.html index cc28eeddb..16d506c41 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-getting.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-getting.en.html @@ -438,7 +438,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-kernel.en.html b/includes/squeeze/common/doc/FAQ/html/ch-kernel.en.html index 995f64819..58781c998 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-kernel.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-kernel.en.html @@ -376,7 +376,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-nexttime.en.html b/includes/squeeze/common/doc/FAQ/html/ch-nexttime.en.html index 0b2724860..cd6c875e5 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-nexttime.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-nexttime.en.html @@ -364,7 +364,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-pkg_basics.en.html b/includes/squeeze/common/doc/FAQ/html/ch-pkg_basics.en.html index d67b3d7a2..72799b217 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-pkg_basics.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-pkg_basics.en.html @@ -1110,7 +1110,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-pkgtools.en.html b/includes/squeeze/common/doc/FAQ/html/ch-pkgtools.en.html index 763c63acf..391e6560f 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-pkgtools.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-pkgtools.en.html @@ -1186,7 +1186,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-redistrib.en.html b/includes/squeeze/common/doc/FAQ/html/ch-redistrib.en.html index 6a2b65d87..77bbf561b 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-redistrib.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-redistrib.en.html @@ -327,7 +327,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-software.en.html b/includes/squeeze/common/doc/FAQ/html/ch-software.en.html index e2beb961d..2c2d7458e 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-software.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-software.en.html @@ -626,7 +626,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-support.en.html b/includes/squeeze/common/doc/FAQ/html/ch-support.en.html index a078153a5..5036cb539 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-support.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-support.en.html @@ -666,7 +666,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/ch-uptodate.en.html b/includes/squeeze/common/doc/FAQ/html/ch-uptodate.en.html index 5f13eb5ba..33cc9f08e 100644 --- a/includes/squeeze/common/doc/FAQ/html/ch-uptodate.en.html +++ b/includes/squeeze/common/doc/FAQ/html/ch-uptodate.en.html @@ -623,7 +623,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/footnotes.en.html b/includes/squeeze/common/doc/FAQ/html/footnotes.en.html index eede4011b..881269fa1 100644 --- a/includes/squeeze/common/doc/FAQ/html/footnotes.en.html +++ b/includes/squeeze/common/doc/FAQ/html/footnotes.en.html @@ -281,7 +281,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/FAQ/html/index.en.html b/includes/squeeze/common/doc/FAQ/html/index.en.html index 7575c572b..c7115e0d1 100644 --- a/includes/squeeze/common/doc/FAQ/html/index.en.html +++ b/includes/squeeze/common/doc/FAQ/html/index.en.html @@ -509,7 +509,7 @@ The Debian GNU/Linux FAQ </p> <address> -version 4.0.4+nmu1, 3 January 2010<br> +version 4.0.3, 6 August 2008<br> <br> Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br> <br> diff --git a/includes/squeeze/common/doc/bug-log-access.txt b/includes/squeeze/common/doc/bug-log-access.txt index 748b01633..c8fa75f57 100644 --- a/includes/squeeze/common/doc/bug-log-access.txt +++ b/includes/squeeze/common/doc/bug-log-access.txt @@ -1,10 +1,12 @@ +Methods of accessing the bug tracking system logs + Accessing active bug reports - Each message received at or sent by the bug processing system is logged - and made available in a number of ways. + Each message received at or sent by the bug processing system is + logged and made available in a number of ways. - The primary access method is to use the web pages. See the forms on the - main BTS page at http://bugs.debian.org/ + The primary access method is to use the web pages. See the forms on + the main BTS page at http://bugs.debian.org/ There is a mailserver which can send bug reports as plain text on request. To use it send the word help as the sole contents of an email @@ -16,8 +18,9 @@ Accessing archived bug reports Each closed bug report is archived 28 days after the last message relating to it is received and filed. This means that it is no longer - possible to access it or change anything about it using the control and - service bots. However, the reports are still accessible for viewing. + possible to access it or change anything about it using the control + and service bots. However, the reports are still accessible for + viewing. You can search the bug report archive using the WWW forms at http://bugs.debian.org/, simply select the "archived bugs" option. @@ -41,12 +44,12 @@ Accessing the raw bug data Please do not rely on *.status files in the bug spools, as they are obsolete, for compatibility purposes only, and will be removed at some point in the future. Use the *.summary files instead. - __________________________________________________________________ + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/bug-log-mailserver.txt b/includes/squeeze/common/doc/bug-log-mailserver.txt index 764d25a9e..447a059f7 100644 --- a/includes/squeeze/common/doc/bug-log-mailserver.txt +++ b/includes/squeeze/common/doc/bug-log-mailserver.txt @@ -1,30 +1,32 @@ +Introduction to the bug system request server + There is a mailserver which can send the bug reports and indices as plain text on request. To use it you send a mail message to request@bugs.debian.org. The - Subject of the message is ignored, except for generating the Subject of - the reply. + Subject of the message is ignored, except for generating the Subject + of the reply. The body you send should be a series of commands, one per line. You'll receive a reply which looks like a transcript of your message being - interpreted, with a response to each command. No notifications are sent - to anyone for the commands listed here and the mail isn't logged + interpreted, with a response to each command. No notifications are + sent to anyone for the commands listed here and the mail isn't logged anywhere publicly available. Any text on a line starting with a hash sign # is ignored; the server will stop processing when it finds a line with a control terminator ( - quit, thank you, or two hyphens are common examples). It will also stop - if it encounters too many unrecognised or badly-formatted commands. If - no commands are successfully handled it will send the help text for the - server. + quit, thank you, or two hyphens are common examples). It will also + stop if it encounters too many unrecognised or badly-formatted + commands. If no commands are successfully handled it will send the + help text for the server. Commands available send bugnumber send-detail bugnumber Requests the transcript for the bug report in question. - send-detail sends all of the "boring" messages in the transcript - as well, such as the various auto-acks. + send-detail sends all of the "boring" messages in the + transcript as well, such as the various auto-acks. index [full] index-summary by-package @@ -34,8 +36,8 @@ Commands available number, respectively. index-maint - Requests the index page giving the list of maintainers with bugs - (open and recently-closed) in the tracking system. + Requests the index page giving the list of maintainers with + bugs (open and recently-closed) in the tracking system. index maint maintainer Requests the index pages of bugs in the system for the @@ -55,8 +57,8 @@ Commands available send-unmatched last|-1 send-unmatched old|-2 Requests logs of messages not matched to a particular bug - report, for this week, last week and the week before. (Each week - ends on a Wednesday.) + report, for this week, last week and the week before. (Each + week ends on a Wednesday.) getinfo filename Request a file containing information about package(s) and or @@ -100,18 +102,19 @@ Commands available -- Stops processing at this point of the message. After this you may include any text you like, and it will be ignored. You can - use this to include longer comments than are suitable for #, for - example for the benefit of human readers of your message - (reading it via the tracking system logs or due to a CC or BCC). + use this to include longer comments than are suitable for #, + for example for the benefit of human readers of your message + (reading it via the tracking system logs or due to a CC or + BCC). #... One-line comment. The # must be at the start of the line. debug level - Sets the debugging level to level, which should be a nonnegative - integer. 0 is no debugging; 1 is usually sufficient. The - debugging output appears in the transcript. It is not likely to - be useful to general users of the bug system. + Sets the debugging level to level, which should be a + nonnegative integer. 0 is no debugging; 1 is usually + sufficient. The debugging output appears in the transcript. It + is not likely to be useful to general users of the bug system. There is a reference card for the mailservers, available via the WWW, in bug-mailserver-refcard.txt or by email using the refcard command @@ -119,19 +122,19 @@ Commands available If you wish to manipulate bug reports you should use the control@bugs.debian.org address, which understands a superset of the - commands listed above. This is described in another document, available - on the WWW, in the file bug-maint-mailcontrol.txt, or by sending help - to control@bugs. + commands listed above. This is described in another document, + available on the WWW, in the file bug-maint-mailcontrol.txt, or by + sending help to control@bugs. - In case you are reading this as a plain text file or via email: an HTML - version is available via the bug system main contents page + In case you are reading this as a plain text file or via email: an + HTML version is available via the bug system main contents page http://www.debian.org/Bugs/. - __________________________________________________________________ + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/bug-mailserver-refcard.txt b/includes/squeeze/common/doc/bug-mailserver-refcard.txt index 757fb2dad..04a075b9c 100644 --- a/includes/squeeze/common/doc/bug-mailserver-refcard.txt +++ b/includes/squeeze/common/doc/bug-mailserver-refcard.txt @@ -1,3 +1,5 @@ +Mail servers' reference card + Full documentation of the mail servers is available on the WWW, in the files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by sending the word help to each mailserver. @@ -68,12 +70,12 @@ Synopsis of bug submission and followup addresses * nnn-done * nnn-close * nnn-subscribe - __________________________________________________________________ + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/bug-maint-info.txt b/includes/squeeze/common/doc/bug-maint-info.txt index 332541279..b584c6671 100644 --- a/includes/squeeze/common/doc/bug-maint-info.txt +++ b/includes/squeeze/common/doc/bug-maint-info.txt @@ -1,12 +1,15 @@ +Developers' information regarding the bug processing system + Initially, a bug report is submitted by a user as an ordinary mail message to submit@bugs.debian.org. This will then be given a number, acknowledged to the user, and forwarded to debian-bugs-dist. If the submitter included a Package line listing a package with a known maintainer the maintainer will get a copy too. - The Subject line will have Bug#nnn: added, and the Reply-To will be set - to include both the submitter of the report and nnn@bugs.debian.org. - __________________________________________________________________ + The Subject line will have Bug#nnn: added, and the Reply-To will be + set to include both the submitter of the report and + nnn@bugs.debian.org. + _________________________________________________________________ * Closing bug reports * Followup messages @@ -19,20 +22,20 @@ * Subscribing to bugs * More-or-less obsolete subject-scanning feature * Obsolete X-Debian-PR: quiet feature - __________________________________________________________________ + _________________________________________________________________ Closing bug reports - Debian bug reports should be closed when the problem is fixed. Problems - in packages can only be considered fixed once a package that includes - the bug fix enters the Debian archive. + Debian bug reports should be closed when the problem is fixed. + Problems in packages can only be considered fixed once a package that + includes the bug fix enters the Debian archive. Normally, the only people that should close a bug report are the - submitter of the bug and the maintainer(s) of the package against which - the bug is filed. There are exceptions to this rule, for example, the - bugs filed against unknown packages or certain generic pseudo-packages. - When in doubt, don't close bugs, first ask for advice on the - debian-devel mailing list. + submitter of the bug and the maintainer(s) of the package against + which the bug is filed. There are exceptions to this rule, for + example, the bugs filed against unknown packages or certain generic + pseudo-packages. When in doubt, don't close bugs, first ask for advice + on the debian-devel mailing list. Bug reports should be closed by sending email to nnn-done@bugs.debian.org. The message body needs to contain an @@ -49,8 +52,8 @@ Closing bug reports The person closing the bug, the person who submitted it and the debian-bugs-closed mailing list will each get a notification about the - change in status of the report. The submitter and the mailing list will - also receive the contents of the message sent to nnn-done. + change in status of the report. The submitter and the mailing list + will also receive the contents of the message sent to nnn-done. Followup messages @@ -59,9 +62,9 @@ Followup messages forwarding the bug report. Please note that these are two distinct addresses. - If a developer wishes to reply to a bug report they should simply reply - to the message, respecting the Reply-To header. This will not close the - bug. + If a developer wishes to reply to a bug report they should simply + reply to the message, respecting the Reply-To header. This will not + close the bug. The bug tracking system will receive the message at nnn@bugs.debian.org, pass it on to the package maintainer, file the @@ -94,8 +97,8 @@ Severity levels The bug system records a severity level with each bug report. This is set to normal by default, but can be overridden either by supplying a Severity line in the pseudo-header when the bug is submitted (see the - instructions for reporting bugs), or by using the severity command with - the control request server. + instructions for reporting bugs), or by using the severity command + with the control request server. The severity levels are: @@ -111,9 +114,9 @@ Severity levels serious is a severe violation of Debian policy (roughly, it violates a - "must" or "required" directive), or, in the package maintainer's - or release manager's opinion, makes the package unsuitable for - release. + "must" or "required" directive), or, in the package + maintainer's or release manager's opinion, makes the package + unsuitable for release. important a bug which has a major effect on the usability of a package, @@ -131,10 +134,10 @@ Severity levels difficult to fix due to major design considerations. Certain severities are considered release-critical, meaning the bug - will have an impact on releasing the package with the stable release of - Debian. Currently, these are critical, grave and serious. For complete - and canonical rules on what issues merit these severities, see the list - of Release-Critical Issues for Lenny. + will have an impact on releasing the package with the stable release + of Debian. Currently, these are critical, grave and serious. For + complete and canonical rules on what issues merit these severities, + see the list of Release-Critical Issues for Lenny. Tags for bug reports @@ -143,9 +146,9 @@ Tags for bug reports when you look at the full bug log. Tags can be set by supplying a Tags line in the pseudo-header when the - bug is submitted (see the instructions for reporting bugs), or by using - the tags command with the control request server. Separate multiple - tags with commas, spaces, or both. + bug is submitted (see the instructions for reporting bugs), or by + using the tags command with the control request server. Separate + multiple tags with commas, spaces, or both. The current bug tags are: @@ -159,15 +162,15 @@ Tags for bug reports This bug won't be fixed. Possibly because this is a choice between two arbitrary ways of doing things and the maintainer and submitter prefer different ways of doing things, possibly - because changing the behaviour will cause other, worse, problems - for others, or possibly for other reasons. + because changing the behaviour will cause other, worse, + problems for others, or possibly for other reasons. moreinfo This bug can't be addressed until more information is provided by the submitter. The bug will be closed if the submitter doesn't provide more information in a reasonable (few months) - timeframe. This is for bugs like "It doesn't work". What doesn't - work? + timeframe. This is for bugs like "It doesn't work". What + doesn't work? unreproducible This bug can't be reproduced on the maintainer's system. @@ -178,8 +181,8 @@ Tags for bug reports The maintainer is requesting help with dealing with this bug. pending - A solution to this bug has been found and an upload will be made - soon. + A solution to this bug has been found and an upload will be + made soon. fixed This bug is fixed or worked around (by a non-maintainer upload, @@ -235,8 +238,8 @@ Tags for bug reports This bug particularly applies to the woody distribution. sarge - This is a distribution tag, which has two effects. When set on a - bug, the bug can only affect sarge (though it may also affect + This is a distribution tag, which has two effects. When set on + a bug, the bug can only affect sarge (though it may also affect other distributions if other distribution tags are set) but otherwise normal buggy/fixed/absent rules apply. The bug also should not be archived until it is fixed in sarge. @@ -248,8 +251,8 @@ Tags for bug reports from them. etch - This is a distribution tag, which has two effects. When set on a - bug, the bug can only affect etch (though it may also affect + This is a distribution tag, which has two effects. When set on + a bug, the bug can only affect etch (though it may also affect other distributions if other distribution tags are set) but otherwise normal buggy/fixed/absent rules apply. The bug also should not be archived until it is fixed in etch. @@ -261,11 +264,11 @@ Tags for bug reports from them. lenny - This is a release tag, which has two effects. When set on a bug, - the bug can only affect lenny (though it may also affect other - releases if other release tags are set) but otherwise normal - buggy/fixed/absent rules apply. The bug also should not be - archived until it is fixed in lenny. + This is a release tag, which has two effects. When set on a + bug, the bug can only affect lenny (though it may also affect + other releases if other release tags are set) but otherwise + normal buggy/fixed/absent rules apply. The bug also should not + be archived until it is fixed in lenny. lenny-ignore This release-critical bug is to be ignored for the purposes of @@ -274,11 +277,11 @@ Tags for bug reports authorization from them. squeeze - This is a release tag, which has two effects. When set on a bug, - the bug can only affect squeeze (though it may also affect other - releases if other release tags are set) but otherwise normal - buggy/fixed/absent rules apply. The bug also should not be - archived until it is fixed in squeeze. + This is a release tag, which has two effects. When set on a + bug, the bug can only affect squeeze (though it may also affect + other releases if other release tags are set) but otherwise + normal buggy/fixed/absent rules apply. The bug also should not + be archived until it is fixed in squeeze. squeeze-ignore This release-critical bug is to be ignored for the purposes of @@ -287,48 +290,40 @@ Tags for bug reports authorization from them. sid - This is a release tag, which has two effects. When set on a bug, - the bug can only affect sid (though it may also affect other - releases if other release tags are set) but otherwise normal - buggy/fixed/absent rules apply. The bug also should not be - archived until it is fixed in sid. - - experimental - This is a release tag, which has two effects. When set on a bug, - the bug can only affect experimental (though it may also affect + This is a release tag, which has two effects. When set on a + bug, the bug can only affect sid (though it may also affect other releases if other release tags are set) but otherwise normal buggy/fixed/absent rules apply. The bug also should not - be archived until it is fixed in experimental. - - The meanings of the latter 8 distribution-specific tags have changed - recently; the -ignore tags ignore the bug for the purposes of testing - propagation. The release tags indicate that the bug in question should - not be archived until it is fixed in the set of releases specified. The - release tags also indicate that a bug should only be considered buggy - in the set of releases specified. [In other words, the bug is absent in - any release whose corresponding release tag is not set if any release - tags are set; otherwise the normal found/fixed rules apply.] - - Release tags should not be used if proper versioning of the bug would - achieve the desired effect, as they require manual addition and - removal. If you are unsure if a release tag is required, contact the - Debian BTS Administrators (owner@bugs.debian.org) or the release team - for advice. + be archived until it is fixed in sid. + + experimental + This is a release tag, which has two effects. When set on a + bug, the bug can only affect experimental (though it may also + affect other releases if other release tags are set) but + otherwise normal buggy/fixed/absent rules apply. The bug also + should not be archived until it is fixed in experimental. + + The meanings of the latter 8 tags have changed recently; the ignore + tags ignore the bug for the purpose of a testing propagation. The + release tags, which used to only indicate which bugs affected a + specific release, now indicate when a bug can be archived and the set + of releases for which a bug can be considered to be found or fixed. Recording that you have passed on a bug report - When a developer forwards a bug report to the developer of the upstream - source package from which the Debian package is derived, they should - note this in the bug tracking system as follows: + When a developer forwards a bug report to the developer of the + upstream source package from which the Debian package is derived, they + should note this in the bug tracking system as follows: Make sure that the To field of your message to the author has only the author(s) address(es) in it; put the person who reported the bug, nnn-forwarded@bugs.debian.org and nnn@bugs.debian.org in the CC field. - Ask the author to preserve the CC to nnn-forwarded@bugs.debian.org when - they reply, so that the bug tracking system will file their reply with - the original report. These messages are only filed and are not sent on; - to send a message as normal, send them to nnn@bugs.debian.org as well. + Ask the author to preserve the CC to nnn-forwarded@bugs.debian.org + when they reply, so that the bug tracking system will file their reply + with the original report. These messages are only filed and are not + sent on; to send a message as normal, send them to nnn@bugs.debian.org + as well. When the bug tracking system gets a message at nnn-forwarded it will mark the relevant bug as having been forwarded to the address(es) in @@ -347,8 +342,8 @@ Changing bug ownership have an owner. The owner can be set by supplying an Owner line in the pseudo-header - when the bug is submitted (see the instructions for reporting bugs), or - by using the owner and noowner commands with the control request + when the bug is submitted (see the instructions for reporting bugs), + or by using the owner and noowner commands with the control request server. Incorrectly listed package maintainers @@ -366,24 +361,24 @@ Reopening, reassigning and manipulating bugs It is possible to reassign bug reports to other packages, to reopen erroneously-closed ones, to modify the information saying to where, if - anywhere, a bug report has been forwarded, to change the severities and - titles of reports, to set the ownership of bugs, to merge and unmerge - bug reports, and to record the versions of packages in which bugs were - found and in which they were fixed. This is done by sending mail to - control@bugs.debian.org. + anywhere, a bug report has been forwarded, to change the severities + and titles of reports, to set the ownership of bugs, to merge and + unmerge bug reports, and to record the versions of packages in which + bugs were found and in which they were fixed. This is done by sending + mail to control@bugs.debian.org. - The format of these messages is described in another document available - on the World Wide Web or in the file bug-maint-mailcontrol.txt. A plain - text version can also be obtained by mailing the word help to the - server at the address above. + The format of these messages is described in another document + available on the World Wide Web or in the file + bug-maint-mailcontrol.txt. A plain text version can also be obtained + by mailing the word help to the server at the address above. Subscribing to bugs The bug tracking system also allows bug submitters, developers and other interested third parties to subscribe to individual bugs. This feature can be used by those wishing to keep an eye on a bug, without - having to subscribe to a package through the PTS. All messages that are - received at nnn@bugs.debian.org, are sent to subscribers. + having to subscribe to a package through the PTS. All messages that + are received at nnn@bugs.debian.org, are sent to subscribers. Subscribing to a bug can be done by sending an email to nnn-subscribe@bugs.debian.org. The subject and body of the email are @@ -394,16 +389,17 @@ Subscribing to bugs It is also possible to unsubscribe from a bug. Unsubscribing can be done by sending an email to nnn-unsubscribe@bugs.debian.org. The subject and body of the email are again ignored by the BTS. Users will - be sent a confirmation message which they must reply to if they wish to - be unsubscribed from the bug. - - By default, the address subscribed is the one found in the From header. - If you wish to subscribe another address to a bug, you will need to - encode the address to be subscribed into the subscription message. This - takes the form of: nnn-subscribe-localpart=example.com@bugs.debian.org. - That example would send localpart@example.com a subscription message - for bug nnn. The @ sign must be encoded by changing it to an = sign. - Similarly, an unsubscription takes the form + be sent a confirmation message which they must reply to if they wish + to be unsubscribed from the bug. + + By default, the address subscribed is the one found in the From + header. If you wish to subscribe another address to a bug, you will + need to encode the address to be subscribed into the subscription + message. This takes the form of: + nnn-subscribe-localpart=example.com@bugs.debian.org. That example + would send localpart@example.com a subscription message for bug nnn. + The @ sign must be encoded by changing it to an = sign. Similarly, an + unsubscription takes the form nnn-unsubscribe-localpart=example.com@bugs.debian.org. In both cases, the subject and body of the email will be forwarded to the email address within the request for confirmation. @@ -417,12 +413,13 @@ More-or-less obsolete subject-scanning feature example, by using reply to all recipients). A similar scheme operates for maintonly, done, quiet and forwarded, - which treat mail arriving with a Subject tag as having been sent to the - corresponding nnn-whatever@bugs.debian.org address. + which treat mail arriving with a Subject tag as having been sent to + the corresponding nnn-whatever@bugs.debian.org address. - Messages arriving at plain forwarded and done -- ie, with no bug report - number in the address -- and without a bug number in the Subject will - be filed under "junk" and kept for a few weeks, but otherwise ignored. + Messages arriving at plain forwarded and done -- ie, with no bug + report number in the address -- and without a bug number in the + Subject will be filed under "junk" and kept for a few weeks, but + otherwise ignored. Obsolete X-Debian-PR: quiet feature @@ -430,14 +427,14 @@ Obsolete X-Debian-PR: quiet feature forwarding anywhere messages it received at debian-bugs, by putting an X-Debian-PR: quiet line in the actual mail header. - This header line is now ignored. Instead, send your message to quiet or - nnn-quiet (or maintonly or nnn-maintonly). - __________________________________________________________________ + This header line is now ignored. Instead, send your message to quiet + or nnn-quiet (or maintonly or nnn-maintonly). + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/bug-maint-mailcontrol.txt b/includes/squeeze/common/doc/bug-maint-mailcontrol.txt index 10fb802af..56ddd08c0 100644 --- a/includes/squeeze/common/doc/bug-maint-mailcontrol.txt +++ b/includes/squeeze/common/doc/bug-maint-mailcontrol.txt @@ -1,11 +1,13 @@ +Introduction to the bug control and manipulation mailserver + Just as request@bugs.debian.org allows the retrieval of bug data and documentation by email, control@bugs.debian.org allows bug reports to be manipulated in various ways. The control server works just like the request server, except that it has some additional commands; in fact, it's the same program. The two - addresses are only separated to avoid users making mistakes and causing - problems while merely trying to request information. + addresses are only separated to avoid users making mistakes and + causing problems while merely trying to request information. Since the commands specific to the control server actually change the status of a bug, a notification about processing the commands is sent @@ -24,36 +26,34 @@ Commands available at the control mailserver - General Versioning Duplicates Misc. + General Versioning Duplicates Misc. reassign severity tag retitle submitter - affects - summary - found | notfound - fixed | notfixed - reopen + found | notfound + fixed | notfixed + reopen - merge | unmerge - forcemerge - clone + merge | unmerge + forcemerge + clone - thanks - # - forwarded | notforwarded - owner | noowner - block | unblock - archive | unarchive + thanks + # + forwarded | notforwarded + owner | noowner + block | unblock + archive | unarchive reassign bugnumber package [ version ] Records that bug #bugnumber is a bug in package. This can be - used to set the package if the user forgot the pseudo-header, or - to change an earlier assignment. No notifications are sent to - anyone (other than the usual information in the processing + used to set the package if the user forgot the pseudo-header, + or to change an earlier assignment. No notifications are sent + to anyone (other than the usual information in the processing transcript). If you supply a version, the bug tracking system will note that @@ -62,55 +62,52 @@ Commands available at the control mailserver You can assign a bug to two packages at once by separating the package names with a comma. However, you should only do this if the bug can be fixed by a change to either package. If this is - not the case, you should clone the bug and reassign the clone to - the other package. + not the case, you should clone the bug and reassign the clone + to the other package. reopen bugnumber [ originator-address | = | ! ] Reopens #bugnumber if it is closed. - By default, or if you specify =, the original submitter is still - as the originator of the report, so that they will get the ack - when it is closed again. + By default, or if you specify =, the original submitter is + still as the originator of the report, so that they will get + the ack when it is closed again. If you supply an originator-address the originator will be set to the address you supply. If you wish to become the new - originator of the reopened report you can use the ! shorthand or - specify your own email address. + originator of the reopened report you can use the ! shorthand + or specify your own email address. It is usually a good idea to tell the person who is about to be recorded as the originator that you're reopening the report, so that they will know to expect the ack which they'll get when it is closed again. - If the bug is not closed then reopen won't do anything, not even - change the originator. To change the originator of an open bug - report, use the submitter command; note that this will inform - the original submitter of the change. + If the bug is not closed then reopen won't do anything, not + even change the originator. To change the originator of an open + bug report, use the submitter command; note that this will + inform the original submitter of the change. If the bug was recorded as being closed in a particular version of a package but recurred in a later version, it is better to use the found command instead. found bugnumber [ version ] - Record that #bugnumber has been encountered in the given version - of the package to which it is assigned. version may be a fully - qualified version, of the form sourcepackagename/version. + Record that #bugnumber has been encountered in the given + version of the package to which it is assigned. The bug tracking system uses this information, in conjunction - with fixed versions recorded when closing bugs, to display lists - of bugs open in various versions of each package. It considers a - bug to be open when it has no fixed version, or when it has been - found more recently than it has been fixed. + with fixed versions recorded when closing bugs, to display + lists of bugs open in various versions of each package. It + considers a bug to be open when it has no fixed version, or + when it has been found more recently than it has been fixed. If no version is given, then the list of fixed versions for the bug is cleared. This is identical to the behaviour of reopen. - version may be a fully qualified version, of the form - sourcepackagename/version. This command will only cause a bug to be marked as not done if - no version is specified, or if the version being marked found is - equal to or greater than the highest version marked fixed. (If - you are certain that you want the bug marked as not done, use + no version is specified, or if the version being marked found + is equal to the version which was last marked fixed. (If you + are certain that you want the bug marked as not done, use reopen in conjunction with found.) This command was introduced in preference to reopen because it @@ -119,18 +116,16 @@ Commands available at the control mailserver notfound bugnumber version Remove the record that #bugnumber was encountered in the given - version of the package to which it is assigned. version may be a - fully qualified version, of the form sourcepackagename/version. + version of the package to which it is assigned. This differs from closing the bug at that version in that the bug is not listed as fixed in that version either; no - information about that version will be known. It is intended for - fixing mistakes in the record of when a bug was found. + information about that version will be known. It is intended + for fixing mistakes in the record of when a bug was found. fixed bugnumber version Indicate that bug #bugnumber was fixed in the given version of - the package to which it is assigned. version may be a fully - qualified version, of the form sourcepackagename/version. + the package to which it is assigned. This does not cause the bug to be marked as closed, it merely adds another version in which the bug was fixed. Use the @@ -139,16 +134,11 @@ Commands available at the control mailserver notfixed bugnumber version Remove the record that bug #bugnumber has been fixed in the - given version. version may be a fully qualified version, of the - form sourcepackagename/version. + given version. This command is equivalent to found followed by notfound (the found removes the fixed at a particular version, and notfound - removes the found) with the exception that the bug is not - reopened if the found version is greater than any existing fixed - version. It is intended for fixing mistakes in the record of - when a bug was fixed; in most cases, you actually want found, - not notfixed. + removes the found.) submitter bugnumber originator-address | ! Changes the originator of #bugnumber to originator-address. @@ -165,14 +155,7 @@ Commands available at the control mailserver maintainer at address. This does not actually forward the report. This can be used to change an existing incorrect forwarded-to address, or to record a new one for a bug that - wasn't previously noted as having been forwarded. address should - generally be a URI, or possibly an email address. Using a URI - where possible allows tools to query a remote bug tracking - system (such as bugzilla) for a bug's status. - - Example usage: - - forwarded 12345 http://bugz.illa.foo/cgi/54321 + wasn't previously noted as having been forwarded. notforwarded bugnumber Forgets any idea that bugnumber has been forwarded to any @@ -180,14 +163,17 @@ Commands available at the control mailserver forwarded then this will do nothing. retitle bugnumber new-title - Changes the title of a bug report to that specified (the default - is the Subject mail header from the original report). Will also - change the titles of all bug reports which this bug is merged - with. + Changes the title of a bug report to that specified (the + default is the Subject mail header from the original report). + + Unlike most of the other bug-manipulation commands when used on + one of a set of merged reports this will change the title of + only the individual bug requested, and not all those with which + it is merged. severity bugnumber severity - Set the severity level for bug report #bugnumber to severity. No - notification is sent to the user who reported the bug. + Set the severity level for bug report #bugnumber to severity. + No notification is sent to the user who reported the bug. Severities are critical, grave, serious, important, normal, minor, and wishlist. @@ -195,27 +181,6 @@ Commands available at the control mailserver For their meanings please consult the general developers' documentation for the bug system. - affects bugnumber [ + | - | = ] package [ package ... ] - Indicates that a bug affects another package. In the case where - bugnumber causes breakage in package even though the bug is - actually present in the package to which it is assigned, this - causes the bug to be listed by default in the package list of - package. This should generally be used where the bug is severe - enough to cause multiple reports from users to be assigned to - the wrong package. - - summary bugnumber [message number] - Selects a message to use as a summary of a bug. The first - non-pseudoheader paragraph of that message is parsed and set as - the summary of the bug which is displayed on the top of the bug - report page. This is useful in cases where the original report - doesn't correctly describe the problem or the bug has many - messages which make it difficult to identify the actual problem. - - If message number is not given, clears the summary. message - number is the message number as listed in the bugreport cgi - script output. - clone bugnumber NewID [ new IDs ... ] The clone control command allows you to duplicate a bug report. It is useful in the case where a single report actually @@ -238,21 +203,21 @@ Commands available at the control mailserver merge -1 -3 merge bugnumber bugnumber ... - Merges two or more bug reports. When reports are merged opening, - closing, marking or unmarking as forwarded and reassigning any - of the bugs to a new package will have an identical effect on - all of the merged reports. + Merges two or more bug reports. When reports are merged + opening, closing, marking or unmarking as forwarded and + reassigning any of the bugs to a new package will have an + identical effect on all of the merged reports. Before bugs can be merged they must be in exactly the same - state: either all open or all closed, with the same forwarded-to - upstream author address or all not marked as forwarded, all - assigned to the same package or package(s) (an exact string - comparison is done on the package to which the bug is assigned), - and all of the same severity. If they don't start out in the - same state you should use reassign, reopen and so forth to make - sure that they are before using merge. Titles are not required - to match, and will not be affected by the merge. Tags are not - required to match, either, they will be joined. + state: either all open or all closed, with the same + forwarded-to upstream author address or all not marked as + forwarded, all assigned to the same package or package(s) (an + exact string comparison is done on the package to which the bug + is assigned), and all of the same severity. If they don't start + out in the same state you should use reassign, reopen and so + forth to make sure that they are before using merge. Titles are + not required to match, and will not be affected by the merge. + Tags are not required to match, either, they will be joined. If any of the bugs listed in a merge command is already merged with another bug then all the reports merged with any of the @@ -262,15 +227,17 @@ Commands available at the control mailserver Merging reports causes a note to appear on each report's logs; on the WWW pages this is includes links to the other bugs. - Merged reports are all expired simultaneously, and only when all - of the reports each separately meet the criteria for expiry. + Merged reports are all expired simultaneously, and only when + all of the reports each separately meet the criteria for + expiry. forcemerge bugnumber bugnumber ... - Forcibly merges two or more bug reports. The settings of the - first bug listed which must be equal in a normal merge are - assigned to the bugs listed next. To avoid typos erroneously - merging bugs, bugs must be in the same package. See the text - above for a description of what merging means. + Forcibly merges two or more bug reports. The first bug listed + is the master bug, and its settings (the settings which must be + equal in a normal merge) are assigned to the bugs listed next. + To avoid typos erroneously merging bugs, bugs must be in the + same package. See the text above for a description of what + merging means. Note that this makes it possible to close bugs by merging; you are responsible for notifying submitters with an appropriate @@ -292,13 +259,12 @@ Commands available at the control mailserver you want to disconnect more than one bug simply include several unmerge commands in your message. - tags bugnumber [ + | - | = ] tag [ tag ... ] [ + | - | = tag ... ] ] - Sets tags for the bug report #bugnumber. No notification is sent - to the user who reported the bug. Setting the action to + means - to add each tag following, - means to remove each tag following, - and = means to set the following tags to the list provided. - Intervening +, -, or = change the action for the tags following. - The default action is adding. + tags bugnumber [ + | - | = ] tag [ tag ... ] + Sets tags for the bug report #bugnumber. No notification is + sent to the user who reported the bug. Setting the action to + + means to add each given tag, - means to remove each given tag, + and = means to ignore the current tags and set them afresh to + the list provided. The default action is adding. Example usage: @@ -317,9 +283,6 @@ Commands available at the control mailserver # set tags to exactly 'moreinfo' and 'unreproducible' tags 123456 = moreinfo unreproducible - # remove the moreinfo tag and add a patch tag - tags 123456 - moreinfo + patch - Available tags currently include patch, wontfix, moreinfo, unreproducible, help, pending, fixed, fixed-in-experimental, fixed-upstream, security, upstream, confirmed, d-i, ipv6, lfs, @@ -341,24 +304,24 @@ Commands available at the control mailserver close bugnumber [ fixed-version ] (deprecated) Close bug report #bugnumber. - A notification is sent to the user who reported the bug, but (in - contrast to mailing bugnumber-done@bugs.debian.org) the text of - the mail which caused the bug to be closed is not included in - that notification. The maintainer who closes a report needs to - ensure, probably by sending a separate message, that the user - who reported the bug knows why it is being closed. The use of - this command is therefore deprecated. See the developer's - information about how to close a bug properly. + A notification is sent to the user who reported the bug, but + (in contrast to mailing bugnumber-done@bugs.debian.org) the + text of the mail which caused the bug to be closed is not + included in that notification. The maintainer who closes a + report needs to ensure, probably by sending a separate message, + that the user who reported the bug knows why it is being + closed. The use of this command is therefore deprecated. See + the developer's information about how to close a bug properly. - If you supply a fixed-version, the bug tracking system will note - that the bug was fixed in that version of the package. + If you supply a fixed-version, the bug tracking system will + note that the bug was fixed in that version of the package. package [ packagename ... ] Limits the following commands so that they will only apply to - bugs filed against the listed packages. You can list one or more - packages. If you don't list any packages, the following commands - will apply to all bugs. You're encouraged to use this as a - safety feature in case you accidentally use the wrong bug + bugs filed against the listed packages. You can list one or + more packages. If you don't list any packages, the following + commands will apply to all bugs. You're encouraged to use this + as a safety feature in case you accidentally use the wrong bug numbers. Example usage: @@ -374,12 +337,13 @@ Commands available at the control mailserver severity 234567 wishlist owner bugnumber address | ! - Sets address to be the "owner" of #bugnumber. The owner of a bug - claims responsibility for fixing it. This is useful to share out - work in cases where a package has a team of maintainers. + Sets address to be the "owner" of #bugnumber. The owner of a + bug claims responsibility for fixing it. This is useful to + share out work in cases where a package has a team of + maintainers. - If you wish to become the owner of the bug yourself, you can use - the ! shorthand or specify your own email address. + If you wish to become the owner of the bug yourself, you can + use the ! shorthand or specify your own email address. noowner bugnumber Forgets any idea that the bug has an owner other than the usual @@ -392,20 +356,17 @@ Commands available at the control mailserver requirements for archival, ignoring time. unarchive bugnumber - Unarchives a bug that was previously archived. Unarchival should - generally be coupled with reopen and found/fixed as appropriate. - Bugs that have been unarchived can be archived using archive - assuming the non-time based archival requirements are met. You - should not be using unarchive to make trivial changes to - archived bugs, such as changing the submitter; its primary - purpose is to allow for the reopening of bugs which have been - archived without the intervention of BTS administrators. + Unarchives a bug that was previously archived. Unarchival + should generally be coupled with reopen and found/fixed as + appropriate. Bugs that have been unarchived can be archived + using archive assuming the non-time based archival requirements + are met. #... One-line comment. The # must be at the start of the line. The - text of comments will be included in the acknowledgement sent to - the sender and to affected maintainers, so you can use this to - document the reasons for your commands. + text of comments will be included in the acknowledgement sent + to the sender and to affected maintainers, so you can use this + to document the reasons for your commands. quit stop @@ -419,12 +380,12 @@ Commands available at the control mailserver message; the remainder of the message can include explanations, signatures or anything else, none of it will be detected by the control server. - __________________________________________________________________ + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/bug-reporting.txt b/includes/squeeze/common/doc/bug-reporting.txt index 675a4d9cb..974eb2085 100644 --- a/includes/squeeze/common/doc/bug-reporting.txt +++ b/includes/squeeze/common/doc/bug-reporting.txt @@ -1,8 +1,9 @@ +How to report a bug in Debian using reportbug + We strongly recommend that you report bugs in Debian using the reportbug program. To install and start it, simply run: - # aptitude install reportbug - $ reportbug + aptitude install reportbug; reportbug It will guide you through the bug reporting process step by step. @@ -26,8 +27,8 @@ What package does your bug report belong to? asking for advice. If your problem doesn't relate just to one package but some general - Debian service, there are several pseudo-packages or even mailing lists - that you can use to relay your message to us instead. + Debian service, there are several pseudo-packages or even mailing + lists that you can use to relay your message to us instead. Has your bug report been filed already? @@ -45,22 +46,24 @@ Send multiple reports for multiple bugs Don't file bugs upstream - If you file a bug in Debian, don't send a copy to the upstream software - maintainers yourself, as it is possible that the bug exists only in - Debian. If necessary, the maintainer of the package will forward the - bug upstream. + If you file a bug in Debian, don't send a copy to the upstream + software maintainers yourself, as it is possible that the bug exists + only in Debian. If necessary, the maintainer of the package will + forward the bug upstream. Sending the bug report via e-mail You can report bugs in Debian by sending an e-mail to - submit@bugs.debian.org with a special format described below. reportbug - (see above) will properly format the e-mails for you; please use it! + submit@bugs.debian.org with a special format described below. + reportbug (see above) will properly format the e-mails for you; please + use it! Headers - Like any e-mail you should include a clear, descriptive Subject line in - your main mail header. The subject you give will be used as the initial - bug title in the tracking system, so please try to make it informative! + Like any e-mail you should include a clear, descriptive Subject line + in your main mail header. The subject you give will be used as the + initial bug title in the tracking system, so please try to make it + informative! If you'd like to send a copy of your bug report to additional recipients (such as mailing lists), you shouldn't use the usual e-mail @@ -84,10 +87,10 @@ Version: <packageversion> tracking system relies on this field to work out which releases are affected by the bug. - You need to supply a correct Package line in the pseudo-header in order - for the bug tracking system to deliver the message to the package's - maintainer. See this example for information on how to find this - information. + You need to supply a correct Package line in the pseudo-header in + order for the bug tracking system to deliver the message to the + package's maintainer. See this example for information on how to find + this information. For other valid pseudo-headers, see Additional pseudo-headers @@ -115,15 +118,16 @@ The body of the report hardware in your system, as problems are often caused by IRQ and I/O address conflicts. * If you have reportbug installed the output of reportbug -q - --template -T none -s none -S normal -b --list-cc none -q <package> - will also be useful, as it contains the output of maintainer - specific scripts and version information. + --template -T none -s none -S normal -b --list-cc none -q + <package> will also be useful, as it contains the output of + maintainer specific scripts and version information. - Include any detail that seems relevant -- you are in very little danger - of making your report too long by including too much information. If - they are small, please include in your report any files you were using - to reproduce the problem. (If they are large, consider making them - available on a publicly available website if possible.) + Include any detail that seems relevant -- you are in very little + danger of making your report too long by including too much + information. If they are small, please include in your report any + files you were using to reproduce the problem. (If they are large, + consider making them available on a publicly available website if + possible.) For more advice on how to help the developers solve your problem, please read How to Report Bugs Effectively. @@ -161,10 +165,10 @@ Sending copies of bug reports to other addresses You could do this by CC'ing your bug report to the other address(es), but then the other copies would not have the bug report number put in - the Reply-To field and the Subject line. When the recipients reply they - will probably preserve the submit@bugs.debian.org entry in the header - and have their message filed as a new bug report. This leads to many - duplicated reports. + the Reply-To field and the Subject line. When the recipients reply + they will probably preserve the submit@bugs.debian.org entry in the + header and have their message filed as a new bug report. This leads to + many duplicated reports. The right way to do this is to use the X-Debbugs-CC header. Add a line like this to your message's mail header: @@ -189,9 +193,9 @@ Severity levels If a report is of a particularly serious bug, or is merely a feature request, you can set the severity level of the bug as you report it. - This is not required however, and the package maintainer will assign an - appropriate severity level to your report even if you do not (or pick - the wrong severity). + This is not required however, and the package maintainer will assign + an appropriate severity level to your report even if you do not (or + pick the wrong severity). To assign a severity level, put a line like this one in the pseudo-header: @@ -211,8 +215,8 @@ Assigning tags Tags: <tags> Replace <tags> with one or more of the available tags, as described in - the advanced documentation. Separate multiple tags with commas, spaces, - or both. + the advanced documentation. Separate multiple tags with commas, + spaces, or both. User: <username> Usertags: <usertags> @@ -236,8 +240,8 @@ Source: foopackage foopackage; for most bugs in most packages you don't want to use this option. - Finally, if your MUA doesn't allow you to edit the headers, you can set - the various X-Debbugs- headers in the pseudo-headers. + Finally, if your MUA doesn't allow you to edit the headers, you can + set the various X-Debbugs- headers in the pseudo-headers. Additional information @@ -245,9 +249,9 @@ Different submission addresses (minor or mass bug reports) If a bug report is minor, for example, a documentation typo or a trivial build problem, please adjust the severity appropriately and - send it to maintonly@bugs.debian.org instead of submit@bugs.debian.org. - maintonly will forward the report to the package maintainer only, it - won't forward it to the BTS mailing lists. + send it to maintonly@bugs.debian.org instead of + submit@bugs.debian.org. maintonly will forward the report to the + package maintainer only, it won't forward it to the BTS mailing lists. If you're submitting many reports at once, you should definitely use maintonly@bugs.debian.org so that you don't cause too much redundant @@ -255,60 +259,49 @@ Different submission addresses (minor or mass bug reports) you may also want to post a summary on debian-bugs-dist. If wish to report a bug to the bug tracking system that's already been - sent to the maintainer, you can use quiet@bugs.debian.org. Bugs sent to - quiet@bugs.debian.org will not be forwarded anywhere, only filed. + sent to the maintainer, you can use quiet@bugs.debian.org. Bugs sent + to quiet@bugs.debian.org will not be forwarded anywhere, only filed. When you use different submission addresses, the bug tracking system - will set the Reply-To of any forwarded message so that the replies will - by default be processed in the same way as the original report. That - means that, for example, replies to maintonly will go to - nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless of - course one overrides this manually. + will set the Reply-To of any forwarded message so that the replies + will by default be processed in the same way as the original report. + That means that, for example, replies to maintonly will go to + nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless + of course one overrides this manually. Acknowledgements - Normally, the bug tracking system will return an acknowledgement to you - by e-mail when you report a new bug or submit additional information to - an existing bug. If you want to suppress this acknowledgement, include - an X-Debbugs-No-Ack header or pseudoheader in your e-mail (the contents - of this header do not matter). If you report a new bug with this - header, you will need to check the web interface yourself to find the - bug number. + Normally, the bug tracking system will return an acknowledgement to + you by e-mail when you report a new bug or submit additional + information to an existing bug. If you want to suppress this + acknowledgement, include an X-Debbugs-No-Ack header in your e-mail + (the contents of this header do not matter; however, it must be in the + mail header and not in the pseudo-header with the Package field). If + you report a new bug with this header, you will need to check the web + interface yourself to find the bug number. Note that this header will not suppress acknowledgements from the control@bugs.debian.org mailserver, since those acknowledgements may contain error messages which should be read and acted upon. -Spamfighting and missing mail - - The bug tracking system implements a rather extensive set of rules - designed to make sure that spam does not make it through the BTS. While - we try to minimize the number of false positives, they do occur. If you - suspect your mail has triggered a false positive, feel free to contact - owner@bugs.debian.org for assistance. Another common cause of mail not - making it through to the BTS is utilizing addresses which match - procmail's FROM_DAEMON, which includes mail from addresses like - mail@foobar.com. If you suspect your mail matches FROM_DAEMON, see - procmailrc(5) to verify, and then resend the mail using an address - which does not match FROM_DAEMON. - Bug reports against unknown packages If the bug tracking system doesn't know who the maintainer of the - relevant package is it will forward the report to debian-bugs-dist even - if maintonly was used. + relevant package is it will forward the report to debian-bugs-dist + even if maintonly was used. When sending to maintonly@bugs.debian.org or nnn-maintonly@bugs.debian.org you should make sure that the bug report is assigned to the right package, by putting a correct Package at the top of an original submission of a report, or by using the - control@bugs.debian.org service to (re)assign the report appropriately. + control@bugs.debian.org service to (re)assign the report + appropriately. Using dpkg to find the package and version for the report When using reportbug to report a bug in a command, say grep, the - following will automatically select the right package and let you write - the report right away: reportbug --file $(which grep) + following will automatically select the right package and let you + write the report right away: reportbug --file $(which grep) You can also find out which package installed it by using dpkg --search. You can find out which version of a package you have @@ -356,14 +349,14 @@ Other useful commands and packages provides a convenient text-based interface to the bug tracking system. Emacs users can also use the debian-bug command provided by the - debian-el package. When called with M-x debian-bug, it will ask for all - necessary information in a similar way to reportbug. - __________________________________________________________________ + debian-el package. When called with M-x debian-bug, it will ask for + all necessary information in a similar way to reportbug. + _________________________________________________________________ Debian BTS administrators <owner@bugs.debian.org> Debian bug tracking system Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd, 1994-1997 Ian Jackson. - __________________________________________________________________ + _________________________________________________________________ diff --git a/includes/squeeze/common/doc/mailing-lists.txt b/includes/squeeze/common/doc/mailing-lists.txt index 93e8dff74..c72295b1b 100644 --- a/includes/squeeze/common/doc/mailing-lists.txt +++ b/includes/squeeze/common/doc/mailing-lists.txt @@ -56,405 +56,271 @@ User lists debian-announce@lists.debian.org - Description : Major news and very important changes in the project - are announced here. + Description : Important announcements Moderated : yes Subscription: open - debian-backports-announce@lists.debian.org - - Description : Announcements relating to the debian-backports project include security related announcements - Moderated : yes - Subscription: open - - debian-backports@lists.debian.org - - Description : Discussion about the debian-backports archive - Moderated : no - Subscription: open - debian-chinese-big5@lists.debian.org - Description : Debian Chinese Project: Chinese localization (l10n), - documentation and web site translation, user support - etc. - - Posts may be in English or Big5-encoded Chinese. - All posts are automatically converted to GB encoding - and cross-posted to the debian-chinese-gb mailing list. - - If you would rather read and post in GB-encoded - Chinese, please subscribe to debian-chinese-gb instead. + Description : debian-user in Chinese [Big5] Language : Chinese Moderated : subscribers Subscription: open debian-chinese-gb@lists.debian.org - Description : Debian Chinese Project: Chinese localization (l10n) - issues, documentation and web site translation, user - support etc. - - Posts may be in English or GB-encoded Chinese. - All posts are automatically converted to Big5 encoding - and cross-posted to the debian-chinese-big5 mailing list. - - If you would rather read and post in Big5-encoded - Chinese, please subscribe to debian-chinese-big5 instead. + Description : debian-user in Chinese [GB] Language : Chinese Moderated : subscribers Subscription: open debian-edu-announce@lists.debian.org - Description : Announcements regarding Skolelinux/debian-edu + Description : Announcements for the debian-edu archive Moderated : yes Subscription: open debian-enterprise@lists.debian.org - Description : Discussions about special needs in enterprise - environments and ways to fulfill those needs. + Description : Debian for the enterprise Moderated : no Subscription: open debian-esperanto@lists.debian.org - Description : Debian users who speak Esperanto. + Description : debian-user in Esperanto Language : Esperanto Moderated : no Subscription: open debian-firewall@lists.debian.org - Description : Discussion of implementation and maintenance of - firewalls using Debian. Both basic issues and new - more exotic developments are discussed here. + Description : Running a firewall on Debian Moderated : no Subscription: open debian-infrastructure-announce@lists.debian.org - Description : This list covers announcements about changes in the (public and - private) Debian infrastructure including services the Debian - project directly or indirectly provides. + Description : Infrastructure announcements Moderated : signed Subscription: open debian-isp@lists.debian.org - Description : Discussion about issues and problems specific to - Internet Service Providers (ISPs for short) that - use Debian. + Description : Debian at Internet Service Providers Moderated : no Subscription: open debian-italian@lists.debian.org - Description : Support for Debian users that speak Italian. - (High-volume mailing list.) + Description : debian-user in Italian Language : Italian Moderated : no Subscription: open debian-japanese@lists.debian.org - Description : Support for Debian users that speak Japanese, - Japanese localization issues, integrating - Debian JP packages into Debian etc. - - The English language is allowed, but using Japanese is - encouraged even for those who aren't native speakers. - - For native Japanese, Debian JP Project provides - several mailing lists discussing the Debian system in - Japanese, see http://www.debian.or.jp/MailingList.html + Description : debian-user in Japanese Language : English/Japanese Moderated : no Subscription: open debian-kde@lists.debian.org - Description : Discussions related to KDE in Debian. - Those developing KDE-based packages are - encouraged to use this to discuss issues - and share their experience. + Description : KDE in Debian Moderated : no Subscription: open debian-laptop@lists.debian.org - Description : Installing, updating and using laptops with Debian. - Suggestions on special packaging, complaints, etc. - are welcome. + Description : Debian on mobile computers Moderated : no Subscription: open debian-news-french@lists.debian.org - Description : News about Debian for users speaking French. + Description : French Debian News, weekly and otherwise Language : French Moderated : yes Subscription: open debian-news-german@lists.debian.org - Description : News about Debian for users speaking German. + Description : German Debian News, weekly and otherwise Language : German Moderated : yes Subscription: open debian-news-italian@lists.debian.org - Description : Releases, news, internationalization efforts and - other related news about Debian for Italian-speaking users. + Description : Italian Debian News, weekly and otherwise Language : Italian Moderated : yes Subscription: open debian-news-portuguese@lists.debian.org - Description : Releases, news, internationalization efforts and other - related news about Debian for users speaking Portuguese. + Description : Portuguese Debian News, weekly and otherwise Language : Portuguese Moderated : yes Subscription: open debian-news-spanish@lists.debian.org - Description : Releases, news, internationalization efforts and - other related news about Debian for Spanish-speaking users. + Description : Spanish Debian News, weekly and otherwise Language : Spanish Moderated : yes Subscription: open debian-news@lists.debian.org - Description : General news about the distribution and the project. - - The current events and news about Debian are - summarized in the Debian Weekly News, a newsletter - regularly posted on this list. + Description : Debian News, weekly and otherwise Moderated : yes Subscription: open debian-photo@lists.debian.org - Description : Using software in Debian for photography, and discussion about problems, - challenges and opportunities related to that. All parts of the - photographic process are on topic: controlling the camera, transferring - pictures to the computer, managing, editing, converting, printing, - uploading, displaying, etc. - . - For bandwidth and disk space reasons, it is not, however, appropriate - to send images to the list. Put them on a web site and include the URL - in a mail sent to the list instead. - Moderated : no - Subscription: open - - debian-research@lists.debian.org - - Description : This list's goal is to gather those interested in Debian from an - academic perspective. + Description : Using Debian for photography Moderated : no Subscription: open debian-russian@lists.debian.org - Description : Support for Debian users that speak Russian, - and Russian localization issues: translating - "po" files, coordinating patches for Debian - packages to work with the Russian language. + Description : debian-user in Russian Language : Russian Moderated : no Subscription: open debian-security-announce@lists.debian.org - Description : The security team informs the users about security - problems by posting security advisories about - Debian packages on this list. + Description : Security announcements Moderated : yes Subscription: open debian-security@lists.debian.org - Description : Discussion about security issues, including - cryptographic issues, that are of interest to - all parts of the Debian community. - - Please note that this is NOT an announcement - mailing list. If you're looking for security - advisories from Debian, subscribe to - debian-security-announce instead. + Description : Security in Debian Moderated : no Subscription: open - debian-stable-announce@lists.debian.org - - Description : Updates to stable packages will be announced on this list. - Moderated : yes - Subscription: open - debian-testing-security-announce@lists.debian.org - Description : The testing-security team informs users about security problems by - posting summaries about fixed packages in Debian testing on this list. + Description : Security announcements for testing Moderated : yes Subscription: open debian-user-catalan@lists.debian.org - Description : Support for Debian users that speak Catalan. + Description : debian-user in Catalan Language : Catalan Moderated : no Subscription: open debian-user-danish@lists.debian.org - Description : Support for Debian users who speak Danish. + Description : debian-user in Danish Language : Danish Moderated : no Subscription: open - debian-user-dutch@lists.debian.org - - Description : Support for Debian users that speak Dutch - Language : Dutch - Moderated : no - Subscription: open - - debian-user-finnish@lists.debian.org - - Description : Support for Debian users who speak Finnish. - Language : Finnish - Moderated : no - Subscription: open - debian-user-french@lists.debian.org - Description : Support for Debian users that speak French. - (High-volume mailing list.) + Description : debian-user in French Language : French Moderated : no Subscription: open debian-user-german@lists.debian.org - Description : Support for Debian users that speak German. - (High-volume mailing list.) + Description : debian-user in German Language : German Moderated : no Subscription: open - debian-user-greek@lists.debian.org - - Description : Support for Debian users that speak Greek. - Moderated : no - Subscription: open - debian-user-hungarian - Description : Support for Debian users that speak Hungarian. + Description : debian-user in Hungarian Language : Hungarian Subscription: http://lists.linux.hu/mailman/listinfo/debian debian-user-icelandic@lists.debian.org - Description : Support for Debian users that speak Icelandic. + Description : debian-user in Icelandic Moderated : no Subscription: open debian-user-indonesian@lists.debian.org - Description : Support for Debian users who speak Indonesian. + Description : debian-user in Indonesian Language : Indonesian Moderated : no Subscription: open debian-user-polish@lists.debian.org - Description : Support for Debian users that speak Polish. + Description : debian-user in Polish Language : Polish Moderated : no Subscription: open debian-user-portuguese@lists.debian.org - Description : Support for Debian users who speak Portuguese. - (High-volume mailing list.) + Description : debian-user in Portuguese Language : Portuguese (both European and Brazilian, and other dialects are welcome) Moderated : no Subscription: open - debian-user-slovenian@lists.debian.org - - Description : Support for Debian users that speak Slovenian. - Language : Slovenian - Moderated : no - Subscription: open - debian-user-spanish@lists.debian.org - Description : Support for Debian users that speak Spanish. - (High-volume mailing list.) + Description : debian-user in Spanish Language : Spanish Moderated : no Subscription: open debian-user-swedish@lists.debian.org - Description : Support for Debian users that speak Swedish. + Description : debian-user in Swedish Language : Swedish Moderated : no Subscription: open - debian-user-tamil@lists.debian.org - - Description : Mailing list to discuss Tamil localisation efforts for Debian and to coordinate - Tamil localisation activities. You can also get Debian support in Tamil here. - Language : Tamil - Moderated : no - Subscription: open - debian-user-turkish@lists.debian.org - Description : Support for Debian users that speak Turkish. + Description : debian-user in Turkish Language : Turkish Moderated : no Subscription: open debian-user-ukrainian@lists.debian.org - Description : Support for Debian users who speak Ukrainian. + Description : debian-user in Ukrainian Language : Ukrainian Moderated : no Subscription: open debian-user-vietnamese@lists.debian.org - Description : Support for Debian users that speak Vietnamese, and discussions on translations + Description : debian-user in Vietnamese Language : Vietnamese Moderated : no Subscription: open debian-user@lists.debian.org - Description : Support for Debian users who speak English. - (High-volume mailing list.) + Description : Help and discussion among users of Debian Digest : debian-user-digest@lists.debian.org Moderated : no Subscription: open debian-volatile-announce@lists.debian.org - Description : Announcements relating to the debian-volatile project include new uploads and changes + Description : Announcements for the debian-volatile archive Moderated : yes Subscription: open debian-volatile@lists.debian.org - Description : Discussion about the debian-volatile archive + Description : Using the debian-volatile archive Moderated : no Subscription: open @@ -467,652 +333,450 @@ Development lists debian-accessibility@lists.debian.org - Description : User and Developer list for accessibility-related issues. - Moderated : no - Subscription: open - - debian-ada@lists.debian.org - - Description : Discussion of Ada in Debian. - - This list is intended for: - - discussion of the Debian Policy for Ada - - release coordination among Ada packages in Debian - - packaging advice - - general help for Ada programmers using the Debian packages - - You can find the Debian Policy for Ada at - http://people.debian.org/~lbrenta/debian-ada-policy.html + Description : Making Debian more accessible to people with disabilities Moderated : no Subscription: open debian-apache@lists.debian.org - Description : Maintenance of the Apache HTTP server and related - packages in Debian: code changes, reproducing bugs, - talking to upstream etc. - - It is neither for submitting bug reports (please - use the BTS for that), nor for support requests. + Description : Maintaining the Debian Apache (web server) and related packages Moderated : no Subscription: open debian-beowulf@lists.debian.org - Description : Discussion about Beowulf systems running Debian. - Moderated : no - Subscription: open - - debian-blends@lists.debian.org - - Description : Debian Pure Blends (formerly known as Custom Debian Distributions) - provide support for special user interests. They implement a new - approach to cover interests of specialised users, who might be - children, lawyers, medical staff, visually impaired people, etc. - Of late, several Debian Pure Blends have evolved. The common goal - of those is to make installation and administration of computers - for their target users as easy as possible, and to serve in the - role as the missing link between software developers and users - well. - - You can get more information at - http://blends.alioth.debian.org/blends/ + Description : Debian on Beowulf clusters Moderated : no Subscription: open debian-boot@lists.debian.org - Description : Discussion and maintenance of the Debian - installation system. + Description : Developing the installation system Moderated : no Subscription: open debian-cd@lists.debian.org - Description : Creating Debian CD sets, official and unofficial. - Moderated : no - Subscription: open - - debian-cli@lists.debian.org - - Description : This list is about using and/or developing for the Common Language - Infrastructure (CLI). - If you want to develop software or create Debian packages - that uses Mono, GNU Portable.NET or LLVM VMKit then you are right on this - mailing list. - If you are writing software in C#, VB.NET, Boo, Nemerle or other - CLI based/enabled programming languages then you are also welcome on this list. + Description : Creating Debian CD Images Moderated : no Subscription: open debian-ctte-private@lists.debian.org - Description : Private communication between tech committee members. + Description : Debian Technical Committee private list [dead list] Moderated : yes Subscription: Debian Technical Committee only debian-ctte@lists.debian.org - Description : Public meeting, business and announcements of the Debian - Technical Committee + Description : Debian Technical Committee Moderated : subscribers Subscription: open + debian-custom@lists.debian.org + + Description : Developing common infrastructure for custom Debian distributions + Moderated : no + Subscription: open + debian-dak@lists.debian.org - Description : Discussion about the Debian Archive Software, consisting of dak for the - archive and the buildd related parts wanna-build/sbuild. + Description : Debian Archive Kit / Buildd list Moderated : no Subscription: open debian-debbugs-cvs@lists.debian.org - Description : CVS commit messages when modifications are done to - debbugs + Description : debbugs CVS commits Moderated : yes Subscription: open debian-debbugs@lists.debian.org - Description : Discussion and development of debbugs, the Debian - Bug Tracking System software. + Description : debbugs, the Debian bug tracking system Moderated : no Subscription: open debian-desktop@lists.debian.org - Description : Discussion about the Debian Desktop sub-project, - the integration of the various desktop-related - packages, bug reports, questions and patches. + Description : Debian Desktop project Moderated : no Subscription: open debian-devel-announce@lists.debian.org - Description : Announcements of development issues like policy changes, - important release issues &c. + Description : Announcements for developers Moderated : signed Subscription: open debian-devel-austrian - Description : Discussion among the Debian developers in Austria. + Description : Development discussions among Austrians Language : (mostly) German Subscription: https://www.gibraltar.at/mailman/listinfo/debian-at debian-devel-french@lists.debian.org - Description : This is the list used to discuss development - issues in French. + Description : Development discussions in French Language : French Moderated : no Subscription: open debian-devel-games@lists.debian.org - Description : Development and packaging discussion for games and game-related software in Debian. - Identification of potential new games suitable for Debian. Discussion about - infrastructure issues covering a wider range of games (e.g. multiplayer issues). + Description : Development of games in Debian Moderated : no Subscription: open debian-devel-italian@lists.debian.org - Description : Discussion on development issues in Italian. + Description : Development discussions in Italian Language : Italian Moderated : no Subscription: open debian-devel-portuguese@lists.debian.org - Description : This is the list used by Portuguese developers - (or wannabes) to discuss development issues. + Description : Development discussions in Portuguese Language : Portuguese Moderated : no Subscription: open debian-devel-spanish@lists.debian.org - Description : This is the list used by Spanish developers - (or wannabes) to discuss issues besides - translation: provide help for new Spanish - developers, arrange key-signing meetings, arrange - work in booths on different shows, share experience - etc. + Description : Development discussions in Spanish Language : Spanish Moderated : no Subscription: open debian-devel@lists.debian.org - Description : Discussion about technical development topics. - (High-volume mailing list.) + Description : Development of Debian Digest : debian-devel-digest@lists.debian.org Moderated : no Subscription: open debian-doc@lists.debian.org - Description : Debian Documentation Project: anything related - to documentation in Debian is on topic here. + Description : Writing documentation for Debian Moderated : no Subscription: open debian-dpkg-bugs@lists.debian.org - Description : Email sent by the bug tracking system regarding - the dpkg packages. + Description : dpkg bug reports Moderated : no Subscription: open debian-dpkg-cvs@lists.debian.org - Description : The CVS commit messages from the dpkg CVS tree. + Description : dpkg CVS commits Moderated : yes Subscription: open debian-dpkg@lists.debian.org - Description : Discussions and maintenance of dpkg, the basis of - the Debian packaging system. + Description : Development of dpkg Moderated : no Subscription: open debian-edu-french@lists.debian.org - Description : Discussions in french between all educational Debian-based projects. - This list should ease the collaboration between the projects themselves - and between Debian and those projects. + Description : Discussion between French educational Debian-based projects Moderated : no Subscription: open debian-edu@lists.debian.org - Description : Making Debian the best distribution in the - education landscape. + Description : Making Debian desirable for education purposes Moderated : no Subscription: open debian-emacsen@lists.debian.org - Description : Discussion of all things related to the several - Debian Emacs packages and their add-ons. + Description : Maintaining Emacsen Moderated : no Subscription: open debian-email@lists.debian.org - Description : A generic "grab-bag" list for Debian related - correspondence such as contacting upstream authors - about licenses, bugs etc, or discussing the project - with others where it might be useful to have the - discussion archived somewhere. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. + Description : Generic "grab-bag" list for Debian-related communication Moderated : no Subscription: developers only debian-embedded@lists.debian.org - Description : Discussion about improving Debian for use with - embedded systems, including building cross-compiler - toolchains, cross-compiling packages, creating and - updating system images, using alternate libraries, - compile-time configuration of packages, etc. + Description : Debian on embedded systems Moderated : no Subscription: open debian-flash@lists.debian.org - Description : For discussion of issues relating to the development and use of Debian for - Flash development and viewing of Flash content. For general discussion of Flash - related free software, please visit the osflash community: http://osflash.org + Description : development and use of flash technologies on Debian Moderated : no Subscription: open debian-gcc@lists.debian.org - Description : Discussion on Debian packaging of GCC, the - GNU compiler collection: bug reports, porting - issues, any kind of questions or patches. + Description : Debian GCC Maintainers Moderated : no Subscription: open - debian-gis@lists.debian.org - - Description : Discussion about Geographical Information Systems (GIS) in Debian. For more - information about the Debian GIS Blend see + debian-glibc@lists.debian.org - http://wiki.debian.org/DebianGis + Description : Maintaining GNU C Library packages Moderated : no Subscription: open - debian-glibc@lists.debian.org + debian-gtk-gnome@lists.debian.org - Description : Discussion on Debian packaging of the GNU C Library, - the most important library on Debian systems. + Description : Packages using GTK+ and/or GNOME Moderated : no Subscription: open - debian-gtk-gnome@lists.debian.org + debian-hams@lists.debian.org - Description : Discussion and coordination among maintainers of - Debian's GTK+, GNOME and dependent or related - packages. + Description : Development of HAM Radio under Debian Moderated : no Subscription: open - debian-hams@lists.debian.org + debian-handheld@lists.debian.org - Description : Support for HAMRadio within Debian GNU/Linux. + Description : Debian on handheld computers Moderated : no Subscription: open debian-haskell@lists.debian.org - Description : Discussion of issues related to Haskell on Debian systems, with an - emphasis towards coordinating Haskell packaging standards. Relevant - for anyone packaging Haskell compilers, libraries, or programs on - Debian. + Description : Haskell packages and maintenance Moderated : no Subscription: open debian-ipv6@lists.debian.org - Description : Discussions on the use of Debian in an IPv6 network - and implementing IPv6 support in Debian packages. + Description : IPv6 Maintenance Moderated : no Subscription: open debian-java@lists.debian.org - Description : Discussion about the packaging and use in Debian of VMs - and compilers for the Java(tm) language, and programs - written on it. + Description : Java Maintenance Moderated : no Subscription: open debian-jr@lists.debian.org - Description : Discussion and working on making Debian the sort - of operating system that children will want to use. - - The Debian Jr. Project web page is at - http://www.debian.org/devel/debian-jr/ + Description : Making Debian desirable for children Moderated : no Subscription: open debian-kernel-maint@lists.debian.org - Description : Discussion and development of Debian kernel packaging, - for the kernel team and other developers. + Description : Debian kernel development and discussion Moderated : no Subscription: open debian-kernel@lists.debian.org - Description : Kernels used with Debian (Linux, Hurd, etc.), available - patches and flavors, packaging issues, bug reports, - porting issues, automated tools, and any other - questions or patches that are kernel-related. Mostly - bug reporting is done here. + Description : Kernel packages in Debian Moderated : no Subscription: open debian-knoppix@lists.debian.org - Description : Development of the Debian-based live CD/DVD takes place. As it is mainly a - development list, user questions are best placed on the debian-user list. + Description : Development of the Knoppix Live CD/DVD Moderated : no Subscription: open debian-lex@lists.debian.org - Description : Discussion on developing Debian into an operating - system that is particularly well fit for the - requirements for legal offices. The goal of - Debian-Lex is a complete system for all tasks in - legal practice which is built completely on free - software. + Description : Making Debian desirable for lawyers Moderated : no Subscription: open debian-lint-maint@lists.debian.org - Description : The maintenance of Debian "lint" tools like lintian or linda - is discussed on this list. This may or may not be limited to - bug reports regarding the checks. + Description : Maintenance of Debian `lint' tools like lintian or linda Moderated : no Subscription: open debian-live@lists.debian.org - Description : Development of the Debian Live systems (i.e. live cds). + Description : Discussion and maintenance of the Debian Live systems Moderated : no Subscription: open debian-lsb@lists.debian.org - Description : Discussion and coordination of efforts towards ensuring - Debian meets the requirements of the Linux Standard Base. + Description : Debian and the Linux Standard Base Moderated : no Subscription: open debian-med@lists.debian.org - Description : Discussion on providing a free operating system - for medical care. - - The Debian-Med Project web page is at - http://www.debian.org/devel/debian-med/ + Description : Making Debian desirable for doctors Moderated : no Subscription: open debian-mentors@lists.debian.org - Description : Newbie Debian developers can seek help with - packaging and other developer-related issues here. - - This list is not meant for users' questions, - but for new maintainers'! + Description : Helping newbie developers Moderated : no Subscription: open debian-multimedia@lists.debian.org - Description : Discussion about the development of applications - that produce multimedia content, handling multimedia - data, supporting multimedia hardware etc. + Description : Multimedia support and applications Moderated : no Subscription: open debian-ocaml-maint@lists.debian.org - Description : Packaging of Objective Caml programs and libraries. - (http://pauillac.inria.fr/caml/) + Description : ocaml package maintenance and development Moderated : no Subscription: open debian-openoffice@lists.debian.org - Description : Coordination of the maintenance of the OpenOffice - packages in Debian. + Description : OpenOffice packages maintenance Moderated : no Subscription: open debian-perl@lists.debian.org - Description : The list is dedicated to coordinate the work of various - perl package maintainer and to write a kind of perl - sub-policy. + Description : Perl packages maintenance Moderated : no Subscription: open debian-policy@lists.debian.org - Description : Discussion and editing of the Debian Policy Manual. + Description : Creating and editing Debian Policy Moderated : no Subscription: open debian-printing@lists.debian.org - Description : Discussion of issues related to printing on Debian systems. This - covers all aspects of printing, from spoolers, to RIPs and printer - drivers. The list is used for coordination of development, - integration and bugfixing of printing packages between package - maintainers. User printing and printing setup questions are also - on topic. + Description : Debian Printing Infrastructure Moderated : no Subscription: open debian-private@lists.debian.org - Description : Private discussions among developers: only for - issues that may not be discussed on public lists. - - Anything sent there should be treated as sensitive - and not to be spread to other lists; thus - cross-posting between it and an open list defeats - the purpose of this list. - - This list is archived internally on a Debian Project - machine, only developers have access to the archive. + Description : Private discussions among developers Moderated : no Subscription: developers only debian-python@lists.debian.org - Description : Discussion of issues related to Python on Debian - systems with a stress on packaging standards. Therefore - relevant for maintainers of Python related packages. + Description : Python packages maintenance Moderated : no Subscription: open debian-qa-packages@lists.debian.org - Description : Bug reports against orphaned packages and discussions - about fixing them. + Description : Orphaned packages maintained by the QA group Moderated : no Subscription: open debian-qa@lists.debian.org - Description : Quality assurance is important for a distribution. This - list addresses this quality. + Description : Quality Assurance Moderated : no Subscription: open debian-qt-kde@lists.debian.org - Description : Discussion and coordination among maintainers of - Debian's Qt, KDE and dependent or related packages. + Description : Packages using Qt and/or KDE Moderated : no Subscription: open debian-release@lists.debian.org - Description : Coordination of Debian releases issues such as testing migrations, transitions - and removals. - - This list should not be considered a discussion list; discussions related to - releases issues should be held on more appropriate lists such as debian-devel, - debian-legal or debian-project. + Description : Coordinating Debian releases Moderated : no Subscription: open debian-ruby@lists.debian.org - Description : Discussion of issues related to Ruby on Debian systems - with a stress on packaging standards. Therefore - relevant for maintainers of Ruby related packages. + Description : Ruby packages maintenance Moderated : no Subscription: open debian-science@lists.debian.org - Description : Discussion of issues relating to the use of Debian for science research, - including useful packages, particular problems faced by scientists using - Debian, how to make Debian more useful to scientists, etc. + Description : using debian for science and related research Moderated : no Subscription: open debian-security-tracker@lists.debian.org - Description : Discussion about topics that are relevant about the - Debian Security Tracker, e.g. feature improvements, - bugreports about incorrect data entries or server - updates. + Description : Discussion about the Debian Security Tracker Moderated : no Subscription: open debian-sgml@lists.debian.org - Description : Discussion of issues related to SGML on Debian systems - with a stress on proper integration of tools, packaging - standards and the writing of documentation for SGML - users. Therefore relevant for maintainers of SGML - related packages. + Description : Debian and SGML Moderated : no Subscription: open debian-ssh@lists.debian.org - Description : Maintenance of the OpenSSH packages for Debian. - It exists to facilitate coordination of ssh - maintenance (talking to upstream, reproducing bugs, - hacking on the code, etc.). - - It is *not* the place to mail bug reports - (use the BTS for that), nor support requests. + Description : SSH packages maintenance Moderated : no Subscription: open debian-testing@lists.debian.org - Description : Finding problems with the next Debian release: - testing the installation and the upgrade process. + Description : Testing for the next release Moderated : no Subscription: open debian-tex-maint@lists.debian.org - Description : Coordination of the maintenance of Debian TeX - and related packages. - - It is not meant for user support; for that, please - use debian-user or one of the general TeX mailing - lists or news groups. + Description : Coordination of the maintenance of TeX packages in Debian Moderated : no Subscription: open debian-toolchain@lists.debian.org - Description : Discussion about the Debian toolchain: compilers, - assemblers, linkers and such. New releases for - many of these tools are coordinated here. - Moderated : no - Subscription: open - - debian-upstream@lists.debian.org - - Description : A contact point for upstream software developers who want to get in touch with - Debian, whether the software is already packaged for Debian or not. + Description : Compilers, assemblers etc. Moderated : no Subscription: open - debian-wb-team@lists.debian.org - - Description : Primary contact address for the wanna-build maintainers. - Requests about this piece of infrastructure should - be sent here. Discussions directly concerning wanna-build. - Moderated : yes - Subscription: open - debian-webapps@lists.debian.org - Description : This list is used to coordinate the maintenance of web application packages. + Description : Web applications packaging Moderated : no Subscription: open debian-wnpp@lists.debian.org - Description : Orphaning and adopting packages which is done through - the `wnpp' BTS pseudo-package is recorded on this - list. Additionally, discussion about particular bugs - and the WNPP web pages is held here. + Description : Work-Needing and Prospective Packages Moderated : no Subscription: open debian-www-cvs@lists.debian.org - Description : CVS commit logs for the Debian web pages in the - webwml CVS tree. + Description : Web pages CVS commits Moderated : yes Subscription: open debian-www@lists.debian.org - Description : Design, structure and translation of Debian - web pages. All important changes to the web - site are announced here as well. + Description : Web pages design and maintenance Moderated : no Subscription: open debian-x@lists.debian.org - Description : Discussion about the X Window System within Debian. - This is NOT a user support list; this list is - intended for those who deal with the source code. + Description : Debian XFree86 packaging Moderated : no Subscription: open deity@lists.debian.org - Description : Debian GNU/Linux will get a new, friendly frontend to - its package maintenance system. Its codename is deity - (now known as APT) and its development is discussed - here. The -digest is open to everyone. + Description : APT packages maintenance Moderated : no Subscription: open @@ -1123,256 +787,196 @@ Internationalization and Translations debian-i18n@lists.debian.org - Description : Internationalization (i18n) of the distribution is - discussed here. + Description : Debian Internationalization Moderated : no Subscription: open debian-l10n-arabic@lists.debian.org - Description : Discussing Arabic localization issues, mainly - translating Debian docs and programs to Arabic. + Description : Arabic Localization Language : Arabic Moderated : no Subscription: open debian-l10n-basque@lists.debian.org - Description : Discussing Basque localization issues, mainly translating Debian - docs and programs to Basque. + Description : Basque localization Language : Basque Moderated : no Subscription: open debian-l10n-belarusian@lists.debian.org - Description : Discussing Belarusian localization issues, mainly - translating Debian docs and programs to Belarusian. + Description : Belarusian Localization Language : Belarusian Moderated : no Subscription: open debian-l10n-catalan@lists.debian.org - Description : Discussing Catalan localization issues, mainly - translating Debian docs and programs to Catalan. + Description : Catalan Localization Language : Catalan Moderated : no Subscription: open - debian-l10n-chinese@lists.debian.org - - Description : Discussing Chinese localization issues, mainly translating Debian - docs and programs to Chinese. - Language : Chinese - Moderated : no - Subscription: open - debian-l10n-czech@lists.debian.org - Description : Discussion forum for the translators of - Debian-specific packages and documentation to the Czech language. + Description : Czech Localization Moderated : no Subscription: open debian-l10n-danish@lists.debian.org - Description : Discussing Danish localization issues, mainly - translating Debian docs and programs to Danish. + Description : Danish Localization Language : Danish Moderated : no Subscription: open debian-l10n-dutch@lists.debian.org - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the Dutch language. + Description : Dutch Localization Language : Dutch Moderated : no Subscription: open debian-l10n-english@lists.debian.org - Description : Discussing English localization issues, mainly - translating Debian docs and programs to English. + Description : English Localization Language : English Moderated : no Subscription: open debian-l10n-esperanto@lists.debian.org - Description : Discussing Esperanto localization issues, mainly - translating Debian docs and programs to Esperanto. + Description : Esperanto Localization Language : Esperanto Moderated : no Subscription: open debian-l10n-finnish@lists.debian.org - Description : Discussing Finnish localization issues, mainly - translating Debian docs and programs to Finnish. + Description : Finnish Localization Language : Finnish Moderated : no Subscription: open debian-l10n-french@lists.debian.org - Description : Discussion forum for the translators of Debian-specific - packages and documentation to the French language. + Description : French Localization Language : French Moderated : no Subscription: open debian-l10n-galician@lists.debian.org - Description : Discussing Galician localization issues, mainly translating Debian docs and - programs to Galician. + Description : Galician Localization Language : Galician Moderated : no Subscription: open debian-l10n-german@lists.debian.org - Description : Discussing German localization issues, mainly - translating Debian docs and programs to German. + Description : German Localization Language : German Moderated : no Subscription: open debian-l10n-greek@lists.debian.org - Description : Discussion on Greek localization issues, mainly - translating Debian docs and programs to Greek. + Description : Greek Localization Language : Greek Moderated : no Subscription: open debian-l10n-hungarian@lists.debian.org - Description : Discussing Hungarian localization issues, mainly - translating Debian docs and programs to Hungarian. + Description : Hungarian Localization Language : Hungarian Moderated : no Subscription: open - debian-l10n-indonesian@lists.debian.org - - Description : Discussing Indonesian localization issues, mainly translating Debian docs and - website into Indonesian, improving Indonesian environment support in Debian. - Language : Indonesian - Moderated : no - Subscription: open - debian-l10n-italian@lists.debian.org - Description : Italian localization efforts within Debian. + Description : Italian Localization Language : Italian Moderated : no Subscription: open debian-l10n-kannada@lists.debian.org - Description : Debian Kannada (kn_IN) localization, documentation and web site translation, - user support, user-developers coordination + Description : Kannada Localization Language : Kannada Moderated : no Subscription: open debian-l10n-korean@lists.debian.org - Description : Discussion forum for the translators of Debian-specific packages and - documentation to the Korean language. + Description : Korean Localization Moderated : no Subscription: open debian-l10n-malayalam@lists.debian.org - Description : Discussion forum for the translators of Debian-specific packages and - documentation to the Malayalam language. + Description : Malayalam Localization Language : Malayalam Moderated : no Subscription: open debian-l10n-persian@lists.debian.org - Description : Discussing Persian/Farsi localization issues, mainly translating - Debian docs and programs to Persian/Farsi. + Description : Persian/Farsi Localization Language : Persian Moderated : no Subscription: open debian-l10n-polish@lists.debian.org - Description : Polish localization issues, mainly translating Debian - web pages, documentation and programs to Polish. + Description : Polish Localization Language : Polish Moderated : no Subscription: open debian-l10n-portuguese@lists.debian.org - Description : Portuguese localization issues such as translating - the documentation and programs. + Description : Portuguese Localization Language : Portuguese Moderated : no Subscription: open debian-l10n-romanian@lists.debian.org - Description : Discussing Romanian localization issues, mainly - translating Debian docs and programs to Romanian. + Description : Romanian Localization Language : Romanian Moderated : no Subscription: open debian-l10n-russian@lists.debian.org - Description : Discussing Russian localization issues, mainly - translating Debian docs and programs to Russian. + Description : Russian Localization Language : Russian Moderated : no Subscription: open - debian-l10n-sicilian@lists.debian.org - - Description : Sicilian localization issues within Debian. - Language : Sicilian - Moderated : no - Subscription: open - debian-l10n-spanish@lists.debian.org - Description : Discussing Spanish localization issues, mainly - translating Debian docs and programs to Spanish. + Description : Spanish Localization Language : Spanish Moderated : no Subscription: open debian-l10n-swedish@lists.debian.org - Description : Discussion forum for translators of Debian-specific packages - and documentation for the Swedish language. + Description : Swedish Localization Moderated : no Subscription: open debian-l10n-turkish@lists.debian.org - Description : Discussing Turkish localization issues, mainly - translating Debian docs and website into Turkish, - improving Turkish environment support in Debian. + Description : Turkish Localization Language : Turkish Moderated : no Subscription: open - debian-l10n-vietnamese@lists.debian.org - - Description : This is the Debian localization list for Vietnamese localization announcements - and translation status checks, discussions between Vietnamese translators and - questions from Vietnamese community users with language-related issues. - Language : Vietnamese - Moderated : no - Subscription: open - Ports to non-i386 Linux architectures and to non-Linux kernels Debian GNU/Linux is ported to several other types of computers, and there @@ -1380,96 +984,91 @@ Ports to non-i386 Linux architectures and to non-Linux kernels debian-68k@lists.debian.org - Description : Discussions on the m68k port of Debian GNU/Linux. + Description : Debian port to m68k Moderated : no Subscription: open debian-alpha@lists.debian.org - Description : Discussion on the Alpha port of Debian GNU/Linux. + Description : Debian port to Alpha Moderated : no Subscription: open debian-amd64@lists.debian.org - Description : Porting Debian to AMD x86-64 architecture. + Description : Debian port to AMD64 Moderated : no Subscription: open debian-arm@lists.debian.org - Description : Discussion on the ARM port for Debian GNU/Linux. + Description : Debian port to ARM Moderated : no Subscription: open debian-bsd@lists.debian.org - Description : Porting Debian to BSD (all *BSD variants). + Description : Debian port to BSD Moderated : no Subscription: open debian-hppa@lists.debian.org - Description : Discussions on the PA-RISC port of Debian GNU/Linux. + Description : Debian port to HPPA Moderated : no Subscription: open debian-hurd@lists.debian.org - Description : Debian port of the GNU Hurd operating system. + Description : Debian port to Hurd Moderated : no Subscription: open debian-ia64@lists.debian.org - Description : Discussions on the intel IA64 (aka Itanium, Merced) - port of Debian GNU/Linux. + Description : Debian port to Intel IA-64 Moderated : no Subscription: open debian-interix@lists.debian.org - Description : Discussion on the Interix port of Debian/GNU. - For more information see: http://www.debian-interix.net/ + Description : Debian port to Interix Moderated : no Subscription: open debian-mips@lists.debian.org - Description : Discussions on the MIPS port of Debian GNU/Linux. + Description : Debian port to MIPS Moderated : no Subscription: open debian-powerpc@lists.debian.org - Description : Discussion on the PowerPC port of Debian GNU/Linux. + Description : Debian port to PowerPC Moderated : no Subscription: open debian-s390@lists.debian.org - Description : Discussions on the IBM S/390 port of Debian GNU/Linux. + Description : Debian port to IBM S/390 Moderated : no Subscription: open debian-sparc@lists.debian.org - Description : Discussions on the SPARC port of Debian GNU/Linux. + Description : Debian port to SPARC Moderated : no Subscription: open debian-superh@lists.debian.org - Description : Discussions on the SuperH port of Debian GNU/Linux. For - more information about running Linux on SH processors, - have a look at http://www.m17n.org/linux-sh/ + Description : Debian port to SuperH Moderated : no Subscription: open debian-win32@lists.debian.org - Description : Porting the Debian distribution to Win32 systems - (Debian GNU/Win32). + Description : Debian port to Win32 Moderated : no Subscription: open @@ -1481,31 +1080,25 @@ The Bug Tracking System debian-bugs-closed@lists.debian.org - Description : Messages that close Debian bug reports. + Description : Debian BTS, closed bugs Moderated : yes Subscription: open debian-bugs-dist@lists.debian.org - Description : All submitted bug reports as well as further information - on them are distributed here. + Description : Debian BTS, received bugs Moderated : yes Subscription: open debian-bugs-forwarded@lists.debian.org - Description : Mails in which Debian maintainers forward bugs - to their upstream authors. + Description : Debian BTS, forwarded bugs Moderated : yes Subscription: open debian-bugs-rc@lists.debian.org - Description : All mail regarding release-critical bugs is - copied to this mailing list. - - See http://bugs.debian.org/release-critical/ - for more information. + Description : Debian BTS, release-critical bugs Moderated : yes Subscription: open @@ -1518,212 +1111,119 @@ Miscellaneous Debian lists debian-admin@lists.debian.org - Description : This is our internal list used for administering the - Debian machine park. + Description : Internal list for Debian Project machine admins Moderated : no Subscription: closed - debian-backports-changes@lists.debian.org - - Description : Changes to the "debian-backports" distribution are announced - here. This includes queued and dak mail. - Moderated : yes - Subscription: open - debian-changes@lists.debian.org - Description : Changes to the releases are announced here. This - includes security upgrades as well as important - bugfixes. + Description : Stable packages' upgrade announcements Digest : debian-changes-digest@lists.debian.org Moderated : yes Subscription: open debian-consultants@lists.debian.org - Description : Communication among Debian consultants. See at the bottom of the - consultants page (http://www.debian.org/consultants/#policy) for how - to add/update entries to this page. + Description : Debian consultants, paid support Moderated : no Subscription: open debian-curiosa@lists.debian.org - Description : Funny thing from and with the project, funny quotes, - discussions irc communication and fortune cookies. - Some kind of (de.)alt.netdigest for Debian-related stuff. + Description : All the funny stuff regarding Debian Moderated : no Subscription: open debian-devel-changes@lists.debian.org - Description : Notices about uploaded packages for the unstable - distribution, from developers, buildds and katie, - the archive sentinel. - (High-volume mailing list.) + Description : Unstable packages' upgrade announcements Moderated : yes Subscription: open - debian-dug-in@lists.debian.org - - Description : Discussion list for the Debian community in India without being tied to a - particular group in order to link all groups and individuals in the country and - facilitate the coordination of local events. - Moderated : no - Subscription: open - - debian-dug-mx@lists.debian.org - - Description : Discussion list for the Debian community in Mexico without being tied to a - particular group in order to link all groups and individuals in the country and - facilitate the coordination of local events. - Moderated : no - Subscription: open - debian-events-eu@lists.debian.org - Description : Discussions and organizational stuff about booths for - Debian at european exhibitions. - Moderated : no - Subscription: open - - debian-events-ha@lists.debian.org - - Description : Mailing list for announcements and events organization - with Debian affiliation in Hispanic America. + Description : Events with Debian affiliation in Europe Moderated : no Subscription: open debian-events-na@lists.debian.org - Description : Discussions and organizational stuff about booths and - presentations for Debian at North American exhibitions. + Description : Events with Debian affiliation in North America Moderated : no Subscription: open debian-events-nl@lists.debian.org - Description : Announcements of small meetings and keysigning parties of Dutch - Debian Developers and other discussions of interest mainly for - Debian people in the Netherlands. Posts in both Dutch and English - are common. + Description : Events with Debian affiliation in the Netherlands Moderated : no Subscription: open debian-jobs@lists.debian.org - Description : Job postings can be published on this list in - order to make them public to members of the Debian - community. While the jobs do not necessarily have - to involve the use of Debian, it is encouraged that - they do. Jobs can be about the development of - proprietary system, but jobs involving free software - (either development or system administration) are - preferred. Please include information such as - location and remuneration if appropriate. The list - is moderated; it is also an open list - job postings - which have to be kept private should be sent to - leader@debian.org who will distribute them. + Description : Job postings for members of the Debian community Moderated : yes Subscription: open debian-legal@lists.debian.org - Description : Discussions about legality issues such as - copyrights, patents etc. + Description : Copyright, licensing and patent issues Moderated : no Subscription: open debian-mirrors-announce@lists.debian.org - Description : Important changes to the FTP archive are announced here. - These are mainly useful to maintainers of Debian - mirrors. + Description : News and announcements regarding FTP archive mirrors Moderated : signed Subscription: open debian-mirrors@lists.debian.org - Description : Discussions relating to the Debian mirror network, - and the maintenance of mirrors. + Description : Discussions about the Debian mirror network Moderated : no Subscription: open debian-newmaint@lists.debian.org - Description : Discussion about the Debian New Maintainer process, - application manager reports etc. + Description : Debian New Maintainer process discussion Moderated : no Subscription: open debian-project@lists.debian.org - Description : Discussion about non-technical topics related - to the Debian Project. + Description : Discussions about non-technical issues in the project Moderated : no Subscription: open debian-publicity@lists.debian.org - Description : Coordination of all the work related to the external - communication of Debian: drafting new announces, - collecting important information that Debian should relay - to its community, improving the infrastructure offered to - people who want to create Debian booth, etc. - Moderated : no - Subscription: open - - debian-snapshot@lists.debian.org - - Description : This list covers discussion and maintenance of the snapshot.debian.org archive - as well as the development of enhancements of this service. + Description : Making Debian famous Moderated : no Subscription: open debian-testing-changes@lists.debian.org - Description : Changes to the "testing" distribution are announced - here. This includes various bugfixes. + Description : Testing packages' upgrade announcements Moderated : yes Subscription: open debian-vote@lists.debian.org - Description : Proposals, discussions and announcements related to - Official Debian Votes. + Description : Voting announcements and discussion Moderated : no Subscription: open debian-women@lists.debian.org - Description : Debian users and developers who wish to involve more - women in the Debian project. For discussion and - sharing of ideas as well as project collaboration. + Description : Discussion and collaboration involving women in Debian Moderated : no Subscription: open whitelist@lists.debian.org - Description : This is a special pseudo-mailing list to which - people can subscribe to prove they are not - spammers. - - This allows one to avoid the restrictions imposed - on non-subscriber posts to other mailing lists, - in particular the mailing lists that allow posts - only from subscribers. + Description : Generic whitelist Moderated : yes Subscription: open -Other - - - debian-derivatives@lists.debian.org - - Description : front-desk for developers of Debian-based distributions - Moderated : no - Subscription: open - Lists hosted for other projects Our list server provides mailing list facilities for other free @@ -1731,18 +1231,13 @@ Lists hosted for other projects other-cdwrite@lists.debian.org - Description : cdwrite mailing list + Description : cdwrite Moderated : no Subscription: open other-sart@lists.debian.org - Description : Discussions and announcements about SART, - a free raytracer that uses Guile extension - language and is distributed under GPL. - - The SART website is at - http://petra.zesoi.fer.hr/~silovic/sart/ + Description : Discussions and announcements about SART Moderated : no Subscription: open |