From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] elogind: update to 246.9
Date: Mon, 21 Dec 2020 15:45:50 +0100 [thread overview]
Message-ID: <20201221144550.blyjid0ZUYTvpJsbNAI-J_qwEMMpYefCOYqHgGlKcug@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27276@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
There is an updated pull request by st3r4g against master on the void-packages repository
https://github.com/st3r4g/void-packages elogind-246.9
https://github.com/void-linux/void-packages/pull/27276
elogind: update to 246.9
@pbui @travankor
Close #27132
Testing on `x86_64` sway and gnome
A patch file from https://github.com/void-linux/void-packages/pull/27276.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-elogind-246.9-27276.patch --]
[-- Type: text/x-diff, Size: 1400 bytes --]
From d80919cafda9b570b21a298e7975844d947895d9 Mon Sep 17 00:00:00 2001
From: Stefano Ragni <st3r4g@protonmail.com>
Date: Mon, 21 Dec 2020 15:42:23 +0100
Subject: [PATCH] elogind: update to 246.9.r1
---
srcpkgs/elogind/template | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/elogind/template b/srcpkgs/elogind/template
index 35480b0ece0..8792d03e16d 100644
--- a/srcpkgs/elogind/template
+++ b/srcpkgs/elogind/template
@@ -1,8 +1,9 @@
# Template file for 'elogind'
pkgname=elogind
-reverts="243.7_1"
-version=243.4
-revision=3
+version=246.9.r1
+revision=1
+_version=246.9-r1
+wrksrc=${pkgname}-${_version}
build_style=meson
configure_args="-Dcgroup-controller=elogind -Dhalt-path=/usr/bin/halt
-Drootlibexecdir=/usr/libexec/elogind -Dreboot-path=/usr/bin/reboot
@@ -17,8 +18,8 @@ short_desc="Standalone logind fork"
maintainer="Enno Boland <gottox@voidlinux.org>"
license="GPL-2.0-or-later, LGPL-2.0-or-later"
homepage="https://github.com/elogind/elogind"
-distfiles="https://github.com/${pkgname}/${pkgname}/archive/v${version}.tar.gz"
-checksum=f1098745863138e6270ea22e78a39baef9a0356b48246c5a53b34211992dc7db
+distfiles="https://github.com/${pkgname}/${pkgname}/archive/v${_version}.tar.gz"
+checksum=11912864fbd0eeb8ba43530be4ae5ef95b7a036e20c85f4a6e63e6e04ddf2d21
conf_files="/etc/elogind/*.conf"
if [ "$XBPS_TARGET_LIBC" = "musl" ]; then
next prev parent reply other threads:[~2020-12-21 14:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 13:05 [PR PATCH] " st3r4g
2020-12-19 15:17 ` pbui
2020-12-19 17:08 ` st3r4g
2020-12-19 20:41 ` pbui
2020-12-19 20:53 ` st3r4g
2020-12-19 20:53 ` st3r4g
2020-12-19 20:54 ` st3r4g
2020-12-19 20:57 ` pbui
2020-12-19 21:05 ` pbui
2020-12-20 3:34 ` travankor
2020-12-21 14:45 ` st3r4g [this message]
2020-12-21 14:46 ` st3r4g
2020-12-21 15:28 ` pbui
2020-12-21 17:19 ` [PR PATCH] [Updated] " st3r4g
2020-12-28 10:51 ` travankor
2021-01-03 9:06 ` travankor
2021-01-17 14:23 ` UsernameRandomlyGenerated
2021-01-17 14:53 ` [PR PATCH] [Updated] " st3r4g
2021-01-18 19:39 ` ericonr
2021-01-18 19:45 ` pbui
2021-01-18 21:18 ` st3r4g
2021-01-18 21:24 ` ericonr
2021-01-18 23:43 ` pbui
2021-01-19 6:44 ` travankor
2021-01-19 6:46 ` travankor
2021-01-19 14:08 ` ericonr
2021-01-19 15:52 ` st3r4g
2021-01-19 20:45 ` travankor
2021-01-19 21:02 ` travankor
2021-01-20 7:06 ` travankor
2021-01-21 14:32 ` [PR PATCH] [Closed]: " ericonr
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=20201221144550.blyjid0ZUYTvpJsbNAI-J_qwEMMpYefCOYqHgGlKcug@z \
--to=st3r4g@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).