3
Cyril Brulebois <kibi@debian.org>
6
## Packaging bugs or upstream bugs?
8
It’d be nice to get all upstream bugs tagged as such (`upstream` tag),
9
forwarded upstream (which means the bugzilla instance on
10
<http://bugs.freedesktop.org/> for most packages), and marked as such.
12
A mail to `control@bugs.debian.org` would look like:
15
forwarded X https://bugs.freedesktop.org/show_bug.cgi?id=Y
18
Then [`bts-link`](http://bts-link.alioth.debian.org/) comes into play
19
and help us tracking upstream status, which is pretty nice to have.
24
Another feature of the BTS is usertagging. That lets people keep track
25
of additional tags, “attached” to a given mail address. For XSF,
26
that’s `debian-x@lists.debian.org`.
28
The list of all usertagged bugs can be seen on the following page; the
29
list of all used usertags is at the bottom, in the form.
30
→ <http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org>
32
Let’s give some examples:
34
* `i810`, `i915`: helps triaging `-video-intel` bugs depending on the
36
* `r200`, `r300`: ditto for `-video-ati`.
37
* `xset`, `xrandr`: helps triaging `x11-xserver-utils` bugs depending
38
on the affected tool (like other `x11-*` packages, that’s a bundle
40
* `squeeze-candidate`: helps keeping a list of bugs we’d like to get
41
fixed in a point release (through a stable update).
42
* `needs-forwarding`: of course, it’d be nice to have all upstream
43
bugs reported upstream, but some might need special attention
44
(*e.g.* security bugs).
46
Here’s an example of URL, for the last tags:
47
→ <http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org&tag=squeeze-candidate>
48
→ <http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org&tag=needs-forwarding>
50
By the way one should keep an eye on the list of found/fixed
51
versions since those bugs are likely marked as resolved (in `unstable`
52
or `experimental`), but might still affect a stable release.
54
To list the bugs marked `squeeze-candidate` but not
56
→ <http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org&tag=squeeze-candidate&exclude=tag:squeeze-accepted>
61
The BTS has yet another feature which can help, categories. That’s
62
based on usertags as well, but one has to use the package address
63
(`$package@packages.debian.org`), so that’s package-specific rather
67
[documented on the wiki](http://wiki.debian.org/bugs.debian.org/usertags),
68
and they would probably be welcome in the `intel` and `ati` cases
69
above, as well as in the “multiple tools in a single bundle”
70
cases… An example of what we could achieve is the
71
[devscripts bug page](http://bugs.debian.org/devscripts) (it takes
72
some time to load, plenty of bugs).
74
Needed steps for that to happen:
76
* create usercategories.
77
* move usertags from `debian-x@lists.debian.org` to
78
`$package@packages.debian.org`, probably using the `bts select`
79
command to get the list over which to iterate.
82
To move the usertags, something like that should do the job:
85
user $package1@packages.debian.org
88
user $package2@packages.debian.org
91
# Removing tags which are no longer needed:
92
user debian-x@lists.debian.org