Re: Fwd: Bug#740862: duck: Should cease to pass "mailto:" URLs to curl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Am 2014-03-06 11:55, schrieb Andreas Tille:
> Hi Simon,
>
> I think the proper place to discuss this is debian-qa list (please
> correct me if I'm wrong.
>
> On Thu, Mar 06, 2014 at 11:30:32AM +0100, Simon Kainz wrote:
> Hello!
>
> I just got bug #740862 and wanted to ask you about your opinion:
>
> [1] defines e.g. Bug-Submit as
>
> "A URL that is the place where new bug reports should be sent."
>
> I assumed this to be an hyperlink, not an mailto:..@.. entry.
>
> The definition for Eprint is
>
> "Hyperlink to the PDF file of the article."
>
> which clearly defines this to be a Web address.
>
> So my question is this: If somebody enters a mailto:-link or even
> an email address alone, is this what you intended, or should URLs
> in the context of upstream-metadata only be Hyperlinks?
>
> Thanks for your thoughts,
>
>> My *personal* opinion is that I would be fine with either of
>> these two options:
>
>> 1. Bug-Submit might allow Hyperlinks and mailto: links 2.
>> Bug-Submit should be a Hyperlink and we should enable another
>> field Bug-Mailto for e-mail addresses.
>
2 is currently implemented and working, 1 is close to being finished,
with the following check:
If Bug-Submit is mailto: - Style: Grab the email address, and try to
find out if an A(AAA) record for the given domain exists. Checking for
MX record is not enough in my opinion, as MTA use A(AAA) records to
deliver mail if no MX was found. This should at least report email
addresses which cannot receive emails because there is no domain
registered.
If it's a Hyperlink: business as usual.
Please share your thoughts about this.
Another issue:
The Repository: field is specified as "URL to a repository containing
the upstream sources." This is just the plain URL, without indication
what kind of VCS upstream might use. So I'm having a hard time to
distinguish an https:// based SVN url from an https:// based GIT url.
Same for hg,darcs and some others.
Currently I try to be smart about detecting this (grepping for shh://,
git://, etc, but for those not-so-clear cases i can currently only
check whether the url is not 404, without actually being able to check
if the given VCS would work.
Should this field be changed somehow, like Repository-Git? I'm not
sure if trying to find out which kind of repo upstream uses by trying
to appen well known postfixes (eg. _darcs/hashed_inventory for DARCS)
is the right way. I think this is also an issue for humans, trying to
use the Repository URL: One would havve to first open the url using a
browser and then try to find out which VCS was used.
Please share your thoughts about this.
Thank you,
Simon
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJTGX6VAAoJEBy08PeN7K/pXjcQAKJT+R75/VHf3PxHFWlgYISI
4k+NpZXKQ72U3Zf1VjAPy0zj00kZizjAOxPcsbGjyOG5ymADxt6YrO+DPveKKgne
UCWYGiFyMHQDqPf4hoDAM38CwPd0bhJMsqIwtXwesVH5/sq8xrV/Vf1XZK358Oz6
wInLASAykVnlUO5EoOH3G/tWHZQVlzLyjhiIJ1PFBsXs6oIA2ZC+RfI3VZM4XrbF
nkTnUC61MTNYaONTqhmJtqASF6BhnYJlPIVfAfGETEGbAg1RUWOks/eTdSYSQquP
rfNSv1Wi7tNJfvD6KVSYmWTpLpUpdluZEbUkttjedRqB7qNLpu9vxORCwoGU2bA+
JZfjlIxd7FGN9XA2rvkU9EjaXFUY5Q57XK6/QPrJu9g+Df9hoSSIiMk8ACkW1MKp
cbckj78JTLdTfBb+B/ZEPCvS3Wdm+cx4tgS0GQEVgQLslJeKyBlQb0loNezDeG+W
Vv0JXmWbxwMvhf32bvlRp9IUEaKfkIhX48bkaRoAHZ9yIwaTdSfJPKajKC21X4nl
kx+XwA18oZ02dv0JKMx64q2eK4VYCQU0Oyf1h8fGzqFj5+DwbchxJQQxAAiMbqlf
/Q/cp2KGq48DBsG///uD1FGjEC/5MHN4dAZRq/Ovuo6+fPLGYHCgmL//znDrXsAM
OnXS9UIHmB4OUwZ4YEMr
=TS/Q
-----END PGP SIGNATURE-----
Reply to: