From: "Catriel Omar D'Elía" <cdelia@dc.uba.ar>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org, julien lepiller <roptat@lepiller.eu>
Subject: Re: enchant hash, fail to upgrade
Date: Tue, 24 Sep 2019 15:44:55 -0300 [thread overview]
Message-ID: <878sqdwn2w.fsf@dc.uba.ar> (raw)
In-Reply-To: <87sgon0zbb.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 23 Sep 2019 18:09:28 +0200")
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> 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.
>
vOv not shure I follow, that was Thomas? ... anyway your commit fixed the
issue!
> Thanks!
To you!
>
> T G-R
>
> [0]:
> https://github.com/AbiWord/enchant/pull/221#issuecomment-528858811
next prev parent reply other threads:[~2019-09-24 20:03 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
2019-09-24 18:44 ` Catriel Omar D'Elía [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sqdwn2w.fsf@dc.uba.ar \
--to=cdelia@dc.uba.ar \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.