all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 72257@debbugs.gnu.org, Julien Lepiller <julien@lepiller.eu>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#72257: Non-English manuals for 1.4.0 are unavailable
Date: Thu, 25 Jul 2024 14:41:21 +0200	[thread overview]
Message-ID: <878qxpzlse.fsf@pelzflorian.de> (raw)
In-Reply-To: <87ttgesrxd.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Wed, 24 Jul 2024 17:58:22 +0200")

Could someone knowledgeable in maintenance.git in
hydra/modules/sysadmin/web.scm change the guix-extensions to use an
older guix package earlier than June 2024, such as guix version 1.4.0?

I try

((options->transformation '((with-commit . "guix=v1.4.0"))) guix)

but could it be made to get a guix@1.4.0 with substitutes instead?

Or should it define a new guix@1.4.0 package with (package (inherit
guix))?

Should it look more like how guix.git’s guix/scripts/time-machine.scm
uses old guix?

Then the doc/build.scm would again @@ out to a (guix self) module that
does not require po4a.cfg, which is not yet present when building old
guix’s manual.

Regards,
Florian




  reply	other threads:[~2024-07-25 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 14:36 bug#72257: Non-English manuals for 1.4.0 are unavailable Ludovic Courtès
2024-07-23 15:18 ` Ludovic Courtès
2024-07-23 19:59   ` Maxim Cournoyer
2024-07-24 10:04   ` pelzflorian (Florian Pelz)
2024-07-24 11:34     ` pelzflorian (Florian Pelz)
2024-07-24 15:58       ` pelzflorian (Florian Pelz)
2024-07-25 12:41         ` pelzflorian (Florian Pelz) [this message]
2024-07-25 22:32       ` Ludovic Courtès
2024-07-27  8:34         ` pelzflorian (Florian Pelz)
2024-07-28  7:35           ` pelzflorian (Florian Pelz)

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=878qxpzlse.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=72257@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@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 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.