From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] crun: update to 1.7.
Date: Sat, 26 Nov 2022 21:17:42 +0100 [thread overview]
Message-ID: <20221126201742.2oaNxbCmbwbZSdJcrh2hdn4QsPruXd9txJ2H00z_1Ak@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40436@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
There is an updated pull request by natrys against master on the void-packages repository
https://github.com/natrys/void-packages crun-1.7
https://github.com/void-linux/void-packages/pull/40436
crun: update to 1.7.
<!-- 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**|**NO**
-->
<!-- 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/40436.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crun-1.7-40436.patch --]
[-- Type: text/x-diff, Size: 1081 bytes --]
From c6cb9ae89f5737487ed3ea7b83e01e8906b3115f Mon Sep 17 00:00:00 2001
From: Imran Khan <contact@imrankhan.live>
Date: Thu, 10 Nov 2022 17:16:34 +0600
Subject: [PATCH] crun: update to 1.7.1.
---
srcpkgs/crun/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/crun/template b/srcpkgs/crun/template
index 6b9e98a51d60..be75469c58ea 100644
--- a/srcpkgs/crun/template
+++ b/srcpkgs/crun/template
@@ -1,6 +1,6 @@
# Template file for 'crun'
pkgname=crun
-version=1.6
+version=1.7.1
revision=1
build_style=gnu-configure
configure_args="--disable-systemd"
@@ -11,7 +11,7 @@ maintainer="Imran Khan <imrankhan@teknik.io>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://github.com/containers/crun"
distfiles="https://github.com/containers/crun/releases/download/${version}/crun-${version}.tar.gz"
-checksum=d6b100d22b718a8d490c2725935d202843becb24caf830b88119cfaff630c0ce
+checksum=3a6e80fd17f0c167c8fbc69d23e9331754bf65642a16727c830dd220f3f9fc30
if [ "$XBPS_TARGET_LIBC" = "musl" ]; then
makedepends+=" argp-standalone"
next prev parent reply other threads:[~2022-11-26 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 11:20 [PR PATCH] " natrys
2022-11-26 20:17 ` natrys [this message]
2022-11-30 23:30 ` [PR PATCH] [Updated] crun: update to 1.7.1 natrys
2023-01-02 20:49 ` [PR PATCH] [Merged]: crun: update to 1.7.2 leahneukirchen
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=20221126201742.2oaNxbCmbwbZSdJcrh2hdn4QsPruXd9txJ2H00z_1Ak@z \
--to=natrys@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).