unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Guu, Jin-Cheng" <jin-cheng.guu@stonybrook.edu>,
	Mathieu Othacehe <othacehe@gnu.org>
Cc: 53594@debbugs.gnu.org
Subject: bug#53594: no matching pattern #<package polkit..
Date: Fri, 22 Apr 2022 17:44:15 +0200	[thread overview]
Message-ID: <87k0bh3yy8.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAErjG5efUuB7aW-x13whyXQKNsbWB2A_NqcqFUnWp81Ca2iPpQ@mail.gmail.com>

Hello everyone,

Someone reported the exact same issue today on IRC [1], with polkit
being the culprit.  With a bigger backtrace, the match error happens at
line 901 in guix/gexp.scm, in the match inside the return part of
lower-inputs.  This suggests that lower-object doesn't manage to return
a derivation but only the polkit package.  I suspect that this has to do
with the complex polkit package interactions that we have, with polkit
being an identifier syntax for either polkit-mozjs or polkit-duktape,
with duktape package/inherit'ing polkit-mozjs with is itself replaced by
polkit-mozjs/fixed.

Maybe there's an interaction with the caching as well, while grafting
and looping?

I've tried to reproduce this locally by building a gexp that has either
polkit, polkit-duktape or polkit-mozjs as an input, enabling or
disabling fallback or grafting, to no avail.

Maybe someone else has another idea?

[1] https://logs.guix.gnu.org/guix/2022-04-22.log#154402

Best,
-- 
Josselin Poiret




  reply	other threads:[~2022-04-22 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  1:45 bug#53594: no matching pattern #<package polkit Guu, Jin-Cheng via Bug reports for GNU Guix
2022-02-02 17:28 ` Mathieu Othacehe
2022-02-02 17:31   ` Guu, Jin-Cheng via Bug reports for GNU Guix
2022-04-22 15:44     ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-05-11 20:15       ` Ludovic Courtès
2022-05-14 15:55         ` Ludovic Courtès
2022-11-20 21:27           ` Ludovic Courtès
2022-11-21  8:32             ` Mathieu Othacehe

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=87k0bh3yy8.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=53594@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=jin-cheng.guu@stonybrook.edu \
    --cc=othacehe@gnu.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).