On Wed, Sep 21, 2016 at 2:04 AM, Ken Dreyer <kdreyer@xxxxxxxxxx> wrote: > On Tue, Sep 20, 2016 at 9:28 AM, kefu chai <tchaikov@xxxxxxxxx> wrote: >> agreed, actually, a test-ready ceph-disk needs venv which pip to install the >> dependencies, but debian pbuilder uses a cleanroom for building packages >> in which no network access is allowed by default. > > I'm curious why we need a virtualenv at all (or why we "pip install" anything) ? > > The distros should have all the packaged python-* and python3-* > dependencies already, right? > > If we could switch to using the packaged python dependencies for > everything, we'd fix the pbuilder USENETWORK issue, and avoid the > indeterminate nature of depending on whatever happens to be going on > with pypi. Maybe I'm missing something, though? we could. the python modules installed by pip are only used for testing purpose, like tox, pytest, flake8, testtools, fixtures, i think we can add them to the Build-Depends list. and let pbuilder to take care of them. @loic what do you think? > > - Ken -- Regards Kefu Chai -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
