unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: sirgazil <sirgazil@zoho.com>, 40079@debbugs.gnu.org
Subject: bug#40079: emacs-elpy-1.31.0: failed to build
Date: Fri, 20 Mar 2020 18:05:55 -0400	[thread overview]
Message-ID: <87tv2iisvw.fsf@gmail.com> (raw)
In-Reply-To: <87v9mylmd7.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 20 Mar 2020 22:58:28 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>>
>>> I couldn't upgrade the packages in my user profile because "emacs-elpy" check phase fails. 
>>>
>>>
>>> ## Steps to reproduce
>>>
>>> 1. guix pull
>>> 2. guix build emacs-elpy
>>>
>>>
>>> ## Unexpected result
>>>
>>>
>>> The output of the check phase:
>>>
>>> ---------------------------
>>> starting phase `check'
>>>
>>> Can’t guess python-indent-offset, using defaults: 4
>>
>> This seems to stem from the update of 'python-black' in
>> 5f603fab23e7df7e7b76566b3add24b65e92f807.  Reverting that commit makes
>> this package build.
>>
>> @Ricardo: Any objections to reverting the commit?
>
> I’d rather not revert but add an older variant of python-black for elpy.

Perhaps the issue would vanish if we move to Elpy 1.32?  I had started
packaging it, but hit some issues.

Maxim

  reply	other threads:[~2020-03-20 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 17:27 bug#40079: emacs-elpy-1.31.0: failed to build sirgazil via Bug reports for GNU Guix
2020-03-20 17:57 ` Marius Bakke
2020-03-20 21:58   ` Ricardo Wurmus
2020-03-20 22:05     ` Maxim Cournoyer [this message]
2020-03-20 22:32       ` Marius Bakke
2020-03-23  1:49         ` 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=87tv2iisvw.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40079@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    --cc=sirgazil@zoho.com \
    /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).