From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] apparmor: update to 3.1.4.
Date: Sat, 27 May 2023 14:59:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44112@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
There is a new pull request by mhmdanas against master on the void-packages repository
https://github.com/mhmdanas/void-packages apparmor-3.1.4
https://github.com/void-linux/void-packages/pull/44112
apparmor: update to 3.1.4.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
@paper42
<!--
#### 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/44112.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-apparmor-3.1.4-44112.patch --]
[-- Type: text/x-diff, Size: 1116 bytes --]
From 9c60d0c2f87c0d0cf48162b2fdb5fbacb164ea6e Mon Sep 17 00:00:00 2001
From: triallax <triallax@tutanota.com>
Date: Sat, 27 May 2023 12:29:50 +0100
Subject: [PATCH] apparmor: update to 3.1.4.
---
srcpkgs/apparmor/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/apparmor/template b/srcpkgs/apparmor/template
index 50e2992aafbb..b81fab0d0f02 100644
--- a/srcpkgs/apparmor/template
+++ b/srcpkgs/apparmor/template
@@ -1,6 +1,6 @@
# Template file for 'apparmor'
pkgname=apparmor
-version=3.1.3
+version=3.1.4
revision=1
build_wrksrc=libraries/libapparmor
build_style=gnu-configure
@@ -17,7 +17,7 @@ license="GPL-2.0-only"
homepage="https://gitlab.com/apparmor/apparmor"
changelog="https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_${version}"
distfiles="https://launchpad.net/apparmor/${version%.*}/${version}/+download/apparmor-${version}.tar.gz"
-checksum=b8ffac45d0b283afe574ddd5542142ba1a62c354df110cff862b99201f29c843
+checksum=6bee0c3941836dae2c635fe82f09b666123fcac16563aa0fedf4a63c22b91f40
replaces="apparmor-vim>=0"
if [ -z "$CROSS_BUILD" ]; then
next reply other threads:[~2023-05-27 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:59 mhmdanas [this message]
2023-05-29 20:01 ` [PR PATCH] [Merged]: " abenson
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-44112@inbox.vuxu.org \
--to=mhmdanas@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).