From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python3-dateparser: update to 1.1.1, patch breakage on python3-regex
Date: Tue, 06 Sep 2022 11:19:17 +0200 [thread overview]
Message-ID: <20220906091917.i7oQ78cquHfFxgjg4D_8Ye24gbihWgRRkLBFWGDMaEU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38833@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
There's a closed pull request on the void-packages repository
python3-dateparser: update to 1.1.1, patch breakage on python3-regex
https://github.com/void-linux/void-packages/pull/38833
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
Note that the breakage is not caused by updating the package rather due to an API change introduced in [`python3-regex-2022.3.15`](https://github.com/scrapinghub/dateparser/issues/1045#issuecomment-1069484011). Upstream mitigates this by pinning to an older version of that regex library in their setup.py but that doesn't work for [distro packages](https://github.com/scrapinghub/dateparser/issues/1052#issuecomment-1136438340). This patch is deemed sufficient by one of the [dateparser authors](https://github.com/scrapinghub/dateparser/issues/1052#issuecomment-1131559215) as a temporary fix till they make a new release with a proper fix.
Only one package, `Komikku-0.40.0` depends on this currently.
prev parent reply other threads:[~2022-09-06 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 17:28 [PR PATCH] " icp1994
2022-08-22 18:00 ` icp1994
2022-08-22 19:07 ` icp1994
2022-09-06 9:19 ` sgn [this message]
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=20220906091917.i7oQ78cquHfFxgjg4D_8Ye24gbihWgRRkLBFWGDMaEU@z \
--to=sgn@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).