Github messages for voidlinux
 help / color / mirror / Atom feed
From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] snoopy: update to 2.4.14
Date: Fri, 14 May 2021 05:59:38 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30838@inbox.vuxu.org> (raw)

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

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

https://github.com/heliocat/void-packages snoopy
https://github.com/void-linux/void-packages/pull/30838

snoopy: update to 2.4.14
Also fixes the test environment, though maybe not in the best way.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->

#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl



A patch file from https://github.com/void-linux/void-packages/pull/30838.patch is attached

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

From 170b17d476d123173f6bc9edb192f7e736d1ba15 Mon Sep 17 00:00:00 2001
From: Colin Booth <colin@heliocat.net>
Date: Thu, 13 May 2021 20:57:06 -0700
Subject: [PATCH] snoopy: update to 2.4.14

Also fixes the test environment, though maybe not in the best way
---
 srcpkgs/snoopy/template | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/snoopy/template b/srcpkgs/snoopy/template
index 3d1b338fb245..9c33a30924e4 100644
--- a/srcpkgs/snoopy/template
+++ b/srcpkgs/snoopy/template
@@ -1,20 +1,27 @@
 # Template file for 'snoopy'
 pkgname=snoopy
-version=2.4.6
+version=2.4.14
 revision=1
 build_style=gnu-configure
 hostmakedepends="socat"
+checkdepends="procps-ng"
 conf_files="/etc/snoopy.ini"
 short_desc="Log every executed command to syslog"
 maintainer="Orphaned <orphan@voidlinux.org>"
-license="GPL-2"
+license="GPL-2.0-or-later"
 homepage="https://github.com/a2o/snoopy"
-distfiles="http://source.a2o.si/download/snoopy/snoopy-${version}.tar.gz"
-checksum=6442e1145a5cad725f6aae0887030ee3db34bafc40bbe3bb84da836cbb5f1569
+distfiles="https://github.com/a2o/snoopy/releases/download/snoopy-${version}/snoopy-${version}.tar.gz"
+checksum=6f305f49d87d56906061ded9083dc0308365f966a13edacc3eb59191221ced1a
 
-pre_configure() {
+post_patch() {
 	find . -type f -name Makefile.in -exec sed -i 's| -Werror||' {} +
 }
+
+# some tests are degenerate and blindly source os-release prior to running
+post_build() {
+	[ -f /etc/os-release ] || echo 'ID="void"' > /etc/os-release
+}
+
 post_install() {
 	vconf etc/snoopy.ini
 }

             reply	other threads:[~2021-05-14  3:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  3:59 heliocat [this message]
2021-05-14  4:23 ` [PR PATCH] [Closed]: " heliocat

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