unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 55003-done@debbugs.gnu.org, Bryan Paronto <bryan@cablecar.digital>
Subject: bug#55003: emacs-dash test failing,
Date: Wed, 08 Jun 2022 16:34:17 -0400	[thread overview]
Message-ID: <877d5qki7q.fsf@gmail.com> (raw)
In-Reply-To: <f9b630117f022e42f2fabab2c9feb42cbe7782bf.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Tue, 19 Apr 2022 09:58:26 +0200")

Hello,

Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:

> 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?

It builds repeatedly fine for me as well.

Closing, but do reopen if you can reproduce on a fresh Guix commit.

Maxim




      reply	other threads:[~2022-06-08 20:37 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
2022-06-08 20:34   ` Maxim Cournoyer [this message]

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=877d5qki7q.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55003-done@debbugs.gnu.org \
    --cc=bryan@cablecar.digital \
    --cc=liliana.prikler@ist.tugraz.at \
    /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).