From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Cc: Catriel <cdelia@dc.uba.ar>, julien lepiller <roptat@lepiller.eu>
Subject: Re: enchant hash, fail to upgrade
Date: Mon, 23 Sep 2019 18:09:28 +0200 [thread overview]
Message-ID: <87sgon0zbb.fsf@nckx> (raw)
In-Reply-To: <9FCDF2CE-1390-47D2-B5F2-BC8B40E88037@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
Catriel, Julien,
Julien Lepiller 写道：
> I'll update to 2.2.7 when I have access to my gpg key, so the
> problem should be fixed after that. The 2.2.5 release was made
> twice by accident, which overwrote the old tarball. The new
> 2.2.5 tarball actually is the 2.2.6 release. See
> https://github.com/AbiWord/enchant/pull/221 fos details.
I'd noticed this too, and probably retraced your steps above.
Enchant upstream[0] 写道：
>> The original tarball is still available on
>> https://src.fedoraproject.org/repo/pkgs/enchant2/enchant-2.2.5.tar.gz/.
>
> Thanks, but I'd rather not publish something I haven't
> generated. What's the problem you're trying to solve here?
…which doesn't make any sense to me (it's their own tarball), but
oh well. I've pushed enchant@2.2.7 to master with commit
bfe194b5331fe9a60ed9e1d373fe1de9e2606d34.
Thanks!
T G-R
[0]:
https://github.com/AbiWord/enchant/pull/221#issuecomment-528858811
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-23 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 19:22 enchant hash, fail to upgrade Catriel
2019-09-22 21:30 ` Julien Lepiller
2019-09-22 22:38 ` Catriel
2019-09-23 10:11 ` Julien Lepiller
2019-09-23 16:09 ` Tobias Geerinckx-Rice [this message]
2019-09-24 18:44 ` Catriel Omar D'Elía
2019-09-24 19:25 ` Tobias Geerinckx-Rice
2019-09-24 15:32 ` Catriel Omar D'Elía
2019-09-24 16:19 ` Ludovic Courtès
2019-09-24 19:18 ` Catriel Omar D'Elía
2019-09-24 19:51 ` Tobias Geerinckx-Rice
2019-09-25 17:43 ` Catriel Omar D'Elía
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgon0zbb.fsf@nckx \
--to=me@tobias.gr \
--cc=cdelia@dc.uba.ar \
--cc=help-guix@gnu.org \
--cc=roptat@lepiller.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).