-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, and thanks for the report.
Currently i choose the VCS tool to use not by the URL scheme but by the field name: VCS-Git, VCS-Svn, ... This works currently only for d/control file. In upstream metadata, the Repository: field gives no indication which VCS was used. So it's quite impossible to find the "correct" VCS, because at least GIT, SVN and HG (and some others) may also use HTTP(S) for transport. I currently implemented detection of non-HTTP based URL schemas with the follwing implications: git:// and svn:// Urls are checked usign the appropriate tool, all other HTTP(S) based URLS with no indication as what VCS they might be using, are simply checked for basic availability via HTTP. This means only reporting HTTP 403, 404, 500 and some more HTTP errors. I would prefer doing a check with the appropriate tool, but I think this is currently better than wildly guessing which VCS might have been used by trying different permutations of the Repository URL, which might give even more unreliable results. This is implemented in duck 0.4, to be uploaded soon. Bye, Simon Am 2014-03-05 17:27, schrieb Axel Beckert: > Package: duck Version: 0.2 > > Hi Simon, > > thanks for making duck also available as package for maintainers to > test their packages themselves! > > I'm running duck on the git checkout of the screen package (which > contains an debian/upstream directory): > > ~/screen/screen $ duck -v debian/control: Vcs-Git: > git://anonscm.debian.org/collab-maint/screen.git: OK > debian/control: Vcs-Browser: > http://anonscm.debian.org/gitweb/?p=collab-maint/screen.git: OK > debian/control: Homepage: http://savannah.gnu.org/projects/screen: > OK debian/upstream/metadata: Repository: URL: > git://git.sv.gnu.org/screen.git: ERROR Curl:1 HTTP:0 Unsupported > protocol Protocol git not supported or disabled in libcurl > > > debian/upstream/metadata: Homepage: URL: > https://www.gnu.org/software/screen/: OK debian/upstream/metadata: > Bug-Database: URL: https://savannah.gnu.org/bugs/?group=screen: OK > debian/upstream/metadata: Repository-Browse: URL: > http://git.savannah.gnu.org/cgit/screen.git/: OK > debian/upstream/metadata: Changelog: URL: > http://git.savannah.gnu.org/cgit/screen.git/plain/src/ChangeLog: > OK debian/upstream/metadata: FAQ: URL: > http://aperiodic.net/screen/faq: OK ~/screen/screen $ > > While duck recognizes git:// URLs in the Vcs-Git field without > issues, it does not recognizes git:// URLs in > debian/upstream/metadata's Repository field. > > I would have expected that it handles all fields the same way, at > least all fields where not only HTTP based URLs are expected. > > -- 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/ iQIcBAEBCgAGBQJTHr/hAAoJEBy08PeN7K/p/5oP/iHegC+dPuDxJm8QL+OFhPcI ofrUFcfw7l3OVXPxzoxQp2xqtLQS9K8uK4P4PCehRoC0dPNDInSgqKAGm4Gvt24O KeDGkC5g/TPB7hJot/CU4MhlzwhtIcRvHPqytHycxsHRzImd/d3bRB8EbPetr6RJ O8c8U7sOSEbLhqEmTM59+6q1Lom12741zEJimspyqKFM9RF8qE/w6Zp8+aumPxLf vTJKYnrHgEhoHx3UCtqrTaVuIcN/sP5tSVeXteYYYZTCBugXPxJp3qnEVl7TjvfI jorAN4RO1WvCKEzEvzOUFN2HJbzQ7MW2ZIFhCliHPuRkO+9C0jTyj+bPaMttW0/n gf8RExVWXEP3piGB2RN/GJGxAzfllpCCDR3y9VKIs9E5mPumJILmlTV3uwd0K6qv PtUTmatr8HKc8P5wh+q5wDlOzZ21/0DuYyEFvik6gmTyRSCXBgyBDYfADPNfm7zd PPCoqSGf1PGRaUtL/sEzmthgs9PWuY9y5xfSumKyF3/FsAZ4bKYnebaIjNZigrnM rB8c4HMTc2/jivnJVDzpi0iCpqzK1aIjeqyt+MAVoiQ8+AT1PySPW9OPScIaFmyr pRsRiMdrqMm9BTf0FGJeWJLmP9qm7iQynusdT6YQyV5VTUqMMHCxLBbGV7gNbq3B Vfxo0ZsfJe5mEHETHyAa =NoIK -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
