On Mon, Oct 19, 2009 at 11:20, Olivier Berger <[email protected]> wrote: > Le samedi 17 octobre 2009 à 23:27 +0200, Joachim Breitner a écrit : > >> just an idea that occured to me right now when filing a bug against a >> package where I already know that it’s an upstream bug, but I don’t want >> to spend time finding out >> * where the upstream bugtracker is >> and >> * how to properly list all upstream bugs. >> > > Such information is already used by bts-link to track changes on remote > bugs linked with the 'forwarded' tag from Debian bugs. > > The sources of bts-link ('s configuration file) contain already a > description of many bugtrackers of source packages. > > More details at : http://bts-link.alioth.debian.org/
While it is true that bts-link contains several references to upstream issue tracking sysmtes, please note that: - the list is maintained by hand - with a particular formatting an-hoc for the tool - by people not related to the packaging effort so I don't see it as the canonical place where too look at, but would probably work as a good starting point for the list preparation. bts-link would probably become a client of such a Upstream Issue Tracking sys once it will be available. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
