Re: Preconditions for python-moto finished - help needed to build package itself

2018-02-06 Thread Lumin
Hi Andreas,

I checked the packaging, and my debuild ended up with an
error different from

   > AttributeError: 'module' object has no attribute 'backport_assert_raises'

According to a quick investigation on this problem, I'm sure there
are still some missing B-Ds in control file.

With patch [1] dpkg-buildpackage can go a bit further while building
this package.
See requirements-dev.txt. And new problems arose:

1. $ make test  # python2

ImportError: No module named vendored

2. $ make test_server  # python2

ConnectionError: HTTPConnectionPool(host='localhost', port=5000): Max
retries exceeded with url:

3. $ nosetests3 -sv --with-coverage --cover-html ./tests/

ModuleNotFoundError: No module named 'botocore.vendored'
AttributeError: module 'botocore' has no attribute 'vendored'

It seems that the "vendored" is from botocore package. I'm not
sure which package or script to blame. Further investigation needed.

4. $ debuild

A bunch of errors. e.g.
error: [Errno 111] Connection refused


I don't know whether it helps to add all the dependencies specified by
requirements-dev.txt to control.


[1] as follows.

diff --git a/debian/control b/debian/control
index d950b12..5418dd3 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,7 @@ Section: python
 Priority: optional
 Build-Depends: debhelper (>= 11),
dh-python,
+   flake8,
python-all,
python-setuptools,
python-aws-xray-sdk,
@@ -15,11 +16,14 @@ Build-Depends: debhelper (>= 11),
python-botocore (>= 1.7.12),
python-cookies,
python-cryptography (>= 2.0.0),
+   python-freezegun,
python-jinja2,
python-jsondiff,
+   python-nose,
python-requests,
python-xmltodict,
python-six,
+   python-sure,
python-werkzeug,
python-dateutil,
python-mock,
@@ -36,11 +40,14 @@ Build-Depends: debhelper (>= 11),
python3-botocore (>= 1.7.12),
python3-cookies,
python3-cryptography (>= 2.0.0),
+   python3-freezegun,
python3-jinja2,
python3-jsondiff,
+   python3-nose,
python3-requests,
python3-xmltodict,
python3-six,
+   python3-sure,
python3-werkzeug,
python3-dateutil,
python3-mock,


-- 
Best,



Re: Preconditions for python-moto finished - help needed to build package itself

2018-02-06 Thread Andreas Tille
Hi Lumin,

On Tue, Feb 06, 2018 at 03:27:22PM +, Lumin wrote:
> I checked the packaging,

Thanks a lot!

> and my debuild ended up with an
> error different from
> 
>> AttributeError: 'module' object has no attribute 'backport_assert_raises'
> 
> According to a quick investigation on this problem, I'm sure there
> are still some missing B-Ds in control file.
> 
> With patch [1] dpkg-buildpackage can go a bit further while building
> this package.

Would you mind pushing your patch directly?  I do not see any advantage
if I would proxy your patch. ;-)

> See requirements-dev.txt. And new problems arose:
> 
> 1. $ make test  # python2
> 
> ImportError: No module named vendored
>
> 2. $ make test_server  # python2
> 
> ConnectionError: HTTPConnectionPool(host='localhost', port=5000): Max
> retries exceeded with url:

Seems there is some service needed at port 5000.  But which one???
 
> 3. $ nosetests3 -sv --with-coverage --cover-html ./tests/
> 
> ModuleNotFoundError: No module named 'botocore.vendored'
> AttributeError: module 'botocore' has no attribute 'vendored'
> 
> It seems that the "vendored" is from botocore package. I'm not
> sure which package or script to blame. Further investigation needed.

May be if somebody has a solution for this one also 1. (No module named
vendored) might be related.
 
> 4. $ debuild
> 
> A bunch of errors. e.g.
> error: [Errno 111] Connection refused
> 
> 
> I don't know whether it helps to add all the dependencies specified by
> requirements-dev.txt to control.

I admit up to know I have not checked this file but probably having
these will help.

Kind regards

  Andreas.
 
> [1] as follows.
> 
> diff --git a/debian/control b/debian/control
> index d950b12..5418dd3 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -5,6 +5,7 @@ Section: python
>  Priority: optional
>  Build-Depends: debhelper (>= 11),
> dh-python,
> +   flake8,
> python-all,
> python-setuptools,
> python-aws-xray-sdk,
> @@ -15,11 +16,14 @@ Build-Depends: debhelper (>= 11),
> python-botocore (>= 1.7.12),
> python-cookies,
> python-cryptography (>= 2.0.0),
> +   python-freezegun,
> python-jinja2,
> python-jsondiff,
> +   python-nose,
> python-requests,
> python-xmltodict,
> python-six,
> +   python-sure,
> python-werkzeug,
> python-dateutil,
> python-mock,
> @@ -36,11 +40,14 @@ Build-Depends: debhelper (>= 11),
> python3-botocore (>= 1.7.12),
> python3-cookies,
> python3-cryptography (>= 2.0.0),
> +   python3-freezegun,
> python3-jinja2,
> python3-jsondiff,
> +   python3-nose,
> python3-requests,
> python3-xmltodict,
> python3-six,
> +   python3-sure,
> python3-werkzeug,
> python3-dateutil,
> python3-mock,
> 
> 
> -- 
> Best,
> 

-- 
http://fam-tille.de



Re: Preconditions for python-moto finished - help needed to build package itself

2018-02-06 Thread Lumin
Hi,

On 6 February 2018 at 15:56, Andreas Tille  wrote:

> Would you mind pushing your patch directly?  I do not see any advantage
> if I would proxy your patch. ;-)

Done.

> I admit up to know I have not checked this file but probably having
> these will help.

Then I believe it worth a try and will help. Flask is required by that
*-dev.txt file,
and the default listening port of flask is exactly 5000.

I have to sleep now. :-)

Have a good day.

-- 
Best,



Request to join DPMT

2018-02-06 Thread Scott Talbert

Hi,

I would like to join DPMT so that I could maintain the python-pytest-xdist 
package (that I've recently discussed adopting with Daniel Stender). 
Additionally, I'll need to package a new dependency for a new upstream 
release of python-pytest-xdist.


My Alioth login is swt2c-guest.

I've read https://python-modules.alioth.debian.org/policy.html and accept 
it.


Thanks,
Scott



Move to salsa? Merge modules and apps team?

2018-02-06 Thread W. Martin Borgert
Hi,

how about moving the Python team(s) to salsa?
And how about merging the modules and apps teams into one?

Moving git packages (modules team) is very easy using
import.sh from https://salsa.debian.org/mehdi/salsa-scripts.git

Moving svn packages (apps team) is probably more work.

Any opinions? Any doubts?

TIA & Cheers