Github messages for voidlinux
 help / color / mirror / Atom feed
From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] crun: update to 1.5.
Date: Wed, 20 Jul 2022 17:49:40 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38153@inbox.vuxu.org> (raw)

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

There is a new pull request by natrys against master on the void-packages repository

https://github.com/natrys/void-packages crun-1.5
https://github.com/void-linux/void-packages/pull/38153

crun: update to 1.5.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/38153.patch is attached

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

From 459ee48aaac9039b3d0011482e8a8a724e55d183 Mon Sep 17 00:00:00 2001
From: Imran Khan <imrankhan@teknik.io>
Date: Wed, 20 Jul 2022 21:31:10 +0600
Subject: [PATCH] crun: update to 1.5.

---
 srcpkgs/crun/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/crun/template b/srcpkgs/crun/template
index a5d5429c5c4c..8358961ac4f8 100644
--- a/srcpkgs/crun/template
+++ b/srcpkgs/crun/template
@@ -1,6 +1,6 @@
 # Template file for 'crun'
 pkgname=crun
-version=1.4.5
+version=1.5
 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=923ea3557691990c972b3ed587a2f9703a03a0f83e0ea52d584ec668a59908e5
+checksum=acd24012daa951cf1674b20b2d5f87975d5d6c8e8c80bfe12e4cffa3495cae67
 
 if [ "$XBPS_TARGET_LIBC" = "musl" ]; then
 	makedepends+=" argp-standalone"

             reply	other threads:[~2022-07-20 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 15:49 natrys [this message]
2022-09-17 10:45 ` daniel-eys
2022-09-17 14:08 ` natrys
2022-09-20 15:23 ` leahneukirchen
2022-09-20 16:08 ` [PR PATCH] [Updated] " natrys
2022-09-20 19:02 ` [PR PATCH] [Updated] crun: update to 1.6 natrys
2022-09-21 22:18 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38153@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).