Install fails with namespace pkg + data

[Tom Davis]

If I have a project layout such as,

+ foo/
-- setup.py
-- setup.cfg
+ nspkg/
-- -- __init__.py
-- + pkg/
-- -- __init__.py
-- -- + data/
-- -- -- conf/

And a setup.cfg such as,

[files]
namespace_packages = nspkg
packages = nspkg.pkg

Then running `setup.py install` (or `pip install .`) will result in a failure,

error: can't copy 'nspkg/pkg/data/conf': doesn't exist or not a regular file

This does *not* happen when using a manually-written setup.py

[Tom Davis (09rp9wq1q1h0lx-tom)]

I should mention it also doesn't happen when running `setup.py develop`, presumably because nothing is being copied.

[Doug Hellmann (doug-hellmann)]

In your example, it appears that conf is a directory. If I set up the structure you describe and include a file in that directory it is packaged when I use pbr 0.10.0. When I do not include a file in that directory, the nspkg/pkg/data/conf directory is not included in the sdist, but I don't get any errors installing the package.

Which version of pbr were you using when you encountered the problem?

[Robert Collins (lifeless)]

To avoid any ambiguity, could you please attach a tarball which minimally demonstrates the issue? Thanks.

[Tom Davis (09rp9wq1q1h0lx-tom)]

Robert,

Sorry, I gave up on getting PBR to work months ago. I actually submitted a patch via GitHub for this issue, including an explanation of what the root problem turned out to be. It was automatically closed, however, and I lost interest before making it through the OpenStack contribution document. If the problem hasn't been fixed yet, feel free to use this however you see fit: https://github.com/openstack-dev/pbr/pull/9

[Allen Riddell (ariddell)]

I think this is being addressed in https://bugs.launchpad.net/pbr/+bug/1530867