From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 26949@debbugs.gnu.org
Subject: bug#26949: Python path conflict
Date: Wed, 17 May 2017 12:42:15 +0200 [thread overview]
Message-ID: <20170517104215.GA16273@thebird.nl> (raw)
In-Reply-To: <20170516100008.GA8723@thebird.nl>
The two errors are not related. When I choose a different target
profile the second error goes away.
In a clean profile both errors will probably go away...
--
next prev parent reply other threads:[~2017-05-17 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 10:00 bug#26949: Python path conflict Pjotr Prins
2017-05-17 10:42 ` Pjotr Prins [this message]
2017-05-17 13:08 ` Ludovic Courtès
2017-05-17 13:23 ` Pjotr Prins
2017-05-17 19:54 ` Ludovic Courtès
2017-05-18 8:36 ` Pjotr Prins
2017-05-18 9:43 ` Ludovic Courtès
2017-05-19 6:33 ` Pjotr Prins
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=20170517104215.GA16273@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=26949@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 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).