From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ludovic Court??s <ludo@gnu.org>
Cc: 26949@debbugs.gnu.org
Subject: bug#26949: Python path conflict
Date: Thu, 18 May 2017 10:36:08 +0200 [thread overview]
Message-ID: <20170518083608.GA24424@thebird.nl> (raw)
In-Reply-To: <87vaozuun4.fsf@gnu.org>
On Wed, May 17, 2017 at 09:54:07PM +0200, Ludovic Court??s wrote:
> > I remember the python.1 path is a symlink not pointing anywhere. We
> > dealt with that a year ago. Maybe it now confuses the man db builder.
> > Does it somehow use the (existing) profile?
>
> Yes, it could be that it happens with a particular combination of
> packages in the profile.
>
> Could you try to see if you could reproduce the problem in a fresh
> profile starting from what the offending profile has and gradually
> reducing the package set?
I can reproduce the problem, but I can not reproduce the environment.
I tried.
All I can see is that when the profile gets updated the new path
$profile/share/man/man1/python.1
is a symlink pointing to nothing. You can see that when installing
python-2.7.13.
All I can tell is that the version that was installed (2.7.11).
actually pointed to something. When overwriting the old version,
strangely, the man pages generator balks.
Strangely because installing in a fresh profile gives no complaints.
The old package path was
/gnu/store/vcx1n5nj4gr52xx5m6gvi7zrwngy06s3-python-2.7.11/share/man/man1/python.1
Pj.
--
next prev parent reply other threads:[~2017-05-18 8:37 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
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 [this message]
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=20170518083608.GA24424@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=26949@debbugs.gnu.org \
--cc=ludo@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).