From 7e3baec34b3c8f606fb33cef56f1959192a8a899 Mon Sep 17 00:00:00 2001 From: taca Date: Tue, 22 Oct 2019 07:29:24 +0000 Subject: [PATCH] archivers/ruby-minitar: update to 0.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. --- archivers/ruby-minitar/Makefile | 6 ++++-- archivers/ruby-minitar/distinfo | 10 +++++----- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/archivers/ruby-minitar/Makefile b/archivers/ruby-minitar/Makefile index 6c50383133e8..473ebaf32147 100644 --- a/archivers/ruby-minitar/Makefile +++ b/archivers/ruby-minitar/Makefile @@ -1,6 +1,6 @@ -# $NetBSD: Makefile,v 1.1 2017/03/13 16:05:01 taca Exp $ +# $NetBSD: Makefile,v 1.2 2019/10/22 07:29:24 taca Exp $ -DISTNAME= minitar-0.6.1 +DISTNAME= minitar-0.9 CATEGORIES= archivers MAINTAINER= pkgsrc-users@NetBSD.org @@ -8,5 +8,7 @@ HOMEPAGE= https://github.com/halostatue/minitar/ COMMENT= Pure-Ruby library to deal with POSIX tar(1) archive files LICENSE= ruby-license OR 2-clause-bsd +USE_LANGUAGES= # none + .include "../../lang/ruby/gem.mk" .include "../../mk/bsd.pkg.mk" diff --git a/archivers/ruby-minitar/distinfo b/archivers/ruby-minitar/distinfo index 1274c23b71c5..eae43acd31c2 100644 --- a/archivers/ruby-minitar/distinfo +++ b/archivers/ruby-minitar/distinfo @@ -1,6 +1,6 @@ -$NetBSD: distinfo,v 1.1 2017/03/13 16:05:01 taca Exp $ +$NetBSD: distinfo,v 1.2 2019/10/22 07:29:24 taca Exp $ -SHA1 (minitar-0.6.1.gem) = 5e2c3938cb6bb3e0d76682e08eed774ccb2f5328 -RMD160 (minitar-0.6.1.gem) = 7b352a7cb83af2a2054296e6ff7f84692bc18366 -SHA512 (minitar-0.6.1.gem) = e8a4acd8c831ef587d9571376ae111454faba1d6d4db5c88f2087c84d3dbb5487cdcac8ad47c5f717e195262b95040a9ee72cdaeaad23715b8a1270baec6ec70 -Size (minitar-0.6.1.gem) = 29184 bytes +SHA1 (minitar-0.9.gem) = bc3fc95d74f4b5587e203cf1bec0616fcc96c345 +RMD160 (minitar-0.9.gem) = be4bdd8b23df97201d467f577e1852692dae8811 +SHA512 (minitar-0.9.gem) = de9d75a2839d7c1bbcfe23eec3d77d2e9fd233b4469d70a9d037f3bca3565102e6978286428e0bcde9748ca635915b73ecaa11356e1d45ccc8521fc663e4925e +Size (minitar-0.9.gem) = 32768 bytes