Github messages for voidlinux
 help / color / mirror / Atom feed
From: jovanlanik <jovanlanik@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] metalog: update to 20230707
Date: Fri, 07 Jul 2023 18:20:58 +0200	[thread overview]
Message-ID: <20230707162058.QuOijwPGhHHt5zF3-wUckh2P3q4Wz30Od1uRlqYPElQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44912@inbox.vuxu.org>

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

There is an updated pull request by jovanlanik against master on the void-packages repository

https://github.com/jovanlanik/void-packages master
https://github.com/void-linux/void-packages/pull/44912

metalog: update to 20230707
#### Testing the changes
- I tested the changes in this PR: **briefly**

Updated and added changelog as asked in #35617 (seems it was only recently changed again)

@teldra Would it also possible be for me to adopt metalog as maintainer? I am a contributor and user of the program so I follow development closely...


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

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

From 081020aab8dc4edc3f120a751f8d482328c4e402 Mon Sep 17 00:00:00 2001
From: Jovan Lanik <jox969@gmail.com>
Date: Fri, 7 Jul 2023 15:54:34 +0200
Subject: [PATCH] metalog: update to 20230707

---
 srcpkgs/metalog/template | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/metalog/template b/srcpkgs/metalog/template
index 792b4bd32b48..ee54b2c82a7f 100644
--- a/srcpkgs/metalog/template
+++ b/srcpkgs/metalog/template
@@ -1,6 +1,6 @@
 # Template file for 'metalog'
 pkgname=metalog
-version=20220214
+version=20230707
 revision=1
 build_style=gnu-configure
 conf_files="/etc/metalog.conf"
@@ -10,8 +10,9 @@ short_desc="Modern replacement for syslogd and klogd"
 maintainer="teldra <teldra@rotce.de>"
 license="GPL-2.0-only"
 homepage="https://github.com/hvisage/metalog"
+changelog="https://github.com/hvisage/metalog/blob/master/NEWS"
 distfiles="https://github.com/hvisage/metalog/archive/metalog-${version}.tar.gz"
-checksum=3a9dd6f1460d90296771c81aa71fc0f45dd25ef22af63f48e6cbe5422a88f3bf
+checksum=135caf2cc9ce48364f7cd39a58c904cbd63631c9963e1c239b2df8b2ca023dc1
 
 pre_configure() {
 	./autogen.sh
@@ -19,4 +20,8 @@ pre_configure() {
 
 post_install() {
 	vsv metalog
+
+	# Disable logging for metaloga to avoid any issues
+	# https://github.com/void-linux/void-packages/pull/44912#issuecomment-1625625388
+	rm -rf "${DESTDIR}/etc/sv/metalog/log"
 }

  parent reply	other threads:[~2023-07-07 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 14:00 [PR PATCH] " jovanlanik
2023-07-07 14:48 ` jovanlanik
2023-07-07 15:00 ` jovanlanik
2023-07-07 16:01 ` jovanlanik
2023-07-07 16:04 ` classabbyamp
2023-07-07 16:05 ` classabbyamp
2023-07-07 16:20 ` jovanlanik [this message]
2023-07-08 15:13 ` jovanlanik
2023-07-12 13:43 ` [PR PATCH] [Merged]: " Duncaen
2023-08-18 10:06 ` sgn

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=20230707162058.QuOijwPGhHHt5zF3-wUckh2P3q4Wz30Od1uRlqYPElQ@z \
    --to=jovanlanik@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).