all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 51837-done@debbugs.gnu.org
Subject: bug#51837: [Cuirass] Wrong type: #f in cuirass/templates.scm
Date: Mon, 29 Nov 2021 14:26:29 +0100	[thread overview]
Message-ID: <87tufvjdoa.fsf@gnu.org> (raw)
In-Reply-To: <87k0hb0ygk.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sun, 14 Nov 2021 12:25:29 +0100")


Hello Tobias,

This error was likely caused by the core-updates-frozen-batched-changes
specification removal in Cuirass. Some builds keep referring to removed
specifications causing unexpected behaviours.

The strange thing is that I'm using the "DELETE CASCADE" SQL property
that should remove Builds pointing to a removed specification
automatically.

Regardless of this misunderstanding, it might not be great idea to
remove specifications altogether because a build that is added by the
core-updates-frozen specification might be referred by the master
specification once the merge has happened.

I introduced specification deactivation with
https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=b362f06b9134f99a476e0f2ec32335ce6ddc6e8c
to work around this problem.

This is not yet deployed, but I think it should solve the issue you
reported.

Thanks,

Mathieu






  reply	other threads:[~2021-11-29 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14 11:14 bug#51837: [Cuirass] Wrong type: #f in cuirass/templates.scm Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-11-14 11:25 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-11-29 13:26   ` Mathieu Othacehe [this message]
2021-11-14 16:31 ` John Kehayias via Bug reports for GNU Guix
2021-11-14 16:59   ` John Kehayias via Bug reports for GNU Guix

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=87tufvjdoa.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=51837-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.