Differences between revisions 14 and 19 (spanning 5 versions)
Revision 14 as of 2017-12-22 08:51:47
Size: 1677
Editor: GuillemJover
Comment: This is a field in the header or pseudo-header
Revision 19 as of 2020-06-16 01:09:47
Size: 1966
Editor: PaulWise
Comment: add another family exception
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. When filing architecture-specific bugs, please also ensure that you add an X-Debbugs-CC field listing each of the appropriate porter lists. 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.

For architecture-specific [[DebianInstaller/Bugs|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.
Line 6: Line 10:
 * User: ports mailinglist  * User: ports mailing list
Line 11: 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 19: Line 23:
 * ppc64: debian-powerpc@lists.debian.org
Line 21: Line 26:
 * sparc64: debian-sparc@lists.debian.org
Line 30: Line 36:
 * x32: debian-x32@lists.debian.org  * x32: debian-x32@lists.debian.org, but the list does not exist yet.

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.

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.