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.8.6.
Date: Fri, 04 Aug 2023 12:16:45 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45414@inbox.vuxu.org> (raw)

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

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

https://github.com/natrys/void-packages crun-1.8.6
https://github.com/void-linux/void-packages/pull/45414

crun: update to 1.8.6.
<!-- 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/45414.patch is attached

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

From f6e289c23fe14313caeb4f1e3a7b9de5d0bfb542 Mon Sep 17 00:00:00 2001
From: Imran Khan <imran@khan.ovh>
Date: Fri, 4 Aug 2023 16:00:20 +0600
Subject: [PATCH] crun: update to 1.8.6.

---
 srcpkgs/crun/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/crun/template b/srcpkgs/crun/template
index 15c643959056a..a382f6c64068e 100644
--- a/srcpkgs/crun/template
+++ b/srcpkgs/crun/template
@@ -1,17 +1,17 @@
 # Template file for 'crun'
 pkgname=crun
-version=1.8.5
+version=1.8.6
 revision=1
 build_style=gnu-configure
 configure_args="--disable-systemd"
 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 <imrankhan@teknik.io>"
+maintainer="Imran Khan <imran@khan.ovh>"
 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=5a786d7a0ece5068447e730f8a67c9cb18a95c883f5314e154865ad87c520106
+checksum=9137e9c5246ad7f5f9ec33bf76029ef7d78ea779e177998c32ae6dfed55a182c
 # most of the tests don't work inside a container
 make_check=ci-skip
 

             reply	other threads:[~2023-08-04 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 10:16 natrys [this message]
2023-08-04 19:15 ` [PR PATCH] [Merged]: " Duncaen

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-45414@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).