Bug#551386: Per-package link to upstreams bugtracker

2009-11-03 Thread Olivier Berger
Hi. Some more feedback, again. Le lundi 19 octobre 2009 à 11:21 -0700, Don Armstrong a écrit : > On Mon, 19 Oct 2009, Joachim Breitner wrote: > > @dons: What are your requirements until you will accept this feature on > > bugs.d.o, in terms of number of packages or clear consensus on d-devel > >

Bug#551386: Per-package link to upstreams bugtracker

2009-11-03 Thread Olivier Berger
Hi. Sorry to be late on that discussion (vacation time in between). I'm just adding a few bits in case it would help. Le lundi 19 octobre 2009 à 12:54 +0200, Joachim Breitner a écrit : > Hi, > SNIP > I thought about bts-link as well, of course, but there are some > differences in what is tried

Bug#551386: Per-package link to upstreams bugtracker

2009-10-19 Thread Don Armstrong
On Mon, 19 Oct 2009, Joachim Breitner wrote: > @dons: What are your requirements until you will accept this feature on > bugs.d.o, in terms of number of packages or clear consensus on d-devel > or such or actual inclusion in the policy? Depends on the complexity of me actually getting the informat

Bug#551386: Per-package link to upstreams bugtracker

2009-10-19 Thread Joachim Breitner
Hi, Am Montag, den 19.10.2009, 11:20 +0200 schrieb Olivier Berger: > 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 spe

Bug#551386: Per-package link to upstreams bugtracker

2009-10-19 Thread Sandro Tosi
On Mon, Oct 19, 2009 at 11:20, Olivier Berger 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

Bug#551386: Per-package link to upstreams bugtracker

2009-10-19 Thread Olivier Berger
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 t

Bug#551386: Per-package link to upstreams bugtracker

2009-10-18 Thread gregor herrmann
On Sun, 18 Oct 2009 10:23:02 +0800, Paul Wise wrote: > > In order not to bloat the Packages file we where thinking about a > > header in debian/copyright (which has, according to DEP5, already > > information about the Upstream-Author and Upstream-Source). > I'd like to re-iterate my earlier mail

Bug#551386: Per-package link to upstreams bugtracker

2009-10-17 Thread Paul Wise
On Sun, Oct 18, 2009 at 6:23 AM, gregor herrmann wrote: > On Sat, 17 Oct 2009 23:27:45 +0200, Joachim Breitner wrote: > >> Implementation-wise, this is probably best implemented via a new >> control header, similar to Homepage, containing the URL. But of course >> I’m open for other ideas. > > In

Bug#551386: Per-package link to upstreams bugtracker

2009-10-17 Thread gregor herrmann
On Sat, 17 Oct 2009 23:27:45 +0200, Joachim Breitner wrote: > Therefore, I’d find it handy to have, on the header of the package’s bug > page a link "Search upstream bugtracker" that directly sends me to the > upstream bugtracker, ideally to a search request for all bugs affecting > this particula

Bug#551386: Per-package link to upstreams bugtracker

2009-10-17 Thread Don Armstrong
tag 551386 moreinfo help thanks On Sat, 17 Oct 2009, Joachim Breitner wrote: > Therefore, I'd find it handy to have, on the header of the package's > bug page a link "Search upstream bugtracker" that directly sends me > to the upstream bugtracker, ideally to a search request for all bugs > affecti

Bug#551386: Per-package link to upstreams bugtracker

2009-10-17 Thread Joachim Breitner
Package: bugs.debian.org Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, 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