From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 36708@debbugs.gnu.org
Subject: bug#36708: Serving an up-to-date https://guix.gnu.org/packages
Date: Thu, 22 Aug 2019 17:24:53 +0200 [thread overview]
Message-ID: <87r25dp6ii.fsf@gnu.org> (raw)
In-Reply-To: <87k1cga1dt.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 17 Jul 2019 21:48:14 +0200")
Hello!
Ludovic Courtès <ludo@gnu.org> skribis:
> The package list at <https://guix.gnu.org/packages> is made from the
> current ‘guix’ package, not from the latest ‘master’. We should
> work to build it dynamically with something like hpcguix-web, or to
> generate it from an inferior of ‘master’.
I went for the latter option in commit
9dbb0073be83c25b44400a62ec22d0b240a88130 of guix-artwork.git.
That approach was also motivated by the fact that people would get
different behavior depending on whether their ‘guix’ package depends on
guile-json@1 or @3, as reported by nixo on IRC.
That’s also the reason why the web site was no longer updated since
9c6f714305460e99c681d9b7f368e13bfe49fdd9 was pushed: the ‘guix’ on
berlin is still on guile-json@1, but said commit expects guile-json@3.
If everything goes well, we should see an up-to-date list at
<https://guix.gnu.org/packages> within 40 minutes.
Ludo’.
next prev parent reply other threads:[~2019-08-22 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 18:50 bug#36708: guix.gnu.org/packages is 6 weeks stale, claims recent update Mark H Weaver
2019-07-17 19:48 ` bug#36708: Serving an up-to-date https://guix.gnu.org/packages Ludovic Courtès
2019-08-22 15:24 ` Ludovic Courtès [this message]
2019-08-22 21:11 ` Mark H Weaver
2019-07-17 20:00 ` bug#36708: guix.gnu.org/packages is 6 weeks stale, claims recent update Ricardo Wurmus
2019-07-17 20:03 ` 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
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=87r25dp6ii.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36708@debbugs.gnu.org \
--cc=mhw@netris.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 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).