From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: upower: update to 0.99.17
Date: Sat, 09 Apr 2022 12:27:09 +0200 [thread overview]
Message-ID: <20220409102709.po-jqU-Ef74SYJ4WfSGb59YmwKNtdrRqhylmUSAUNtQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36485@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/36485#issuecomment-1093866202
Comment:
> I don't think this is correct:
>
> ```diff
> @@ -1,9 +1,9 @@
> /etc/UPower/UPower.conf
> /usr/bin/upower
> /usr/lib/girepository-1.0/UPowerGlib-1.0.typelib
> -/usr/lib/udev/rules.d/95-upower-hid.rules
> -/usr/lib/udev/rules.d/95-upower-wup.rules
> /usr/libexec/upowerd
> +/usr/rules.d/95-upower-hid.rules
> +/usr/rules.d/95-upower-wup.rules
> /usr/share/dbus-1/interfaces/org.freedesktop.UPower.Device.xml
> /usr/share/dbus-1/interfaces/org.freedesktop.UPower.KbdBacklight.xml
> /usr/share/dbus-1/interfaces/org.freedesktop.UPower.Wakeups.xml
> ```
Thanks for letting me know.
eudev has `udevdir`, but upower is looking for `udev_dir`. Not sure how best that should be fixed, but I just added a sed command to replace it for now.
Looking at systemd-udev, it has both `udevdir` and `udev_dir`: https://github.com/systemd/systemd/blob/main/src/udev/udev.pc.in
next prev parent reply other threads:[~2022-04-09 10:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 1:53 [PR PATCH] " oreo639
2022-04-03 2:10 ` [PR PATCH] [Updated] " oreo639
2022-04-03 2:11 ` oreo639
2022-04-03 2:26 ` oreo639
2022-04-03 2:51 ` oreo639
2022-04-03 3:02 ` oreo639
2022-04-03 15:50 ` paper42
2022-04-05 1:48 ` cinerea0
2022-04-09 1:52 ` cinerea0
2022-04-09 1:56 ` [PR PATCH] [Updated] " oreo639
2022-04-09 1:57 ` oreo639
2022-04-09 9:29 ` [PR REVIEW] " paper42
2022-04-09 9:29 ` paper42
2022-04-09 10:19 ` oreo639
2022-04-09 10:19 ` [PR PATCH] [Updated] " oreo639
2022-04-09 10:27 ` oreo639 [this message]
2022-04-09 10:27 ` oreo639
2022-04-09 11:02 ` [PR PATCH] [Updated] " oreo639
2022-04-09 12:56 ` oreo639
2022-04-09 12:56 ` oreo639
2022-04-09 12:57 ` oreo639
2022-04-09 13:10 ` oreo639
2022-04-09 15:27 ` paper42
2022-04-09 16:03 ` [PR PATCH] [Updated] " oreo639
2022-04-09 16:08 ` oreo639
2022-04-09 16:15 ` oreo639
2022-04-09 19:42 ` oreo639
2022-04-10 8:55 ` [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=20220409102709.po-jqU-Ef74SYJ4WfSGb59YmwKNtdrRqhylmUSAUNtQ@z \
--to=oreo639@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).