Github messages for voidlinux
 help / color / mirror / Atom feed
From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] elogind: update to 246.10.
Date: Sun, 11 Sep 2022 20:55:16 +0200	[thread overview]
Message-ID: <20220911185516.EFCDriocAisuimpvPpRJA6Jecxjp9Yzb5Ac1LNnYWMs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38347@inbox.vuxu.org>

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

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

https://github.com/motorto/void-packages elogind-246.10
https://github.com/void-linux/void-packages/pull/38347

elogind: update to 246.10.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv6l

Going to test on a vm using seatd to see if the errors still occurs 

@Gottox in case you didn't see the message IRC could you check if the problem with libseat still occurs ? Ok my quick test it doesn't, but to be honest I don't have a lot of experience it with 

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

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

From 5e56fad26f3842040bf5983c74d0b47d3997e7ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Thu, 28 Jul 2022 23:15:17 +0100
Subject: [PATCH] elogind: update to 246.10.

---
 srcpkgs/elogind/patches/polkit.patch | 27 +++++++++++++++++++++++++++
 srcpkgs/elogind/template             | 10 +++++-----
 2 files changed, 32 insertions(+), 5 deletions(-)
 create mode 100644 srcpkgs/elogind/patches/polkit.patch

diff --git a/srcpkgs/elogind/patches/polkit.patch b/srcpkgs/elogind/patches/polkit.patch
new file mode 100644
index 000000000000..4bdf1289f268
--- /dev/null
+++ b/srcpkgs/elogind/patches/polkit.patch
@@ -0,0 +1,27 @@
+commit 2b09e13f7aec13105380d9d9fddc96ae51911b0c
+Author: Daniel Kolesa <daniel@octaforge.org>
+Date:   Sat Dec 18 02:53:26 2021 +0100
+
+    reenable polkit
+
+diff --git a/meson.build b/meson.build
+index 72825a2..b14cb64 100644
+--- a/meson.build
++++ b/meson.build
+@@ -1155,15 +1155,6 @@ if want_polkit != 'false' and not skip_deps
+                 message('Old polkit detected, will install pkla files')
+                 install_polkit_pkla = true
+         endif
+-#if 1 /// Disable polkit completely if libpolkit is not there. See elogind issue #167
+-        if not libpolkit.found()
+-                if want_polkit != 'auto'
+-                        error('Polkit requested but libpolkit was not found.')
+-                endif
+-                install_polkit = false
+-                want_polkit    = false
+-        endif
+-#endif // 1
+ endif
+ conf.set10('ENABLE_POLKIT', install_polkit)
+ 
+
diff --git a/srcpkgs/elogind/template b/srcpkgs/elogind/template
index 8e9fb0ef6c81..b8d2d8ce8696 100644
--- a/srcpkgs/elogind/template
+++ b/srcpkgs/elogind/template
@@ -1,13 +1,13 @@
 # Template file for 'elogind'
 pkgname=elogind
-reverts="246.10_1"
-version=246.9.2
-revision=3
+version=246.10
+revision=1
 build_style=meson
 configure_args="-Dcgroup-controller=elogind -Dhalt-path=/usr/bin/halt
  -Drootlibexecdir=/usr/libexec/elogind -Dreboot-path=/usr/bin/reboot
  -Dkexec-path=/usr/bin/kexec -Ddefault-hierarchy=legacy
- -Ddefault-kill-user-processes=false -Dman=true"
+ -Ddefault-kill-user-processes=false -Dman=true
+ -Dpolkit=true"
 hostmakedepends="docbook-xsl gettext-devel gperf intltool libxslt m4
  pkg-config shadow glib-devel"
 makedepends="acl-devel eudev-libudev-devel gettext-devel libglib-devel libcap-devel
@@ -18,7 +18,7 @@ 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=dd2fcf22a89a078cad22e633d2f14a4cc9f4a9c8bae25c0e39fc4aec3e273bc9
+checksum=c490dc158c8f5bca8d00ecfcc7ad5af24d1c7b9e59990a0b3b1323996221a922
 conf_files="/etc/elogind/*.conf"
 # tests fail differently due to containerization and kernel features
 make_check=ci-skip

  parent reply	other threads:[~2022-09-11 18:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 22:44 [PR PATCH] " motorto
2022-08-02 19:30 ` motorto
2022-08-03 21:46 ` motorto
2022-08-03 21:47 ` motorto
2022-08-04 11:04 ` motorto
2022-08-04 11:04 ` motorto
2022-08-04 17:58 ` [PR PATCH] [Updated] " motorto
2022-08-04 18:02 ` motorto
2022-08-04 18:09 ` motorto
2022-08-04 18:09 ` motorto
2022-08-04 21:11 ` [PR PATCH] [Updated] " motorto
2022-08-04 21:16 ` motorto
2022-08-04 21:22 ` motorto
2022-08-04 21:25 ` motorto
2022-08-11 23:19 ` motorto
2022-09-10 23:12 ` [PR PATCH] [Updated] " motorto
2022-09-11 18:55 ` motorto [this message]
2022-09-11 22:58 ` oreo639
2022-09-11 22:59 ` oreo639
2022-09-13 20:30 ` paper42
2022-09-13 20:31 ` [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=20220911185516.EFCDriocAisuimpvPpRJA6Jecxjp9Yzb5Ac1LNnYWMs@z \
    --to=motorto@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).