Re: Python package issues

[Greg Troxel <gdt%lexort.com@localhost>]

Sad Clouds <cryintothebluesky%gmail.com@localhost> writes:

> On Thu, May 23, 2019 at 7:40 PM Greg Troxel <gdt%lexort.com@localhost> wrote:
>>
>> Sad Clouds <cryintothebluesky%gmail.com@localhost> writes:
>>
>> > Well, something is not right here. I completely removed /usr/pkg and
>> > build directories, and started from scratch but I'm getting this error
>>
>> But are you removing the work directories *every time* before you build
>> things?
>
> Yes, but not for every package. I completely removed /usr/pkg and all
> object/work directories and started from a clean slate. So it's either
> pkgsrc or my config is broken somewhere, or I have issues with file
> system that resurrects deleted files. This is on raspberry pi 3. I
> have a script that has a list of packages I want to build and for each
> package it builds and installs it, so I don't remove work directories
> for each package, but I do remove all work directories prior to
> running this script.

The basic problem is that the work directory for py37-foo and py27-foo
is the same directory.  So if one has been built, and not cleaned, then
the dependency on the other can run into trouble.  Yes, this is a bug
and should be fixed, but that needs a clean well-thought-out patch, not
reports :-)

So remove all the work directories before building each package, if you
don't run "make clean clean-depends" after each one.  And then if you
get an error, look to see if they are there, and what's in them.  Then
remove them all like you've been told, and build the troublesome package
again.