#1453 mingw32-make lzma package error

component_package
closed-fixed
MinGW (57)
2010-07-13
2010-07-12
Mark B
No

the package hosted at http://sourceforge.net/projects/mingw/files/MinGW/make/make-3.81.90-20100618-mingw32/make-3.81.90-20100618-1-mingw32-bin.tar.lzma/download - that is the package mingw-get retrieves - gives an error when unlzma'd [silent error in mingw-get]; hence the binary is not properly installed

$ unlzma make-3.81.90-20100618-1-mingw32-bin.tar.lzma
unlzma: SetDecoderProperties() error

I've tried several mirrors; identical results, so it looks as though it's the package

host OS - windows 7 32-bit for the mingw-get, Ubuntu 10.04 64-bit for the unlzma

mingw-get is 0.1alpha2
lzma is 4.43-14ubuntu2_amd64
archive manager - gives identical error - is file-roller_2.30.1.1-0ubuntu2_amd64

Discussion

  • Chris Sutcliffe

    Chris Sutcliffe - 2010-07-13

    Re-uploaded with corrected archives.

     
  • Chris Sutcliffe

    Chris Sutcliffe - 2010-07-13
    • assigned_to: nobody --> ir0nh34d
    • status: open --> closed-fixed
     
  • Keith Marshall

    Keith Marshall - 2010-07-16

    While the issue of the malformed package archive may have been resolved by repackaging, the underlying failure of mingw-get to effectively diagnose the problem remains.

    Rather than reopen this ticket, I've raised new ticket #3030483 (https://sourceforge.net/tracker/index.php?func=detail&aid=3030483&group_id=2435&atid=102435), to address the associated issue. Chris, any chance you could provide (or regenerate) a copy of the original malformed archive, to assist in further problem diagnosis?

     
  • Chris Sutcliffe

    Chris Sutcliffe - 2010-07-16

    Sure, I can regenerate the old 'corrupted' archives again. What happened with the previous archives was that I used 'tar -Jcvf <achrive name>.tar.lzma', at the time not realizing '-J' defaults to .xz archiving. As a result, though named '<archive name>.tar.lzma' they were actually xz compressed. What confused me initially was that tar handled the archive correctly (via 'tar -Jtvf') despite being incorrectly named, as did 7-zip (the other tool I use to validate an archive). It was just unlzma that complained.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks