unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: Konrad Hinsen <konrad.hinsen@cnrs.fr>
To: Thibault Lestang <t.lestang@imperial.ac.uk>,
	guix-science <guix-science@gnu.org>
Subject: Re: Conda environments and reproducibility
Date: Mon, 28 Nov 2022 20:45:30 +0100	[thread overview]
Message-ID: <m1h6yioobp.fsf@fastmail.net> (raw)
In-Reply-To: <87pmd7ar8k.fsf@imperial.ac.uk>

Hi Thibault,

> -----
> @luispedrocoelho
> Me, 6 months ago: I am going to save this conda
> environment with all the versions of all the packages so it can be
> recreated later; this is Reproducible Science!
>
> conda, today: these versions don't work together, lol.
> -----
>
> I simply can't explain how such a behavior can happen.

The error message is not exactly as cited. Conda doesn't claim that
these versions don't work together, it claims that it cannot find a
combination of package known to work together and available in the
archive.

One possible reason for this is an update in conda's build
infrastructure. That's what happened to the software environment for the
reproducible research MOOC on Fun (of which I am an author). We
published the environment file, but a few months later conda could not
reconstruct it any more. They had updated the compiler infrastructure,
which requires a rebuild of all packages. But they didn't rebuild all
the versions from the past, so most older environment files became
unusable.

The lesson is that packages are reproducible only if you can re-run the
construction of the entire environment, from source code. Which is what
Guix can do (though if you actually have to do this, it will be a very
long process).

There may be other causes for the conda problem cited, I don't claim to
be an authority of conda! After the MOOC experience, I have never used
conda again.

> Is it the case that someone at Anaconda would modify some package,
> keeping the same version tag and other identifiers used by conda, whilst
> at the same time marking this package as incompatible with packages it
> was previously compatible with?

That's in a way what happened in my scenario: rebuilding with a new
compilation infrastructure produces different packages that share
version numbers and tags with the prior ones.

Cheers,
  Konrad.
-- 
---------------------------------------------------------------------
Konrad Hinsen
Centre de Biophysique Moléculaire, CNRS Orléans
Synchrotron Soleil - Division Expériences
Saint Aubin - BP 48
91192 Gif sur Yvette Cedex, France
Tel. +33-1 69 35 97 15
E-Mail: konrad DOT hinsen AT cnrs DOT fr
http://dirac.cnrs-orleans.fr/~hinsen/
ORCID: https://orcid.org/0000-0003-0330-9428
Twitter: @khinsen
---------------------------------------------------------------------


  reply	other threads:[~2022-11-28 19:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 17:28 Conda environments and reproducibility Thibault Lestang
2022-11-28 19:45 ` Konrad Hinsen [this message]
2022-11-29 10:32   ` Thibault Lestang
2022-11-29 13:12     ` Hugo Buddelmeijer
2022-11-29 13:39       ` Konrad Hinsen
2022-12-01 14:01         ` Hugo Buddelmeijer
2022-12-02 13:01           ` Konrad Hinsen
2022-11-29 20:10       ` Simon Tournier
2022-12-16 10:16         ` Thibault Lestang
2023-03-11 11:05           ` Ludovic Courtès
2023-03-11 11:43             ` Simon Tournier
2023-03-13 10:26               ` Lestang, Thibault
2023-03-13 11:00                 ` Ricardo Wurmus
2023-03-13 12:38                   ` Simon Tournier
2023-03-16 10:26                     ` Ludovic Courtès
2023-03-16 13:40                       ` Thibault Lestang
2023-04-03 15:22                         ` Simon Tournier
2023-04-04 12:19                           ` Thibault Lestang
2022-12-02 10:52       ` Ludovic Courtès
2022-12-02 11:05       ` Ludovic Courtès
2022-12-02 13:59         ` Simon Tournier
2022-12-02 14:06         ` Hugo Buddelmeijer
2022-11-28 20:46 ` Simon Tournier
2022-11-29 10:41   ` Thibault Lestang
2022-11-29 14:25     ` Simon Tournier

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=m1h6yioobp.fsf@fastmail.net \
    --to=konrad.hinsen@cnrs.fr \
    --cc=guix-science@gnu.org \
    --cc=t.lestang@imperial.ac.uk \
    /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).