Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
New features in UnZip 6.0, released 20 April 2009:
* Support PKWARE ZIP64 extensions, allowing Zip archives and Zip
archive entries larger than 4 GiBytes and more than 65536 entries
within a single Zip archive. This support is currently only
available for Unix, OpenVMS and Win32/Win64.
* Support for bzip2 compression method.
* Support for UTF-8 encoded entry names, both through PKWARE's
"General Purpose Flags Bit 11" indicator and Info-ZIP's new "up"
unicode path extra field. (Currently, on Windows the UTF-8
handling is limited to the character subset contained in the
configured non-unicode "system code page".)
* Added "wrong implementation used" warning to error messages of
the MSDOS port when used under Win32, in an attempt to reduce
false bug reports.
* Fixed "Time of Creation/Time of Use" vulnerability when setting
attributes of extracted files, for Unix and Unix-like ports.
* Fixed memory leak when processing invalid deflated data.
* Fixed long-standing bug in unshrink (partial_clear), added
boundary checks against invalid compressed data.
* On Unix, keep inherited SGID attribute bit for extracted
directories unless restoration of owner/group id or SUID/SGID/Tacky
attributes was requested.
* On Unix, allow extracted filenames to contain embedded control
characters when explicitly requested by specifying the new command
line option "-^".
* On Unix, support restoration of symbolic link attributes.
* On Unix, support restoration of 32-bit UID/GID data using the
new "ux" IZUNIX3 extra field introduced with Zip 3.0.
* Support for ODS5 extended filename syntax on new OpenVMS systems.
* Support symbolic links zipped up on VMS.
* On VMS (only 8.x or better), support symbolic link creation.
* On VMS, support option to create converted text files in
Stream_LF format.
* New -D option to suppress restoration of timestamps for extracted
directory entries (on those ports that support setting of directory
timestamps). By specifying "-DD", this new option also allows
to suppress timestamp restoration for ALL extracted files on
all UnZip ports which support restoration of timestamps. On
VMS, the default behaviour is now to skip restoration of
directory timestamps; here, "--D" restores ALL timestamps,
"-D" restores none.
* On OS/2, Win32, and Unix, the (previously optional) feature
UNIXBACKUP to allow saving backup copies of overwritten files on
extraction is now enabled by default.
For the UnZip 6.0 release, we want to give special credit to Myles
Bennet, who started the job of supporting ZIP64 extensions and
Large-File (> 2GiB) and provided a first (alpha-state) port.
|
|
internal version 1.8.11.
Changes are unknown, please refer PHP's changes.
|
|
|
|
|
|
pkgsrc changes:
- "drop" explicit core dependency
Upstream changes:
* important changes in version 1.58 17/02/2010
- Apply a patch from toddr@null.net that addreses RT #54714
Subject: $@ not cleaned up after eval
This section of code seems to be trying to use future functionality
not yet present in IO::Zlib (tell). I was chasing another bug and
getting very confused by this population of $@. Could I request you
cleanup $@ if you expect and/or don't care about failure from this eval?
|
|
Nick Coleman in PR 40658.
Bump PKGREVISION.
Set LICENSE.
|
|
|
|
|
|
|
|
- Infrastructure:
- Allow command line tools as fallback for missing compression
libraries. If compiled without gzip for example, gunzip will
be used automatically.
- Improved support for a number of platforms like high-resolution
timestamps and Extended Attributes on various Unix systems
- New convience interface for creating archives based on disk content,
complement of the archive_write_disk interface.
- Frontends:
- bsdcpio ready for public consumption
- hand-written date parser replaces the yacc code
- Filter system:
- Simplified read filter chains
- Option support for filters
- LZMA, XZ, uudecode handled
- Format support:
- Write support for mtree files based on file system or archive
content
- Basic read support for Joliet
- Write support for zip files
- Write support for shar archives, both text-only and binary-safe
|
|
|
|
|
|
|
|
bulk builds.
|
|
|
|
* important changes in version 1.56 03/02/2010
- Apply a patch from Mark Swayne that addresses RT #50471;
Archive::Tar generates file headers with space padded numbers for size,
mtime and checksum. This format is incompatible with some versions of
the busybox implementation of tar (I am using 1.13.2), which requires 0
padded numbers (despite comments in the source that say otherwise).
I've included a patch that adds a control flag that enables zero padded
numbers in the header. It passes all tests with ActiveState Perl 5.8.8
on WinXP.
|
|
|
|
Bump PKGREVISION.
|
|
0.9.2 [2010/01/31]
* Avoid passing uninitialized data to deflate().
* Fix memory leak when closing zip archives.
|
|
|
|
|
|
|
|
The changes from 2.1.5 are:
- Added pigz.spec to distribution for RPM systems [Brown]
- Avoid some compiler warnings
- Process symbolic links if piping to stdout [Hoffst?tte]
- Decompress if executable named "gunzip" [Hoffst?tte]
- Allow ".tgz" suffix [Chernookiy]
- Fix adler32 comparison on .zz files
|
|
|
|
0.9.1 [2010/01/24]
* Fix infinite loop on reading some broken files.
* Optimization in time conversion (don't call localtime()).
* Clear data descriptor flag in central directory, fixing Open Office files.
* Allow more than 64k entries.
|
|
OSI but it is derived from BSD so I added it to the acceptable set of
licenses.
|
|
|
|
|
|
|
|
changes:
-bugfixes
-translation updates
|
|
With gcc 3.3.3 (from NetBSD/i386 3.1) there are problems with
undefined references to LZMA_CRC32_TABLE and LZMA_CRC64_TABLE in crc32.S
and crc64_x86.S.
|
|
|
|
without gnu-ld
|
|
|
|
|
|
|
|
include the encryption support, but that has been addressed ages ago.
|
|
|
|
unzip: Unsupported ZIP compression method (imploded)
|
|
This switches to the gnome-2.28 release branch.
|
|
|
|
|
|
NetBSD 5.99.16 with unzip in base.
|
|
|
|
|
|
Fixes build failure on SUA 6.0.
|
|
|
|
|
|
Upstream changes:
* important changes in version 1.54 10/09/2009
- Apply a patch from Niko Tyni (ntyni@debian.org) that resolves RT #48879;
As seen in [rt.cpan.org #48879], although the recommended way of
retrieving the last error is to use an instance method ($tar->error),
the returned value is effectively global: an error in one Archive::Tar
instance changes the error string of another instance.
This change separates the error strings from each other while keeping
the (deprecated) global value of $Archive::Tar::error pointing to the
last error regardless of its instance.
We also support calling error() as a class method (Archive::Tar->error).
In this case it returns the global value, which matches the old behaviour.
|