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

Re: Huge list of broken Vcs-Svn entries in control files



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 08/28/13 10:31, schrieb Alexander Wirt:
> Andreas Tille schrieb am Wednesday, den 28. August 2013:
> 
>> On Mon, Aug 26, 2013 at 07:55:44AM -0400, James McCoy wrote:
>>>> _BUT_: After changing svn://svn.debian.org/... to 
>>>> svn://anonscm.debian.org/... makes it work again:
>>> 
>>> See also
>>> <http://lintian.debian.org/tags/vcs-field-not-canonical.html>, 
>>> so maintainers should be aware of the problem.
>> 
>> IMHO this is the wrong attitude.  While I tend to respect lintian
>> issues of severity info you can not at all expect maintainers to
>> just seek long standing bug free packages for such things and
>> upload packages just because of this.
>> 
>> And back to this actual issue:  I *totally* fail to see in how
>> far a package becomes a better user / developer experience just
>> because I do
>> 
>> g/^Vcs/s/svn/anonscm/
>> 
>> IMHO requiring this from maintainers is a singularity in my 15
>> years Debian experience where a change is totally unmotivated and
>> just drains developer time for no use at all.
> Just for the record, this was a bug and is now fixed on alioth.
> 
> svn ls svn://svn.debian.org/adduser branches/ tags/ trunk/
> 
> so keep your polemic at home and thank buxy (who brought this topic
> up on #alioth) and sgran that fixed it.
> 
> Alex
> 
Hi,

1st: Thanks for fixing this, reduces the number of packages with url
issues by ~2.5 k.

2nd: Sorry, I didn't want to make someone annoyed by bringing this
issue to debian-qa, but it somehow seemed like a qa thing to me, and
not something which resulted from changes on alioth. Sorry for that.


Regards,

Simon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSHccFAAoJEBy08PeN7K/pj70P/1hrx3HZp1z9l1KX8goXyaM1
hq+pxo7h7UdeLbnfpmQoy8m9+qXChYtV4bn92fYxaa8oY7cm2wLDU6q2xHlFCVU3
BFuEd5FMMi6J/6811OjHA3KSxRQA5TB4C+IqQKio4JWb7/yPFhTjrVVwFt26Dsg1
+FatS+tzG4RcvEDLfjDq0Bgno0M+J+xniZvfKuxeoQw2hJWWlYh3W9Rm62v7uf03
/QK1L2pItEZVJmgt32Q8PW4Zq8je7dH4RG86q0d7l+1HM7G7zAqENGx8/9iIGfUP
mIjAmfmdGFulpfYHxOf8HcIlRDFkl8iimFU9Ar1LaaBGn2fazsH2CPi6/aK9vc8V
1U+12DawOb9l3DCxDFfHNCykbEHwZRzSzvpqoGD+S03cua4TzBuiRPGDReQ8CmHO
sCNjxNyBB61FmEKQMNzFGw5FUZakk3Ru0mMMFdieQSiUgwbBUPX3ZG58a1/9qim9
pLQ/Oag0BAaieM4c0Mf5Og6ZG4IuZ8Z8p7s1mN2BovWAawwkxJQLEVXVCNKuHmFz
M0NsLqqgBbF1T7sC6Bp487jSN8LBJt1Mapq6HkAlVgHaxOi983KnNbBpJDT/Y0/u
HfyKOwxRQF4JNBnUpjPwY15NvT91y/eeuM4aMh8FsuvMUok9kylNJIjKYwtoJdYQ
wKSDubNs2yCQltgYCk6f
=W3S0
-----END PGP SIGNATURE-----


Reply to: