Some useful views of the DebianInstaller bugs in the bug tracking system:
[http://bugs.debian.org/debian-boot@lists.debian.org Bugs in packages maintained by the d-i team], excluding old installation reports and other cruft:
The same bugs as above, but sorted [http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-boot@lists.debian.org;ordering=archfirst 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.
[http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-boot@lists.debian.org;ordering=bts-default Traditional index] of bugs
Bugs in other packages in Debian that [http://bugs.debian.org/tag:d-i affect d-i]
Installation reports, categorised using usertags: http://people.debian.org/~fjp/d-i/installation-reports.html
We use ?UserTags to categorise the bugs, with a user of debian-boot@lists.debian.org. Some of the tags we use 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
- old-report - for old installation reports
- usability
- accessibility
- serial - bugs involving serial console installs
- Any Debian architecture for bugs specific to that architecture. (i386, powerpc, etc)
debian-edu - bugs affecting only DebianEdu
The d-i tag should be used only on bugs that are not in packages maintained by debian-boot, but which still affect d-i. (It is not a usertag.)