• Home

  • Custom Ecommerce
  • Application Development
  • Database Consulting
  • Cloud Hosting
  • Systems Integration
  • Legacy Business Systems
  • Security & Compliance
  • GIS

  • Expertise

  • About Us
  • Our Team
  • Clients
  • Blog
  • Careers

  • VisionPort

  • Contact
  • Our Blog

    Ongoing observations by End Point Dev people

    Signs of a too-old Git version

    Jon Jensen

    By Jon Jensen
    July 28, 2008

    When running git clone, if you get an error like this:

    Couldn’t get http://some.domain/somerepo.git/refs/remotes/git-svn for remotes/git-svn
    The requested URL returned error: 404 error: Could not interpret remotes/git-svn as something to pull

    You’re probably using a really old version of Git that can’t handle some things in the newer repository. The above example was from Git, the very old version included with Debian Etch. The best way to handle that is to use Debian Backports to upgrade to Git 1.5.5.

    On Red Hat Enterprise Linux, Fedora, or CentOS, the Git maintainers’ RPMs usually work (though you may need to get a dependency, the perl-Error package from RPMforge).

    If all else fails, grab the Git source and build it. I’ve never had a problem building the code anywhere, though building the docs requires a newer version of asciidoc than is easy to get on RHEL 3.