1677
Comment: This is a field in the header or pseudo-header
|
2432
typo
|
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 [[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 4: | Line 4: |
The generic format of these tags is: | For architecture-specific [[DebianInstaller/Bugs|Debian installer bugs]], also add the architecture name as a usertag for the debian-boot@lists.debian.org user. |
Line 6: | Line 6: |
* User: ports mailinglist * Usertags: port name |
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. When filing a bug that affects multiple architectures, you can add multiple pairs of User + Usertags pseudo-headers to set multiple architecture usertags. The generic format of these [[https://www.debian.org/Bugs/Reporting#tags|tags]] is: * User: first ports mailing list * Usertags: first port name * User: second ports mailing list * Usertags: second port name |
Line 11: | Line 19: |
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 27: |
* ppc64: debian-powerpc@lists.debian.org | |
Line 21: | Line 30: |
* sparc64: debian-sparc@lists.debian.org | |
Line 30: | Line 40: |
* x32: debian-x32@lists.debian.org | * x32: debian-x32@lists.debian.org, but the list does not exist yet. |
Line 41: | Line 51: |
---- ## 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.
When filing a bug that affects multiple architectures, you can add multiple pairs of User + Usertags pseudo-headers to set multiple architecture usertags.
The generic format of these tags is:
- User: first ports mailing list
- Usertags: first port name
- User: second ports mailing list
- Usertags: second 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:
armel: debian-arm@lists.debian.org
armhf: debian-arm@lists.debian.org
arm64: debian-arm@lists.debian.org
hurd-i386: debian-hurd@lists.debian.org
mips64el: debian-mips@lists.debian.org
mipsel: debian-mips@lists.debian.org
ppc64el: debian-powerpc@lists.debian.org
riscv64: debian-riscv@lists.debian.org
sparc64: debian-sparc@lists.debian.org
s390x: debian-s390@lists.debian.org
There are some exceptions to these rules:
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.