From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: OpenLP: update to 3.0.0
Date: Mon, 09 Jan 2023 15:37:13 +0100 [thread overview]
Message-ID: <20230109143713.aYw_QX3oVQIBvL2FT5YTzS6R7ZxnDpazJDp0DLHSNqs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41526@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
New comment by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/pull/41526#issuecomment-1375717394
Comment:
Yes, it did, after some fiddling, see `git log -p srcpkgs/OpenLP/patches`. It probably is broken upstream too as those patches were from upstream, so they might not be as attentive to making sure all tests are passing. Alternatively, it could be an out-of-date python dependency as they don't version guard most of the dependencies.
next prev parent reply other threads:[~2023-01-09 14:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 22:12 [PR PATCH] " joelchrono12
2023-01-08 23:39 ` [PR PATCH] [Updated] " joelchrono12
2023-01-09 1:33 ` joelchrono12
2023-01-09 1:42 ` joelchrono12
2023-01-09 13:36 ` TinfoilSubmarine
2023-01-09 14:27 ` joelchrono12
2023-01-09 14:36 ` TinfoilSubmarine
2023-01-09 14:37 ` TinfoilSubmarine [this message]
2023-01-09 17:33 ` joelchrono12
2023-01-09 17:33 ` joelchrono12
2023-01-10 15:49 ` TinfoilSubmarine
2023-01-10 16:03 ` TinfoilSubmarine
2023-01-10 16:22 ` joelchrono12
2023-01-10 16:23 ` joelchrono12
2023-01-10 16:23 ` joelchrono12
2023-01-10 16:37 ` TinfoilSubmarine
2023-01-10 16:51 ` [PR PATCH] [Updated] " joelchrono12
2023-01-10 16:52 ` joelchrono12
2023-01-20 16:28 ` TinfoilSubmarine
2023-02-23 20:11 ` [PR PATCH] [Updated] " Chocimier
2023-02-23 20:12 ` Chocimier
2023-02-26 15:59 ` joelchrono12
2023-03-22 21:40 ` [PR PATCH] [Merged]: " Chocimier
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=20230109143713.aYw_QX3oVQIBvL2FT5YTzS6R7ZxnDpazJDp0DLHSNqs@z \
--to=tinfoilsubmarine@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).