Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: lziprecover-1.23
Date: Sat, 24 Jun 2023 15:37:53 +0200	[thread overview]
Message-ID: <20230624133753.veKBzJYQsFizTnBSgl43vvOq0cKqwH5Bk-Tl39ERzpQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39999@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

New package: lziprecover-1.23
https://github.com/void-linux/void-packages/pull/39999

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

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

[Lziprecover](https://lzip.nongnu.org/lziprecover.html) is a data recovery tool and decompressor for files in the lzip format. From the website: "Lziprecover is not a replacement for regular backups, but a last line of defense for the case where the backups are also damaged."

Lziprecover can remove the damaged members from multimember files created using tarlz (see #38898), a format which is designed to minimize the amount of data lost in case of corruption.

<!-- 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
-->


      parent reply	other threads:[~2023-06-24 13:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 23:24 [PR PATCH] " mtboehlke
2023-01-16  1:59 ` github-actions
2023-01-17 20:24 ` [PR PATCH] [Updated] " mtboehlke
2023-01-17 20:28 ` mtboehlke
2023-01-17 20:52 ` mtboehlke
2023-04-19  1:54 ` github-actions
2023-04-20 19:04 ` [PR PATCH] [Updated] " mtboehlke
2023-06-24 13:37 ` Duncaen [this message]

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=20230624133753.veKBzJYQsFizTnBSgl43vvOq0cKqwH5Bk-Tl39ERzpQ@z \
    --to=duncaen@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).