Github messages for voidlinux
 help / color / mirror / Atom feed
From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mozc: update to 2.26.4353.100. (new package for fcitx5-mozc)
Date: Sat, 01 May 2021 15:30:18 +0200	[thread overview]
Message-ID: <20210501133018.aWxrJm3HcS4AE4gDcumnALhdLelJqFfGako1Eet0dTQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30492@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

New comment by mvf on void-packages repository

https://github.com/void-linux/void-packages/pull/30492#issuecomment-830625588

Comment:
@ericonr Will do. ~Turns out the version update was unavoidable since `fcitx-mozc` was rebased and the old sources are simply no longer available.~ I will submit a followup change.

Edit: The old sources are available after all. Just missed it at first because both GitLab (old upstream) and GitHub (new upstream) changed their tarball URLs. But anyway, the update seems worth it. Arch doesn't ship `ibus-mozc` either and it's inferior to `fcitx`.

      parent reply	other threads:[~2021-05-01 13:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 15:55 [PR PATCH] [WIP] mozc: update to 2.26.4346.100. " sgn
2021-04-27  1:26 ` [PR PATCH] [Updated] " sgn
2021-04-30  7:56 ` sgn
2021-04-30  7:57 ` mozc: update to 2.26.4353.100. " sgn
2021-04-30  7:57 ` sgn
2021-04-30  8:04 ` sgn
2021-04-30 13:51 ` noarchwastaken
2021-05-01  1:53 ` [PR PATCH] [Updated] " sgn
2021-05-01  2:00 ` sgn
2021-05-01  2:01 ` [PR PATCH] [Merged]: " sgn
2021-05-01 10:27 ` mvf
2021-05-01 12:18 ` ericonr
2021-05-01 12:33 ` mvf
2021-05-01 13:30 ` mvf [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=20210501133018.aWxrJm3HcS4AE4gDcumnALhdLelJqFfGako1Eet0dTQ@z \
    --to=mvf@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).