Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dbus: update to 1.14.8.
Date: Mon, 26 Jun 2023 11:30:46 +0200	[thread overview]
Message-ID: <20230626093046.mhRzG1bgT_mTZUkf2JB2G2kEqCcdQLA-WF-HGCHPK98@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44605@inbox.vuxu.org>

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

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/pull/44605#issuecomment-1607076270

Comment:
I was still able to boot with dbus-elogind 1.14.8 while both dbus-elogind-x11 and dbus-elogind-libs were still on 1.14.6, but dbus-run-session failed to start. Bumping them all to 1.14.8 fixed this (I think bumping only dbus-elogind-libs was necessary, though I'm not sure). The best thing to do is to make sure that only the same version of the packages are installed, but I'm not sure what's the best way to do that.

  parent reply	other threads:[~2023-06-26  9:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 11:49 [PR PATCH] " Bnyro
2023-06-24 12:26 ` mhmdanas
2023-06-24 16:05 ` [PR PATCH] [Updated] " Bnyro
2023-06-24 16:08 ` Bnyro
2023-06-24 16:46 ` mhmdanas
2023-06-24 16:46 ` mhmdanas
2023-06-24 16:46 ` mhmdanas
2023-06-26  9:30 ` mhmdanas [this message]
2023-07-18  6:49 ` [PR PATCH] [Updated] dbus{,-elogind}: " Bnyro
2023-07-18  6:51 ` [PR PATCH] [Updated] dbus: " Bnyro
2023-07-18  6:53 ` Bnyro
2023-07-22 13:37 ` mhmdanas
2023-07-22 19:38 ` [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=20230626093046.mhRzG1bgT_mTZUkf2JB2G2kEqCcdQLA-WF-HGCHPK98@z \
    --to=mhmdanas@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).