unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Catriel <cdelia@dc.uba.ar>
Cc: help-guix@gnu.org
Subject: Re: enchant hash, fail to upgrade
Date: Mon, 23 Sep 2019 12:11:21 +0200	[thread overview]
Message-ID: <9FCDF2CE-1390-47D2-B5F2-BC8B40E88037@lepiller.eu> (raw)
In-Reply-To: <87y2ygrm6o.fsf@dc.uba.ar>

Le 23 septembre 2019 00:38:39 GMT+02:00, Catriel <cdelia@dc.uba.ar> a écrit :
>Julien Lepiller <julien@lepiller.eu> writes:
>>
>> Sorry I'm too tired to answer properly. Their is a section about
>contributing in the manual. Have you read that?
>>
>
>yes, but I was asking a way or methodology to modify packages from guix
>and using them even when they are dependencies. Because just defining a
>package doesn't seem to handle that situation very well. As opose to
>inheriting emacs package definition, calling it
>awesome-mario-bros-emacs, patching it, and installing it. I was not
>interested so much on the details of contributing.

I see, sorry for the misunderstanding. Honestly, I'm not sure how to do it. My best answer is: get the repository, make your change, build it and use ./pre-inst-env.

>
>> As a workaround, you can try guix package -u
>> --with-source=enchant=`guix download …` where … is the url of the
>> sources you want to use. Iirc, it applies to dependencies
>recursively.
>>
>
>mmm the problem remaings the same. The source is accesible and
>downloads
>just fine, the issue here is with the package definition: it have a
>wrong sha256 (asuming that is the case and not a sec. vulnerability in
>upstream).
>
>So even if I download it manually and write:
>
>$guix upgrade --fallback --with-source=enchant=path-to-downloaded-file
>
>it's equivalent to let guix download the package by itself. When it
>tries to build the derivation the sha256 mismatch aborts the upgrade.

That's weird: enchant should be replaced everywhere and build with the new source, it shouldn't even look for a hash. The file is available at the ci server though, so maybe check your substitute servers? You can download it directly at https://ci.guix.gnu.org/nar/wsyfm5avik0wvh82gyxw9acbixp0ygbp-enchant-2.2.5.tar.gz

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.

>
>> Good night, and good luck :)
>
>Have a good sleep!
>and really thank you for answering!

  reply	other threads:[~2019-09-23 10:11 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 [this message]
2019-09-23 16:09       ` Tobias Geerinckx-Rice
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=9FCDF2CE-1390-47D2-B5F2-BC8B40E88037@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=cdelia@dc.uba.ar \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).