From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dbus-elogind: remove package, migrate to regular dbus
Date: Sat, 15 Jul 2023 17:39:14 +0200 [thread overview]
Message-ID: <20230715153914.WNJ077Iph71a3EWhbScn1ydATyq9yC1T0tLR0bv32_k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45026@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/45026#issuecomment-1636803393
Comment:
OK, the upgrade path is broken: even though the new `dbus-elogind` no longer provides `dbus`, XBPS sees the currently installed version as providing the needed dependency for the upgraded package's new dependency. I've worked around this by bumping `dbus` and adding a strict minimum version in the new dummy package. This seems to do the right thing for full-system upgrades as well as an explicit `xbps-install -u dbus-elogind` even when `dbus-libs` was pulled in by default.
next prev parent reply other threads:[~2023-07-15 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 0:54 [PR PATCH] " ahesford
2023-07-14 17:47 ` Duncaen
2023-07-14 19:37 ` ahesford
2023-07-15 15:20 ` ahesford
2023-07-15 15:37 ` [PR PATCH] [Updated] " ahesford
2023-07-15 15:39 ` ahesford [this message]
2023-07-17 16:15 ` [PR PATCH] [Closed]: " ahesford
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=20230715153914.WNJ077Iph71a3EWhbScn1ydATyq9yC1T0tLR0bv32_k@z \
--to=ahesford@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).