Github messages for voidlinux
 help / color / mirror / Atom feed
From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] New package: tarlz-0.24
Date: Sat, 28 Oct 2023 07:55:55 +0200	[thread overview]
Message-ID: <20231028055555.NJPi8cPLs82aS6L0HxEqijqtfhPh75xiHu97h6uqOo8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38898@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]

There is an updated pull request by mtboehlke against master on the void-packages repository

https://github.com/mtboehlke/void-packages tarlz
https://github.com/void-linux/void-packages/pull/38898

[WIP] New package: tarlz-0.24
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

From the [tarlz homepage](https://www.nongnu.org/lzip/tarlz.html): "Tarlz creates tar archives using a simplified and safer variant of the POSIX pax format compressed in lzip format, keeping the alignment between tar members and lzip members. The resulting multimember tar.lz archive is fully backward compatible with standard tar tools like GNU tar, which treat it like any other tar.lz archive."

Keeping the alignment has advantages, which the webpage explains nicely.

Also from the homepage: "Tarlz does not understand other tar formats like gnu, oldgnu, star or v7. The command 'tarlz -tf archive.tar.lz > /dev/null' can be used to verify that the format of the archive is compatible with tarlz."

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/38898.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tarlz-38898.patch --]
[-- Type: text/x-diff, Size: 3282 bytes --]

From 641670ee3a61947478cc054d1fd45033faad1221 Mon Sep 17 00:00:00 2001
From: Mat Boehlke <mtboehlke@gmail.com>
Date: Wed, 24 Aug 2022 20:23:44 -0500
Subject: [PATCH] New package: tarlz-0.24

---
 srcpkgs/tarlz/patches/skip-mtime-checks.patch | 36 +++++++++++++++++++
 srcpkgs/tarlz/template                        | 20 +++++++++++
 2 files changed, 56 insertions(+)
 create mode 100644 srcpkgs/tarlz/patches/skip-mtime-checks.patch
 create mode 100644 srcpkgs/tarlz/template

diff --git a/srcpkgs/tarlz/patches/skip-mtime-checks.patch b/srcpkgs/tarlz/patches/skip-mtime-checks.patch
new file mode 100644
index 0000000000000..4969c7e4fa5d7
--- /dev/null
+++ b/srcpkgs/tarlz/patches/skip-mtime-checks.patch
@@ -0,0 +1,36 @@
+Skip testing problematic dates in the test suite.
+These dates result in 'out of limits' for the --mtime option on i686.
+
+A couple of these dates show up as 'mod time differs' on x86_64,
+I am presuming because they are even at the limits of 64-bit time_t.
+
+diff --git a/testsuite/check.sh b/testsuite/check.sh
+index 66c525b..a3ae6f1 100755
+--- a/testsuite/check.sh
++++ b/testsuite/check.sh
+@@ -727,22 +727,13 @@ cmp cfoo foo || test_failed $LINENO
+ rm -f out.tar foo bar baz || framework_failure
+ 
+ # test --create --mtime
+-dates='@-9223372036854775808 @-9223372036854775807
+-       -2147481748-12-31T23:59:59 -1970-01-01T00:00:00
+-       0000-01-01T00:00:00 0000-01-01T00:00:01 0000-01-02T00:00:00
+-       1697-10-17T11:03:27 1697-10-17T11:03:28 1697-10-17T11:03:29
+-       1833-11-24T17:31:43 1833-11-24T17:31:44 1833-11-24T17:31:45
+-       1901-12-13T20:45:51 1901-12-13T20:45:52 1901-12-13T20:45:53
++dates='1901-12-13T20:45:52 1901-12-13T20:45:53
+        1901-12-14T20:45:51
+        1969-12-31T23:59:58 1969-12-31T23:59:59
+        1970-01-01T00:00:00 1970-01-01T00:00:01 @0
+-       2038-01-18T03:14:07 2038-01-19T03:14:07 2038-01-19T03:14:08
+-       2106-02-07T06:28:15 2106-02-07T06:28:16
+-       2242-03-16T12:56:31 2242-03-16T12:56:32 @8589934591 @8589934592
+-       9999-12-31T23:59:58 9999-12-31T23:59:59
+-       2147483647-12-31T23:59:59 @9223372036854775807'
++       2038-01-18T03:14:07'
+ touch -d 2022-01-05T12:22:13 bar || framework_failure
+-for i in ${dates} @-8Ei '2017-10-01 09:00:00' '2017-10-1 9:0:0' \
++for i in ${dates} '2017-10-01 09:00:00' '2017-10-1 9:0:0' \
+          '2017-10-01 09:00' '2017-10-01 09' 2017-10-01 ./bar ; do
+   touch foo || framework_failure
+   "${TARLZ}" -cf out.tar --mtime="$i" foo || test_failed $LINENO "$i"
diff --git a/srcpkgs/tarlz/template b/srcpkgs/tarlz/template
new file mode 100644
index 0000000000000..3d5c8deafd1db
--- /dev/null
+++ b/srcpkgs/tarlz/template
@@ -0,0 +1,20 @@
+# Template file for 'tarlz'
+pkgname=tarlz
+version=0.24
+revision=1
+build_style=configure
+makedepends="lzlib-devel"
+short_desc="Archiver with multimember lzip compression"
+maintainer="Matt Boehlke <mtboehlke@gmail.com>"
+license="GPL-2.0-or-later"
+homepage="https://www.nongnu.org/lzip/tarlz.html"
+distfiles="${NONGNU_SITE}/lzip/tarlz/tarlz-${version}.tar.lz"
+checksum=49838effe95acb29d548b7ef2ddbb4b63face40536df0d9a80a62900c7170576
+
+do_configure() {
+	./configure --prefix=/usr \
+		CXX="${CXX}" \
+		CPPFLAGS="${CPPFLAGS}" \
+		CXXFLAGS="${CXXFLAGS}" \
+		LDFLAGS="${LDFLAGS}"
+}

  parent reply	other threads:[~2023-10-28  5:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  1:39 [PR PATCH] New package: tarlz-0.22 mtboehlke
2022-09-13 20:43 ` [PR PATCH] [Updated] " mtboehlke
2022-09-20 22:37 ` mtboehlke
2022-11-10 18:43 ` mtboehlke
2022-11-10 18:51 ` New package: tarlz-0.23 mtboehlke
2023-02-09  2:35 ` github-actions
2023-02-13  0:44 ` [PR PATCH] [Updated] " mtboehlke
2023-05-15  1:54 ` github-actions
2023-05-23 23:46 ` [PR PATCH] [Updated] " mtboehlke
2023-08-23  1:44 ` github-actions
2023-08-23 15:12 ` Chocimier
2023-08-23 20:05 ` [PR PATCH] [Updated] " mtboehlke
2023-08-26  0:42 ` mtboehlke
2023-08-26  0:45 ` mtboehlke
2023-10-27  0:53 ` [PR PATCH] [Updated] " mtboehlke
2023-10-28  3:31 ` [PR PATCH] [Updated] [WIP] New package: tarlz-0.24 mtboehlke
2023-10-28  3:48 ` mtboehlke
2023-10-28  5:55 ` mtboehlke [this message]
2023-10-28  6:05 ` mtboehlke
2023-10-28  6:05 ` mtboehlke
2024-01-07 17:19 ` [PR PATCH] [Updated] " mtboehlke
2024-04-07  1:46 ` New package: tarlz-0.25 github-actions
2024-04-07  4:10 ` [PR PATCH] [Updated] " mtboehlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231028055555.NJPi8cPLs82aS6L0HxEqijqtfhPh75xiHu97h6uqOo8@z \
    --to=mtboehlke@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).