all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bryan Paronto <bryan@cablecar.digital>
To: 55003@debbugs.gnu.org
Subject: bug#55003: emacs-dash test failing,
Date: Mon, 18 Apr 2022 06:23:08 -0500	[thread overview]
Message-ID: <CAD=1s9f6u0H+EZK2ODCQNSYoK_=S7P=-neSidUB-1NkBx5HotQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hello Guixers

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.

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.

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.

Best Regards,

Bryan Paronto
bryan@cablecar.digital

-- 
*Bryan Paronto*
Software Engineer, Principal Consultant
bryan@cablecar.digital | 239.200.2312
Book A Meeting with Me <https://calendly.com/bryan-cablecar-digital/30>
<http://cablecar.digital>

[-- Attachment #2: Type: text/html, Size: 2073 bytes --]

             reply	other threads:[~2022-04-20 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 11:23 Bryan Paronto [this message]
2022-04-19  7:58 ` bug#55003: emacs-dash test failing, Liliana Marie Prikler
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD=1s9f6u0H+EZK2ODCQNSYoK_=S7P=-neSidUB-1NkBx5HotQ@mail.gmail.com' \
    --to=bryan@cablecar.digital \
    --cc=55003@debbugs.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 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.