All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Loic Dachary <loic@dachary.org>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Virtualenv tests still nort running...
Date: Tue, 29 Mar 2016 17:12:28 +0200	[thread overview]
Message-ID: <56FA9B5C.5060307@digiware.nl> (raw)
In-Reply-To: <56FA74F4.5040905@dachary.org>

On 29-3-2016 14:28, Loic Dachary wrote:
> Hi Willem,
> 
> This has undergone various fixes all of them wrong in a context or
> another. The last of them is (hopefully ;-)
> https://github.com/ceph/ceph/pull/8320

Hi Loic,

I watched the discussion carefully, and was under the assemption that
everything was already merged. But I'll take your pull and see what happens.

--WjW

> Cheers
> 
> On 29/03/2016 13:31, Willem Jan Withagen wrote:
>> 
>> Hi,
>> 
>> I have rebased to the most recent HEAD before building verything
>> again. But the testrun still is unable to get the virtualenv
>> correct.
>> 
>> Suggestions on how to diagnose this?
>> 
>> =========== cp -f ./fetch_config ./sample.fetch_config cd
>> ./ceph-detect-init ; ../tools/setup-virtualenv.sh ; test -d
>> wheelhouse && export NO_INDEX=--no-index ; virtualenv/bin/pip
>> install $NO_INDEX --use-wheel --find-links=file://$(pwd)/wheelhouse
>> -e . /bin/sh: ../tools/setup-virtualenv.sh: not found /bin/sh:
>> virtualenv/bin/pip: not found Makefile:32259: recipe for target
>> 'ceph-detect-init/virtualenv' failed ===========
>> 
>> path for setup-virtual ./src/tools/setup-virtualenv.sh
>> 
>> =========== cat ./src/tools/setup-virtualenv.sh rm -fr virtualenv 
>> virtualenv virtualenv . virtualenv/bin/activate # older versions of
>> pip will not install wrap_console scripts # when using wheel
>> packages pip --log virtualenv/log.txt install --upgrade 'pip >=
>> 6.1' if test -d wheelhouse ; then export NO_INDEX=--no-index fi pip
>> --log virtualenv/log.txt install $NO_INDEX --use-wheel
>> --find-links=file://$(pwd)/wheelhouse --upgrade di stribute pip
>> --log virtualenv/log.txt install $NO_INDEX --use-wheel
>> --find-links=file://$(pwd)/wheelhouse 'tox >=1.9' if test -f
>> requirements.txt ; then pip --log virtualenv/log.txt install
>> $NO_INDEX --use-wheel --find-links=file://$(pwd)/wheelhouse -r
>> requi rements.txt fi =========== Perhaps here the virtualenv paths
>> need to be converted into SHELLVARs as well?
>> 
>> --WjW -- To unsubscribe from this list: send the line "unsubscribe
>> ceph-devel" in the body of a message to majordomo@vger.kernel.org 
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> 
> 


  reply	other threads:[~2016-03-29 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 11:31 Virtualenv tests still nort running Willem Jan Withagen
2016-03-29 12:28 ` Loic Dachary
2016-03-29 15:12   ` Willem Jan Withagen [this message]
2016-03-30  9:25     ` Willem Jan Withagen
2016-03-30 10:10       ` Loic Dachary
2016-03-30 20:39         ` Willem Jan Withagen
2016-03-31  9:31           ` Loic Dachary
2016-03-31 10:04             ` Willem Jan Withagen
2016-03-31 10:14               ` Loic Dachary
     [not found]                 ` <56FCFD69.10307@digiware.nl>
2016-03-31 11:14                   ` Loic Dachary
2016-03-31 11:47                     ` Willem Jan Withagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56FA9B5C.5060307@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.