On Jun 13, 2007, at 11:15 PM, shirish wrote:
... Ok lemme take a real world example to illustrate what I mean. The libburn, libisofs & cdrskin all of them use trac & all work with each other. Now when I registered the libburnia tracker https://launchpad.net/bugs/bugtrackers/libburn-bugs then there should be a way for the guys who are looking/maintaining bugs of the three components.
I don't think you finished that sentence. There should be a way for the people who are maintaining libburn/libisofs/cdrskin bugs to ... something. What is the something?
Now as it turns out libburn4, libisofs4 & cdrskin are
maintained by MOTU then I should be able to send them a pm/mail or
somehow let them know that the upstream bug-tracker is registered here
& they associate the same.
What do you mean by "associate the same"? Are you suggesting that the MOTUs might not have bothered to link to upstream bug reports because they didn't know the upstream bugtracker was registered?
If you want to send a message to a package maintainer, I don't see that that's something Launchpad needs to help you with.
This is with the caveat that MOTU is
packaging from the sources & not from debian as otherwise it would
have to follow ubuntu-bug > debian > upstream if I understand
correctly.
...
As far as the Launchpad bug tracker is concerned, Ubuntu, Debian, and upstream are on the same level. You can mark an Ubuntu bug as also occurring in Debian, also occurring in the original project, or both, or neither.
Cheers -- Matthew Paul Thomas http://mpt.net.nz/
PGP.sig
Description: This is a digitally signed message part
-- launchpad-users mailing list launchpad-users@lists.canonical.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
