Bug#551386: Per-package link to upstreams bugtracker

On Sun, Oct 18, 2009 at 6:23 AM, gregor herrmann <gregoa.DeleteThis@debian.org> 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 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 on this subject about splitting
up the Packages file:

http://lists.debian.org/debian-devel/2009/08/msg00057.html

I heard a rumor that the Description fields were going to be split out
into Translation-en files and I'd like this trend to continue.

--
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-REQUEST.DeleteThis@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.DeleteThis@lists.debian.org

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/

Hope this helps.
--
Olivier BERGER <olivier.berger.TakeThisOut@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)




--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

On Mon, Oct 19, 2009 at 11:20, Olivier Berger
<olivier.berger.RemoveThis@it-sudparis.eu> 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 debian-bugs-dist-REQUEST.RemoveThis@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.RemoveThis@lists.debian.org

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 information to
the bts,[0] but assuming that there's:

1) a clear consensus on the methodology to make/update the links[1]

2) a tab-delineated text file generated somewhere[2] with the source
package name in the first field, the link to the upstream bts in the
second, and the wiki page on wiki.debian.org for additional bug
reporting/triage information in the third

3) enough source packages implementing #1 for me to actually test it;
I imagine if we get at least a half dozen packages from different
maintainers it'll be enough to demonstrate that it's workable.

then I'll shove it into my queue to implement.


Don Armstrong

0: the more complexity, the longer it'll take; the actual code change
to debbugs is relatively trivial.

1: probably a good idea to also have a draft for inclusion in
devel-reference

2: where this is depends on the method, but probably ftpmaster is the
ideal place; dunno, though.

--
Some pirates achieved immortality by great deeds of cruelty or
derring-do. Some achieved immortality by amassing great wealth. But
the captain had long ago decided that he would, on the whole, prefer
to achieve immortality by not dying.
-- Terry Pratchet _The Color of Magic_

http://www.donarmstrong.com http://rzlab.ucr.edu


--
To UNSUBSCRIBE, email to debian-devel-REQUEST DeleteThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster DeleteThis @lists.debian.org

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
> > or such or actual inclusion in the policy?
>
> Depends on the complexity of me actually getting the information to
> the bts,[0] but assuming that there's:
>
> 1) a clear consensus on the methodology to make/update the links[1]
>
> 2) a tab-delineated text file generated somewhere[2] with the source
> package name in the first field, the link to the upstream bts in the
> second, and the wiki page on wiki.debian.org for additional bug
> reporting/triage information in the third

The conf file of bts-link is very close to that IMHO, and is probably
one of the best resources for building this (unless launchpad holds
better data ?) :
http://git.debian.org/?p=bts-link/bts-link.git;a=blob;f=btslink.cfg;hb=HEAD

>
> 3) enough source packages implementing #1 for me to actually test it;
> I imagine if we get at least a half dozen packages from different
> maintainers it'll be enough to demonstrate that it's workable.
>

It seems to me that more than 150 packages are configured in bts-link's
config file... so that makes it more evident maybe that this is already
a pretty common need for Debian, even if it's only implemented inside
bts-lik and not in a more general way.

Just my 2 cents,

> then I'll shove it into my queue to implement.
>
>
> Don Armstrong
>
> 0: the more complexity, the longer it'll take; the actual code change
> to debbugs is relatively trivial.
>
> 1: probably a good idea to also have a draft for inclusion in
> devel-reference
>
> 2: where this is depends on the method, but probably ftpmaster is the
> ideal place; dunno, though.
>
> --
> Some pirates achieved immortality by great deeds of cruelty or
> derring-do. Some achieved immortality by amassing great wealth. But
> the captain had long ago decided that he would, on the whole, prefer
> to achieve immortality by not dying.
> -- Terry Pratchet _The Color of Magic_
>
> http://www.donarmstrong.com http://rzlab.ucr.edu

Best regards,
--
Olivier BERGER <olivier.berger.DeleteThis@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


--
To UNSUBSCRIBE, email to debian-devel-REQUEST.DeleteThis@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.DeleteThis@lists.debian.org

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 to achieve:
>
> bts-link is
> * per-bug.

Not exactly as far as the definition of where the upstream bugtracker
lies, which was your concern IIRC.

Even if the forwarded tag is set on individual bugs, it's very much
likely that all those being forwarded to URLs point to the same
bugtracker for all of the bugs filed on the same package. So the
bts-link config file contains references of bugtrackers per packages
IIRC as you can see in :
http://git.debian.org/?p=bts-link/bts-link.git;a=blob;f=btslink.cfg;hb=HEAD

> * thus can and needs to handle different trackers per package

I'm not sure this is the case actually.

> * needs manual intervention once (by setting the forwarded field)
> * aim for high-level technical integration.

SNIP

> Greetings,
> Joachim

Just my 2 cents,

Best regards,
--
Olivier BERGER <olivier.berger.RemoveThis@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)




--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.RemoveThis@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.RemoveThis@lists.debian.org