On Sat, Jul 05, 2008 at 04:58:29PM +1000, Ben Finney wrote:
> =====
> $ svn checkout 
> svn://qingy.svn.sourceforge.net/svnroot/qingy/trunk/qingy
> svn: Can't connect to host 'qingy.svn.sourceforge.net': No route to host
> =====
> 
> Please correct the 'Vcs-Svn' control field to the correct URL for use 
> with the Subversion client.

Funny... If I remember correctly it used to work. Perhaps they changed
something at sourceforge, as http://sourceforge.net/svn/?group_id=82854
now states that the repository can be used with
"svn co https://qingy.svn.sourceforge.net/svnroot/qingy qingy".

Anyway, that field in debian/control is going to be removed as I made a
wrong assumption about it: the repository I linked is the upstream one,
but that field is meant to contain the location of the repository used to
maintain the package.
http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-vcs

(I don't plan to release an updated version of qingy just to close this
bug and the other you reported as I prefer to wait that upstream releases
a fix for #447512)

ciao
Riccardo

Attachment: signature.asc
Description: Digital signature

Reply via email to