You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ariatosca.apache.org by DeWayne Filppi <de...@cloudify.co> on 2017/11/29 19:08:33 UTC
problem using cloudify extension with dev branch
I see the following when trying to install the cloudify extension with the
ARIA-1 branch:
Installing collected packages: apache-ariatosca, aria-extension-cloudify
Found existing installation: apache-ariatosca 0.2.0
Uninstalling apache-ariatosca-0.2.0:
Then it fails.
Re: problem using cloudify extension with dev branch
Posted by Maxim Orlov <ma...@cloudify.co>.
The extension repo was built based on Aria 0.1.1 base code. The dependency
is strictly set to 0.1.1 , which kinda make sense since 0.2.0 wasn't (and
still isn't) released. It probably uninstalls the 0.2.0 one and installs
0.1.1 instead, which sound to me as a wanted behavior.
On Thu, Nov 30, 2017, 01:06 Tal Liron <ta...@cloudify.co> wrote:
> Ah, the dreaded multi-repo problems that I so detest, and am trying to
> avoid by having it all in one repo...
>
> The issue is that you are using a newer version of aria-extension-cloudify
> than what is supported by aria on PyPI. I suggest keeping the two versions
> matching to avoid problems.
>
> On Wed, Nov 29, 2017 at 5:03 PM, DeWayne Filppi <de...@cloudify.co>
> wrote:
>
> > I worked around this by installing the cloudify extention using the
> > --no-deps argument (to pip).
> >
> > On Wed, Nov 29, 2017 at 2:32 PM, DeWayne Filppi <de...@cloudify.co>
> > wrote:
> >
> > > OK. I guess I didn't provide enough context. I installed the ARIA-1
> > > branch of ARIA in order to pick up a bug fix I needed. When attempting
> > to
> > > install aria-extension-cloudify, it complains that ariatosca 0.2.0 is
> > > installed, and it proceeds to remove it. So, the cloudify extension
> > > deletes ARIA, apparently because it's looking for a different version
> of
> > > it. The full message:
> > >
> > > Installing collected packages: apache-ariatosca,
> aria-extension-cloudify
> > > Found existing installation: apache-ariatosca 0.2.0
> > > Uninstalling apache-ariatosca-0.2.0:
> > > Successfully uninstalled apache-ariatosca-0.2.0
> > > Running setup.py develop for apache-ariatosca
> > > Complete output from command /home/vagrant/venv/bin/python -c "import
> > > setuptools, tokenize;__file__='/home/vagrant/venv/src/apache-
> > > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > > open)(__file__);code=f.read().replace('\r\n',
> > > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop
> --no-deps
> > > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1:
> > > running develop
> > > Checking .pth file support in /home/vagrant/.aria/plugins/
> > > aria-extension-cloudify-4.1/lib/python2.7/site-packages
> > > /home/vagrant/venv/bin/python -E -c pass
> > > TEST FAILED: /home/vagrant/.aria/plugins/aria-extension-cloudify-4.1/
> > lib/python2.7/site-packages
> > > does NOT support .pth files
> > > error: bad install directory or PYTHONPATH
> > > Command "/home/vagrant/venv/bin/python -c "import setuptools,
> > > tokenize;__file__='/home/vagrant/venv/src/apache-
> > > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > > open)(__file__);code=f.read().replace('\r\n',
> > > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop
> --no-deps
> > > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1"
> failed
> > > with error code 1 in /home/vagrant/venv/src/apache-ariatosca/
> > > Could not install package: aria-extension-cloudify (Command
> > > "/home/vagrant/venv/bin/python -c "import setuptools,
> > > tokenize;__file__='/home/vagrant/venv/src/apache-
> > > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > > open)(__file__);code=f.read().replace('\r\n',
> > > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop
> --no-deps
> > > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1"
> failed
> > > with error code 1 in /home/vagrant/venv/src/apache-ariatosca/)
> > >
> > >
> > > On Wed, Nov 29, 2017 at 11:13 AM, Tal Liron <ta...@cloudify.co> wrote:
> > >
> > >> Sorry, hard to understand exactly what you're trying to do, what's
> > >> "failing" etc.
> > >>
> > >> All I can gather from this is that you are installing something that
> > >> requires "apache-ariatosca" but that is already installed, so it's
> > >> removing
> > >> it in order to upgrade. You stopped the log there.
> > >>
> > >> On Wed, Nov 29, 2017 at 1:08 PM, DeWayne Filppi <de...@cloudify.co>
> > >> wrote:
> > >>
> > >> > I see the following when trying to install the cloudify extension
> with
> > >> the
> > >> > ARIA-1 branch:
> > >> >
> > >> > Installing collected packages: apache-ariatosca,
> > aria-extension-cloudify
> > >> > Found existing installation: apache-ariatosca 0.2.0
> > >> > Uninstalling apache-ariatosca-0.2.0:
> > >> >
> > >> > Then it fails.
> > >> >
> > >>
> > >
> > >
> >
>
Re: problem using cloudify extension with dev branch
Posted by Tal Liron <ta...@cloudify.co>.
Ah, the dreaded multi-repo problems that I so detest, and am trying to
avoid by having it all in one repo...
The issue is that you are using a newer version of aria-extension-cloudify
than what is supported by aria on PyPI. I suggest keeping the two versions
matching to avoid problems.
On Wed, Nov 29, 2017 at 5:03 PM, DeWayne Filppi <de...@cloudify.co> wrote:
> I worked around this by installing the cloudify extention using the
> --no-deps argument (to pip).
>
> On Wed, Nov 29, 2017 at 2:32 PM, DeWayne Filppi <de...@cloudify.co>
> wrote:
>
> > OK. I guess I didn't provide enough context. I installed the ARIA-1
> > branch of ARIA in order to pick up a bug fix I needed. When attempting
> to
> > install aria-extension-cloudify, it complains that ariatosca 0.2.0 is
> > installed, and it proceeds to remove it. So, the cloudify extension
> > deletes ARIA, apparently because it's looking for a different version of
> > it. The full message:
> >
> > Installing collected packages: apache-ariatosca, aria-extension-cloudify
> > Found existing installation: apache-ariatosca 0.2.0
> > Uninstalling apache-ariatosca-0.2.0:
> > Successfully uninstalled apache-ariatosca-0.2.0
> > Running setup.py develop for apache-ariatosca
> > Complete output from command /home/vagrant/venv/bin/python -c "import
> > setuptools, tokenize;__file__='/home/vagrant/venv/src/apache-
> > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > open)(__file__);code=f.read().replace('\r\n',
> > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1:
> > running develop
> > Checking .pth file support in /home/vagrant/.aria/plugins/
> > aria-extension-cloudify-4.1/lib/python2.7/site-packages
> > /home/vagrant/venv/bin/python -E -c pass
> > TEST FAILED: /home/vagrant/.aria/plugins/aria-extension-cloudify-4.1/
> lib/python2.7/site-packages
> > does NOT support .pth files
> > error: bad install directory or PYTHONPATH
> > Command "/home/vagrant/venv/bin/python -c "import setuptools,
> > tokenize;__file__='/home/vagrant/venv/src/apache-
> > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > open)(__file__);code=f.read().replace('\r\n',
> > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
> > with error code 1 in /home/vagrant/venv/src/apache-ariatosca/
> > Could not install package: aria-extension-cloudify (Command
> > "/home/vagrant/venv/bin/python -c "import setuptools,
> > tokenize;__file__='/home/vagrant/venv/src/apache-
> > ariatosca/setup.py';f=getattr(tokenize, 'open',
> > open)(__file__);code=f.read().replace('\r\n',
> > '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> > --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
> > with error code 1 in /home/vagrant/venv/src/apache-ariatosca/)
> >
> >
> > On Wed, Nov 29, 2017 at 11:13 AM, Tal Liron <ta...@cloudify.co> wrote:
> >
> >> Sorry, hard to understand exactly what you're trying to do, what's
> >> "failing" etc.
> >>
> >> All I can gather from this is that you are installing something that
> >> requires "apache-ariatosca" but that is already installed, so it's
> >> removing
> >> it in order to upgrade. You stopped the log there.
> >>
> >> On Wed, Nov 29, 2017 at 1:08 PM, DeWayne Filppi <de...@cloudify.co>
> >> wrote:
> >>
> >> > I see the following when trying to install the cloudify extension with
> >> the
> >> > ARIA-1 branch:
> >> >
> >> > Installing collected packages: apache-ariatosca,
> aria-extension-cloudify
> >> > Found existing installation: apache-ariatosca 0.2.0
> >> > Uninstalling apache-ariatosca-0.2.0:
> >> >
> >> > Then it fails.
> >> >
> >>
> >
> >
>
Re: problem using cloudify extension with dev branch
Posted by DeWayne Filppi <de...@cloudify.co>.
I worked around this by installing the cloudify extention using the
--no-deps argument (to pip).
On Wed, Nov 29, 2017 at 2:32 PM, DeWayne Filppi <de...@cloudify.co> wrote:
> OK. I guess I didn't provide enough context. I installed the ARIA-1
> branch of ARIA in order to pick up a bug fix I needed. When attempting to
> install aria-extension-cloudify, it complains that ariatosca 0.2.0 is
> installed, and it proceeds to remove it. So, the cloudify extension
> deletes ARIA, apparently because it's looking for a different version of
> it. The full message:
>
> Installing collected packages: apache-ariatosca, aria-extension-cloudify
> Found existing installation: apache-ariatosca 0.2.0
> Uninstalling apache-ariatosca-0.2.0:
> Successfully uninstalled apache-ariatosca-0.2.0
> Running setup.py develop for apache-ariatosca
> Complete output from command /home/vagrant/venv/bin/python -c "import
> setuptools, tokenize;__file__='/home/vagrant/venv/src/apache-
> ariatosca/setup.py';f=getattr(tokenize, 'open',
> open)(__file__);code=f.read().replace('\r\n',
> '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1:
> running develop
> Checking .pth file support in /home/vagrant/.aria/plugins/
> aria-extension-cloudify-4.1/lib/python2.7/site-packages
> /home/vagrant/venv/bin/python -E -c pass
> TEST FAILED: /home/vagrant/.aria/plugins/aria-extension-cloudify-4.1/lib/python2.7/site-packages
> does NOT support .pth files
> error: bad install directory or PYTHONPATH
> Command "/home/vagrant/venv/bin/python -c "import setuptools,
> tokenize;__file__='/home/vagrant/venv/src/apache-
> ariatosca/setup.py';f=getattr(tokenize, 'open',
> open)(__file__);code=f.read().replace('\r\n',
> '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
> with error code 1 in /home/vagrant/venv/src/apache-ariatosca/
> Could not install package: aria-extension-cloudify (Command
> "/home/vagrant/venv/bin/python -c "import setuptools,
> tokenize;__file__='/home/vagrant/venv/src/apache-
> ariatosca/setup.py';f=getattr(tokenize, 'open',
> open)(__file__);code=f.read().replace('\r\n',
> '\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
> --prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
> with error code 1 in /home/vagrant/venv/src/apache-ariatosca/)
>
>
> On Wed, Nov 29, 2017 at 11:13 AM, Tal Liron <ta...@cloudify.co> wrote:
>
>> Sorry, hard to understand exactly what you're trying to do, what's
>> "failing" etc.
>>
>> All I can gather from this is that you are installing something that
>> requires "apache-ariatosca" but that is already installed, so it's
>> removing
>> it in order to upgrade. You stopped the log there.
>>
>> On Wed, Nov 29, 2017 at 1:08 PM, DeWayne Filppi <de...@cloudify.co>
>> wrote:
>>
>> > I see the following when trying to install the cloudify extension with
>> the
>> > ARIA-1 branch:
>> >
>> > Installing collected packages: apache-ariatosca, aria-extension-cloudify
>> > Found existing installation: apache-ariatosca 0.2.0
>> > Uninstalling apache-ariatosca-0.2.0:
>> >
>> > Then it fails.
>> >
>>
>
>
Re: problem using cloudify extension with dev branch
Posted by DeWayne Filppi <de...@cloudify.co>.
OK. I guess I didn't provide enough context. I installed the ARIA-1
branch of ARIA in order to pick up a bug fix I needed. When attempting to
install aria-extension-cloudify, it complains that ariatosca 0.2.0 is
installed, and it proceeds to remove it. So, the cloudify extension
deletes ARIA, apparently because it's looking for a different version of
it. The full message:
Installing collected packages: apache-ariatosca, aria-extension-cloudify
Found existing installation: apache-ariatosca 0.2.0
Uninstalling apache-ariatosca-0.2.0:
Successfully uninstalled apache-ariatosca-0.2.0
Running setup.py develop for apache-ariatosca
Complete output from command /home/vagrant/venv/bin/python -c "import
setuptools,
tokenize;__file__='/home/vagrant/venv/src/apache-ariatosca/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
--prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1:
running develop
Checking .pth file support in
/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1/lib/python2.7/site-packages
/home/vagrant/venv/bin/python -E -c pass
TEST FAILED:
/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1/lib/python2.7/site-packages
does NOT support .pth files
error: bad install directory or PYTHONPATH
Command "/home/vagrant/venv/bin/python -c "import setuptools,
tokenize;__file__='/home/vagrant/venv/src/apache-ariatosca/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
--prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
with error code 1 in /home/vagrant/venv/src/apache-ariatosca/
Could not install package: aria-extension-cloudify (Command
"/home/vagrant/venv/bin/python -c "import setuptools,
tokenize;__file__='/home/vagrant/venv/src/apache-ariatosca/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" develop --no-deps
--prefix=/home/vagrant/.aria/plugins/aria-extension-cloudify-4.1" failed
with error code 1 in /home/vagrant/venv/src/apache-ariatosca/)
On Wed, Nov 29, 2017 at 11:13 AM, Tal Liron <ta...@cloudify.co> wrote:
> Sorry, hard to understand exactly what you're trying to do, what's
> "failing" etc.
>
> All I can gather from this is that you are installing something that
> requires "apache-ariatosca" but that is already installed, so it's removing
> it in order to upgrade. You stopped the log there.
>
> On Wed, Nov 29, 2017 at 1:08 PM, DeWayne Filppi <de...@cloudify.co>
> wrote:
>
> > I see the following when trying to install the cloudify extension with
> the
> > ARIA-1 branch:
> >
> > Installing collected packages: apache-ariatosca, aria-extension-cloudify
> > Found existing installation: apache-ariatosca 0.2.0
> > Uninstalling apache-ariatosca-0.2.0:
> >
> > Then it fails.
> >
>
Re: problem using cloudify extension with dev branch
Posted by Tal Liron <ta...@cloudify.co>.
Sorry, hard to understand exactly what you're trying to do, what's
"failing" etc.
All I can gather from this is that you are installing something that
requires "apache-ariatosca" but that is already installed, so it's removing
it in order to upgrade. You stopped the log there.
On Wed, Nov 29, 2017 at 1:08 PM, DeWayne Filppi <de...@cloudify.co> wrote:
> I see the following when trying to install the cloudify extension with the
> ARIA-1 branch:
>
> Installing collected packages: apache-ariatosca, aria-extension-cloudify
> Found existing installation: apache-ariatosca 0.2.0
> Uninstalling apache-ariatosca-0.2.0:
>
> Then it fails.
>