Differences between revisions 1 and 22 (spanning 21 versions)
⇤ ← Revision 1 as of 2009-03-04 12:10:59 →
Size: 966
Editor: WouterVerhelst
Comment:
← Revision 22 as of 2022-05-08 03:29:48 → ⇥
Size: 2147
Editor: PaulWise
Comment: linkify usertags
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Teams/Debbugs/ArchchitectureTags
Line 2: Line 3:

For architecture-specific [[DebianInstaller/Bugs|Debian installer bugs]], also add the architecture name as a [[https://www.debian.org/Bugs/Reporting#tags|usertag]] for the debian-boot@lists.debian.org user.

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 5: Line 10:
 user: ports mailinglist
 usertag: port name		  * User: ports mailing list
 * Usertags: port name
Line 8: Line 13:
The port mailinglist name is usually 'debian-$architecture@lists.debian.org'. The exceptions to this rule are as follows: ----

The port mailing list name is usually '`debian-$architecture@lists.debian.org`' or '`debian-$archfamily@lists.debian.org`'. Examples of the latter include:
Line 11: Line 18:
 * kfreebsd-*: debian-bsd@lists.debian.org  * armhf: debian-arm@lists.debian.org
 * arm64: debian-arm@lists.debian.org
Line 13: Line 21:
 * mips64el: debian-mips@lists.debian.org
Line 14: Line 23:
 * sh: debian-superh@mlists.debian.org  * ppc64: debian-powerpc@lists.debian.org
 * ppc64el: debian-powerpc@lists.debian.org
 * riscv64: debian-riscv@lists.debian.org
 * sparc64: debian-sparc@lists.debian.org
 * sh: debian-superh@lists.debian.org
 * sh4: debian-superh@lists.debian.org
 * s390x: debian-s390@lists.debian.org
Line 16: Line 31:
Additionally, the m68k port's mailinglist is officially called debian-68k@lists.debian.org, but has an alias 'debian-m68k@lists.debian.org'. In the interest of consistency, maintainers should use the m68k name of the list rather than the official name. ----

There are some exceptions to these rules:

 * m86k: debian-68k@lists.debian.org
 * x32: debian-x32@lists.debian.org, but the list does not exist yet.
 * kfreebsd-i386: debian-bsd@lists.debian.org
 * kfreebsd-amd64: debian-bsd@lists.debian.org

----

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.

----

## 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 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.

CategoryPermalink