Package: git-svn
Version: 1:1.5.2.2-3
Followup-For: Bug #430091

I stumbled on the same problem while trying to import the dpkg repository.
Starting git-svn fetch again seems to work ok.

It looks likes it fails each time that it encounters a commit on a new
tag/branch.

You mention downgrading libsvn-perl to the testing version, why? Is the
sid version known to be buggy? Because I don't see a bugreport
confirming that information. :-)

r363 = ee63be02d56e4936550409e0caf02666b1705da5 (trunk)
        M       debian/changelog
        M       ChangeLog
        M       configure.ac
r364 = 031822391eee15e3a24fb0523411e1cdae34b086 (trunk)
Malformed network data: Malformed network data at /usr/bin/git-svn line 964
[EMAIL PROTECTED]:~/partages/debian/git/dpkg-svn$ LC_ALL=C git-svn fetch
Found possible branch point: svn+ssh://svn.debian.org/svn/dpkg/trunk => 
svn+ssh://svn.debian.org/svn/dpkg/tags/1.13.20, 364
Found branch parent: (tags/1.13.20) 031822391eee15e3a24fb0523411e1cdae34b086
Following parent with do_switch
Successfully followed parent
r365 = 76b385b6782589efcb8e087ed9c57752855ce2c1 (tags/1.13.20)
        M       debian/changelog
        M       ChangeLog
        M       configure.ac


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-svn depends on:
ii  git-core                    1:1.5.2.2-3  fast, scalable, distributed revisi
ii  libsvn-perl [libsvn-core-pe 1.4.4dfsg1-1 Perl bindings for Subversion
ii  libterm-readkey-perl        2.30-3       A perl module for simple terminal 
ii  libwww-perl                 5.805-1      WWW client/server library for Perl

Versions of packages git-svn recommends:
ii  git-doc                      1:1.5.2.2-3 fast, scalable, distributed revisi

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to