From: P via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Kyle Andrews <kyle.c.andrews@gmail.com>
Cc: "37803@debbugs.gnu.org" <37803@debbugs.gnu.org>
Subject: bug#37803: [BUG] installer does seem to know about pep8 patch
Date: Fri, 18 Oct 2019 09:35:15 +0000 [thread overview]
Message-ID: <9fnWK4-PhOB_Or7pufLWK7LmQ6-KqZTgCwJA_EXD7ubUc-xzip_65Ji2Jq0VfsNGlvaZk9X6G3OFxpctDCMmPQ0qt__4gb4VFMlvV9iXtwQ=@protonmail.com> (raw)
In-Reply-To: <87eezabwg2.fsf@gmail.com>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, October 18, 2019 2:48 AM, Kyle Andrews <kyle.c.andrews@gmail.com> wrote:
> I just tried to install guix on desktop system by piggy-backing from a
> disk-image created on a laptop.
>
> I chose "Guided - using the entire disk with encryption" option.
>
> I then selected GNOME, openbox, and ratpoison to be installed as desktop
> environments. I'm not sure if that's relevant, but wanted to be thorough
> in case this may be limited to a GNOME issue.
>
> The installation errored out with the following message:
>
> > guix system: error: python-pep8-stdlib-tokenize-compat.patch: patch not found
>
> Thus the guix on the disk image seems to be missing the patch mentioned
> in the issue below (corresponding to the python-pep8 package):
>
> https://issues.guix.gnu.org/issue/36643
The patch seems to be present in the latest master. I don't have space to test out the installer.
prev parent reply other threads:[~2019-10-18 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 2:48 bug#37803: [BUG] installer does seem to know about pep8 patch Kyle Andrews
2019-10-18 9:35 ` P via Bug reports for GNU Guix [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='9fnWK4-PhOB_Or7pufLWK7LmQ6-KqZTgCwJA_EXD7ubUc-xzip_65Ji2Jq0VfsNGlvaZk9X6G3OFxpctDCMmPQ0qt__4gb4VFMlvV9iXtwQ=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=37803@debbugs.gnu.org \
--cc=kyle.c.andrews@gmail.com \
--cc=pronaip@protonmail.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 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.