From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] crun: update to 1.18.
Date: Wed, 30 Oct 2024 13:16:27 +0100 [thread overview]
Message-ID: <20241030121628.0D39D2EABD@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52799@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
There is an updated pull request by natrys against master on the void-packages repository
https://github.com/natrys/void-packages crun-1.18
https://github.com/void-linux/void-packages/pull/52799
crun: update to 1.18.
<!-- 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/52799.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crun-1.18-52799.patch --]
[-- Type: text/x-diff, Size: 1359 bytes --]
From fd489d8f3b4704cfbf10dc7f99e6f171562ec29e Mon Sep 17 00:00:00 2001
From: Imran Khan <imran@khan.ovh>
Date: Sun, 27 Oct 2024 18:21:49 +0600
Subject: [PATCH] crun: update to 1.18.1.
---
srcpkgs/crun/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/crun/template b/srcpkgs/crun/template
index b9de1c4760d6e9..3f051d345c7c03 100644
--- a/srcpkgs/crun/template
+++ b/srcpkgs/crun/template
@@ -1,6 +1,6 @@
# Template file for 'crun'
pkgname=crun
-version=1.17
+version=1.18.1
revision=1
build_style=gnu-configure
configure_args="--disable-systemd"
@@ -8,11 +8,11 @@ hostmakedepends="pkg-config python3 $(vopt_if man go-md2man)"
makedepends="libcap-devel libseccomp-devel yajl-devel"
short_desc="Lightweight OCI runtime written in C"
maintainer="Imran Khan <imran@khan.ovh>"
-license="GPL-2.0-or-later, LGPL-2.1-or-later"
+license="GPL-2.0-or-later AND LGPL-2.1-or-later"
homepage="https://github.com/containers/crun"
changelog="https://raw.githubusercontent.com/containers/crun/main/NEWS"
distfiles="https://github.com/containers/crun/releases/download/${version}/crun-${version}.tar.gz"
-checksum=b766609814c0b0a3c0d2d235af1b061bd71da1aa2e8bb181d66e89f1b9a4e874
+checksum=390cbbb022457aa705c802ad7ba9a5aace8562192d57365ce8bed0325770c6bc
# most of the tests don't work inside a container
make_check=no
next prev parent reply other threads:[~2024-10-30 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 12:24 [PR PATCH] " natrys
2024-10-30 12:16 ` natrys [this message]
2024-10-30 16:08 ` [PR PATCH] [Merged]: crun: update to 1.18.1 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=20241030121628.0D39D2EABD@inbox.vuxu.org \
--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).