From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pjotr Prins Subject: bug#26949: Python path conflict Date: Thu, 18 May 2017 10:36:08 +0200 Message-ID: <20170518083608.GA24424@thebird.nl> References: <20170516100008.GA8723@thebird.nl> <878tlvy6kq.fsf@gnu.org> <20170517132312.GA17216@thebird.nl> <87vaozuun4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48339) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dBGvh-0002go-Li for bug-guix@gnu.org; Thu, 18 May 2017 04:37:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dBGve-0001WM-K0 for bug-guix@gnu.org; Thu, 18 May 2017 04:37:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:49176) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dBGve-0001WE-GX for bug-guix@gnu.org; Thu, 18 May 2017 04:37:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dBGve-0000cd-2g for bug-guix@gnu.org; Thu, 18 May 2017 04:37:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87vaozuun4.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic Court??s Cc: 26949@debbugs.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. --