1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

tomato git repository error

Discussion in 'Tomato Firmware' started by replabrobin, Jul 22, 2014.

  1. replabrobin

    replabrobin Network Newbie Member

    I would like to try a self build of tomato shibby, but when I try and clone the repository on my arch linux system I see this

    robin@everest ~:
    $ git clone git://repo.or.cz/tomato.git
    Cloning into 'tomato'...
    remote: Counting objects: 300601, done.
    remote: Compressing objects: 100% (137482/137482), done.
    remote: Total 300601 (delta 155370), reused 300196 (delta 155017)
    Receiving objects: 100% (300601/300601), 1.10 GiB | 465.00 KiB/s, done.
    error: inflate: data stream error (incorrect data check)
    fatal: serious inflate inconsistency
    fatal: index-pack failed

    any idea what's going wrong here? It seems a broken repository is created, but it doesn't seem to have everything usable.
     
  2. koitsu

    koitsu Network Guru Member

    Issue can be caused by networking oddities (including Internet unreliability), or by local hardware problems (ex. disks going bad, faulty RAM, a filesystem that needs to be fsck'd, etc.). Googling "inflate: data stream error (incorrect data check)" will turn up lots of results indicating many of those things, but there doesn't seem to be a conclusive explanation.

    For me right now:

    Code:
    jdc@debian:~$ rm -fr tomato
    jdc@debian:~$ git clone git://repo.or.cz/tomato.git
    Cloning into 'tomato'...
    remote: Counting objects: 300601, done.
    remote: Compressing objects: 100% (137482/137482), done.
    remote: Total 300601 (delta 155370), reused 300196 (delta 155017)
    Receiving objects: 100% (300601/300601), 1.10 GiB | 1.86 MiB/s, done.
    Resolving deltas: 100% (155370/155370), done.
    Checking out files: 100% (53588/53588), done.
    jdc@debian:~$
    
     
  3. replabrobin

    replabrobin Network Newbie Member

    I tried three times on the 32bit machine and it failed every time. Tried again on an ubuntu 12.04 64bit machine and it worked straight away. I'm wondering if it could be the large repos size or lack of memory etc etc.
     
  4. koitsu

    koitsu Network Guru Member

    No; the OS being 32-bit vs. 64-bit has no bearing on this. The above machine I showed you output from is a Debian 7.4 32-bit running as a virtual machine under VMware Workstation, where the host is a Windows XP Pro (32-bit) system. :)

    You can try as many times as you like, but I'd suggest forcing an fsck to rule out filesystem problems.

    My point: the repo is not broken.
     

Share This Page