It's most likely unrelated to your problem, but...
* Thomas Goirand , 2014-08-12, 02:51:
set -e && set -x && for i in 2.7 $(PYTHON3S) ; do \
"set -e" has no effect on statements that use "&&".
So you probably want s/&&/;/g here.
TEMP_REZ=`mktemp -t` && \
> override_dh_auto_test:
> ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
> @echo "===> Running tests"
> set -e && set -x && for i in 2.7 $(PYTHON3S) ; do \
> PYMAJOR=`echo $$i | cut -d'.' -f1` ; \
> echo "===> Testing with python$$i (python$$PYM
On 08/11/2014 07:30 PM, Piotr Ożarowski wrote:
> [Thomas Goirand, 2014-08-11]
>> During the build of oslo packages for OpenStack, I'm having the issue
>> that python3 seems to first look into
>> /usr/lib/python3.4/dist-packages/olso, finds stuff in it, and then do
>
> set PYTHONPATH to local dir w
[Thomas Goirand, 2014-08-11]
> During the build of oslo packages for OpenStack, I'm having the issue
> that python3 seems to first look into
> /usr/lib/python3.4/dist-packages/olso, finds stuff in it, and then do
set PYTHONPATH to local dir with your module ("." or where your build
target copies/c
Hi,
During the build of oslo packages for OpenStack, I'm having the issue
that python3 seems to first look into
/usr/lib/python3.4/dist-packages/olso, finds stuff in it, and then do
not search in the local directory. Because of that, unit tests are
failing during the build. For example, when tryin
5 matches
Mail list logo
