From: shahab-vahedi <shahab-vahedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] metalog: fix bleeding logs onto tty1
Date: Mon, 21 Aug 2023 10:47:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45700@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
There is a new pull request by shahab-vahedi against master on the void-packages repository
https://github.com/shahab-vahedi/void-packages fix-metalog-bleeding
https://github.com/void-linux/void-packages/pull/45700
metalog: fix bleeding logs onto tty1
This fixes issue #45653 [1].
[1]
https://github.com/void-linux/void-packages/issues/45653
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture: x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/45700.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix-metalog-bleeding-45700.patch --]
[-- Type: text/x-diff, Size: 1165 bytes --]
From dd818adeb1091a0fc72bd217d09cbdba809b4597 Mon Sep 17 00:00:00 2001
From: Shahab Vahedi <16524902+shahab-vahedi@users.noreply.github.com>
Date: Mon, 21 Aug 2023 10:41:28 +0200
Subject: [PATCH] metalog: fix bleeding logs onto tty1
This fixes issue #45653 [1].
[1]
https://github.com/void-linux/void-packages/issues/45653
---
srcpkgs/metalog/files/metalog/run | 1 -
srcpkgs/metalog/template | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/srcpkgs/metalog/files/metalog/run b/srcpkgs/metalog/files/metalog/run
index 5b7ff14eba605..0f801d171017e 100755
--- a/srcpkgs/metalog/files/metalog/run
+++ b/srcpkgs/metalog/files/metalog/run
@@ -1,5 +1,4 @@
#!/bin/sh
-exec 2>&1
exec 1>&2
[ -r conf ] && . ./conf
exec metalog ${OPTS=-v}
diff --git a/srcpkgs/metalog/template b/srcpkgs/metalog/template
index 1f1a4c5c9496f..ed5e4435a6213 100644
--- a/srcpkgs/metalog/template
+++ b/srcpkgs/metalog/template
@@ -1,7 +1,7 @@
# Template file for 'metalog'
pkgname=metalog
version=20230719
-revision=1
+revision=2
build_style=gnu-configure
conf_files="/etc/metalog.conf"
hostmakedepends="autoconf autoconf-archive automake pkg-config"
next reply other threads:[~2023-08-21 8:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 8:47 shahab-vahedi [this message]
2023-08-21 11:46 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 15:36 ` aryandb
2023-08-21 15:39 ` aryandb
2023-08-21 15:45 ` Duncaen
2023-08-21 18:15 ` shahab-vahedi
2023-08-21 18:26 ` Duncaen
2023-08-21 18:32 ` shahab-vahedi
2023-08-21 18:34 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 18:34 ` shahab-vahedi
2023-08-21 18:45 ` Duncaen
2023-08-21 18:47 ` Duncaen
2023-08-21 19:01 ` aryandb
2023-08-21 19:50 ` [PR PATCH] [Updated] " shahab-vahedi
2023-08-21 19:51 ` shahab-vahedi
2023-08-26 20:21 ` shahab-vahedi
2023-08-31 11:57 ` shahab-vahedi
2023-08-31 14:09 ` [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-45700@inbox.vuxu.org \
--to=shahab-vahedi@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).