all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36026@debbugs.gnu.org
Subject: [bug#36026] [PATCH 0/4] Update Conda
Date: Thu, 13 Jun 2019 11:08:25 +0200	[thread overview]
Message-ID: <87o9313l9y.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87o9316fhs.fsf@gnu.org>

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

Thanks for the clarifications around the libarchive business.

The problem is that this patch still does not work because
python-libarchive-c does not support zstd, which
python-conda-package-handling needs.  I don't understand how upstream
does this.  I've reported it upstream:

https://github.com/conda/conda-package-handling/issues/14

My knowledge of python is not enough to understand if upstream is wrong
or if I'm using python-libarchive-c incorrectly.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2019-06-13  9:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 13:57 [bug#36026] [PATCH 0/4] Update Conda Pierre Neidhardt
2019-05-31 14:04 ` [bug#36026] [PATCH 1/4] gnu: libarchive: Add zstd support Pierre Neidhardt
2019-05-31 14:04   ` [bug#36026] [PATCH 2/4] gnu: python-libarchive-c: Explicitly rely on latest libarchive Pierre Neidhardt
2019-05-31 14:04   ` [bug#36026] [PATCH 3/4] gnu: Add python-conda-package-handling Pierre Neidhardt
2019-05-31 14:04   ` [bug#36026] [PATCH 4/4] gnu: python-conda: Update to 4.7.0 Pierre Neidhardt
2019-06-13 18:59     ` Ricardo Wurmus
2019-06-13  8:44   ` [bug#36026] [PATCH 1/4] gnu: libarchive: Add zstd support Ludovic Courtès
2019-06-13  8:45 ` [bug#36026] [PATCH 0/4] Update Conda Ludovic Courtès
2019-06-13  9:08   ` Pierre Neidhardt [this message]
2019-06-13 18:57 ` Ricardo Wurmus
2019-06-13 19:06   ` Pierre Neidhardt
2020-08-12 22:07 ` bug#36026: " Ricardo Wurmus

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=87o9313l9y.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=36026@debbugs.gnu.org \
    --cc=ludo@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.