Differences between revisions 16 and 23 (spanning 7 versions)
Revision 16 as of 2020-06-14 01:43:21
Size: 1878
Editor: PaulWise
Comment: mention d-i bugs
Revision 23 as of 2022-05-08 03:31:19
Size: 2195
Editor: PaulWise
Comment: better spots for the usertag
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
These tags are meant to signal that particular bugs are architecture-specific. Maintainers are encouraged to mark any and all architecture-specific bugs with the below tag, whether or not a fix is available; this will allow porters to get a better overview of the state of their port. These tags are meant to signal that particular bugs are architecture-specific. Maintainers are encouraged to mark any and all architecture-specific bugs with the below [[https://www.debian.org/Bugs/Reporting#tags|tags]], whether or not a fix is available; this will allow porters to get a better overview of the state of their port.
Line 6: Line 6:
When filing architecture-specific bugs, please also ensure that you add an X-Debbugs-CC field listing each of the appropriate porter lists. When filing architecture-specific bugs, please also ensure that you add an [[https://www.debian.org/Bugs/Reporting#xcc|X-Debbugs-CC]] field listing each of the appropriate porter lists.
Line 8: Line 8:
The generic format of these tags is: The generic format of these [[https://www.debian.org/Bugs/Reporting#tags|tags]] is:
Line 10: Line 10:
 * User: ports mailinglist  * User: ports mailing list
Line 15: Line 15:
The port mailinglist name is usually '`debian-$architecture@lists.debian.org`' or '`debian-$archfamily@lists.debian.org`'. Examples of the latter include: The port mailing list name is usually '`debian-$architecture@lists.debian.org`' or '`debian-$archfamily@lists.debian.org`'. Examples of the latter include:
Line 23: Line 23:
 * ppc64: debian-powerpc@lists.debian.org
Line 25: Line 26:
 * sparc64: debian-sparc@lists.debian.org
Line 45: Line 47:

----

## linked from https://www.debian.org/Bugs/Reporting#tags
CategoryPermalink

These tags are meant to signal that particular bugs are architecture-specific. Maintainers are encouraged to mark any and all architecture-specific bugs with the below tags, whether or not a fix is available; this will allow porters to get a better overview of the state of their port.

For architecture-specific Debian installer bugs, also add the architecture name as a usertag for the debian-boot@lists.debian.org user.

When filing architecture-specific bugs, please also ensure that you add an X-Debbugs-CC field listing each of the appropriate porter lists.

The generic format of these tags is:

  • User: ports mailing list
  • Usertags: port name


The port mailing list name is usually 'debian-$architecture@lists.debian.org' or 'debian-$archfamily@lists.debian.org'. Examples of the latter include:


There are some exceptions to these rules:


For both kfreebsd-i386 and kfreebsd-amd64 (aka GNU/kFreeBSD) please add the usertag kfreebsd in addition to the architecture names.


For x32 the list does not exist so you should X-Debbugs-CC: debian-amd64@lists.debian.org instead.


CategoryPermalink