On Mon, Jul 14, 2014 at 9:04 AM, Philipp Marek wrote:
>> > It might be better to work with the python-dbus authors to get a
>> > pip-installable package released to PyPI, so that it can be included
>> > in the tox virtualenv (though for DevStack we'd still want to use
>> > distro packages instead
> > It might be better to work with the python-dbus authors to get a
> > pip-installable package released to PyPI, so that it can be included
> > in the tox virtualenv (though for DevStack we'd still want to use
> > distro packages instead of PyPI, I think).
> I sent Simon an email about that now.
> It might be better to work with the python-dbus authors to get a
> pip-installable package released to PyPI, so that it can be included
> in the tox virtualenv (though for DevStack we'd still want to use
> distro packages instead of PyPI, I think).
I sent Simon an email about that now.
--
: In
On Tue, Jul 8, 2014 at 10:18 AM, Jeremy Stanley wrote:
> On 2014-07-08 09:09:35 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> You'll also need to modify cinder's tox.ini to set "sitepackages =
>> True" so the virtualenvs created for the unit tests can see the global
>> site-packages directory. No
On 2014-07-08 09:09:35 -0400 (-0400), Doug Hellmann wrote:
[...]
> You'll also need to modify cinder's tox.ini to set "sitepackages =
> True" so the virtualenvs created for the unit tests can see the global
> site-packages directory. Nova does the same thing for some of its
> dependencies.
Nova di
> >> The 1.2.0 release from
> >> http://dbus.freedesktop.org/releases/dbus-python/ doesn't look like an
> >> sdist, either (I see a configure script, so I think they've switched
> >> to autoconf). Uploading that version to PyPI isn't going to give you
> >> something you can install with pip. Are th
On Tue, Jul 8, 2014 at 8:55 AM, Philipp Marek wrote:
>> > The other tarballs in that hierarchy follow the same schema; perhaps the
>> > cached download is broken?
>>
>> I downloaded the tarball and didn't find a setup.py at all.
> Oh, that is the requirement? I'd have guessed that the directory na
> > The other tarballs in that hierarchy follow the same schema; perhaps the
> > cached download is broken?
>
> I downloaded the tarball and didn't find a setup.py at all.
Oh, that is the requirement? I'd have guessed that the directory name is at
fault here.
> > The most current releases are av
On Tue, Jul 8, 2014 at 1:46 AM, Philipp Marek wrote:
>
> Hello Doug,
>
>
> thank you for your help.
>
>> > I guess the problem is that the subdirectory within that tarball includes
>> > the version number, as in "dbus-python-0.84.0/". How can I tell the extract
>> > script that it should look into
Hello Doug,
thank you for your help.
> > I guess the problem is that the subdirectory within that tarball includes
> > the version number, as in "dbus-python-0.84.0/". How can I tell the extract
> > script that it should look into that one?
>
> It looks like that package wasn't built correctly
On Mon, Jul 7, 2014 at 5:14 AM, Philipp Marek wrote:
> Hi everybody,
>
> I'm trying to get
> https://review.openstack.org/#/c/99013/
> through Jenkins, but keep failing.
>
>
> The requirement I'm trying to add is
>> dbus-python>=0.83 # MIT License
>
>
> The logfile at
>
> http://l
Hi everybody,
I'm trying to get
https://review.openstack.org/#/c/99013/
through Jenkins, but keep failing.
The requirement I'm trying to add is
> dbus-python>=0.83 # MIT License
The logfile at
http://logs.openstack.org/13/99013/2/check/check-requirements-integration-dsvm/d6e54
12 matches
Mail list logo
