• Diff for "DebianInstaller/Bugs"

Bugs in the Installer

Some useful views of the DebianInstaller bugs in the bug tracking system:

• Bugs in packages maintained by the d-i team, excluding old installation reports and other cruft.

• Bugs sorted by architecture.

  • Note that bugs may be tagged as applying to more than one architecture, but will only show up once, in the first listed architecture.

• Here are some links to just display architecture-specific bugs: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc

• Traditional index of bugs.

• Bugs in other packages in Debian that affect d-i.

Tagging Bug Reports

We use usertags to categorise the bugs, with a user of debian-boot@lists.debian.org.

• How to set usertags is documented in this E-mail, see also the wiki page.

• Selecting sets of bugs using usertags is not properly documented.

Some of the usertags we have defined include:

• not-d-i : for bugs that don't actually affect d-i, just some other aspect of a package maintained by debian-boot@lists.debian.org. bts link

• old-report : for "old" installation reports. bts link

  • FIXME: what criteria are used when applying this?

• usability

• accessibility

• serial : bugs involving serial console installs. bts link

• <arch> : Any Debian architecture for bugs specific to that architecture, e.g. i386, powerpc, etc.

• debian-edu : bugs affecting only DebianEdu. bts link

The d-i tag should be used only on bugs that are not in packages maintained by the d-i team, but which still affect d-i. (It is a BTS tag not a usertag.)

We don't have an exhaustive list of tags in regular use. Perhaps we should develop one similar to that used by the KDE team.

Further Processing

What to do with the d-i bugs is documented in /BugsPolicy