all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 51413@debbugs.gnu.org
Subject: [bug#51413] [PATCH 00/45] Stackage update to 18.14
Date: Thu, 28 Oct 2021 16:19:40 +0200	[thread overview]
Message-ID: <87ilxh5j0j.fsf@gnu.org> (raw)
In-Reply-To: <YXfvA0C+smxZt+9i@noor.fritz.box> (Lars-Dominik Braun's message of "Tue, 26 Oct 2021 14:05:23 +0200")

Hi!

Lars-Dominik Braun <lars@6xq.net> skribis:

> this is another episode in the never-ending quest to keep Haskell packages
> updated. This series only updates packages on Stackage by running
>
> 	guix refresh -u -t stackage 2>&1 | tee upgrades.log
>
> and adjusting dependency changes by hand

Adjusting them by hand following recommendations printed by ‘guix
refresh’?

We should get ‘guix refresh’ to apply input changes directly.

> and then running etc/committer.scm to create the commits
> themselves. It looks like `guix refresh` swallows exceptions and
> there’s a bug somewhere in the Stackage updater, so this process needs
> to be repeated until there are no more updates.

Uh, would be nice to investigate.

> There is a branch wip-stackage-18.14, which has been run through the CI
> successfully: https://ci.guix.gnu.org/jobset/wip-stackage-18.14

If CI doesn’t report a greater number of build failures compared to the
base commit, I’d say you can go ahead and merge.

Thank you for this herculean effort!

Ludo’.




  reply	other threads:[~2021-10-28 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 12:05 [bug#51413] [PATCH 00/45] Stackage update to 18.14 Lars-Dominik Braun
2021-10-28 14:19 ` Ludovic Courtès [this message]
2021-10-29 18:02   ` Lars-Dominik Braun
2021-11-02 18:01 ` bug#51413: " Lars-Dominik Braun

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=87ilxh5j0j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=51413@debbugs.gnu.org \
    --cc=lars@6xq.net \
    /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.