unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 51986@debbugs.gnu.org
Subject: [bug#51986] [PATCH] Add tlpui
Date: Fri, 26 Nov 2021 09:36:17 +0100	[thread overview]
Message-ID: <874k7zqpoe.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ee74mmuu.fsf@gnu.org> (Mathieu Othacehe's message of "Thu, 25 Nov 2021 12:38:33 +0000")

Hello,

Mathieu Othacehe <othacehe@gnu.org> writes:

Thanks for the feedback.

> When trying to build the following patch on the c-u-f branch, I have the
> following error:

[...]

> error: in phase 'sanity-check': uncaught exception:
> %exception #<&invoke-error program: "python" arguments: ("/gnu/store/nwwr89v2vyg1hs48i49m083vhczsgh3m-sanity-check.py" "/gnu/store/xjvdm652mfks314s1lnvwinn6pnrbz5a-tlpui-1.4.0/lib/python3.9/site-packages") exit-status: 1 term-signal: #f stop-signal: #f> 
> phase `sanity-check' failed after 0.2 seconds
> command "python" "/gnu/store/nwwr89v2vyg1hs48i49m083vhczsgh3m-sanity-check.py" "/gnu/store/xjvdm652mfks314s1lnvwinn6pnrbz5a-tlpui-1.4.0/lib/python3.9/site-packages" failed with status 1

I disabled tests in the package definition because the program insists
on reading "/etc" directory. 

However, c-u-f added a new phase, `sanity-check' which has the same
issue (trying to read "/etc"). We could delete that phase too, but I'm
not sure about the consequences.

Meawhile, there's the upstream pending open issue:
<https://github.com/d4nj1/TLPUI/issues/86>

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2021-11-26  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 21:36 [bug#51986] [PATCH] Add tlpui Nicolas Goaziou
2021-11-25 12:38 ` Mathieu Othacehe
2021-11-26  8:36   ` Nicolas Goaziou [this message]
2021-12-21 21:25 ` bug#51986: " Nicolas Goaziou

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=874k7zqpoe.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=51986@debbugs.gnu.org \
    --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).