PBR

oslo.concurrency doesn't get openstack/common installed correctly

Bug #1405101 reported by Thomas Goirand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PBR
Invalid
Undecided
Unassigned

Bug Description

During the build of cinder (Kilo, beta 1), I noticed that it couldn't find oslo-concurrency/openstack/common/fileutils.py. In fact, oslo.concurrency doesn't get the openstack folder installed in the non-namespaced folder. I had to do this in my Debian package to fix the issue:

override_dh_install:
        set -e ; for pyvers in $(PYTHONS); do \
                python$$pyvers setup.py install --install-layout=deb \
                        --root $(CURDIR)/debian/python-oslo.concurrency; \
                cp -r oslo_concurrency/openstack $(CURDIR)/debian/python-oslo.concurrency/usr/lib/python$$pyvers/dist-packages/oslo_concurrency ; \
        done

This shouldn't be normally needed, and must be fixed upstream.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

I'm not able to reproduce this on my system. Which version of pbr are you using?

Changed in pbr:
status: New → Incomplete
Revision history for this message
Thomas Goirand (thomas-goirand) wrote :

Hi,

I'm using PBR 0.10.7 currently, but I had the issue with older versions too. FYI, I also had the issue with oslo.messaging. In oslo.messaging, I had to add:

recursive-include oslo *

in the MANIFEST.in

For oslo.concurency, I did add this to the MANIFEST.in:

recursive-include oslo_concurrency *.py
+recursive-include oslo/concurrency *.py

(and yes, unfortunately, some stuff in Kilo RC1 are still using the namespace...)

If you want to reproduce the build, you can read on instructions here:

http://openstack.alioth.debian.org/

I have no idea how to reproduce that issue in a non-package-building env, though with the instructions above, it should be fairly easy to install sbuild and all.

Revision history for this message
Robert Collins (lifeless) wrote :

Please try with master. Thanks!

Revision history for this message
Robert Collins (lifeless) wrote :

Closing due to no feedback. Please reopen if confirmed with 1.2.0.

Changed in pbr:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.