diff options
| author | Timo Teräs <timo.teras@iki.fi> | 2010-12-17 09:36:19 +0200 |
|---|---|---|
| committer | Timo Teräs <timo.teras@iki.fi> | 2011-01-25 13:21:57 +0200 |
| commit | c206c0efae08c82f1352f94cf52c510a213afd25 (patch) | |
| tree | 560aa24c02c3d9942455beb1e6a8a98388b51871 /src/io.c | |
| parent | 4d89c0744488ddf828a8d1cf4e80ec6f1a390ebc (diff) | |
| download | apk-tools-c206c0efae08c82f1352f94cf52c510a213afd25.tar.gz apk-tools-c206c0efae08c82f1352f94cf52c510a213afd25.tar.bz2 apk-tools-c206c0efae08c82f1352f94cf52c510a213afd25.tar.xz apk-tools-c206c0efae08c82f1352f94cf52c510a213afd25.zip | |
gunzip: fix ordering of boundary callbacks
The boundary callback should not happen until all the uncompressed
data has been consumed. This previously seems to have worked
because normally gzip library returns "no error" instead of the
"stream end" if we extract exactly the amount of bytes remaining
in the archive. (Perhaps this was changed in new zlib.) In any
case, verification was broken with some apks due to this callback
ordering issue.
(cherry picked from commit f126316c791371bd3dfd7c348b10e93e49f5e2d4)
Diffstat (limited to 'src/io.c')
0 files changed, 0 insertions, 0 deletions