From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: tarlz-0.24
Date: Sat, 28 Oct 2023 08:05:54 +0200 [thread overview]
Message-ID: <20231028060554.W_RQ353vWotPlTvR-1xgxMaFbI4Og_N69okaGR2R52I@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: 418 bytes --]
New comment by mtboehlke on void-packages repository
https://github.com/void-linux/void-packages/pull/38898#issuecomment-1783716022
Comment:
I added a patch to skip testing dates outside the limits on 32-bit arches. A couple of the dates result in 'mod time differs' on x86_64, I think because they are even at the limit for 64 bit time_t.
From what I can tell, Debian packaging currently skips the test target.
next prev parent reply other threads:[~2023-10-28 6:05 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
2023-10-28 6:05 ` mtboehlke
2023-10-28 6:05 ` mtboehlke [this message]
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=20231028060554.W_RQ353vWotPlTvR-1xgxMaFbI4Og_N69okaGR2R52I@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).