From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Bryan Paronto <bryan@cablecar.digital>, 55003@debbugs.gnu.org
Subject: bug#55003: emacs-dash test failing,
Date: Tue, 19 Apr 2022 09:58:26 +0200 [thread overview]
Message-ID: <f9b630117f022e42f2fabab2c9feb42cbe7782bf.camel@ist.tugraz.at> (raw)
In-Reply-To: <CAD=1s9f6u0H+EZK2ODCQNSYoK_=S7P=-neSidUB-1NkBx5HotQ@mail.gmail.com>
Am Montag, dem 18.04.2022 um 06:23 -0500 schrieb Bryan Paronto:
> Hello Guixers
Hi Bryan
> I’ll prefacing by saying I’m still rather green to Guix System and
> Home, but am loving every minute of hacking, even when things dont
> immediate go according to plan.
>
> This morning I’m attempting to use Guix for all of my Emacs package
> management needs, however one package, emacs-dash-2.19.1 seems to be
> failing to build. According to the logs, this is due to a long-than-
> 80-character doctring. According to their repository, this issue has
> been address, but a new release has not yet been cut containing the
> fix.
That's rather peculiar given that emacs-dash builds fine in CI as far
as I am aware. I also have a build locally cached.
/gnu/store/63r1i2mpgivb2f99h2dscmrymcv9n257-emacs-dash-2.19.1
On which Guix commit are you currently? Do you perhaps use a channel,
that provides its own definition of emacs-dash?
> What is the prescribed way of addressing such an issue, where emacs-
> dash is an input on one or more of the packages I’m attempting to
> install as part of my reconfigure.
The short fix would be to cut out emacs-dash from your config for now.
Use `guix graph' to find out what pulls it in. The long fix would be
to find out what makes emacs-dash fail and repair that.
> I’ve run `guix pull' and `guix package -u' . I’m uncertain of
> creating a new package definition with tests disabled would be the
> solution, but I’ve yet to try.
You can use a transformation for that, it's called --without-tests.
Using it does not guarantee a successful build, though.
Cheers
next prev parent reply other threads:[~2022-04-19 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 11:23 bug#55003: emacs-dash test failing, Bryan Paronto
2022-04-19 7:58 ` Liliana Marie Prikler [this message]
2022-06-08 20:34 ` 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=f9b630117f022e42f2fabab2c9feb42cbe7782bf.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=55003@debbugs.gnu.org \
--cc=bryan@cablecar.digital \
/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).