Huge list of broken Vcs-Svn entries in control files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
(Sorry, this might be a bit longer to read, but I really want to make
my points clear...)
Currently (as of 2012-08-26) duck.debian.net shows me 9301 binary
packages with URL issues, resulting from 4318 source packages.
I took a closer look and noticed the following (just taking package
icedove-bidiui as an example):
icedove-bidiui [1] is built by source package bidiui [2] which
contains the collowing control file:
Source: bidiui
Section: mail
Priority: optional
Maintainer: Debian Hebrew Packaging Team
<debian-hebrew-package@lists.alioth.debian.org>
Uploaders: Baruch Even <baruch@debian.org>, Lior Kaplan
<kaplan@debian.org>, Shachar Shemesh <shachar@debian.org>, Tzafrir
Cohen <tzafrir@debian.org>
Build-Depends: debhelper (>= 5), zip, unzip, perl
Standards-Version: 3.9.1
Vcs-Svn: svn://svn.debian.org/svn/debian-hebrew/pkg/bidiui
Vcs-Browser: http://svn.debian.org/wsvn/debian-hebrew/pkg/bidiui/
Homepage: http://bidiui.mozdev.org/mail/
Package: icedove-bidiui
...
...
There Vcs-Svn: points to
svn://svn.debian.org/svn/debian-hebrew/pkg/bidiui and Vcs-Browser
points to http://svn.debian.org/wsvn/debian-hebrew/pkg/bidiui/
Using the Vcs-Browser link, my browser ultimately points to
http://anonscm.debian.org/viewvc/debian-hebrew/pkg/bidiui/, so there
must be some rewrite rule/vhost config/magic fairy to make this work -
So Vcs-Browser _works!_
Using the svn cli too, i get:
skainz@zidpc9027:~$ svn info
"svn://svn.debian.org/svn/debian-hebrew/pkg/bidiui"
svn: No repository found in
'svn://svn.debian.org/svn/debian-hebrew/pkg/bidiui'
_BUT_: After changing svn://svn.debian.org/... to
svn://anonscm.debian.org/... makes it work again:
skainz@zidpc9027:~$ svn info
"svn://anonscm.debian.org/svn/debian-hebrew/pkg/bidiui"
Path: bidiui
URL: svn://anonscm.debian.org/svn/debian-hebrew/pkg/bidiui
Repository Root: svn://anonscm.debian.org/svn/debian-hebrew
Repository UUID: 682e114d-45fc-0310-b2b6-9171eff3cb32
Revision: 987
Node Kind: directory
Last Changed Author: kaplan
Last Changed Rev: 864
Last Changed Date: 2011-04-04 22:50:45 +0200 (Mon, 04 Apr 2011)
skainz@zidpc9027:~$
So I took a look into the DUCK database and found about 2500 broken
SVN urls, which follow this schema.
I Actually identified 2 different types of debian-based SVN-url:
1: svn://svn.debian.org/<foo> which works after changing to
svn://svn://anonscn.debian.org/<foo>
2: svn://svn.debian.org/svn/<bar> which works after changing to
svn://anonscm.debian.org/<bar>
After generating a new list with the presumably correct svn url, I get
no more errors concerning SVN repos.
So it seems as browsing the svn tree is ok, because HTTP-based
rewrites work, but svn:// access doens not, because of a missing
rewrite rule ( if that is even possible in svn:// protocol).
Fact is, this ultimately breaks debcheckout, which relies on the
Vcs-Svn/Git/... url.
I ask you for suggestions how to eventually fix this ( I could
mass-file bugs, that would be ok), or if there is something more to
it, which I didn't see.
The list of source packages with such issues is available here:
http://duck.debian.net/svn/svn_debian_issues.txt
Thanks for your comments,
Simon
[1] http://packages.qa.debian.org/b/bidiui.html
[2] http://packages.debian.org/source/sid/bidiui
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSGvdaAAoJEBy08PeN7K/pJx4P/j0Yob9/pCax+Pa7J92x8ke8
Lz1XPRFXrSq5vBA3zIC2muE51K3LbVal/RSy+3To2ZLgxHYB2sbPq0928Mn4BNT/
wX9TRsvj0VTqF3spm5ujfZWLeOPnsdOXPlUUbWD50ZslGWDnLcYEHbFuLDGjRc18
HVobBLq77hqYTHoqdEG0GoC3JFLgKXyBXhb85LUuUsm+nA24LAwVpbeIazDEtylz
GlV9HNKVq0iIDaNA0ZpaVidJm8S+0F+6Tc4v/k9+lY/dCfMo6HHl+9idLHsoNW6P
JXCWMgl6iRrO6tJTIXpIxyssFvxUr+JRkz4eYMQpIl0XQUbRyftgmgB3dWG3qAwp
TOIHAZRztiDZ2oW52EpLT6pEgoJnp5sK4d8AYZwF3OL9ZFknecc64P8jyYbhWGUJ
vcuoaxQ0gfe3JpsTz/jqTIldZXppqFKWkXjZQZQdA+zWr0X25iWxUZIPR1ELYMFS
yAkv83/LRLSXtgFPx2WkkgXHywPCfs40mShX3YqMbxTvr9ppXhEWRVfpOMxp2fh8
T2NVRPcPyOnLaF5ZHHhbJGu0Imkbfhq+ZD+MnSSMgOtypI/h0+0pREP63R+PZqcH
+TZSAKn2Fk/IwsCizhd2HDRmvdDFYNYRKtmZE+KfRYQkR+foobTDY8iWNaLBoTjA
6d4zb0qFCKJVxD47mf5Q
=JCx9
-----END PGP SIGNATURE-----
Reply to: