From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: webkit2gtk: update to 2.40.0.
Date: Fri, 24 Mar 2023 21:43:12 +0100 [thread overview]
Message-ID: <20230324204312.ZBgrvbgA63tnZ0GFd3pN4wu1SOzoGbEwBC2PS7oxFPM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41698@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/41698#issuecomment-1483384558
Comment:
> If you wait for a bit Komikku might be resolved upstream soon https://gitlab.com/valos/Komikku/-/merge_requests/195
I'll update it when it gets resolved, but I don't anticipate that getting merged sooon.
> Also, this patch seems to break japscan and readcomiconline.
> I do not have enough time to solve the patch right now. And, this patch making any server depending on WebkitGTK fail anyway, it might be wiser to just delete both sources in f38, although I do not know the effect it might have on users using the source upgrading to f38.
next prev parent reply other threads:[~2023-03-24 20:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 19:59 [PR PATCH] webkit2gtk: update to 2.39.4 oreo639
2023-01-17 20:03 ` [PR PATCH] [Updated] " oreo639
2023-01-17 20:23 ` oreo639
2023-01-17 20:26 ` oreo639
2023-01-17 20:53 ` oreo639
2023-01-17 20:55 ` oreo639
2023-03-22 0:49 ` oreo639
2023-03-22 10:19 ` [PR PATCH] [Updated] webkit2gtk: update to 2.40.0 oreo639
2023-03-22 10:33 ` oreo639
2023-03-22 17:11 ` paper42
2023-03-22 20:48 ` [PR PATCH] [Updated] " oreo639
2023-03-22 22:44 ` oreo639
2023-03-23 17:33 ` [PR REVIEW] " paper42
2023-03-23 19:05 ` [PR PATCH] [Updated] " oreo639
2023-03-23 19:05 ` [PR REVIEW] " oreo639
2023-03-24 20:18 ` icp1994
2023-03-24 20:43 ` oreo639 [this message]
2023-03-26 22:04 ` oreo639
2023-03-26 22:04 ` oreo639
2023-03-30 21:22 ` paper42
2023-03-30 22:34 ` oreo639
2023-03-30 22:54 ` [PR PATCH] [Updated] " oreo639
2023-04-01 19:48 ` oreo639
2023-04-01 19:50 ` oreo639
2023-04-02 9:04 ` paper42
2023-04-02 20:10 ` oreo639
2023-04-02 20:10 ` oreo639
2023-04-02 20:12 ` oreo639
2023-04-02 20:13 ` oreo639
2023-04-02 20:33 ` nekopsykose
2023-04-02 20:34 ` nekopsykose
2023-04-02 20:35 ` nekopsykose
2023-04-02 20:38 ` nekopsykose
2023-04-02 20:38 ` nekopsykose
2023-04-02 22:21 ` oreo639
2023-04-02 22:36 ` nekopsykose
2023-04-02 23:32 ` [PR PATCH] [Updated] " oreo639
2023-04-02 23:33 ` oreo639
2023-04-02 23:33 ` oreo639
2023-04-02 23:34 ` oreo639
2023-04-02 23:34 ` oreo639
2023-04-03 2:26 ` [PR PATCH] [Updated] " oreo639
2023-04-03 9:09 ` oreo639
2023-04-03 18:07 ` [PR PATCH] [Merged]: " paper42
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=20230324204312.ZBgrvbgA63tnZ0GFd3pN4wu1SOzoGbEwBC2PS7oxFPM@z \
--to=oreo639@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).