unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 60629@debbugs.gnu.org, h.goebel@crazy-compilers.com
Subject: [bug#60629] [PATCH 0/3] Add '--with-version' package transformation
Date: Fri, 13 Jan 2023 12:12:17 +0100	[thread overview]
Message-ID: <87mt6melim.fsf@gnu.org> (raw)
In-Reply-To: <87o7r3wy55.fsf@gmail.com> (Simon Tournier's message of "Thu, 12 Jan 2023 16:49:58 +0100")

Hello!

Simon Tournier <zimon.toutoune@gmail.com> skribis:

> On sam., 07 janv. 2023 at 16:04, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Now that updaters can (to some extent) import any upstream version, we
>> can provide a ‘--with-version’ package transformation option that picks
>> the given upstream version.
>
> Well, transformation bypasses the checksum control and so it is not
> really a fixed-output, right?

It’s not fixed-output at all because we don’t know in advance what we’ll
get from that download.

> Therefore, the result depends on the state of the world and thus it is
> not necessary reproducible.

Absolutely.

[...]

> All that said, this option is cool to have. :-) It is missing some
> guards, IMHO.  Maybe:
>
>  1. Wording some warning for the manual

Will do, that makes a lot of sense to me, I share your concerns.

>  2. Add comments about reproducibility when exporting manifest with
>     transformations; for example,
>
>     (define transform1
>       ;; WARNING: some transformation might lead to non-reproducible profile.
>       ;; For more details, please see the Package Transformation Options section.
>       (options->transformation
>         '((with-version . "python-numpy=1.22.4")
>           (with-c-toolchain . "python-scipy=gcc-toolchain@7"))))

This one’s a bit more involved technically because we don’t use (guix
read-print) yet here, so I prefer to do that separately.

>  3. Add a warning.  Similarly, to this:
>
>    warning: cannot authenticate source of 'python-numpy', version 1.22.4
>
>    For instance,
>
>    warning: transformation for 'python-numpy' with version 1.22.4 might be non-reproducible

I wonder about this one because it would be displayed unconditionally,
there’s no “I understand the risks” button one can click to make it
disappear.  I’d lean towards making a prominent warning in the manual
and not have a warning message every time here, dunno.

Thoughts?

Thanks for your feedback!

Ludo’.




  reply	other threads:[~2023-01-13 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 15:04 [bug#60629] [PATCH 0/3] Add '--with-version' package transformation Ludovic Courtès
2023-01-07 15:06 ` [bug#60629] [PATCH 1/3] transformations: Add '--with-version' Ludovic Courtès
2023-01-07 15:06   ` [bug#60629] [PATCH 2/3] transformations: Let users know when '--with-latest' has no effect Ludovic Courtès
2023-01-07 15:06   ` [bug#60629] [PATCH 3/3] DRAFT news: Add entry for '--with-version' Ludovic Courtès
2023-01-09 18:13     ` pelzflorian (Florian Pelz)
2023-01-07 16:05 ` [bug#60629] [PATCH 0/3] Add '--with-version' package transformation Hartmut Goebel
2023-01-12 15:49 ` Simon Tournier
2023-01-13 11:12   ` Ludovic Courtès [this message]
2023-01-13 17:00     ` Simon Tournier
2023-01-16 12:45       ` bug#60629: " Ludovic Courtès

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=87mt6melim.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=60629@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=zimon.toutoune@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).