From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-mpd2: update to 3.0.4, fix bum
Date: Tue, 20 Jul 2021 21:12:43 +0200 [thread overview]
Message-ID: <20210720191243.y0c76Ql5cpJdsB9Z2cFJ-dcc2e4juKkFf1faRdCfoeo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31911@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
There's a merged pull request on the void-packages repository
python3-mpd2: update to 3.0.4, fix bum
https://github.com/void-linux/void-packages/pull/31911
Description:
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
I tested almost all the dependants:
* sonata 1.7b1 and 1.7.0 - work fine
* mpdevil - works fine
* python3-mpdnotify - works fine
* bum - works with a small patch, then kind of works, but crashes in different places, but that's not related to a python3-mpd2 update
* mpDris2 - crashes for me, apparently that's an upstream bug specific to my configuration, but I think it's safe to assume it works, because alpine packages only one package which depends on python3-mpd2 - mpdris2, so it's probably well tested there. If someone could test this in a non-GNOME environment, that would be nice.
next prev parent reply other threads:[~2021-07-20 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 18:54 [PR PATCH] " paper42
2021-07-11 19:07 ` [PR PATCH] [Updated] " paper42
2021-07-17 3:57 ` [PR REVIEW] " ericonr
2021-07-18 9:23 ` [PR PATCH] [Updated] " paper42
2021-07-20 19:12 ` ericonr [this message]
2021-07-20 19:13 ` 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=20210720191243.y0c76Ql5cpJdsB9Z2cFJ-dcc2e4juKkFf1faRdCfoeo@z \
--to=ericonr@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).