Issue #29 resolved

bad local file header in library.zip

Anonymous created an issue

{{{

!python

Please report this bug to http://bitbucket.org/tortoisehg/thg/issues Mercurial version (1.7+3-15b8a652b558). TortoiseHg version (1.1.5+11-d4f494ca1456) Command: --nofork vdiff --listfile C:\Users\byates\AppData\Local\Temp\THGBB87.tmp CWD: I:\Ineoquest\FPGA\Class_Exp_Atom_Cricket\Modules\sa7111a_to_jpeg\verif\scripts Extensions loaded: fixfrozenexts, mq, rebase, purge, hgshelve, hgview Python version: 2.6.5 (r265:79096, Mar 19 2010, 21:48:26) [MSC v.1500 32 bit (Intel)] Windows version: (6, 1, 7600, 2, '') Processor architecture: x64 Traceback (most recent call last): File "tortoisehg\hgqt\thgrepo.pyo", line 87, in timerEvent File "tortoisehg\hgqt\thgrepo.pyo", line 96, in pollStatus File "tortoisehg\hgqt\thgrepo.pyo", line 135, in _checkrepotime File "tortoisehg\hgqt\thgrepo.pyo", line 391, in thginvalidate File "mercurial\demandimport.pyo", line 75, in getattribute File "mercurial\demandimport.pyo", line 47, in _load ZipImportError: bad local file header in C:\Program Files (x86)\TortoiseHg\library.zip

}}}

Comments (3)

  1. FlorianGeorge

    Just had the same issue after downgrading from 2.6.0 to 2.5.1:

    ** Mercurial version (2.3.2).  TortoiseHg version (2.5.1)
    ** Command: --nofork workbench
    ** CWD: V:\Development
    ** Encoding: cp1252
    ** Extensions loaded: hgsubversion, rebase
    ** Python version: 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]
    ** Windows version: sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1')
    ** Processor architecture: x86
    ** Qt-4.8.0 PyQt-4.9.1
    Traceback (most recent call last):
      File "tortoisehg\hgqt\thread.pyo", line 277, in run
      File "mercurial\demandimport.pyo", line 86, in __getattribute__
      File "mercurial\demandimport.pyo", line 58, in _load
    ZipImportError: bad local file header in C:\Program Files\TortoiseHg\library.zip
    

    After re-upgrading from 2.5.1 to 2.6.0 it was fixed.

  2. Log in to comment