[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: Bug#740862: duck: Should cease to pass "mailto:" URLs to curl



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:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> 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.
 
Kind regards

      Andreas.

 
> [1] https://wiki.debian.org/UpstreamMetadata
> 
> 
> - -------- Original-Nachricht --------
> Betreff: Bug#740862: duck: Should cease to pass "mailto:"; URLs to curl
> Weitersenden-Datum: Wed, 05 Mar 2014 16:45:02 +0000
> Weitersenden-Von: Axel Beckert <abe@debian.org>
> Weitersenden-An: debian-bugs-dist@lists.debian.org
> Weitersenden-CC: abe@debian.org, Simon Kainz <simon@familiekainz.at>
> Datum: Wed, 05 Mar 2014 17:43:55 +0100
> Von: Axel Beckert <abe@debian.org>
> Antwort an: Axel Beckert <abe@debian.org>, 740862@bugs.debian.org
> An: Debian Bug Tracking System <submit@bugs.debian.org>
> 
> Package: duck
> Version: 0.2
> 
> Hi Simon,
> 
> running duck in Debian's zsh's git repository causes curl errors due to
> one "mailto:"; URL:
> 
> ~/zsh/zsh $ duck -v
> debian/control: Homepage: http://www.zsh.org/: OK
> debian/control: Vcs-Browser:
> http://anonscm.debian.org/gitweb/?p=collab-maint/zsh.git: OK
> debian/control: Vcs-Git: git://anonscm.debian.org/collab-maint/zsh.git: OK
> debian/upstream/metadata: FAQ: URL: http://zsh.sourceforge.net/FAQ/: OK
> debian/upstream/metadata: Changelog: URL:
> http://zsh.sourceforge.net/releases.html: OK
> debian/upstream/metadata: Homepage: URL: http://zsh.sourceforge.net/: OK
> debian/upstream/metadata: Repository-Browse: URL:
> http://sourceforge.net/p/zsh/code/ci/master/tree/: OK
> debian/upstream/metadata: Repository: URL:
> git://git.code.sf.net/p/zsh/code: ERROR
> Curl:1 HTTP:0 Unsupported protocol Protocol git not supported or
> disabled in libcurl
> 
> 
> debian/upstream/metadata: Bug-Submit: URL: mailto:zsh-workers@zsh.org:
> ERROR
> Curl:6 HTTP:0 Couldn't resolve host name Could not resolve host: zsh.org
> 
> 
> ~/zsh/zsh $
> 
> (The first error is the same as reported in #740859, the second one is
> the relevant one.)
> 
> May it should just check if the domain of an e-mail address exists (A,
> AAAA or MX record; or maybe an whois request), but nothing more.
> 
> 
> - -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (600, 'testing'), (400, 'stable'),
> (110, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.12-trunk-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages duck depends on:
> ii  bzr                            2.6.0+bzr6591-1
> ii  git                            1:1.9.0-1
> ii  libfile-which-perl             1.09-1
> ii  libparse-debian-packages-perl  0.03-2
> ii  libwww-curl-perl               4.17-1
> ii  mercurial                      2.9.1-1
> ii  perl                           5.18.2-2+b1
> ii  subversion                     1.8.8-1
> 
> duck recommends no packages.
> 
> duck suggests no packages.
> 
> - -- no debconf information
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQIcBAEBCgAGBQJTGE5CAAoJEBy08PeN7K/pNN8P/1mJ1tsQ0bshU2ETdIi73NYv
> gcFgirtDCWMWS8xipWbZYSzVjt81zvlh1H8IzKBGBeNqAgHzVIBQ0Sj65qXpR58S
> CQQeZB/SJXmjMVcJBR/R1b5B7t4ApVn4SlZ8XFvV2RHlOWheFMnQfU+Dz5MGA4Un
> e3KYGHiQmyk154v55NiUcWwVJQT25IIm0crle1VDvBozokDlwNKo7IEYsZsbKWWC
> Kox/4b9I0IX/5oaE0D63tWeH8D73wNpAV5ef0/sM7Y2Q5qmDjdgBO45Dgy4XUDbK
> V54ElSaA6Y7CBEXrDc0m9ghVMHGFVzLjudW9MlCFM7nqsCg34z6ooqQ3/QRym8C9
> 8cAjlNsbum5Ke2lRUBfkg9PFDJRd5mNv136WqsPRqfPgcVpZNusIMOMvcj4ciV3E
> RucS5g2wLBhDLYm1E1Ibi8djZughj6cv7XcFAeJt6y1zeZH3JdGix61KkeeKExDh
> 6+k+fjecZx6zoDau+OfqqAcumIO2oI4PmnHrBGt5q91AipXCk7umpwmxXE59ZNvz
> 3sbMmID3zM+t9apM8rdw1uU+r/azIHaBI/OjwZu5G4dEXC9T+bh0Zy8CTRVXQ7uw
> xz9lH3Ocn/nnewHLHloAZyja0yfvfgw+GVla7dU1y/pptCMJo0mythzHLdW/AFCD
> K+f0rNxKDh8jOgIBGJNh
> =296H
> -----END PGP SIGNATURE-----
> 

-- 
http://fam-tille.de


Reply to: