You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Livia Sarbu (JIRA)" <ji...@apache.org> on 2013/12/18 17:14:09 UTC

[jira] [Updated] (COMPRESS-252) Writing 7z empty entries with LZMA2 produces incorrect or corrupt archive

     [ https://issues.apache.org/jira/browse/COMPRESS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Livia Sarbu updated COMPRESS-252:
---------------------------------

    Description: 
I couldn't find an exact rule that causes this incorrect behavior, but I tried to reduce it to some simple scenarios to reproduce it:

Input: A folder with certain files -> tried to archive it.
If the folder contains more than 7 files the incorrect behavior appears.

Scenario 1: 7 empty files
Result: The created archive contains a single folder entry with the name of the archive (no matter which was the name of the file)

Scenario 2: 7 files, some empty, some with content
Result: The created archive contains a folder entry with the name of the archive and a number of file entries also with the name of the archive. The number of the entries is equal to the number of non empty files.

Scenario 3: 8 empty files
Result: 7zip Manager cannot open archive and stops working.

Scanario 4.1: 8 files: some empty, some with content, last file (alphabetically) with content
Result: same behavior as described for Scenario 2.

Scanario 4.2: 8 files, some empty, some with content, last file empy
Result: archive is corrupt, the following message is received: "Cannot open file 'archivename.7z' as archive" (7Zip Manager does not crash).

  was:
I couldn't find an exact rule that causes this incorrect behavior, but I tried to reduce it to some simple scenarios to reproduce it:

Input: A folder with certain files -> tried to archive it.
If the folder contains more than 7 files the incorrect behavior appears.

Scenario 1: 7 empty files
Result: The created archive contains a single folder entry with the name of the archive (no matter which was the name of the file)

Scenario 2: 7 files, some empty, some with content
Result: The created archive contains a folder entry with the name of the archive and a number of file entries also with the name of the archive. The number of the entries is equal to the number of non empty files.

Scenario 3: 8 empty files
Result: 7zip Manager cannot open archive and stops working.

Scanario 4.1: 8 files: some empty, some with content, last file (alphabetically) with content
Result: same behavior as described for Scenario 2.

Scanario 4.2: 8 files, some empty, some with content, last file empy
Result: archive is corrupt, the following message is received: "Cannot open file 'archivename.7z' as archive" (7Zip Manager does not crash).

I can provide the test class & project used if it is helpful.


> Writing 7z empty entries with LZMA2 produces incorrect or corrupt archive
> -------------------------------------------------------------------------
>
>                 Key: COMPRESS-252
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-252
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Archivers
>    Affects Versions: 1.6
>         Environment: eclipse 3.7.2, java 1.7
>            Reporter: Livia Sarbu
>            Priority: Blocker
>
> I couldn't find an exact rule that causes this incorrect behavior, but I tried to reduce it to some simple scenarios to reproduce it:
> Input: A folder with certain files -> tried to archive it.
> If the folder contains more than 7 files the incorrect behavior appears.
> Scenario 1: 7 empty files
> Result: The created archive contains a single folder entry with the name of the archive (no matter which was the name of the file)
> Scenario 2: 7 files, some empty, some with content
> Result: The created archive contains a folder entry with the name of the archive and a number of file entries also with the name of the archive. The number of the entries is equal to the number of non empty files.
> Scenario 3: 8 empty files
> Result: 7zip Manager cannot open archive and stops working.
> Scanario 4.1: 8 files: some empty, some with content, last file (alphabetically) with content
> Result: same behavior as described for Scenario 2.
> Scanario 4.2: 8 files, some empty, some with content, last file empy
> Result: archive is corrupt, the following message is received: "Cannot open file 'archivename.7z' as archive" (7Zip Manager does not crash).



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)