bug#26949: Python path conflict

2017-05-18 Thread Pjotr Prins
On Thu, May 18, 2017 at 11:43:31AM +0200, Ludovic Court??s wrote: > Ooh, got it. I managed to reproduce it with a toy example. Should be > fixed in 22ef06b801b284760b4ffd9587ea1a3dffd31baa. Can you confirm? Fixed! Pj.

bug#26949: Python path conflict

2017-05-18 Thread Ludovic Courtès
Pjotr Prins skribis: > In ./guix/build/union.scm: > 117: 3 [union > "/gnu/store/b5rq0sl2jsqpqjxkhi68dy3racz1wfpv-profile/share/man/man1/python.1" > ...] > In unknown file: >?: 2 [partition # #] > In ./guix/build/union.scm: > 50: 1 [file-is-directory? > "/gnu/store/q5kdj7gpawi94pqd15x3wi

bug#26949: Python path conflict

2017-05-18 Thread Pjotr Prins
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 w

bug#26949: Python path conflict

2017-05-17 Thread Ludovic Courtès
Hello, Pjotr Prins skribis: > On Wed, May 17, 2017 at 03:08:05PM +0200, Ludovic Court??s wrote: >> Hi, >> >> Pjotr Prins skribis: >> >> > Note that I do most of my buiding with --no-grafts. >> >> This is an unsafe thing to do. > > Depends on the machine and what it is used for. Yes, for serv

bug#26949: Python path conflict

2017-05-17 Thread Pjotr Prins
On Wed, May 17, 2017 at 03:08:05PM +0200, Ludovic Court??s wrote: > Hi, > > Pjotr Prins skribis: > > > Note that I do most of my buiding with --no-grafts. > > This is an unsafe thing to do. Depends on the machine and what it is used for. Yes, for services that can be vulnerable you need to use

bug#26949: Python path conflict

2017-05-17 Thread Ludovic Courtès
Hi, Pjotr Prins skribis: > Note that I do most of my buiding with --no-grafts. This is an unsafe thing to do. > Using the Guix tree from source 4a3495d57c08dff9287fe559482a6d2009109304 > > ./pre-inst-env guix package -i python@2.7.13 > > renders [...] > In unknown file: >?: 0 [# # # #

bug#26949: Python path conflict

2017-05-17 Thread Pjotr Prins
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... --

bug#26949: Python path conflict

2017-05-16 Thread Pjotr Prins
Note that I do most of my buiding with --no-grafts. Not sure they are related: Using the Guix tree from source 4a3495d57c08dff9287fe559482a6d2009109304 ./pre-inst-env guix package -i python@2.7.13 renders Backtrace: In ice-9/eval.scm: 432: 19 [eval # #] In ice-9/boot-9.scm: 2412: 18 [save-