summaryrefslogtreecommitdiff
path: root/archivers
AgeCommit message (Collapse)AuthorFilesLines
2019-12-17py-zstandard: Use bundled zstd because not adapted to zstd-1.4.4leot1-5/+10
At least ZSTD_FRAMEHEADERSIZE_MIN and ZSTD_FRAMEHEADERSIZE_PREFIX macros in 1.4.4 needs a `format' argument but py-zstandard is not adapted to 1.4.4 yet. PKGREVISION++
2019-12-17archivers: Add py-brotlileot1-1/+2
2019-12-17py-brotli: Import py-brotli-1.0.7 as archivers/py-brotlileot4-0/+40
Brotli is a generic-purpose lossless compression algorithm that compresses data using a combination of a modern variant of the LZ77 algorithm, Huffman coding and 2nd order context modeling, with a compression ratio comparable to the best currently available general-purpose compression methods. It is similar in speed with deflate but offers more dense compression. This package contains Python bindings for Brotli.
2019-12-13Revbump all Go packages after Go 1.12.14 update.bsiegert1-2/+2
2019-12-11unrar: updated to 5.8.5adam2-7/+7
5.8.5 Unknown changes
2019-12-11py-libarchive-c: updated to 2.9adam2-8/+8
2.9: Changes to the library: optimized the ArchiveEntry class added support for the zstd format fixed the top-level __all__ list (7b97d8b) updated the code to support Python 3.8 improved the add_file_from_memory method lowered the level of log messages from warning to info Tests: dropped testing with Python 3.4, added 3.7 and 3.8 fixed unicode handling in entry tests
2019-12-06- Update to 0.86wen2-10/+7
Upstream changes: 0.86 Thu Dec 5 20:53:07 GMT 2019 * Fix RT#131072 which was due to tar.exe and CRLF line endings 0.84 Wed Dec 4 21:20:04 GMT 2019 * Fix RT#119084 - won't compile on MSWin32 with taint 0.82 Fri Nov 22 19:09:35 GMT 2019 * Correctly compare version string for Archive::Tar (#7) * Remove duplicate entry from the MANIFEST file. (#6) * Treat minix the same as NetBSD
2019-11-28unrar: updated to 5.8.4adam2-7/+7
5.8.4: Unknown changes
2019-11-22innoextract: DESCR no longer accuratenia1-2/+1
2019-11-21innoextract: Update to 1.8nia2-10/+9
innoextract 1.8 (2019-09-15) - Added support for Inno Setup 6.0.0 installers - Added support for pre-release Inno Setup 5.6.2 installers used by GOG - Added support for two modified Inno Setup 5.5.7 variants - Added support for Inno Setup 1.3.0 to 1.3.23 - Added support for My Inno Setup Extensions installers older than 3.0.6.1 - Added support for modified Inno Setup variants using an alternative setup loader magic - Added support for using boost_{zlib,bzip2} when statically linking Boost - Added support for automatically reading external setup.0 files - Encoding for non-Unicode installers is now determined from the languages supported by the installer, overridable using the --codepage option - Implemented parsing of GOG Galaxy architecture constraints - The architecture-specific suffixes @32bit and @64bit are now used to disambiguate colliding files - Fixed extracting files from slices larger than 2 GiB with 32-bit builds - Fixed output path for files with absolute paths (canonicalization now strips all unsafe characters) - Fixed output directory being created even when not extracting files - Fixed a hang when using the --language option - Improved checksum verification for files reconstructed from GOG Galaxy file parts - Changed header parsing to select the first version without warnings and failing that the first without errors - Changed filesystem and output encoding to WTF-8 (extended UTF-8) to represent broken UTF-16 data
2019-11-17ark: update to 19.08.3 qt5/kf5 versionmarkd3-57/+155
2019-11-15Fix the stutter.hauke1-2/+2
2019-11-15*: use py-more-itertools via versioned_dependencies.mkwiz1-2/+4
2019-11-11karchive: update to 5.64.0markd1-5/+5
5.62.0 Fix creating archives on Android content: URLs 5.64.0 Fix memory leak in KXzFilter::init Fix null pointer reference when extraction fails decodeBCJ2: Fix assert with broken files KXzFilter::Private: remove unused props K7Zip: Fix memory use in readAndDecodePackedStreams
2019-11-09unshield: Update to 1.4.3nia2-10/+7
Changes: "Make file name encoding work"
2019-11-08archivers/star: Update to 1.6.1nb3micha2-8/+8
Based on schilytools release from 2019-10-25. Changelog ========= - libstreamer: Added new keywords "fsdevmajor" and "fsdevminor" as there are too many incompatible st_dev binary formats. These keywords are not yet created, but they are understood. This permits to switch to the new format (fade out "dev") later. - star: Added new keywords "SCHILY.fsdevmajor" and "SCHILY.fsdevminor" as there are too many incompatible st_dev binary formats. These keywords are not yet created, but they are understood. This permits to switch to the new format (fade out "SCHILY.dev") later. - star: The amount of shared mamory used by default has been reduced to 1 MB on Ultrix. These are old small machines, that do not support 8 MB.
2019-11-06zstd: updated to 1.4.4adam2-7/+7
Zstandard v1.4.4 This release includes some major performance improvements and new CLI features, which make it a recommended upgrade. perf: Improved decompression speed, by > 10% perf: Better compression speed when re-using a context perf: Fix compression ratio when compressing large files with small dictionary perf: zstd reference encoder can generate RLE blocks perf: minor generic speed optimization api: new ability to extract sequences from the parser for analysis api: fixed decoding of magic-less frames api: fixed ZSTD_initCStream_advanced() performance with fast modes, reported by @QrczakMK cli: Named pipes support cli: short tar's extension support cli: command --output-dir-flat=DIE , generates target files into requested directory cli: commands --stream-size=# and --size-hint=# cli: command --exclude-compressed cli: faster -t test mode cli: improved some error messages cli: fix rare deadlock condition within dictionary builder build: single-file decoder with emscripten compilation script build: fixed zlibWrapper compilation on Visual Studio, reported by @bluenlive build: fixed deprecation warning for certain gcc version, reported by @jasonma163 build: fix compilation on old gcc versions build: improved installation directories for cmake script, by Dmitri Shubin pack: modified pkgconfig, for better integration into openwrt, requested by @neheb misc: Improved documentation : ZSTD_CLEVEL, DYNAMIC_BMI2, ZSTD_CDict, function deprecation, zstd format misc: fixed educational decoder : accept larger literals section, and removed UNALIGNED() macro
2019-11-04(archivers/p5-Archive-Tar-Wrapper) Updated from 0.33 to 0.37mef2-9/+8
(from: HomePage) 0.37 (2019/08/24): Fixed issue 14 - https://github.com/glasswalk3r/archive-tar-wrapper-perl/issues/14 0.36 (2019/04/11): Bug fixes since tests on Windows were failing after latests changes. Refactored code due unexpected way bsdtar on Windows and tar on OpenBSD behave. Refactored the tests due the bugs found. Small fixes on Pod, specially the section for MS Windows users. Added the missing tests to the MANIFEST. 0.35 (2019/04/05): Added _rem_dots method, a improved way to remove '.' and '..' from readdir(), supposed to be faster than previous implementation with sort() and shift(). Added two more tests to increase testing coverage. Fixed a small bug regarding Pod, that now covers 100% of the code. Small fixes to documentation. 0.34 (2019/03/22): Increased test coverage. Refactored code to make it easier for testing. Disabled performance-small.t for now. Refactored bzip2 tests. Adding META.yml "provides" from Makefile.PL Covered methods that didn't have Pod. Refactored all Pod following best practices. Refactored a single method to be "private". Slightly changed new() to enable unit testing for OS specific configurations.
2019-11-03archivers: add py-zipstreammarkd1-1/+2
2019-11-03py-zipstream: Add version 1.1.4markd4-0/+48
zipstream.py is a zip archive generator based on python 3.3's zipfile.py. It was created to generate a zip file generator for streaming (ie web apps). This is beneficial for when you want to provide a downloadable archive of a large collection of regular files, which would be infeasible to generate the archive prior to downloading or of a very large file that you do not want to store entirely on disk or on memory. The archive is generated as an iterator of strings, which, when joined, form the zip archive.
2019-11-02archivers: align variable assignmentsrillig27-109/+109
pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-10-25unrar: updated to 5.8.3adam2-7/+7
5.8.3: Unknown changes
2019-10-24archivers/star: Update to 1.6.1nb2micha2-8/+8
Based on Release 2019-10-07. Changelog ========= - configure: Some shells report a syntax error with "< file (cmd)" and need the redirection statement to be *after* the command. Our changes to support the V7 shell by adding round braces caused ash variants like "dash" to fail. Thanks to Harald van Dijk for reporting - cont/cc-config.sh: canged some :>some-file statements into (:)>some-file. they have meen missed when introducing work arounds for the V7 Shell on Ultrix that does not support I/O redirection for builtin commands. Thanks to Robert Clausecker for reporting - libschily/resolvepath.c: resolving a symlink that points to another symlink that points to itself, caused a coredump as a result from an endless recursion. We now detect this situation and abort the check before the endless recursion causes a stack overflow. A symlink that directly loops is immediately stopped. A longer symlink loop chain over more than one symlink can only be detected by the recursion nesting level and is aborted after a nesting level of 1024 has been reached. This works under the assumption that the minimum stack size is more than 1024 * PATH_MAX and that there is no useful directory path with more than 1024 symlinks in the path. ----> This problem affected star and SCCS. Thanks to Philipp Wellner for reporting - star: Added a hint to the man page that helps to find pkglist= as a. similar option to list= - star: The new method to avoid extracting symlinks that point outside the star working directory that has been introduced in October 2018 could cause a core dump if a symlink is checked that points to another aready existing symlink that points to itself. This was caused by a problem in libschily/resolvepath.c, see above. Thanks to Philipp Wellner for reporting - star: The option -no-secure-links now may be configured as a global default via the tag STAR_SECURE_LINKS= in the file /etc/default/star and as a private default via an environment of the same name. If the value for this tag is 'n' or 'N', -no-secure-links is made the default, any other value sets the option -secure-links as the default. This may be useful for sysadmins that frequently use star to copy installation specific files, but it is risky in case that alien TAR archives are imported. The good news is that this permits users to switch to the old star behavior where no checks for risky links existed. Thanks to Dennis Clarke for reporting - star: A new enviroment STAR_NOHINT has been introduced to supress hint messages that are otherwise seen in case STAR_SECURE_LINKS or STAR_FSYNC is in the environment or in /etc/default/star - star: New version date
2019-10-23archivers/Makefile: add and enable ruby-ffi-libarchivetaca1-1/+2
2019-10-23archivers/ruby-ffi-libarchive: add version 0.4.10taca4-0/+35
Add ruby-ffi-libarchive package version 0.4.10. ffi-libarchive A Ruby FFI binding to libarchive.
2019-10-22archivers/ruby-archive-tar-minitar: update to 0.8taca2-8/+12
Update ruby-archive-tar-minitar to 0.8. Now this package is left for compatibility and it using ruby-minitar and ruby-minitar-cli.
2019-10-22archivers/ruby-minitar-cli: update to 0.8taca2-9/+10
Update ruby-minitar-cli to 0.8. ## 0.8 / 2019-01-05 * Updated for compatibility with minitar 0.8 ## 0.7 / 2018-02-19 * Updated for compatibility with minitar 0.7
2019-10-22archivers/ruby-minitar: update to 0.9taca2-7/+9
Update archivers/ruby-minitar to 0.9. ## 0.9 / 2019-09-04 * jtappa added the ability to skip fsync with a new option to Minitar.unpack and Minitar::Input#extract_entry. Provide `:fsync => false` as the last parameter to enable. Merged from a modified version of PR [#37][]. ## 0.8 / 2019-01-05 * inkstak resolved an issue introduced in the fix for [#31][] by allowing spaces to be considered valid characters in strict octal handling. Octal conversion ignores leading spaces. Merged from a slightly modified version of PR [#35][]. * dearblue contributed PR [#32][] providing an explicit call to #bytesize for strings that include multibyte characters. The PR has been modified to be compatible with older versions of Ruby and extend tests. * Akinori MUSHA (knu) contributed PR [#36][] that treats certain badly encoded regular files (with names ending in `/`) as if they were directories on decode. ## 0.7 / 2018-02-19 * Fixed issue [#28][] with a modified version of PR [#29][] covering the security policy and position for Minitar. Thanks so much to ooooooo\_q for the report and an initial patch. Additional information was added as [#30][]. * dearblue contributed PR [#33][] providing a fix for Minitar::Reader when the IO-like object does not have a `#pos` method. * Kevin McDermott contributed PR [#34][] so that an InvalidTarStream is raised if the tar header is not valid, preventing incorrect streaming of files from a non-tarfile. This is a minor breaking change, so the version has been bumped accordingly. * Kazuyoshi Kato contributed PR [#26][] providing support for the GNU tar long filename extension. * Addressed a potential DOS with negative size fields in tar headers ([#31][]). This has been handled in two ways: the size field in a tar header is interpreted as a strict octal value and the Minitar reader will raise an InvalidTarStream if the size ends up being negative anyway.
2019-10-18Revbump all Go packages after lang/go112 updatebsiegert1-2/+2
2019-10-04advancecomp: Avoid compiler warnings due to redefining bswap* on NetBSD.nia2-2/+26
2019-10-04advancecomp: Update to 2.1nia3-26/+12
ADVANCECOMP VERSION 2.1 2018/02 =============================== * Support ZIPs with data descriptor signature. * Fixed a crash condition with invalid ZIP data. ADVANCECOMP VERSION 2.0 2017/06 =============================== * Added support for reading MNG files with depth of 1, 2, and 4 bits. * Added 64 bits binary for Windows. * Updated to libdeflate 29-May-2017. From https://github.com/ebiggers/libdeflate at commit 1726e9e87fb6f98682dfdea2356d5ee58881fe7b.
2019-10-04star: Update to 1.6.1nb1micha5-31/+40
Switch to latest distfile. Update PLIST. Replaced MESSAGE with share/doc/star/INSTALL.pkgsrc. Changelog ========= Release 2019-03-29: - libschily: the lutimens() emulation no longer returns ENOSYS in case that the lstat() call fails, since this error code may e.g. be ENAMETOOLONG and used as an important indicator for long path name handling. This bug caused incorrect behavior when star extracted long pathnames on a platform without utimensat(). - star: The code restructuring to openat() from Summer 2018 did not only cause a noticeable speed up even when not using -find, it at the same time resulted in a wrong error message when a file type was seen that is not archivable (e.g. a socket while using the USTAR format). The correct message was something like "Unsupported filetype", while the bug caused a "file not found " message. This has been fixed by adding a new parameter "fd" to the function stat_to_info(). - star: header.c::get_xhtype() we did forgot to initialize: finfo.f_devminorbits and finfo.f_xflags This is now done. - star: The USTAR format now is able to create base-256 values in the field "t_devmajor". "t_devminor" did already support base-256. - star: The GNU tar format now is able to create base-256 values in the fields "t_devmajor" and "t_devminor". - star: The man page star.4 now mentions which fileds may have base-256 numbers. - star: The man page star.4 now longer contains the doubled "field field" in the explanation of the added UID/GID number for ACLs. - star: The man page star.4 now has a better description for the additional numeric fields in the ACL entries to prevent GNU tar from continuing with it's incompatible ACL implementation. - star: New ACL reference archives for the ultra compact format, that has been defined together with the libachive people, have been added to the directory testscripts/: acl-nfsv4-compact-test.tar.gz acl-nfsv4-compact-test2.tar.gz acl-nfsv4-compact-test3.tar.gz acl-nfsv4-compact-test4.tar.gz acl-nfsv4-compact-test5.tar.gz - star: Linux now uses the new <linux/fs.h> instead of <ext2/ext2_fs.h> to retrieve file flags. Thanks to a hint from Martin Matuska <martin@matuska.org> from the libarchive team. - star: Support for the following new BSD Flags: compressed hidden offline rdonly reparse sparse system has been added. Thanks to a hint from Martin Matuska <martin@matuska.org> from the libarchive team. - star: Support for the following new Linux flags: dirsync nocow notail projinherit topdir has been added. Thanks to a hint from Martin Matuska <martin@matuska.org> from the libarchive team. - star: Support for reading non-comliant libarchive tarballs that use. "securedeletion" or "journal" instead of the documented text has been added. This was used by libarchive until March 20, when libarchive has been fixed. We introduce the above names for compatibility with old TARs created by libarchive. - star: When an "old star" archive is read and this archive is from a system like FreeBSD with non-continous minor bits, star no longer warns unless there is a device file in the archive. - star: unit tests: the scripts now contain LC_ALL=C export LC_ALL instead of just LC_ALL=C to make the environment exported. - star/libstrar: The case where iconv() returns -1 and sets errno to E2BIG is now handled correctly. - star: The testscripts/ directory now contains the tar test archives from the portability tests from Michal Gorny. Check http://cdrtools.sourceforge.net/private/portability-of-tar-features.html for an updated (to match star-1.6) variant of the results from the portability tests from Michal Gorny. - star: older versions of star did not print the messages: "WARNING: Archive is 'xxx' compressed, trying to use the -xxx option.\n" in case that the option -print-artype was in use. Later versions that added support for more than "gzip" and "bzip2" forgot to add the same exception for the new compression methods. We now ommit this message for all compression types. - star: Support for the "lzma" compression has been added. - star: Support for the "freeze2" compression has been added. - star: The compression method name list did not include the text "zstd". We added the missing text. - star: The hint messages that are printed when a compressed input archive is not seekable did forgot to mention "lzip" and "zstd". We added the forgotten messages. - star: New unit tests check whether star is able to auto-detect and auto decompress various compression formats. - star: The unit tests now include the portability tests from Michal Gorny - A new option cli=name (must be argv[1]) allows to select all supported command line interfaces (star, suntar, gnutar, pax, cpio) when called as star. This is needed to be able to test all command line interfaces from out unit tests since star is not installed in this case and a selection from argv[0] would not work. - star: The version date is now "2019/03/20" Release 2019-04-29: - libfind/star: the verbose listing code has ben restructured to have the file permissions in the same string as the file type. This is needed to implement the POSIX pax listformat interpreter format %M in future. - libfind/star: the verbose listing no longer prints "l" for mandatory record locking for non-directory type file, but rather only for plain files. - star: The "gnutar" emulation now prints the --help output to stdout as GNU tar does. - star: The gnutar.1 man page now mentions that the GNU tar options -g / -G did never work and it thus makes no sense to implement them. - star: very outdated code in list.c has been removed. - star: Added new unit tests for incremental backups and restores. This in special include tests that always fail with GNU tar as GNU tar is not usable and never was usable for incremental restores in case that the differences are more than trivial. - star: new version date 2019-04-01 Release 2019-06-13: - star: fixed a bug in the FIFO code that mainly happened on Linux (with a 1000x higher probability than it happens on Solaris). The bug was. caused, as a check for a flag has been done twice instead of only once where it could change it's value between both locations. As a. result, star reported "star: Implementation botch: with FIFO_MEOF" as the tar side of the FIFO did sometimes not wait for the FIFO_IWAIT state when called as "star -multivolume -tv f=... f=... ... For this reason, star incorrectly got a wakeup at the wrong location. The bug appeared in case that star -x/-t -multivol f=.. f=.. .... has been called with very small tar archives. Thanks to Heiko Eissfeldt for reporting. - star: The FIFO code renamed the "flag" member of the "m_head" structure to "gflag" for better readability. - star: The debugging code in the FIFO has been enhanced to print the names of the flag bits in addition to the hex values. - star: A deadlock situation that happens once every 500000 tries on Linux with multi-volume archives has been fixed. The problem was caused by a complex condition where the get side of the FIFO needs to check the EOF FIFO flag and the amount of data available in the FIFO and then decide whether to wait for a wakeup or not. Since the EOF flag needs to be checked first, a context switch in the get side of the FIFO could allow the put side to set the EOF flag before the get side did check the fill ratio of the FIFO. This caused both the get side and the put side to wait for a wakeup. The new code introduced a new variable mp->mayoblock that is set by the get side before checking for EOF. This new flags allows the put side to know that the get side is just in a critical situation and lets the put side wait until mp->mayoblock is no longer set, which signals a stable state in the get side. This permits to avoid the deadlock. - star: Note that the FIFO has been initially written as a lock free design in the late 1980's. This is to allow high portability to even older UNIX versions. The star FIFO works on all UNIX variants that support pipes and shared memory, which is e.g. the case for SunOS-4.0 from 1988. At the time the FIFO has been designed, the target OS did not support multi-CPU systems and problems in the FIFO first appeared with massively faster multi-CPU systems around y2000. The recently detected problems all have been triggered by a different context switch behavior on Linux, even though they could have appeared on any OS in case that many million tries are attempted. - star: bumped version to 1.6.1 Release 2019-07-15: - star: the compress unit test no longer fails on Cygwin because the gzip binary is compiled incorrectly and does not support LZW. The related test is now skipped. Thanks to Heiko Eissfeldt for reporting - star: some new unit tests failed if the schilytools source tree has been installed in a directory with spaces in it's name. Thanks to Heiko Eissfeldt for reporting - star: The unit tests for incremental backups include archives that include userid/groupid and username/groupname that may not be restorable on a different computer. We now ignore these ID meta. data when comparing the results. Thanks to Heiko Eissfeldt for reporting - star: When comparing nanoseconds in time stamps, star now has a mode that treats time stamps as equal in case that tv_nsec % 100 == 0 and the rest of the nano seconds is equal. This is needd on Cygwin since NTFS counts in 1/10 microseconds since Januar 1 1601. This applies to both star -diff and the "newer" check while extracting files. Thanks to Heiko Eissfeldt for reporting - star: a new option diffopts=dnlink has been implemented to support filesystems that do not follow the historic UNIX model for hard links on directories. Since Cygwin usually has a linkcount of 1 on directories, you need to use "star -diff diffopts=!dnlink ..." if you like to diff the meta data from a historical UNIX filesystem. Thanks to Heiko Eissfeldt for reporting - star: The incremental backup/restore tests now use. "star -diff diffopts=!dnlink ..." to make them work on Cygwin. Thanks to Heiko Eissfeldt for reporting - star: star -c -H exustar -acl -xattr-linux . did cause file not found messages from the attempt to archive the Linux xattrs. This was caused by a change from July 2018 when trying to optimize directory access in (non-find) create mode. The call to read the Linux xattrs has now been moved to the location where in former times the ACL code has already been moved. The move is needed because there is no ACL/XATTR related function that is similar to openat(). - star: A similar problem with get_xattr() did exist with star -diff - star: star -diff did not compare ACLs since getinfo() no longer includes a call to get_acl(). We now call get_xattr() and get_acl() in diff.c - star: The Solaris ACL interface now implelements lacl() / lacl_get() / lacl_set() to support very long pathnames with ACLs. - star: The Linux ACL interface now implelements lacl_get_file() / lacl_set_file() to support very long pathnames with ACLs on platforms that implement the withdrawn POSIX ACL draft. - star: The Linux xattr interface now implelements. llgetxattr() / llsetxattr() / lllistxattr() to support very long pathnames with Linux xattrs. - star: New version date Release 2019-07-22: - star: "pax -pe" no longer sets the variable "doxattr" as this caused an error message: "NFSv4 extended attribute files are not yet supported.\n" that caused the OpenSolaris-ON "nightly" compilation to abort as a result of that error and exit code != 0. Release 2019-08-13: - libschily: Various functions and *at() emulation functions call stat() even though the caller does not know about that call. This could cause a missbehavior in case that a file returns EOVERFLOW with a normal stat(). We now compile these functions in unconditional large file mode to overcome that problem. The affected files are: diropen.c lutimens.c findinpath.c linkat.c mkdirs.c searchinpath.c resolvepath.c lchmod.c renameat.c. Note that this problem affected star(1) on platforms that do not fully implement all *at() interfaces, since star started to support really long path names in July 2018. - star: Star did not compile on platforms without ACLs anymore since we did rearrange the code with schilytools 2019-07-15. We now have the needed #undef USE_ACL in diff.c as well. Thanks to Dennis Clarke for reporting. - star: Avoid a warning when a star -dump archive is unpacked on FreeBSD or Linux with non-contiguous minor bits. The warning is not needed since we only use SCHILY.dev in order to detect mount points but not to compute the major/minor parts. Release 2019-08-13: - star: star -xdev -find typically works to exclude mounted files. It still does not always do what is expected, e.g. in case that /proc is in the tree of scanned files, where files deep in the new mounted tree suddenly have the same FS ID as other filesystems, e.g. the file /proc/<pid>/path/a.out. In such cases, "star -find -xdev" is still recommended where the mounted file exclusion is done inside libfind instead of being done inside star. Before, files on other filesystems have not been honored at all when using "star -xdev -find ...".
2019-10-02unshield: Use CMAKE_INSTALL_MANDIR.nia4-14/+29
While here, appease pkglint. Bump PKGREVISION
2019-09-26Revbump all Go packages after 1.12.10 update.bsiegert1-2/+2
ok wiz@ for PMC
2019-09-22Fix PLISTprlw11-1/+2
2019-09-22Merge 64333cef68d7bcc67bef6ecf177fbeaa549b9139 from upstream to unbreakjoerg1-19/+35
build without zlib.
2019-09-22Update for libarchive-3.4.0:joerg274-8363/+14605
- improvements for Android APK and JAR archives - better support for non-recursive list and extract - tar --exclude-vcs support - fixes for file attributes and flags handling - zipx support - rar 5.0 reader
2019-09-22Import libarchive 3.4.0joerg81-33/+14436
2019-09-22Properly merge libarchive-3.3.3joerg3-5/+5
2019-09-22Import libarchive-3.3.3 as should have done originally.joerg1-6/+6
2019-09-21lhasa: Create buildlink3.mknia1-0/+12
2019-09-19py-zstandard: updated to 0.12.0adam6-179/+11
0.12.0: Backwards Compatibility Notes * Support for Python 3.4 has been dropped since Python 3.4 is no longer a supported Python version upstream. (But it will likely continue to work until Python 2.7 support is dropped and we port to Python 3.5+ APIs.) Bug Fixes * Fix ``ZstdDecompressor.__init__`` on 64-bit big-endian systems. * Fix memory leak in ``ZstdDecompressionReader.seek()``. Changes * CI transitioned to Azure Pipelines (from AppVeyor and Travis CI). * Switched to ``pytest`` for running tests (from ``nose``). * Bundled zstandard library upgraded from 1.3.8 to 1.4.3.
2019-09-16py-rarfile: updated to 3.1adam2-8/+8
Version 3.1: This will be last version with support for Python 2.x New feature: Accept pathlib objects as filenames. Accept bytes filenames in Python 3 Fixes: Use bug-compatible SHA1 for longer passwords (> 28 chars) in RAR3 encrypted headers. Return true/false from _check_unrar_tool Include all test files in archive Include volume number in NeedFirstVolume exception if available (rar5). Cleanups: Convert tests to pytest.
2019-09-16py-lz4: updated to 2.2.1adam2-7/+7
v2.2.1: Update the bundled LZ4 library to version 1.9.1 This release updates the bundled LZ4 library to version 1.9.1. The 2.2.x releases will be the final release that support Python 2.7. In the near future we'll begin work on the 3.0.x release which will only support Python >= 3.5, and will require LZ4 > 1.9.0. v2.2.0: Add more detail to the install section of docs
2019-09-14Remove archivers/file-roller - successor fork archivers/engrampania9-417/+1
2019-09-14xfce4-thunar-archive: Depend on xarchiver instead of GNOME 2 file-roller.nia1-4/+3
Makes more sense since we still consider xarchiver part of Xfce...
2019-09-13engrampa: update to 1.22.2gutteridge3-9/+9
Change log: engrampa 1.22.2 * Translations update * java-utils: Remove blank spaces before reading package name * glib-utils: Remove unused function - g_ptr_array_copy * caja extension: fix icon name for compress menu item * fr-command-unarchiver: ask password if required
2019-09-05unrar: updated to 5.8.1adam2-7/+7
5.8.1: Unknown changes
2019-09-02Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for ↵adam1-2/+2
future Python 3.8
2019-09-02py-zipp: updated to 0.6.0adam2-7/+8
v0.6.0 When adding implicit dirs, ensure that ancestral directories are added and that duplicates are excluded. The library now relies on more_itertools