all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org, "Edison Ibáñez" <arkhan@disroot.org>
Subject: Re: docker-compose not work
Date: Mon, 17 Jun 2019 03:27:30 +0200	[thread overview]
Message-ID: <874l4pvw59.fsf@nckx> (raw)
In-Reply-To: <87lfy1m49j.fsf@disroot.org>

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

Edison,

Edison Ibáñez wrote:
> I have tried to update the package as you can see in the paste
>
> https://bin.disroot.org/?d21a1c74236d7ebd#FlZ2iQxLIkrclC1O45wr7YuUI5bjBcjStwc710J6TWo=
>
> but I still have the same error.

Well, I had already said as much in my previous e-mail:

Tobias Geerinckx-Rice wrote:
>> However, even 1.24.0 complains about jsonschema<3,>=2.5.1 not 
>> being
>> found.  Since Docker insists on using an old library, and I 
>> don't feel
>> comfortable removing the version constraints (I don't use 
>> Docker),

So please guix pull, update docker-compose (‘guix upgrade 
docker-compose’), and check whether it works with the old version 
of python-jsonschema I added.

Even if you want to update to 1.24.0, you'll still have to add 
python-jsonschema-2.6 as an input, as done in commit 
914bba28096c1b85e368537c02e9841258887acb.

Lastly, I'm aware that updating to a 1.24.0 that builds is trivial 
(I had to do so to write the above), but I don't know if it will 
actually work in practice without updating the rest of Docker. 
Hence the conservatism.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-06-17  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 15:28 docker-compose not work arkhan
2019-06-16 17:46 ` Tobias Geerinckx-Rice
2019-06-17  0:42   ` Edison Ibáñez
2019-06-17  1:27     ` Tobias Geerinckx-Rice [this message]
2019-06-18  9:10       ` Björn Höfling

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=874l4pvw59.fsf@nckx \
    --to=me@tobias.gr \
    --cc=arkhan@disroot.org \
    --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.
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.