unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 56864-done@debbugs.gnu.org
Subject: bug#56864: qutebrowser: wrap-qt-process-path phase wrong type to string-append
Date: Mon, 01 Aug 2022 09:35:53 -0400	[thread overview]
Message-ID: <8735eg3x3a.fsf_-_@gmail.com> (raw)
In-Reply-To: <877d3s3yc8.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 01 Aug 2022 09:08:55 -0400")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello Jack,
>
> Jack Hill <jackhill@jackhill.us> writes:
>
>> X-Debbugs-CC: maxim.cournoyer@gmail.com
>>
>> With Guix 3a656ea836f87f30f1b34852cb4efc911363d2b4, qutebrowser's
>> wrap-qt-process-path phase fails. Maybe related to the recent Qt work
>> in <https://issues.guix.gnu.org/56771>? Build log attatched.
>
> Uh, this was unexpected.  I believe it's because label-less inputs are
> auto-generated via the package *name* rather than their variable name...
> Since qtwebengine-5 (the variable) still has the name "qtwebengine", the
> following code:
>
> (qt-process-path (string-append (assoc-ref inputs "qtwebengine-5")
>                                       "/lib/qt5/libexec/QtWebEngineProcess"))
>
> Doesn't actually find "qtwebengine-5" and it fails attempting to append
> #f to "/lib/qt5/libexec/QtWebEngineProcess.  The solution that comes to
> mind would be using:
>
> (file-input-search inputs "lib/qt5/libexec/QtWebEngineProcess").

Yep, that did it.

Fixed in aea756ea3312ba7e8229804492ba12001c8de568.

Closing.

Thanks for the report!

Maxim




  reply	other threads:[~2022-08-01 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  5:04 bug#56864: qutebrowser Jack Hill
2022-08-01 13:08 ` Maxim Cournoyer
2022-08-01 13:35   ` Maxim Cournoyer [this message]
2022-08-01 14:10     ` bug#56864: qutebrowser: wrap-qt-process-path phase wrong type to string-append Lars-Dominik Braun
2022-08-01 14:16       ` paren--- via Bug reports for GNU Guix
2022-08-01 14:40       ` paren--- via Bug reports for GNU Guix
2022-08-01 15:43         ` Maxim Cournoyer

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=8735eg3x3a.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=56864-done@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    /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).