Debian - pilot-link plucker jpilot - upstream issue tracking (bts-link)

Sandro Tosi morph at debian.org
Sat Jun 6 12:16:23 UTC 2009


Hi Ludovic,

On Sat, Jun 6, 2009 at 14:10, Ludovic Rousseau
<ludovic.rousseau at gmail.com> wrote:
> 2009/6/6 Sandro Tosi <morph at debian.org>:
>> I'm writing you since you're the maintainer of pilot-link plucker jpilot .
>>
>> As you might know, Debian has a tool to regularly check upstream issue
>> trackers to monitor the status of forwarded bugs: bts-link[1].
>>
>> [1] http://bts-link.alioth.debian.org/
>>
>> Sadly, [2] and [3] (the issue trackers for these packages) tend to
>> blacklist too aggressively clients that generate some traffic on them.
>>
>> [2] http://bugs.pilot-link.org
>> [3] http://bugs.jpilot.org/
>
> Do you receive rejection mails or the mails your robot sends are just lost?

we are not able to connect to the websites to check the bug status.

>> I've already tried to contact upstream but I got no reply (maybe due
>> to some problem with MLs).
>
>
>> Since you got a lot of forwarded bugs for those packages, I think it's
>> important that they can be monitored by bts-link.
>
> These projects are not really active upstream any more.
> And I receive a mail when a bug I submitted upstream has a status change.
>
>> So I'm here to kindly ask you to leverage on upstream to lower the
>> blacklist limit, at least for Debian project machine (as of now, I run
>> the script from merkel). If they want, we can provide IPs or host
>> names/domains to whitelist us.
>>
>> Thanks a lot in advance for your collaboration.
>
> I will try to contact the admin.

Thanks a lot!

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



More information about the Bts-link-devel mailing list