Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libseccomp: update to 2.5.4
Date: Tue, 26 Apr 2022 09:52:58 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36871@inbox.vuxu.org> (raw)

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

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

https://github.com/oreo639/void-packages libseccomp
https://github.com/void-linux/void-packages/pull/36871

libseccomp: update to 2.5.4
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

This fixes:
```
/usr/libexec/tracker-extract-3 -f file.mp3

(tracker-extract-3:9677): Tracker-CRITICAL **: 00:38:18.118: Failed to load seccomp rules.
**
Tracker:ERROR:../src/tracker-extract/tracker-extract.c:707:tracker_extract_get_metadata_by_cmdline: code should not be reached
Bail out! Tracker:ERROR:../src/tracker-extract/tracker-extract.c:707:tracker_extract_get_metadata_by_cmdline: code should not be reached
Aborted
```

<!--
#### 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/36871.patch is attached

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

From 848205a1d21770239b3482f9924bfbea3db0fc6f Mon Sep 17 00:00:00 2001
From: oreo639 <31916379+Oreo639@users.noreply.github.com>
Date: Tue, 26 Apr 2022 00:48:02 -0700
Subject: [PATCH] libseccomp: update to 2.5.4

---
 srcpkgs/libseccomp/template | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/libseccomp/template b/srcpkgs/libseccomp/template
index 6dc73feaee05..63a4ba50c9d1 100644
--- a/srcpkgs/libseccomp/template
+++ b/srcpkgs/libseccomp/template
@@ -1,16 +1,15 @@
 # Template file for 'libseccomp'
 pkgname=libseccomp
-reverts="2.5.0_1"
-version=2.4.3
+version=2.5.4
 revision=2
 build_style=gnu-configure
-hostmakedepends="automake libtool"
+hostmakedepends="automake libtool gperf"
 short_desc="High level interface to the Linux Kernel's seccomp filter"
 maintainer="Anthony Iliopoulos <ailiop@altatus.com>"
 license="LGPL-2.1-or-later"
 homepage="https://github.com/seccomp/libseccomp/"
 distfiles="https://github.com/seccomp/${pkgname}/archive/v${version}.tar.gz"
-checksum=4d86f0bd0847795bf7f7bf6e44cb73edf4417d84f6d8848c23eda99b0c50fce6
+checksum=96bbadb4384716272a6d2be82801dc564f7aab345febfe9b698b70fc606e3f75
 
 post_extract() {
 	case "$XBPS_TARGET_MACHINE" in

             reply	other threads:[~2022-04-26  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  7:52 oreo639 [this message]
2022-04-26  7:53 ` [PR PATCH] [Updated] " oreo639
2022-04-26  8:29 ` oreo639
2022-04-26  8:33 ` oreo639
2022-06-11 10:37 ` [PR PATCH] [Merged]: " paper42

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-36871@inbox.vuxu.org \
    --to=oreo639@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).