[Python-modules-team] Bug#887508: python-attrs: please upgrade to 17.4.0

[Sandro Tosi]

Source: python-attrs
Severity: wishlist

17.4.0 has been released, and it would be great to get attrs upgraded to it.

thanks,
Sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#825095: Bug#825095: Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

[Sandro Tosi]

> The page:
> https://tracker.debian.org/pkg/python-backports-shutil-get-terminal-size
>
> says 1.0.0-3~bpo8+1 is in old-bbpo, 1.0.0-3 is in stable, and 1.0.0-4 is
> in testing and unstable.
>
> The changelog is:
> python-backports-shutil-get-terminal-size (1.0.0-4) unstable; urgency=medium
>
>   * Fix a typo in the substvar depends (Closes: #884687)
>   * Refresh packaging:
> - Use https in d/copyright's Format.
> - Bump dh compat to 10.
> - Bump d/watch to version 4.
> - Bump std-ver to 4.1.2.0.
> - Add lintian override for a silly warning.
>
>  -- Julien Puydt   Tue, 19 Dec 2017 00:30:44 +0100
>
> python-backports-shutil-get-terminal-size (1.0.0-3) unstable; urgency=medium
>
>   * Declare Breaks with old python-backports.ssl-match-hostname so
> upgrading works. (Closes: #825095)
>
>  -- Julien Puydt   Thu, 28 Jul 2016 11:48:50 +0200
>
> python-backports-shutil-get-terminal-size (1.0.0-2) unstable; urgency=medium
>
>   * Fixed file conflict with other python-backports-* packages. (Closes:
> 825095)
>   * Fixed Vcs-* fields.
>
>  -- Julien Puydt   Thu, 21 Jul 2016 13:13:26 +0200
>
> python-backports-shutil-get-terminal-size (1.0.0-1) unstable; urgency=medium
>
>   * Initial release. (Closes: #824984)
>
>  -- Julien Puydt   Sun, 22 May 2016 16:52:23 +0200
>
>

i'm not sure why you're quoting this, not really relevant.

> Where did you get that 1.0.0-1 from?

that's just the version this bug was originally reported against,
unclear why you're surprised

> It's outrageously outdated... and
> that is why you still see the problem!

no. this was correctly addressed in -5

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#825095: Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

[Sandro Tosi]

control: reopen -1
control: blocks -1 884690

(resending now that the bug is unarchived)

On Mon, May 23, 2016 at 10:50 AM, Aaron M. Ucko  wrote:
> Package: python-backports-shutil-get-terminal-size
> Version: 1.0.0-1
> Severity: serious
> Justification: Policy 6.6(4)
>
> python-backports-shutil-get-terminal-size is impossible to install
> alongside python-backports.ssl-match-hostname:
>
>   Unpacking python-backports-shutil-get-terminal-size (1.0.0-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-1_all.deb
>  (--unpack):
>trying to overwrite 
> '/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in 
> package python-backports.ssl-match-hostname 3.4.0.2-1
>
> Could you please take a look?

this is still happening!

i suspect the reason is because
python-backports-shutil-get-terminal-size ships a __init__.py file
upstream and that's the one that's actually being installed, while all
the other packages overriding dh_python2 to add "--namespace
backports" would install a file with a different content.

cfr:

$ cat /usr/lib/python2.7/dist-packages/backports/__init__.py
__path__ = __import__('pkgutil').extend_path(__path__, __name__)

as installed by python-backports.ssl-match-hostname

with

$ cat backports/__init__.py
from pkgutil import extend_path
__path__ = extend_path(__path__, __name__)

as installed by python-backports-shutil-get-terminal-size; and if you
try to install them both:

Selecting previously unselected package
python-backports-shutil-get-terminal-size.
(Reading database ... 586099 files and directories currently installed.)
Preparing to unpack
.../python-backports-shutil-get-terminal-size_1.0.0-4_all.deb ...
Unpacking python-backports-shutil-get-terminal-size (1.0.0-4) ...
dpkg: error processing archive
/var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-4_all.deb
(--unpack):
trying to overwrite
'/usr/lib/python2.7/dist-packages/backports/__init__.py', which is
also in package python-backports.functools-lru-cache 1.4-1
Errors were encountered while processing:
/var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

this means either any of the other backports packages are installed or
ipython is not installable (as it depends on
python-backports-shutil-get-terminal-size)

can you please fix this asap?

Thanks,

On Mon, May 23, 2016 at 10:50 AM, Aaron M. Ucko  wrote:
> Package: python-backports-shutil-get-terminal-size
> Version: 1.0.0-1
> Severity: serious
> Justification: Policy 6.6(4)
>
> python-backports-shutil-get-terminal-size is impossible to install
> alongside python-backports.ssl-match-hostname:
>
>   Unpacking python-backports-shutil-get-terminal-size (1.0.0-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python-backports-shutil-get-terminal-size_1.0.0-1_all.deb
>  (--unpack):
>trying to overwrite 
> '/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in 
> package python-backports.ssl-match-hostname 3.4.0.2-1
>
> Could you please take a look?
>
> Thanks!
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> ___
> Python-modules-team mailing list
> Python-modules-team@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#884020: python3-sphinx: versioned dependency on jinja2 is too loose

[Sandro Tosi]

Package: python3-sphinx
Version: 1.6.5-2
Severity: normal

Hello,
i had an outdated version on jinja2 on my machine (2.9.5-1) and when building a
package i got the error:

  Error: The 'jinja2.asyncsupport' module cannot be found. Did you install
  Sphinx and its dependencies correctly?

after upgrading python3-jinja2 to 2.10-1, the error went away.

Python3-sphinx declare this dep on jinja2: 'python3-jinja2 (>= 2.3)', probably
you need a tigher one

thanks,
sandro

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-sphinx depends on:
ii  python33.6.3-2
ii  python3-alabaster  0.7.8-1
ii  python3-babel  2.3.4+dfsg.1-2
ii  python3-docutils   0.13.1+dfsg-2
ii  python3-imagesize  0.7.1-1
ii  python3-jinja2 2.10-1
ii  python3-pygments   2.2.0+dfsg-1
ii  python3-requests   2.18.1-1
ii  python3-six1.10.0-4
ii  sphinx-common  1.6.5-2

Versions of packages python3-sphinx recommends:
ii  python3-pil  4.3.0-2

Versions of packages python3-sphinx suggests:
ii  dvipng 1.14-2+b3
ii  imagemagick-6.q16  8:6.9.7.4+dfsg-11
pn  latexmk
ii  libjs-mathjax  2.7.0-2
ii  python3-sphinx-rtd-theme   0.2.4-1
ii  sphinx-doc 1.4.9-2
ii  texlive-fonts-recommended  2016.20170123-5
ii  texlive-generic-extra  2016.20170123-5
ii  texlive-latex-extra2016.20170123-5
ii  texlive-latex-recommended  2016.20170123-5

-- no debconf information

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Python-modules-commits] [python-numpy] annotated tag debian/1%1.13.3-2 created (now 560f811)

[Sandro Tosi]

DPMT is in uploaders for numpy, so please respect the team policy and
coordinate/agree with the sole maintainer before uploading numpy
again, thanks

On Mon, Dec 4, 2017 at 5:02 PM, Mattia Rizzolo  wrote:
> This is an automated email from the git hooks/post-receive script.
>
> mattia pushed a change to annotated tag debian/1%1.13.3-2
> in repository python-numpy.
>
> at  560f811   (tag)
>tagging  59d2bec335a0c85e1dd07c154ed4195cd93a8e86 (commit)
>   replaces  debian/1%1.13.3-1
>  tagged by  Mattia Rizzolo
> on  Mon Dec 4 23:02:10 2017 +0100
>
> - Log -
> python-numpy Debian release 1:1.13.3-2
> -BEGIN PGP SIGNATURE-
>
> iQIzBAABCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlolxeIACgkQCBa54Yx2
> K61zuxAAplI4ab32tG4ABQPD7EH/iDfEDTedN8q5TQieQ+ajNxzE+ZLRazX102AE
> t7VZ93oXTGR0i66Y1cgpS+l/LspWqNVooRut3f5ErTG8oXPFyepbM3KIjsD3q7/w
> 2/CaLVZ60PwO6RYXWY4ANfNHyEJ7rSAqTtW1lbOo+4aCQdCE3sekN8AuYU/KmPZk
> NHPrr4TG5AacMbASeQpSbd4xS+MV5+l/w9xxeeZTu9Xc4F/KhoW4kLOdEUjPVRIn
> e4E2fjS/N8ymV1Sx2TG87m+B2mkPIuxxWfxPOqiMNaQ+G7/dhNglpZY2aTUrfFas
> dIkx/yKSYKHtC2o/EZBySAFEHioSHt8fGdN1HICRnOwuShwDMgc+esM5ZP2jLe03
> 8ORoYzV3ovIBsbkuUBwhr7riVgOcTPgNN2WYJt7I9PIx6YnD4Juujt48NMvgKit8
> Z3lkTEDPgMlY7asEhZqixSOIfEjhcIIFhdyFEYUpyKN7OXTvlbIZTNkxZKCw/Nri
> kW0NPFbH4N4dLIyc/benwWUqRU6TlDHu9jpUo+4zWoK5I9CQ8Grn8e7SRA/myazi
> 1F2weGHHZR/RnGlhN13ZXItkeIRTTupbioH9sKXQggwAUJJcp4VRzUwb8FIcdqy/
> 02Zj/qzzgs/UA8OnN6gfNKuKxRFAI5jjXSVxB0MEY2n2QzV/k+U=
> =fw2V
> -END PGP SIGNATURE-
>
> Mattia Rizzolo (5):
>   Remove unneeded d/docs and d/dirs
>   Drop Build-Depends on python3.5-dev.
>   d/control: Bump Standards-Version to 4.1.2, no changes needed.
>   d/control: add several Multi-Arch tags from the m-a hinter.
>   Changelog for 1:1.13.3-2
>
> ---
>
> This annotated tag includes the following new commits:
>
>new  4b6296f   Remove unneeded d/docs and d/dirs
>new  939b02c   Drop Build-Depends on python3.5-dev.
>new  64bd87a   d/control: Bump Standards-Version to 4.1.2, no changes 
> needed.
>new  2eea508   d/control: add several Multi-Arch tags from the m-a 
> hinter.
>new  59d2bec   Changelog for 1:1.13.3-2
>
> The 5 revisions listed above as "new" are entirely new to this
> repository and will be described in separate emails.  The revisions
> listed as "adds" were already present in the repository and have only
> been added to this reference.
>
>
> --
> Alioth's /usr/local/bin/git-commit-notice on 
> /srv/git.debian.org/git/python-modules/packages/python-numpy.git
>
> ___
> Python-modules-commits mailing list
> python-modules-comm...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-commits



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#864580: Bug#864580: Updating the python-twitter Uploaders list

[Sandro Tosi]

On Sun, Oct 22, 2017 at 2:36 AM, Koichi Akabe  wrote:
> Sandro,
>
> I had updated this package without watching this report, but if you hope, I
> can add you to an uploader list.

it's all good (it is obvious i didnt have time to update this package
anyway), thanks for doing the work!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#878418: flake8: cannot check python2 code

[Sandro Tosi]

Package: flake8
Version: 3.2.1-1
Severity: important

Dear Maintainer,

flake8 switched to be a python3 package, so now the `flake8` program runs under
py3k, that means it cannot check python2 code anymore: f.e. if you run it
against a python2 script containing a `print` statement, flake8 generates a
`E999 SyntaxError: invalid syntax` error.

there is no equivalent flake8-py2 tool, so perfectly valid python2 code cannot
be checked with flake8 unless you explicitly call `python /usr/bin/flake8
/path/to/python2/code.py` which is not user friendly

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flake8 depends on:
ii  python33.5.1-1
ii  python3-flake8 3.2.1-1
ii  python3-pkg-resources  17.0-1

flake8 recommends no packages.

flake8 suggests no packages.

-- no debconf information

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#829487: Bug#829487: New upstream release available

[Sandro Tosi]

control: severity -1 important

On Sun, Jul 3, 2016 at 2:17 PM, Martin Michlmayr  wrote:
> Version 2.3.0 came out in February:
> https://github.com/elastic/elasticsearch-py/releases

now we are at v5.4.0, this package is badly outdated, hence the severity bump

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#871665: python-hiredis: requires a more strict b-d on libhiredis-dev

[Sandro Tosi]

Source: python-hiredis
Version: 0.2.0-2
Severity: important

Hello,
python-hiredis/0.2.0 cant be built with libhiredis-dev from jessie (v0.11.0-4)
FingTBFS with the following error:

```
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-fno-strict-aliasing -g -O2 -fPIC -Ivendor -I/usr/include/python2.7 -c
src/reader.c -o build/temp.linux-amd64-2.7/src/reader.o
In file included from src/reader.h:4:0,
 from src/reader.c:1:
src/hiredis.h:5:26: fatal error: hiredis/read.h: No such file or directory
 #include 
  ^
compilation terminated.
```

indeed hiredis/read.h is not available in libhiredis-dev/0.11.0-4 but it is in
python-hiredis/0.13.3-2 as available in stretch and following suites
(https://packages.debian.org/sid/amd64/libhiredis-dev/filelist)

Could you please update the b-d to libhiredis-dev to be a versioned >= 0.13.3-2
?

thanks for considering,
Sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#864580: Bug#864580: Updating the python-twitter Uploaders list

[Sandro Tosi]

On Sat, Jun 10, 2017 at 5:25 PM, Tobias Frost  wrote:
> Koichi Akabe  has not been working on
> the python-twitter package for quite some time.
>
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.

i'm using the `twitter` module in the tweet dput-ng plugin, so i'm
going to take this over

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861175: Bug#861175: cairocffi: Please drop Build-Depends and Recommends on xcffib

[Sandro Tosi]

Hey Jean-Christophe,
do you have time to work on this or would you be ok with me having a
look at fixing it?

thanks!

On Tue, Apr 25, 2017 at 8:44 AM, Niels Thykier  wrote:
> Source: cairocffi
> Version: 0.7.2-1
> Severity: grave
> Justification: stretch-is-blocker / Depends on Source that FTBFS
>
> Hi,
>
> We have unfortunately learned that we cannot compile xcffib (neither
> in unstable nor in stretch).  Fixing it requires changes to more than
> one package and none of these changes are trivial.
>
> The easiest solution for stretch appears to be to have cairocffi drop
> its Build-Depends and Recommends on binaries built from xcffib and
> lose the optional features provided by that.
>
> Thanks,
> ~Niels
>
> ___
> Python-modules-team mailing list
> Python-modules-team@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861245: pytest-mock: needs a versioned b-d on python-mock

[Sandro Tosi]

Source: pytest-mock
Version: 1.3.0-1
Severity: important

Hello,
when backporting pytest-mock to Jessie, it FTBFS with the jessie version of
python-mock (1.0.1-3) with:

```
test_pytest_mock.py::test_assert_not_called_wrapper FAILED

=== FAILURES ===
 test_assert_not_called_wrapper 

mocker = 

@pytest.mark.skipif(sys.version_info[:2] in [(3, 3), (3, 4)],
reason="assert_not_called not available in python 3.3 
and 3.4")
def test_assert_not_called_wrapper(mocker):
stub = mocker.stub()
>   stub.assert_not_called()

test_pytest_mock.py:364:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
name = 'assert_not_called'

def __getattr__(self, name):
if name == '_mock_methods':
raise AttributeError(name)
elif self._mock_methods is not None:
if name not in self._mock_methods or name in _all_magics:
>   raise AttributeError("Mock object has no attribute %r" % name)
E   AttributeError: Mock object has no attribute 'assert_not_called'

/usr/lib/python2.7/dist-packages/mock.py:667: AttributeError
 Interrupted: stopping after 1 failures 
 1 failed, 28 passed, 2 xfailed in 0.31 seconds 
```

that went away when i used the bpo version of python-mock (2.0.0-3~bpo8+1) ;
that implies the unversioned b-d on python-mock is not enough, and that b-d
needs to have a proper version added

thanks,
sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#854701: python-asyncssh: FTBFS (failing tests)

[Sandro Tosi]

Hello Santiago,
are you still able to reproduce this in your environment? i just tried
on an up-to-date pbuilder chroot and it built fine (it was running in
a X environment tho).

On Thu, 09 Feb 2017 16:14:13 + Santiago Vila  wrote:
> Package: src:python-asyncssh
> Version: 1.8.1-2
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:
>
> 
> [...]
>  debian/rules build-indep
> dh build-indep --with python3,sphinxdoc --buildsystem pybuild
>dh_testdir -i -O--buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config
> running config
>dh_auto_build -i -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/asyncssh
> copying asyncssh/agent_win32.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/asyncssh
> copying asyncssh/known_hosts.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/asyncssh
>
> [... snipped ...]
>
> ==
> ERROR: test_xauth_environment (tests.test_x11._TestX11)
> Test getting Xauthority path from the environment
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/unittest/mock.py", line 1159, in patched
> return func(*args, **keywargs)
>   File "/<>/tests/util.py", line 59, in async_wrapper
> return self.loop.run_until_complete(wrapped_func)
>   File "/usr/lib/python3.5/asyncio/base_events.py", line 466, in 
> run_until_complete
> return future.result()
>   File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
> raise self._exception
>   File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
> result = coro.send(None)
>   File "/<>/tests/test_x11.py", line 498, in 
> test_xauth_environment
> yield from self._check_x11()
>   File "/<>/tests/test_x11.py", line 339, in _check_x11
> proc = yield from _create_x11_process(conn, command, **kwargs)
>   File "/<>/tests/test_x11.py", line 52, in _create_x11_process
> x11_display=x11_display, **kwargs))
>   File "/<>/asyncssh/misc.py", line 152, in __iter__
> return (yield from self._coro)
>   File "/<>/asyncssh/connection.py", line 2487, in create_process
> **kwargs)
>   File "/<>/asyncssh/connection.py", line 2408, in create_session
> bool(self._agent_path)))
>   File "/<>/asyncssh/channel.py", line 895, in create
> 'X11 forwarding request failed')
> asyncssh.misc.ChannelOpenError: Channel Open Error: X11 forwarding request 
> failed
>
> --

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#854390: Bug#854390: python-bottle-cork: insecure default hashing algorithm

[Sandro Tosi]

control: tags -1 +fixed-upstream

On Mon, Feb 6, 2017 at 9:52 AM, IOhannes m zmölnig  wrote:
> As reported on https://github.com/FedericoCeratto/bottle-cork/issues/112, the
> "bottle-cork" module uses a very unsecure hashing algorithm (sha1 with 10
> iterations) as default.
>
> the defaults should be changed to use a secure hash (or even better: the user
> should select the hashing algorithm, rather than Cork)

this has been fixed by upstream in
https://github.com/FedericoCeratto/bottle-cork/commit/665c99342db5dd73bc298235f339c9a335e50d7e
(a small change in cork.py and big chunk in tests, which is always
good).

let me know if i can help in any way to get this fixed for stretch

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#852363: inputstream is "private" since html5lib 1.0b9

[Sandro Tosi]

Hey Hugo, please remember to keep the bug in the loop (you mailed only
-submitter) so that everyone is updated

On Tue, 24 Jan 2017 09:14:59 +0100 Hugo Lefeuvre  wrote:
> Hi,
>
> inputstream is "private" since html5lib 1.0b9[0] (renamed _inpustream).
>
> We could (easily?) fix it in stretch via some dirty patch importing
> "_inputstream" instead of "inputstream", however I think this bug should
> be considered as an upstream bug and should probably be forwarded.
>
> I can include such a patch in my team upload if you agree (and if it
> works).
>
> By the way, it looks like this bug should rather be grave, since it
> makes the package almost unusuable.

do you still plan to update this package? let me know if i can help
you in anyway

looking further into this, it turns out pisa has been totally
deprecated[1] in favor or xhtml2pdf[2] so i think the right way
forward is: a workaround to fix it for stretch, and package [2] and
get rid of pisa for buster

[1] https://pypi.python.org/pypi/pisa/
[2] https://pypi.python.org/pypi/xhtml2pdf

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#851013: python-pyramid: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Sandro Tosi]

As Stuart, i cannot replicate this bug: i built pyramid 5 times and
all of them shown no errors in the test suite:


$ grep -A2 ^Ran *.build
Ran 2482 tests in 5.871s

OK
--
Ran 2482 tests in 6.876s

OK
```

(log attached)

i think we can wait a little more days, and then close it if we dont
hear otherwise

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi


python-pyramid_1.6+dfsg-1_amd64.build.gz
Description: GNU Zip compressed data
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#850907: quixote: package in git is not updated with the latest uploads

[Sandro Tosi]

Source: quixote
Severity: important

the last version in DPMT git repo is 2.5, while 2.7~b2-1 was uploaded by the
maintainer

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Bug#848758: Latest upgrade of Numpy breaks tests of other packages (Was: Bug#848758: python-skbio: FTBFS: Test failures)

[Sandro Tosi]

> They are still, what the name suggests: candidates, with no confirmation
> to be useful in a production environment. I don't see why they should
> ever migrate to testing (as they did in 1.11.1rc.1). Last time, we had
> an numpy RC in testing for more than four months (2016-05-06 to
> 2016-10-16)! This doesn't confirm a sigh quality tendency. And imagine

this is the diff between 1.11.2rc1 and 1.11.2 (not the same versions
you mentioned, but the most recent one we can make such comparison):

https://anonscm.debian.org/cgit/python-modules/packages/python-numpy.git/diff/?h=upstream/11.11.2

the version is just a name, there will be bugs even in the most shiny
new release of every software

> that happens now; chances are high that we release Stretch with a numpy
> release candidate.
>
> IMO the way numpy changes are to be tested in Debian needs some adjustment.



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Bug#848758: Latest upgrade of Numpy breaks tests of other packages (Was: Bug#848758: python-skbio: FTBFS: Test failures)

[Sandro Tosi]

On Wed, Dec 21, 2016 at 10:27 AM, Ole Streicher  wrote:
> Sure; what I also don't understand is why numpy pushes its RC and betas
> into unstable instead of experimental (and then maybe check or asks for
> checking for the reverse deps). This makes it harder to revert if there
> are problems.
>
> Sandro, maybe you could explain that a bit?

early/wider exposure, and they tend to be of high quality.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Bug#848758: Latest upgrade of Numpy breaks tests of other packages (Was: Bug#848758: python-skbio: FTBFS: Test failures)

[Sandro Tosi]

On Wed, Dec 21, 2016 at 8:35 AM, Andreas Tille  wrote:
> In my initial response I mentioned skiping the test.  However, I
> intended to discuss this first since simply hiding the eyes from an
> upgrading problem is not the prefered way to go.

youre not closing your eyes to a problem: you find one, you recognize
there is one, and that you cant work on it right now, so skipping that
test is actually a very evident way of say "it's on my radar, will
work on it"

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Bug#848758: Latest upgrade of Numpy breaks tests of other packages (Was: Bug#848758: python-skbio: FTBFS: Test failures)

[Sandro Tosi]

On Wed, Dec 21, 2016 at 5:59 AM, Andreas Tille <andr...@an3as.eu> wrote:
> Hi Adrian and Anton,
>
> On Wed, Dec 21, 2016 at 11:40:16AM +0200, Adrian Bunk wrote:
>> On Tue, Dec 20, 2016 at 09:01:31AM -0500, Sandro Tosi wrote:
>> > > it seems the recent upgrade of numpy has broken some tests in other
>> > > packages like for instance this one in python-skbio.  I wonder whether
>> > > you are either able to suggest patches to get the tests working with the
>> > > new interface of numpy again or whether it might be sensible to revert
>> > > the upgrade of python-numpy to the previous version considering that we
>> > > are quite close to the freeze.
>> >
>> > There is still a month to the freeze for the existing package, so
>> > let's not panic already. I'd suggest contacting the upstream of the
>> > projects with failing test and ask for support
>>
>> For python-skbio it is *really* time to panic *right now*.
>>
>> python-skbio is currently not in testing.

the last upload (0.5.1-1) was done on Nov 19 and skbio hasnt been in
testing for more than 11 months. if it hasnt reached testing by now,
it must have had several other issues.

>>
>> For python-skbio to have any chance of being part of stretch, the
>> latest possible date for an upload of a package without any RC bugs
>> is Christmas Day (and then not touch the package for 10 days).
>>
>> If this issue is not resolved by Christmas, your Christmas present for
>> the python-skbio maintainers is that their package will definitely not
>> be part of stretch.

sarcasm wont help you make your point.

>
> Thanks for confirming that I was not actually panicing. ;-)
>
> Sandro, would you reconsider my suggestion to revert this
> mini-transition?  I do not see a realistic chance that upstream will
> come up with fixes in the next two days.

how did you reach this conclusion? before i reported this bug upstream
(why didnt you do it?) they probably werent even aware of the issue.

I think you have multiple actions you can do:

* actually investigate what the issue is, did you try to do it? you
might also find out the fix is easy and end up submitting a patch
upstream
* engage with upstream to get this fixed by them and backport the
patch to the current package (if they prefer not to release a new
version now)
* skip that test / dont make the build fail if there is a test failure
(for now!). Test suites are made to catch errors, and in this case it
worked! expecting the test suite to pass every time is either
unrealistic or an indication the suite is too shallow. grab
information about the failure and report them upstream, but in the
meantime (since it's a known issue) you can decide to skip the failure

you say you are in a hurry, and yet you decided to waste a whole day
in this blame-game, i'm sure there is much more you can do to fix
skbio.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Latest upgrade of Numpy breaks tests of other packages (Was: Bug#848758: python-skbio: FTBFS: Test failures)

[Sandro Tosi]

> it seems the recent upgrade of numpy has broken some tests in other
> packages like for instance this one in python-skbio.  I wonder whether
> you are either able to suggest patches to get the tests working with the
> new interface of numpy again or whether it might be sensible to revert
> the upgrade of python-numpy to the previous version considering that we
> are quite close to the freeze.

There is still a month to the freeze for the existing package, so
let's not panic already. I'd suggest contacting the upstream of the
projects with failing test and ask for support


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#844569: Bug#844569: ipython-notebook -> jupyter ?

[Sandro Tosi]

On Wed, Nov 16, 2016 at 6:23 PM, Yaroslav Halchenko
 wrote:
> Unfortunately it seems
> that python notebook support for jupyter is simply not present?!  (thus marked
> at normal severity)

i'd say we have to way for
https://ftp-master.debian.org/new/jupyter-notebook_4.2.3-1.html

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Sandro Tosi]

> Looks like your last upload fixed the build on most architectures. However the
> package still failed to build on arm64.
>
> https://buildd.debian.org/status/package.php?p=pyzmq

Hey Julian, do you have time to look at the failures in the
https://buildd.debian.org/status/package.php?p=pyzmq ? it looks like
upstream released 16.0.0 so it might worth a shot packaging it to see
if that solves them. thanks!!

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#837008: python-astropy: FTBFS: test failure

[Sandro Tosi]

On Thu, 8 Sep 2016 08:51:56 +0200 Ole Streicher  wrote:
> Control: reassign -1 src:python-scipy 0.18.0-1
> Control: affects -1 python-astropy
> Control: forwarded -1 https://github.com/scipy/scipy/issues/6420
> Control: tags -1 patch
>
>
> >> === FAILURES 
> >> ===
> >> _ test_circmean_against_scipy 
> >> __
> >>
> >> @pytest.mark.skipif('not HAS_SCIPY')
> >> def test_circmean_against_scipy():
> >> # testing against scipy.stats.circmean function
> >> data = np.random.uniform(-np.pi, np.pi, size=(100, 5))
> >> answer = scipy.stats.circmean(data, np.pi, -np.pi)
> >>>   assert_equal(np.around(answer, 2), np.around(circmean(data), 2))
> >> E   AssertionError:
> >> E   Items are not equal:
> >> EACTUAL: -4.3096
> >> EDESIRED: 1.97
>
> This is actually a regression bug in scipy; see the github issue. A
> patch is available at https://github.com/scipy/scipy/pull/6543

That regression is said to be fixed in scipy 0.18.1, which was
uploaded on Oct 7 - could you verify this bug is actually fixed
rebuilding astropy? thanks!

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] FTBFS under Django 1.10

[Sandro Tosi]

On Sun, 26 Jun 2016 17:14:38 +0100 Chris Lamb  wrote:
> Whilst rebuilding all reverse build-dependencies of python-django
> with the latest beta, I noticed that python-django-extensions FTBFS with 1.10.
>
> Please update your package to work with Django 1.10 (in experimental)
> as I will uploading it to unstable once it is released (and at the same
> time raising the severity of this bug to RC).

Hey Brian it looks like 1.7.4 supports django 1.10 (inferred as
https://github.com/django-extensions/django-extensions/commit/a0e6fb8619d90afe6a81a77059895ead3524707d
is right after the tag to release 1.7.4) so could you try to package
the latest version and verify it works with django 1.10? thanks!!

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pytest/3.0.3 jessie backport

[Sandro Tosi]

Thanks! i prepared a backport for hypotesis and pytest (i disabled the
pypy packages, which are not present in Jessie anyway, to reduce the
number of packages to backport) and will upload soon

On Mon, Oct 24, 2016 at 7:38 PM, Tristan Seligmann
<mithra...@mithrandi.net> wrote:
> Fine by me as well.
>
> A little note about the tests: the test suite is not run at build time since
> it tends to fail too often for performance reasons, but there are
> autopkgtest tests which should work well to verify the working of the
> package.
>
> On Mon, 24 Oct 2016 at 22:22 Vincent Bernat <ber...@debian.org> wrote:
>>
>>  ❦ 24 octobre 2016 16:19 -0400, Sandro Tosi <mo...@debian.org> :
>>
>> > Adding Vincent and same question for python-hypothesis maintainers: is
>> > it ok for me to backport it to jessie or would you prefer to do that
>> > yourself?
>>
>> I am of course OK. Note that the latest uploads have been done by
>> mithrandi, but I suppose he's OK too.
>> --
>> Choose variable names that won't be confused.
>> - The Elements of Programming Style (Kernighan & Plauger)



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pytest/3.0.3 jessie backport

[Sandro Tosi]

thanks!

Adding Vincent and same question for python-hypothesis maintainers: is
it ok for me to backport it to jessie or would you prefer to do that
yourself?

On Mon, Oct 24, 2016 at 3:54 PM, Sebastian Ramacher
<sramac...@debian.org> wrote:
> On 2016-10-24 14:53:07, Sandro Tosi wrote:
>> Hello,
>> we would like to use 3.0.3 in Jessie: are you ok with me backporting
>> pytest/3.0.3 there or would you rather handle the backport yourself?
>
> Feel free to go ahead.
>
> Cheers
> --
> Sebastian Ramacher



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] pytest/3.0.3 jessie backport

[Sandro Tosi]

Hello,
we would like to use 3.0.3 in Jessie: are you ok with me backporting
pytest/3.0.3 there or would you rather handle the backport yourself?

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-pytz_2016.6.1-1_amd64.changes ACCEPTED into unstable, unstable

[Sandro Tosi]

IOhannes, did you read what you were told on 836242?

On Thu, Sep 1, 2016 at 8:00 AM, Debian FTP Masters
 wrote:
>
>
> Accepted:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Thu, 01 Sep 2016 00:12:21 +0200
> Source: python-pytz
> Binary: python-pytz python3-pytz
> Architecture: source all
> Version: 2016.6.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Python Modules Team 
> 
> Changed-By: IOhannes m zmölnig (Debian/GNU) 
> Description:
>  python-pytz - World timezone definitions, modern and historical - Python 2.x
>  python3-pytz - World timezone definitions, modern and historical - Python 3.x
> Closes: 836242
> Changes:
>  python-pytz (2016.6.1-1) unstable; urgency=medium
>  .
>* Initial packaging (Closes: #836242)
> Checksums-Sha1:
>  3fe627cc61bca5470cd5ff961eb39756fefc8786 1958 python-pytz_2016.6.1-1.dsc
>  22746a2b7c71697992c491c57d397329af708637 172223 
> python-pytz_2016.6.1.orig.tar.bz2
>  92c7e41b08d677c6eecbf8f647b5f8275f83347e 2184 
> python-pytz_2016.6.1-1.debian.tar.xz
>  07892e69a59f8b0180cbd1202e7c6fd4398804f5 126638 
> python-pytz_2016.6.1-1_all.deb
>  9d488a7e2e927f69971f5634447f76d4683be261 126630 
> python3-pytz_2016.6.1-1_all.deb
> Checksums-Sha256:
>  89eb78c68d67361266c8c9a392b32d6b36a0db0b648bb14b36aca85a26f9a8c0 1958 
> python-pytz_2016.6.1-1.dsc
>  b5aff44126cf828537581e534cc94299b223b945a2bb3b5434d37bf8c7f3a10c 172223 
> python-pytz_2016.6.1.orig.tar.bz2
>  993ff3f7fdb28dde6c70ca598af6157006b6736e80fe1c6e975275c3c64336d8 2184 
> python-pytz_2016.6.1-1.debian.tar.xz
>  0e9a76a69cf72cd8305126a398b682d820c3c6d94445df3ae2fed686a039b746 126638 
> python-pytz_2016.6.1-1_all.deb
>  01a852b13d36868670b12505e4edeafedfd69a3563fd6552eea6bb332c8397cc 126630 
> python3-pytz_2016.6.1-1_all.deb
> Files:
>  b16217a354f7887882af06bfb562c151 1958 python optional 
> python-pytz_2016.6.1-1.dsc
>  d47f706283f5780a568bdb4a721f1a9c 172223 python optional 
> python-pytz_2016.6.1.orig.tar.bz2
>  db445ae9cda44ca448e9058becf2c62f 2184 python optional 
> python-pytz_2016.6.1-1.debian.tar.xz
>  6ce464d70204ebc768078e267483e1c8 126638 python optional 
> python-pytz_2016.6.1-1_all.deb
>  6c15223f58306198cbce4a2509b91907 126630 python optional 
> python3-pytz_2016.6.1-1_all.deb
>
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCAAGBQJXx1bQAAoJELZQGcR/ejb4Z14P/jTquefatsMoBk8v0XzMeB2g
> B5c4nIHEatReOytzkuviTl9hTuvIIoyeBQtC1qYnzWlp5kJSdzHIeKNBfM9BZZG9
> ulvaeipChXn9YWAhodqmmJxDM+K53PJNEvfc5DSPVsi2dFCatnLU7L5WuPzKf5QX
> w1+cOrBWx/cDG2Dfw6CrdpFWHUb1wYnb4i8lViVxbhe86gJ3aKEcDmZwBj6w3pje
> tXGs2H7Altom+BHybpX69LKU/FuTFcR2GwCJztdXcmasvc1wofCjfREY9dX9FfaJ
> azNTZg+e+aL+ouMIO0/nGf3uXspXX9JC8/2sEbsJWkoA+oGqxtelN+0y/gs2xkwG
> I7bv5RHdXriKTXn6HBvzd6geph6R01NXJeqdEaVtU7YmFwlL5DGa/6LMbJHOjmIL
> 0nx7edp8vvblti7DKJA8avtd85Ys5iyU6LpmNLR+jpUtNFcxQVJv+mx1s43yGjoZ
> Yx15sx3gorQQjvxnMfe+yK6uP9WN3ka1VAoepkc5bXUgMiwyhGfkyuUUNvn9DaFA
> 4+cjUVaQkFIOX/GJBU4MZytzkl5Wljrx33SuKBamft7JLH7zGfzWV99JLn+D4EMU
> 7+1dZYfcgTjUKZ+DGDdm4zvJ5dFJVIPAeBVd0aN00jlyViR3CZOp7psMylwpqvx9
> VkrPZp+ryQBbqcxbZWcq
> =fjvr
> -END PGP SIGNATURE-
>
>
> Thank you for your contribution to Debian.
>
> ___
> Python-modules-team mailing list
> Python-modules-team@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Jessie backport for python-xlrd/1.0.0-1

[Sandro Tosi]

that's done, thanks! (it was a simple no-change rebuild for jessie)

On Tue, Aug 16, 2016 at 2:37 PM, Vincent Bernat <ber...@debian.org> wrote:
>  ❦ 16 août 2016 15:33 CEST, Sandro Tosi <mo...@debian.org> :
>
>> Hey there!
>> we need an updated xlrd in Jessie, would you rather prepare the
>> backport yourself or would it be ok for me to upload one?
>
> I am OK with you doing it (too much work actually).
> --
> Localise input and output in subroutines.
> - The Elements of Programming Style (Kernighan & Plauger)



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Jessie backport for python-xlrd/1.0.0-1

[Sandro Tosi]

Hey there!
we need an updated xlrd in Jessie, would you rather prepare the
backport yourself or would it be ok for me to upload one?

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Jessie/Wheezy backport of pynag

[Sandro Tosi]

Hey there! I would like to use pynag in jessie/wheezy systems - could
you please backport it? i could also do it, if that's ok with you.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#827356: faulthandler: please package new upstream release, 2.4

[Sandro Tosi]

Source: faulthandler
Severity: wishlist

Hello,
2.4 has been released back in May, please update this package to it (or any
later release at the time of the update).

Regards,
Sandro

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-psutil backport

[Sandro Tosi]

Hey Harlan,

On Wed, Jun 1, 2016 at 3:05 AM, Harlan Lieberman-Berg
 wrote:
> Hi Sandro,
>
> Wanted to reach out to you about python-psutil.  Right now, there's an
> extant bug in the version that's in jessie which is causing some
> problems with certbot (aka letsencrypt).
>
> It seems the bug was fixed in 2.2.1, exactly one minor point later than
> what we have in jessie.
>
> Do you think this is something that we might be able to get fixed
> through p-u?

it is unlikely the release team would approve a new upstream release
(no matter how minor that is) or even a patch for software outside of
jessie (as certbot is only in jessie bpo)

> Also, how would you feel about a backport of python-psutil?  I'm happy
> to put that work forth to get 4.1 into jessie-backports.

i think this is a better approach, as most/all the other modules for
certbot are in bpo anyway; if you want you can go ahead and upload
psutil to jessie-backports, or I can do that, but will take me few
days to get to it

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#825900: Bug#825900: Bug#825900: python-numpy: version number breaks distutils.version.StrictVersion

[Sandro Tosi]

control: reassign 825900 spectral-cube

On Tue, May 31, 2016 at 10:50 AM, Ole Streicher <oleb...@debian.org> wrote:
> On 31.05.2016 11:41, Sandro Tosi wrote:
>>> They try to catch changes in numpy over the years to be compliant to
>>> older numpy versions as well. The source code in question is here:
>>>
>>> https://github.com/radio-astro-tools/spectral-cube/blob/master/spectral_cube/np_compat.py
>>>
>>> This is still useful to allow backporting to Debian Jessie, so I
>>> wouldn't like to remove it.
>>
>> then use LooseVersion instead of StrictVersion?
>
> In that specific case LooseVersion would work; however LooseVersion is
> wrong for prereleases:
>
>>>> from distutils.version import LooseVersion
>>>> LooseVersion("1.11rc1") < LooseVersion("1.11")
> False
>
> I am going to discuss that with upstream.

seems the right course of action, reassigning this bug to
spectral-cube as there's nothing broken in numpy

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#825900: Bug#825900: python-numpy: version number breaks distutils.version.StrictVersion

[Sandro Tosi]

please dont reply only to me, and always keep the bug in the loop; I
didnt add the bug back in the recipients and it would disclose your
private email, but you can forward my reply

On Tue, May 31, 2016 at 10:38 AM, Ole Streicher <oleb...@debian.org> wrote:
> Hi Sandro,
>
> On 31.05.2016 11:28, Sandro Tosi wrote:
>> do you have any solution to suggest?
>
> Still not; after numpy upstream pointed me to PEP-440, I forwarded this
> to the spectral-cube upstream [1]. We will probably find a solution for
> spectral-cube.
>
> [1] https://github.com/radio-astro-tools/spectral-cube/issues/308
>
>> numpy releases RC version as
>> 1.11.1rc1 and the correct debian versioning was used for the deb
>> package (and the same pattern was used for years in case of RC
>> releases), so maybe the right solution is to fix the downstream
>> packages and not use StrictVersion (which, btw, what do they use it
>> for?)
>
> They try to catch changes in numpy over the years to be compliant to
> older numpy versions as well. The source code in question is here:
>
> https://github.com/radio-astro-tools/spectral-cube/blob/master/spectral_cube/np_compat.py
>
> This is still useful to allow backporting to Debian Jessie, so I
> wouldn't like to remove it.

then use LooseVersion instead of StrictVersion?


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#825900: Bug#825900: python-numpy: version number breaks distutils.version.StrictVersion

[Sandro Tosi]

On Tue, May 31, 2016 at 9:21 AM, Ole Streicher  wrote:
 from distutils.version import StrictVersion
 StrictVersion("1.11.1.rc1")
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib64/python2.7/distutils/version.py", line 40, in __init__
> self.parse(vstring)
>   File "/usr/lib64/python2.7/distutils/version.py", line 107, in parse
> raise ValueError, "invalid version number '%s'" % vstring
> ValueError: invalid version number '1.11.1.rc1'
>
> This causes FTBS and CI failures on packages (like spectral-cube) that
> use StrictVersion in their build/run time tests [1].

do you have any solution to suggest? numpy releases RC version as
1.11.1rc1 and the correct debian versioning was used for the deb
package (and the same pattern was used for years in case of RC
releases), so maybe the right solution is to fix the downstream
packages and not use StrictVersion (which, btw, what do they use it
for?)

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause

[Sandro Tosi]

On Sat, Apr 30, 2016 at 4:43 PM, Barry Warsaw <ba...@debian.org> wrote:
> On Apr 30, 2016, at 04:10 PM, Sandro Tosi wrote:
>
>>> I'm just going thru Lintian report and fixing few warnings.
>>
>>but for this yes.
>
> But why get pre-approval for *this* particular commit?

the point is not for this specific commit (and I jbrought this up to
him once i got this email as it was the second package I am maintainer
for receiving this change)

>  Which change do you have a problem with?

debian/copyright is a rather delicate (and sometimes annoying, let's
face it) file, a change to it requires the one doing the upload to
actually check that what's been updated actually matches reality,
which is just extra/unplanned work

>  I genuinely want to know because I do think we need to
> have clear guidelines about what our teammates are allowed to work on.
>
> A while ago, we did hash out the semantics of team in Maintainers vs
> Uploaders.  Because commits are always reversible, I don't have any problem
> with our current rules for team-in-Uploaders.  It's the compact we make by
> having team maintained packages, and I for one think it's a good trade-off.  I
> appreciate the help in cleaning up our collective packages.

yeah but changing copyright is a little bit more intrusive than fixing
a typo or s/http/https/

>
>>well, collaborative work kinda requires agreement on what that work
>>would be, and also is not that collaborative to commit whatever you
>>see fit and then let somebody else deal with it in a next upload. but
>>hey "it's me"...
>
> I think we should generally assume that our teammates know what they're doing
> and have the skills and courtesy to follow the rules.

like we assume with sponsorees, but still we double check everything they do

>  I recently noticed that
> Ondrej committed some changes to fix our Vcs- urls to https, and I think that
> was a nice thing to do!

and in fact i havent said anything (even if it could have been
announced to the list and the commit message could have been a *lot*
better, but that might be categorized as nitpicking)

> For a mass change like this, Ondrej should have followed up with an email to
> the list.  But he wasn't outside the bounds to make the change.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause

[Sandro Tosi]

On Sat, Apr 30, 2016 at 4:04 PM, Ondrej Novy <n...@ondrej.org> wrote:
> Hi,
>
> 2016-04-30 16:51 GMT+02:00 Sandro Tosi <mo...@debian.org>:
>>
>> so eventually you could declare your intention of "fixing
>> debian/copyright" to the list before starting this operation?
>
>
> so should I send mail to mailing list before any intention to commit
> anything? :)

no.

>
> I'm just going thru Lintian report and fixing few warnings.

but for this yes.

> If you have any
> concerns about my change(s), just ping me on IRC or via email/mailing list
> with explanation where you see problem. But don't send me "don't not touch,
> it's me" email please - that's not how collaborative work should work.

well, collaborative work kinda requires agreement on what that work
would be, and also is not that collaborative to commit whatever you
see fit and then let somebody else deal with it in a next upload. but
hey "it's me"...

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] [Python-modules-commits] [mpmath] 01/01: d/copyright: Changed licence shortname BSD -> BSD-3-clause

[Sandro Tosi]

so eventually you could declare your intention of "fixing
debian/copyright" to the list before starting this operation?

On Sat, Apr 30, 2016 at 3:49 PM, Ondrej Novy <n...@ondrej.org> wrote:
> Hi,
>
> CCing list, maybe someone have another opinion.
>
> 2016-04-30 16:37 GMT+02:00 Sandro Tosi <mo...@debian.org>:
>>
>> please do not change debian/copyright for the packages I am in the
>> Maintainer field, thanks
>
>
> http://anonscm.debian.org/cgit/python-modules/packages/mpmath.git/tree/debian/control#n4
> Maintainer: Sandro Tosi <mo...@debian.org>
> Uploaders: Debian Python Modules Team
> <python-modules-team@lists.alioth.debian.org>
>
> so according to: http://python-modules.alioth.debian.org/policy.html
>
> Team in Uploaders is a weak statement of collaboration. Help in maintaining
> the package is appreciated, commits to the git repository are freely
> welcomed, but before uploading, please contact the Maintainer for the green
> light.
>
> Package I commited to is team maintained. If you don't want anyone commit to
> it, why is it inside DPMT? I'm not going to upload it without prior
> authorization from you.
>
> I'm sorry, but it's impossible to me to make list of "bans packages" or
> "banned maintainer".
>
> Thank you.
>
> --
> Best regards
>  Bc. Ondrej Novy



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#739300: Bug#739300: dh_sphinxdoc: Please replace MathJax.js with links to the packaged libjs-mathjax

[Sandro Tosi]

Is there any progress on this? I just got bitten by it:

E: python-cycler-doc: privacy-breach-uses-embedded-file
usr/share/doc/python-cycler-doc/html/_modules/cycler.html You may use
libjs-mathjax package. (https://cdn.mathjax.org/mathjax/latest/mat
hjax.js?config=tex-ams-mml_htmlormml)

a quick grep on DPMT packages, shows already scipy and networkx has to
manually symlink the file from libjs-mathjax to their local doc dir

it would be extremely helpful if sphinx could do that for us.

thanks!

On Mon, Feb 17, 2014 at 3:38 PM, Sebastian Ramacher
 wrote:
> Package: sphinx-common
> Version: 1.2.1+dfsg-3
> Severity: wishlist
>
> Documentation using sphinx.ext.mathjax defaults to an online copy of
> MathJax. It is possible to change mathjax_path in conf.py to use a
> packaged or local copy. I think it would be a nice addition to
> dh_sphinxdoc if it detected a local copy of MathJax.js and replaced it
> with symlinks to the packaged one.
>
> MathJax requires plenty of other files from libjs-mathjax, so simply
> symlinking MathJax.js was not enough in my tests and ended up linking
> /usr/share/javascript/mathjax into _static. I don't know if this is
> easily doable in dh_sphinxdoc, but since sphinx.ext.mathjax is a
> extension installed by python(3)-sphinx, I think dh_sphinxdoc is the
> appropriate tool to handle this.
>
> Regards
> --
> Sebastian Ramacher
>
> ___
> Python-modules-team mailing list
> Python-modules-team@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pylint 1.5 and python-astroid in jessie-backports?

[Sandro Tosi]

I'll take care of this in the coming days

On Mon, Feb 1, 2016 at 11:49 AM, Neil Williams  wrote:

> I'd like to be able to use pylint3 on jessie, using jessie-backports.
> From a cursory check, it looks like an updated astroid also needs to be
> backported to allow pylint to be updated in backports.
>
> There's a new version of astroid about to migrate into testing, so I'm
> not sure if this is already planned but just thought I'd ping in case
> it wasn't.
>
> Thanks.
>
> --
>
>
> Neil Williams
> =
> http://www.linux.codehelp.co.uk/
>
>
> ___
> Python-modules-team mailing list
> Python-modules-team@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
>



-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#810807: Bug#810807: python-restless-doc: package description refers to Python 3 instead of Python 2

[Sandro Tosi]

On Tue, Jan 12, 2016 at 1:29 PM, Daniele Forsi  wrote:
> the last line of the description of this package reads:
>
>> This package provides the Python 3.x module.
>
> instead of "Python 2"

not really, that line should be removed entirely (as the correct
tailing line is fine), as it's a -doc pkg. please double check before
submitting bugs, thanks.

-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Wheezy & Jessie backports for ptyprocess

[Sandro Tosi]

Hey, I have prepared the wheezy & jessie backports for ptyprocess (the
only change from the current version in testing is for wheezy, where I
needed to declare the package compatible only with python2.7, as it
uses a syntax not allowed in 2.6).

Do you want to prepare one version yourself or are you ok with
me pushing the packages I rebuilt? how do you want to handle the
repo-side of things?

Regards,
-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Wheezy & Jessie backports for ptyprocess

[Sandro Tosi]

On Mon, Dec 21, 2015 at 3:34 PM, Sandro Tosi <mo...@debian.org> wrote:
> (the
> only change from the current version in testing is for wheezy, where I
> needed to declare the package compatible only with python2.7, as it
> uses a syntax not allowed in 2.6)

sorry that should have been: (the only changes from the current
version in testing is for wheezy, where I ignored the tests failure,
as there was an error with a syntax not allowed in 3.2)

-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Wheezy & Jessie backports for pexpect

[Sandro Tosi]

Hey, I have prepared the wheezy & jessie backports for pexpect (the
only change from the current version in testing is for wheezy, where I
needed to declare the package compatible only with python2.7, as it
uses a syntax not allowed in 2.6).

Do you want to prepare one version yourself or are you ok with
me pushing the packages I rebuilt? how do you want to handle the
repo-side of things?

PS: it seems rganesan is no longer active since a long time, and the
team has taken over the maintainership of pexpect, so that's mainly a
msg for the "team" of maintainers of the latest releases.

Regards,
-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Jessie backport of sqlalchemy 1.0.8

[Sandro Tosi]

Hey Piotr,
do you have any plan to backport sqlalchemy to Jessie? I understand
1.x contains incompatible changes over 0.9.x but it also has pretty
interesting features we could use in stable

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Jessie backport of sqlalchemy 1.0.8

[Sandro Tosi]

On Mon, Oct 26, 2015 at 5:07 PM, Piotr Ożarowski <pi...@debian.org> wrote:
> Hi Sandro,
>
>> do you have any plan to backport sqlalchemy to Jessie? I understand
>> 1.x contains incompatible changes over 0.9.x but it also has pretty
>> interesting features we could use in stable
>
> not in the near feature, go ahead and upload one if you need it
> (I don't think anything other than a rebuild and some tests is needed,
> but if I can make backports easier, let me know)

cool, thanks for the quick reply! I might upload a backport soon, will
let you know.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#800392: Bug#800392: Bug#800392: Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Sandro Tosi]

> those certainly should work, forgot about them.
> you should be able to login to a powerpc porterbox and check.
> cat test.c
> __POWERPC__
> gcc -E test.c

i tried with something like this:

$ cat t.c
#ifdef __POWERPC__
#ifndef NDEBUG
// disable asserts malloc broken
// https://sourceware.org/bugzilla/show_bug.cgi?id=6527
#define NDEBUG
#endif
#endif

#define PY_SSIZE_T_CLEAN

$ gcc -E t.c
# 1 "t.c"
# 1 ""
# 1 ""
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 1 "" 2
# 1 "t.c"

I guess the output means the __POWERPC__ is not recognized right?

I slightly changed your patch to use the same macro as in npy_cpu; if
even that one fails, for teh benefit of the transition I will disable
the failure for tests and will address it in due time

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#800392: Bug#800392: Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Sandro Tosi]

control: reopen -1

>> it would probably be best to disable the assert in
>> lowlevel_strided_loops.c.src on powerpc depending cpp macros, that way
>> it will also continue to work when users would want to use python-dbg on
>> ppc if softfaulting is enabled.
>>
>
> attached a patch

Sadly it didnt have the expected impact (actually the failure is in
the same test):
https://buildd.debian.org/status/fetch.php?pkg=python-numpy=powerpc=1%3A1.9.2-3=1443649824

Do you any other idea how to address it?

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#800392: Bug#800392: Bug#800392: Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Sandro Tosi]

On Wed, Sep 30, 2015 at 11:19 PM, Julian Taylor
<jtaylor.deb...@googlemail.com> wrote:
> hm is __POWERPC__ not the right macro for that platform? that should
> have worked

in numpy/core/include/numpy/npy_cpu.h i can find

#elif defined(__ppc__) || defined(__powerpc__) || defined(_ARCH_PPC)
/*
 * __ppc__ is defined by gcc, I remember having seen __powerpc__ once,
 * but can't find it ATM
 * _ARCH_PPC is used by at least gcc on AIX
 */
#define NPY_CPU_PPC

so maybe that's the one to use?

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#800392: Bug#800392: Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Sandro Tosi]

On Tue, Sep 29, 2015 at 8:05 AM, Julian Taylor
<jtaylor.deb...@googlemail.com> wrote:
> On 28.09.2015 20:58, Scott Kitterman wrote:
>>
>> Seems like this may be related to #702169.
>>
>
> no, powerpc is the arch with the broken malloc:
> https://sourceware.org/bugzilla/show_bug.cgi?id=6527
>
> the test should probably just be ignored (as it has been in the past) it
> has always been broken and nobody ever cared.

Is there an elegant way to instruct numpy testsuite to just ignore
errors on powerpc? I would really love to keep the test failures as
blocking on all Debian archs. I cant think of any smart way to keep
the 'set -e' for all archs except powerpc

on way would be to just skip that test (in the last failure it was
always test_multiarray.TestClip.test_basic) but of course that doesnt
guarantee that other tests might fail after that (and we dont know
now) or that other test starts failing (because of the broken malloc
acting up).

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Jessie/Wheezy backports for python-subprocess32

[Sandro Tosi]

Hey Daniel,
python-subprocess32 will reach testing in the weekend, and we'd like
to have it available in stable/oldstable. Do you want to handle the
backports yourself or do you prefer me doing them?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Potential removal - python-irc

[Sandro Tosi]

 As this package is now almost 2 years behind upstream and has been orphaned
 for a considerable time, I may request removal of this package unless I hear
 otherwise from you.

there are a couple of libraries for python and IRC, namely

python-irc
python-irclib

which seem both are packaging http://python-irclib.sourceforge.net/
(which actually is https://bitbucket.org/jaraco/irc/), dont ask why
there are 2 different packages for the same lib (and irclib has files
in a irc/ directory so it's also violating the python policy).

both are outdated, so which one are you planning to remove? I'd rather
not lose all IRC libraries at once

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Potential removal - python-irc

[Sandro Tosi]

On Sun, Aug 30, 2015 at 1:32 PM, Iain R. Learmonth i...@debian.org wrote:
 Hi Sandro,

 On Sun, Aug 30, 2015 at 12:40:53PM +0100, Sandro Tosi wrote:
 which seem both are packaging http://python-irclib.sourceforge.net/
 (which actually is https://bitbucket.org/jaraco/irc/), dont ask why
 there are 2 different packages for the same lib (and irclib has files
 in a irc/ directory so it's also violating the python policy).

 python-irclib seems to have been trying to migrate for 783 days.

did you *actually* check why?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718309 it is because
python-irc and python-irclib are the same upstream module.

the reason python-irc is orphaned is because Daniele gave up most of
his packages back then.

 both are outdated, so which one are you planning to remove? I'd rather
 not lose all IRC libraries at once

 I think at this point I would be planning to remove both.

well I think it's wrong: removing all the python IRC libraries is
providing a disservice, we should find a better solution. Adding
Thomas to this thread, maybe he can explain a bit more.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Any reason why python-numpy version 1.9.2 is in experimental?

[Sandro Tosi]

On Tue, Aug 4, 2015 at 1:24 PM, Andreas Tille ti...@debian.org wrote:
 Hi Sandro,

 On Wed, Jul 29, 2015 at 04:59:45PM +0100, Sandro Tosi wrote:
 On Wed, Jul 29, 2015 at 4:32 PM, Andreas Tille andr...@an3as.eu wrote:
  I intend to package python-skbio[1] and realised that the latest
  upstream version (0.4.0) requires numpy 1.9.2.  Is there any reason why
  this remains in experimental?

 My lack of time it's probably the main reason. I'll look into
 uploading numpy to sid asap tho.

 Ftpmaster speed has gained and python-skbio 0.4.0 was accepted in faster
 than expected in unstable (it was actually my fault to upload this
 python-skbio version instead of a previous one - but now thats given).
 It Depends from numpy 1.9.2.  May be it would have been safer to upload
 to experimental first.  Please let me know if I can help with a team

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794511

 upload or whether I should do something with python-skbio to let it work
 properly.

upload it to exp and ask a rm from sid is the safest option.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Any reason why python-numpy version 1.9.2 is in experimental?

[Sandro Tosi]

On Wed, Jul 29, 2015 at 4:32 PM, Andreas Tille andr...@an3as.eu wrote:
 I intend to package python-skbio[1] and realised that the latest
 upstream version (0.4.0) requires numpy 1.9.2.  Is there any reason why
 this remains in experimental?

My lack of time it's probably the main reason. I'll look into
uploading numpy to sid asap tho.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#741046: python-pdfminer: Please package latest upstream

[Sandro Tosi]

On Fri, Jul 10, 2015 at 2:38 AM, Daniele Tricoli er...@mornie.org wrote:
 On Tuesday 07 July 2015 11:03:54 Sandro Tosi wrote:
 please let me know if you are still looking for a sponsor as I can
 help here

 Many thanks for your offer, I only would like to ask to my previous sponsor
 first (stefanor).

any update on this?

 (but I want to try to get a a py3k pkg in as well)

 Me too, but it seems upstream doesn't want to support both Python 2 and
 Python3 with a single codebase[¹] so, there is a Python3 fork[²] with Python2
 compatibility.

I pushed a bit the upstream author, lets see how he reacts

 What do you suggest to handle this? The best would be to get PR 71 merged, or
 something similar...

yeah, you could also get that patch and add it to the packaging to
create a py3k package from it

 I will start to work on pdfminer on the week end. My plan is to update the
 package to version 20140328 to fix #741046 and then working on #640303? Does
 it seem reasonable to you?

sure makes sense, any ETA on when this work will start?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] nose_1.3.6-1~bpo70+1_amd64.changes REJECTED

[Sandro Tosi]

oooh, now I understand the table at Supported Distributions, sorry
about that.

On Wed, Jul 15, 2015 at 11:00 AM, Alexander Wirt
debian-backpo...@lists.debian.org wrote:

 This version is not in stable, so you either want to use -sloppy or use the 
 version in jessie for backporting to wheezy-bpo.

 ===

 Please feel free to respond to this email if you don't understand why
 your files were rejected, or if you upload new files which address our
 concerns.




-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Wheezy backport of stdep

[Sandro Tosi]

On Tue, Jul 14, 2015 at 2:24 PM, Piotr Ożarowski pi...@debian.org wrote:
 Hi Sandro,

 [Sandro Tosi, 2015-07-14]
 we'd like to start using stdeb, and since still have some wheezy
 machines, we'd like to backport the 0.8.2-4 version to wheezy: would
 you like to handle the backport yourself or would you be ok if I
 prepare it?

 go ahead, I need to work on 0.8.5 upload to unstable first

awesome, thx! yep, that'd be great, hopefully some of those bugs in
the BTS will be solved with that upload

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Jessie Wheezy backport for python-pex

[Sandro Tosi]

Hi!
we want to start experimenting with python-pex, so we would need a
backport to Jessie and Wheezy: would you handle them yourself or would
you mind me preparing them?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Jessie Wheezy backport for python-pex

[Sandro Tosi]

On Tue, Jul 14, 2015 at 4:32 PM, Barry Warsaw ba...@debian.org wrote:
 On Jul 14, 2015, at 03:19 PM, Sandro Tosi wrote:
I will start with the version currently in testing (1.0.0), as it's
the only one backportable. would you like me to push the 2 branches to
git for review or what other method you prefer?

 Yep, a git branches are fine.

came up with a pretty ugly backport for wheezy but then when I tested
it, it fails quite hard, so I reported #792422 (running the unstable
package tho), no point in pushing the branch yet

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] backport of nose to Wheezy

[Sandro Tosi]

On Wed, Jul 8, 2015 at 3:15 PM, Dmitry Shachnev mity...@debian.org wrote:
 Hi Sandro,

 On Wed, 8 Jul 2015 11:10:25 -0400, Sandro Tosi wrote:
 Hello,
 we are facing some bugs on the Wheezy version of nose which are solved
 in 1.3.x series, so i'd like to have an updated version in Wheezy:
 would you prefer to backport it yourself or do you mind if i do it?

 Sure, please go ahead and backport it.

This is done, thanks!

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] backport of nose to Wheezy

[Sandro Tosi]

Hello,
we are facing some bugs on the Wheezy version of nose which are solved
in 1.3.x series, so i'd like to have an updated version in Wheezy:
would you prefer to backport it yourself or do you mind if i do it?

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Request to join Debian Python Modules Team

[Sandro Tosi]

Can someone approve this request plz? He's working with me to get
python-tabulate in debian and DPMT. thanks already

On Tue, Jun 30, 2015 at 8:16 PM, ChangZhuo Chen (陳昌倬) czc...@gmail.com wrote:
 Hi.

 I request to join Debian Python Modules Team for the package
 python-tabulate [0]. My Alioth account is czchen-guest.

 [0] http://bugs.debian.org/782140
 --
 ChangZhuo Chen (陳昌倬) czc...@gmail.com
 http://czchen.info/
 Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D

 ___
 Python-modules-team mailing list
 Python-modules-team@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Backport of python-tornado/4.2.0-1 to jessie

[Sandro Tosi]

Hello,
I will need kinda urgently (few days) to backport
python-tornado/4.2.0-1 to jessie, I can do it myself no problem, but
wanted to check with you if you prefer to handle it yourself or if
there's any problem if I do it.

let me know

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Backport of python-tornado/4.2.0-1 to jessie

[Sandro Tosi]

Great! I will start working on it right away then!

On Tue, Jun 30, 2015 at 12:29 PM, Yaroslav Halchenko y...@debian.org wrote:

 On Tue, 30 Jun 2015, Sandro Tosi wrote:

 Hello,
 I will need kinda urgently (few days) to backport
 python-tornado/4.2.0-1 to jessie, I can do it myself no problem, but
 wanted to check with you if you prefer to handle it yourself or if
 there's any problem if I do it.

 If you do -- I would only be grateful

 Cheers!
 --
 Yaroslav O. Halchenko, Ph.D.
 http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
 Research Scientist,Psychological and Brain Sciences Dept.
 Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
 Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
 WWW:   http://www.linkedin.com/in/yarik



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Comments regarding django-fsm_2.2.1-1_amd64.changes

[Sandro Tosi]

I've just uploaded it, sorry for the delay

On Mon, Jun 29, 2015 at 2:25 AM, Michael Fladischer mich...@fladi.at wrote:
 On 2015-06-27 20:27, Thorsten Alteholz wrote:
 your package Recommends: python3-pygraphviz, which is not yet available. Do 
 you intend to upload it?

 It is available, but only in experimental. I should have checked this
 before making the upload. CCing Sandro so he can comment on his plans
 for pygraphviz.

 Cheers,
 --
 Michael Fladischer
 Fladi.at




-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#790235: Bug#790235: basemap: [PATCH] please make the build reproducible

[Sandro Tosi]

 While working on the reproducible builds effort [1], we have noticed
 that basemap could not be built reproducibly.

 The attached patches removes extra timestamps from the build system.
 Once applied, basemap can be built reproducibly in our current
 experimental framework.

please base your work on the experimental upload of basemap.

Also, why dont you just patch sphinx instead of changing all the
packages using it? one fix, and we're done.

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Accepted wfrog 0.8.2+svn973-1 (source all) into unstable

[Sandro Tosi]

I'd be happy if someone would step up to maintain pygooglechart, I
just no longer plan to maintain it and it seemed a leaf package when I
submitted the RM

On Mon, Jun 22, 2015 at 2:41 PM, A Mennucc1 mennu...@debian.org wrote:
 dear all,

 may you please reconsider the request 786474 of removal of pygooglechart ?

 Please be aware  that the *Google Image Charts* are deprecated but the
 *Google Charts* are not.
 See https://developers.google.com/chart/image/

 The program 'wfrog' that I mantain uses actively this service /Google
 Charts/ and would not work w/o (unless a large overhaul of the code ,
 that I have no time to perform).

 I can confirm indeed that all the web pages generate by 'wfrog' work
 well, even if the (supposed) deadline of Apr 2015 is past.

 So the service is not dead, it is alive and kicking.

 So please do not remove pygooglechart.

 If noone wishes to mantain pygooglechart, I volunteer.

 It would be (for me) much easier to solve bug 786051 , that is, to
 migrate pygooglechart from python-support to dh_python2 ... rather than
 rewriting large part of wfrog.

 Bye

 a.


 Il 22/06/2015 15:59, Luca Falavigna ha scritto:
 Mi sono accorto ora che wfrog è l'unico pacchetto che dipende da
 pygooglechart, che è in procinto di essere rimosso da unstable
 (#786474).
 Pensi possa essere possibile rimuovere il supporto di pygooglechart da
 wfrog senza comprometterne le funzionalità?






-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#786269: Bug#786269: tvdb-api: deprecation of python-support

[Sandro Tosi]

Hi Luca,

On Tue, May 26, 2015 at 2:01 AM, Luca Falavigna dktrkr...@debian.org wrote:
 Ciao Sandro,

 2015-05-22 4:50 GMT+02:00 Sandro Tosi mo...@debian.org:
 already fixed in SVN, waiting for python-requests-cache to be
 processed out of NEW to upload.

 python-requests-cache has been processed from NEW.

yup, saw it - thanks for that! I will upload tvdb-api soon.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#786269: Bug#786269: tvdb-api: deprecation of python-support

[Sandro Tosi]

On Wed, May 20, 2015 at 12:36 PM,  dktrkr...@debian.org wrote:
 your package either build-depends or depends on the python-support
 package, or uses dh_pysupport in debian/rules file.

already fixed in SVN, waiting for python-requests-cache to be
processed out of NEW to upload.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#786353: Bug#786353: python-musicbrainzs2: deprecated upstream, replacement exists - remove it?

[Sandro Tosi]

Hello,

On Wed, May 20, 2015 at 4:33 PM, Sebastian Ramacher
sramac...@debian.org wrote:
 According to [1] python-musicbrainz2 has been deprecated upstream. A 
 replacement
 exists and is available in the archive (python-musicbrainzngs). Once ears has
 been remove (#786343), python-musicbrainz2 has no reverse dependencies 
 anymore.

It looks like you got your information wrong: on a jessie system I got

$ apt-cache rdepends python-musicbrainz2
python-musicbrainz2
Reverse Depends:
  exfalso
  python-musicbrainz2-doc
  puddletag
  ears
  dir2ogg

which is a bit more than 'ears' alone.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#786353: Bug#786353: python-musicbrainzs2: deprecated upstream, replacement exists - remove it?

[Sandro Tosi]

 I filed bugs for the reverse recommends and suggests:

 exfalso: #786357
 puddletag: #786358
 dir2ogg: #786360

care to share the reason for this battle?

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] PyPi watch line broken at least in python-requests

[Sandro Tosi]

On Tue, May 5, 2015 at 7:40 AM, Scott Kitterman deb...@kitterman.com wrote:
 On Tuesday, May 05, 2015 10:43:07 AM Jaroslav Benkovský wrote:
   http://pypi.python.org/packages/source/r/requests/requests-(.*)\.tar\.gz
 http://pypi.debian.net/pysubnettree/pysubnettree-(.+)\.(?:zip|tgz|tbz|txz|

org != net that's why we use the redirector now

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#780408: Bug#780408: Please package latest upstream

[Sandro Tosi]

control: reopen -1

https://pypi.python.org/pypi/ipython

On Fri, Mar 13, 2015 at 6:14 PM, Ben Finney ben+deb...@benfinney.id.au wrote:
 reassign 780408 src:ipython
 fixed 780408 src:ipython/0.12-1
 thanks

 On 13-Mar-2015, Julien Puydt wrote:
 ipython 3 is available ; could you package it?

 The ‘ipython3’ package installs IPython 3. This has been available
 since ‘ipython3’ 0.12-1, released 2011-12-29.

 Since this bug report already appears resolved by an existing release,
 I am closing this bug report.

 If you wish to request a different upstream version, feel free to open
 a new report citing the specific version to package.

 --
  \“If I melt dry ice, can I swim without getting wet?” —Steven |
   `\Wright |
 _o__)  |
 Ben Finney b...@benfinney.id.au

 ___
 Python-modules-team mailing list
 Python-modules-team@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#779165: ipython: notebook help reference the not exisiting `ipython-notebook` command

[Sandro Tosi]

Package: ipython
Version: 2.3.0-2
Severity: normal

Hello,

```
$ ipython help notebook | head
The IPython HTML Notebook.

This launches a Tornado based HTML Notebook Server that serves up an
HTML5/Javascript Notebook client.

Subcommands
---

Subcommands are launched as `ipython-notebook cmd [args]`. For information on
using subcommand 'cmd', do: `ipython-notebook cmd -h`.
```

but ipython-notebook doesn't exist.

Regards,
Sandro

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ipython depends on:
ii  python2.7.8-3
ii  python-decorator  3.4.0-2
ii  python-pexpect3.2-1
ii  python-simplegeneric  0.8.1-1

ipython recommends no packages.

Versions of packages ipython suggests:
pn  ipython-doc   none
ii  ipython-notebook  2.3.0-2
pn  ipython-qtconsole none
ii  python [python-profiler]  2.7.8-3
ii  python-matplotlib 1.4.3~rc1-1
ii  python-numpy  1:1.9.2~rc1-1
ii  python-zmq14.4.0-1

-- no debconf information

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#778077: Bug#778077: python-numpy: ftbfs with GCC-5

[Sandro Tosi]

 error: Command x86_64-linux-gnu-gcc-ar rc 
 build/temp.linux-x86_64-2.7-pydebug/libnpymath.a 
 build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/numpy/core/src/npymath/npy_math.o
  
 build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/numpy/core/src/npymath/ieee754.o
  
 build/temp.linux-x86_64-2.7-pydebug/build/src.linux-x86_64-2.7/numpy/core/src/npymath/npy_math_complex.o
  build/temp.linux-x86_64-2.7-pydebug/numpy/core/src/npymath/halffloat.o 
 failed with exit status 127sh: 1: x86_64-linux-gnu-gcc-ar: not found

care to explain why this should be a bug in numpy?

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#776579: Bug#776579: ImportError: cannot import name basemap

[Sandro Tosi]

control: tags -1 + moreinfo unreproducible
control: severity -1 minor

Hello,

On Thu, Jan 29, 2015 at 2:21 PM, giacomo boffi bo...@stru.polimi.it wrote:
 I installed all the python-mpltoolkits.basemap* packages, then I tried to
 import the basemap module from the IPython prompt, as described in different
 tutorials

  |  In [1]: from mpl_toolkits import basemap
  |  
 ---
  |  ImportError   Traceback (most recent call 
 last)
  |  ipython-input-1-e11b082cc26f in module()
  |   1 from mpl_toolkits import basemap
  |
  |  ImportError: cannot import name basemap
  |
  |  In [2]:

I just tried in a clean chroot and I can import basemap just fine, so
I suspect you have something specific on your system, like a
mpl_toolkits directory in the path you are running ipython/python or a
local installation of matplotlib; what is the output of:

python -c import mpl_toolkits as m ; print m.__file__

  | In [2]: import mpl_toolkits
  |
  | In [3]: help(mpl_toolkits)
  |
  | Help on package mpl_toolkits:
  |
  | NAME
  | mpl_toolkits
  |
  | FILE
  | (built-in)
  |
  | PACKAGE CONTENTS
  | axes_grid (package)
  | axes_grid1 (package)
  | axisartist (package)
  | exceltools
  | gtktools
  | mplot3d (package)
  |
  | In [4]:

 while the basemap directory is placed in in the mpl_toolkits directory,
 with all the relevant stuff inside.

help() is a static text, so it doesnt proof much here.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#711964: python2.7: running 'pydoc numpy' causes segmentation fault in some cases

[Sandro Tosi]

control: reassign -1 python2.7

On Tue, Dec 2, 2014 at 12:50 PM, Matthias Klose d...@debian.org wrote:
 Control: notforwarded -1
 Control: reassign -1 python-numpy

 most likely an issue with python-numpy itself.

then please check *before* reassigning, thanks

Regards,
Sandro

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-hl7 not maintained since close to three years

[Sandro Tosi]

On Sat, Oct 25, 2014 at 6:48 PM, Andreas Tille andr...@an3as.eu wrote:
 Hi again,

 since I did not recieved any answer I now have uploaded python-hl7

you wrote them 21hrs ago on a Friday evening...

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-hl7 not maintained since close to three years

[Sandro Tosi]

On Sat, Oct 25, 2014 at 7:03 PM, Andreas Tille ti...@debian.org wrote:
 On Sat, Oct 25, 2014 at 06:51:55PM +0100, Sandro Tosi wrote:
 On Sat, Oct 25, 2014 at 6:48 PM, Andreas Tille andr...@an3as.eu wrote:
  Hi again,
 
  since I did not recieved any answer I now have uploaded python-hl7

 you wrote them 21hrs ago on a Friday evening...

 I know and we have about another 21hrs left if the package should reach
 Jessie.  I'm aware that my takeover was against our usual rules but I
 consider my action in the interest of the users of this package.  As I
 wrote I'm fine to revert the move to the Debian Med team.

a NMU would have been more appropriate, IMHO.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#759094: matplotlib: Please update to use wxpython3.0

[Sandro Tosi]

Hello Olly,


On Mon, Oct 13, 2014 at 4:13 AM, Olly Betts o...@survex.com wrote:
 On Fri, Sep 19, 2014 at 03:01:24PM +, mo...@users.alioth.debian.org wrote:
 tag 759094 + pending

 This bug has been marked as pending for 3.5 weeks now - is there a plan
 for when the next upload will be?

I was waiting for some blockers to clear up: panda is fixed to support
mpl 1.4 and now we have cairocffi which is needed to support GTK3
backend on py3k (and actually the preferred backend for GTK an all py
versions), so hopefully I will find the time to finalize the upload in
the coming days, sorry for the delay.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#763451: Bug#763451: mpmath files should be installed in /usr/share/pyshared

[Sandro Tosi]

control: reassign -1 python

On Tue, Sep 30, 2014 at 12:42 PM, Sergey B Kirpichev
skirpic...@gmail.com wrote:
 Package: mpmath
 Severity: serious

 Mpmath's source files are identical across all python's versions.  You
 should share them in /usr/share/pyshared, see the policy [1].

 .. [1] 
 https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths

policy is outdated (or misleading), reassigning.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#759908: Bug#759908: python-graph: FTBFS: tests segfault

[Sandro Tosi]

control: severity -1 normal
control: forcemerge 750362 -1

Hello Lucas,

On Sat, Aug 30, 2014 at 10:04 PM, Lucas Nussbaum
lu...@lucas-nussbaum.net wrote:
 During a rebuild of all packages in sid, your package failed to build on
 amd64.

 Relevant part (hopefully):
 make[2]: Entering directory '/«PKGBUILDDIR»'
 export PYTHONPATH=../core/build/lib.linux-x86_64-2.7  cd tests/  
 python2.7 testrunner.py
 No handlers could be found for logger __main__
 test_accessibility_hypergraph (unittests-accessibility.test_accessibility) 
 ... ok
 test_accessibility_in_digraph (unittests-accessibility.test_accessibility) 
 ... ok
 test_accessibility_in_graph (unittests-accessibility.test_accessibility) ... 
 ok
 test_accessibility_on_very_deep_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_connected_components_hypergraph 
 (unittests-accessibility.test_accessibility) ... ok
 test_connected_components_in_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_connected_components_on_very_deep_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_cut_edges_in_graph (unittests-accessibility.test_accessibility) ... ok
 test_cut_edges_in_hypergraph (unittests-accessibility.test_accessibility) 
 ... ok
 test_cut_edges_on_very_deep_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_cut_nodes_in_graph (unittests-accessibility.test_accessibility) ... ok
 test_cut_nodes_in_hypergraph (unittests-accessibility.test_accessibility) 
 ... ok
 test_cut_nodes_on_very_deep_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_mutual_accessibility_in_digraph 
 (unittests-accessibility.test_accessibility) ... ok
 test_mutual_accessibility_in_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_mutual_accessibility_on_very_deep_graph 
 (unittests-accessibility.test_accessibility) ... ok
 test_critical_path 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_critical_path_with_cycle 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_empty_intersection 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_partial_intersection 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_transitivity 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_transitivity_with_cycle 
 (unittests-critical.test_critical_path_and_transitive_edges) ... ok
 test_find_cycle_on_digraph (unittests-cycles.test_find_cycle) ... ok
 test_find_cycle_on_digraph_without_cycles (unittests-cycles.test_find_cycle) 
 ... ok
 test_find_cycle_on_graph (unittests-cycles.test_find_cycle) ... ok
 test_find_cycle_on_graph_withot_cycles (unittests-cycles.test_find_cycle) 
 ... ok
 test_find_cycle_on_very_deep_graph (unittests-cycles.test_find_cycle) ... 
 Segmentation fault
 make[2]: *** [test] Error 139

the package doesn't FTBFS (as I'm ignoring errors in tests, for now)
(I know this report could have been triggered by parsing logs, so
that's fine :) ), but it's indeed something to fix, hence I'm merging
with the already existing but about it.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#756403: Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)

[Sandro Tosi]

Hello Andreas,

On Mon, Aug 25, 2014 at 8:44 PM, Andreas Barth a...@ayous.org wrote:
 * Mauricio Faria de Oliveira (mauri...@linux.vnet.ibm.com) [140825 20:34]:
 Hi Andi,

 On 08/25/2014 02:43 PM, Andreas Barth wrote:
 * Julian Taylor (jtaylor.deb...@googlemail.com) [140825 18:37]:
 I have committed the patch to svn, would need sponsoring.
 Where could I pull the package from?

 It's on SVN r30233 [1]. I can get with 'debcheckout python-numpy'.

 Interesting that, although the patch is there, it is not applied
 by default.  I had to run 'quilt push -a' to get it applied.

 I'll upload it as soon as I can build it on ppc64el, that is after
 matplotlib is built (which I assume will happen in the next 1-2 days).

any reason to not just upload it right away? You can sort out the
build ordering/giveback on ppc64el later and have a note left in the
todo list :) I can upload it this evening (or you can at your will)

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#756403: Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)

[Sandro Tosi]

On Tue, Aug 26, 2014 at 7:50 PM, Andreas Barth a...@ayous.org wrote:
 * Sandro Tosi (mo...@debian.org) [140826 17:32]:
 Hello Andreas,

 On Mon, Aug 25, 2014 at 8:44 PM, Andreas Barth a...@ayous.org wrote:
  * Mauricio Faria de Oliveira (mauri...@linux.vnet.ibm.com) [140825 20:34]:
  Hi Andi,
 
  On 08/25/2014 02:43 PM, Andreas Barth wrote:
  * Julian Taylor (jtaylor.deb...@googlemail.com) [140825 18:37]:
  I have committed the patch to svn, would need sponsoring.
  Where could I pull the package from?
 
  It's on SVN r30233 [1]. I can get with 'debcheckout python-numpy'.
 
  Interesting that, although the patch is there, it is not applied
  by default.  I had to run 'quilt push -a' to get it applied.
 
  I'll upload it as soon as I can build it on ppc64el, that is after
  matplotlib is built (which I assume will happen in the next 1-2 days).

 any reason to not just upload it right away? You can sort out the
 build ordering/giveback on ppc64el later and have a note left in the
 todo list :) I can upload it this evening (or you can at your will)

 My lazyness to search for another current chroot. But if you upload,
 I'm happy as well.

Eheh I can understand perfectly :) I'm building numpy right now and if
everything goes well I'll upload it shortly - thanks everyone for the
work on it!

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-psutil outdated

[Sandro Tosi]

Hello,
no new upstream versions will be released to Wheezy (which is our
current stable version) so new versions will only be available from
testing (Jessie) onwards.

Regards,
Sandro

On Fri, Jun 20, 2014 at 9:10 AM, cardcaptorccs
cardcaptor...@airpost.net wrote:
 Hi Debian's Python Modules Team,

 Can you please updater python-psutil in debian wheezy repo? It's too
 outdated!

 --
 http://www.fastmail.fm - A no graphics, no pop-ups email service


 ___
 Python-modules-team mailing list
 Python-modules-team@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#749195: Bug#749195: python-numpy: Please add support for OpenRISC/or1k architecture

[Sandro Tosi]

Hello Manuel,
thanks for your interest in numpy!

On Sun, May 25, 2014 at 2:40 AM, Manuel A. Fernandez Montecelo
m...@debian.org wrote:
 The patch provided allows to get this package compiled in OpenRISC/or1k
 architecture that Christian and I are creating in Debian.

 It would be helpful if you could add the patch soonish, so we do not
 have to carry local patches and they build cleanly from the Debian
 archives.

 After installing python-numpy and python-nose, most of the unit tests
 seem to pass, and the ones that do not pass might be due to underlying
 problems in blas or others.

Have you already tried to talk about this with upstream author? it
would be probably the best first step to do, also to cleanup and
expand the patch as needed. Please let me know when you opened a bug
on upstream bug tracker so I can link this bug too, and follow the
discussion there.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#749195: Bug#749195: python-numpy: Please add support for OpenRISC/or1k architecture

[Sandro Tosi]

Hello Manuel,

On Sun, May 25, 2014 at 5:51 PM, Manuel A. Fernandez Montecelo
manuel.montez...@gmail.com wrote:
 Sandro: I will open a bug upstream and link it, but if upstream takes
 a while to make a release with it, it would be good to have it in
 Debian in the meanwhile.  It's only a couple of defines to set
 endianness, which should not affect the rest of the code or
 architectures.

What I want is to them to have a look at it: it's fine to include a
patch is still not released with numpy; what I'd like to avoid is to
ship a patch without the upstream authors to know it exists and
eventually include in the next upstream release (so we remove the
delta from the debian package). Also, please consider adding a DEP-3
header to the patch.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#740369: libapache2-mod-python: new upstream release (3.4.1)

[Sandro Tosi]

Source: libapache2-mod-python
Severity: wishlist

Hello,
as it's not reported by uscan, I'm opening this bug to let you know that
mod_python has released a new version and it's available at
http://www.modpython.org/

The announcement is at :
https://mail.python.org/pipermail/python-announce-list/2013-October/010084.html

Regards,
Sandro

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#686695: Bug#686695: python-graph: FTBFS if built twice in a row: find: `./dot/pygraph/__pycache__': No such file or directory

[Sandro Tosi]

Hello Jakub,
thanks for you report.

 python-graph FTBFS if built twice in a row:
 | dh clean
 |dh_testdir
 |dh_auto_clean
 | make[1]: Entering directory
 `/build/python-graph-3pWeNk/python-graph-1.8.2'
 | find . -name *.pyc -exec rm {} \;
 | find . -name __pycache__ -exec rm -rf {} \;
 | find: `./dot/pygraph/__pycache__': No such file or directory
 | find: `./core/pygraph/__pycache__': No such file or directory
 | find: `./core/build/lib/pygraph/__pycache__': No such file or directory
 | find: `./core/build/lib/pygraph/mixins/__pycache__': No such file or
 directory
 | find: `./core/build/lib/pygraph/readwrite/__pycache__': No such file or
 directory
 | find: `./core/build/lib/pygraph/classes/__pycache__': No such file or
 directory
 | find: `./core/build/lib/pygraph/algorithms/__pycache__': No such file or
 directory
 | find: `./core/build/lib/pygraph/algorithms/filters/__pycache__': No such
 file or directory
 | find: `./core/build/lib/pygraph/algorithms/heuristics/__pycache__': No
 such file or directory
 | find: `./tests/__pycache__': No such file or directory

this is really weird! it seems that find is able to find the directories

$ find . -name __pycache__ -ls
2687877654 drwxr-xr-x   2 morphmorph4096 Feb 28 19:33
./tests/__pycache__
2029039600 drwxr-xr-x   2 morphmorph  66 Feb 28 19:34
./dot/pygraph/__pycache__
1351635670 drwxr-xr-x   2 morphmorph  66 Feb 28 19:32
./core/pygraph/__pycache__
2029716060 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/readwrite/__pycache__
3368373550 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/mixins/__pycache__
2029716090 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/algorithms/heuristics/__pycache__
3368373580 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/algorithms/filters/__pycache__
263771800 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/algorithms/__pycache__
675491780 drwxr-xr-x   2 morphmorph  66 Feb 28 19:33
./core/build/lib/pygraph/__pycache__
and to remove them, but it still emits those errors:

$ find . -name __pycache__ -exec rm -rf {} \;
find: `./tests/__pycache__': No such file or directory
find: `./dot/pygraph/__pycache__': No such file or directory
find: `./core/pygraph/__pycache__': No such file or directory
find: `./core/build/lib/pygraph/readwrite/__pycache__': No such file
or directory
find: `./core/build/lib/pygraph/mixins/__pycache__': No such file or directory
find: `./core/build/lib/pygraph/algorithms/heuristics/__pycache__': No
such file or directory
find: `./core/build/lib/pygraph/algorithms/filters/__pycache__': No
such file or directory
find: `./core/build/lib/pygraph/algorithms/__pycache__': No such file
or directory
find: `./core/build/lib/pygraph/__pycache__': No such file or directory
$ find . -name __pycache__ -ls
$

even strace didn't reveal much. do you have any clue of what's going on?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#725881: Bug#725881: python-pycurl: undefined symbol _PyTrash_thread_destroy_chain in pycurl.so

[Sandro Tosi]

Hello,

On Wed, Oct 9, 2013 at 5:52 PM, Sajith T S saj...@gmail.com wrote:
...
   File /usr/lib/pymodules/python2.7/urlgrabber/grabber.py, line 427, in 
 module
 import pycurl
 ImportError: /usr/lib/pymodules/python2.7/pycurl.so: undefined symbol: 
 _PyTrash_thread_destroy_chain

can you confirm the recent uploads of PyCURL have fixed it?

Regards,

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#739189: Can't run tests at build-time

[Sandro Tosi]

Source: mysql-connector-python
Version: 1.1.4-1
Severity: normal

Last upstream release has the unittest suite broken, when starting up a local
mysql instance for testing.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-levenshtein

[Sandro Tosi]

 BTW, the homepage, copyright and watch in the python-levenshtein package do
 not point to the current upstream location, they point at a convenience copy
 translate-toolkit used to distribute; ttkit instead points people to pypi for
 it now.

 https://pypi.python.org/pypi/python-Levenshtein

 https://github.com/ztane/python-Levenshtein

 Since the new release also offers python3 support, I'd like to provide a
 python3-levenshtein package too. I guess it makes sense to move away from
 pysupport in that process.

I'll take care of it, thanks for the heads up (even though I
personally think bug reports for the problem you've found would have
been best, but not a big deal)

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] python-levenshtein

[Sandro Tosi]

 (even though I
 personally think bug reports for the problem you've found would have
 been best, but not a big deal)

 That was just information for interested readers who were wondering where the
 updated package could be found. Since I was anticipating working on this
 myself a roundtrip to the BTS has less appeal.

ah sure, seen that way made sense just the email.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] Comments regarding astroid_1.0.1-1_amd64.changes

[Sandro Tosi]

Hi,

On Sat, Jan 4, 2014 at 7:45 PM, Thorsten Alteholz
ftpmas...@ftp-master.debian.org wrote:
 can you please document in one of the next uploads of this package, that the 
 license
 information of astroid-1.0.1\test\data\SSL1\Connection1.py has been improved 
 in the
 upstream repository ...

Sure, I've just committed r27056 to the repository and will be
included in the next upload.

Thanks for checking!

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#730703: Bug#730703: python-matplotlib: Unable to create io-slave

[Sandro Tosi]

Hello Tom,

  have recently upgraded to Debian 7 and have Python Python 2.7.3 with
 matplotlib 1.1.1~rc2-1.  When I click on the image save icon of the plotting
 window I get:

 kfilemodule(30646): couldn't create slave: Unable to create io-slave:
 klauncher said: Unknown protocol ''.

I think this is more related to some KDE-thing than matplotlib. Can
you try to investigate with some of the PyQT maintainers and/or seek
guidance in some users support forum?

Regards,

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#710177: Bug#710177: python-numpy: not fully built from source

[Sandro Tosi]

as Julian said:

Fixing 710177 requires a build depend on cython and running the
generator script explicitly. The upstream buildsystem won't do it.

On Tue, May 28, 2013 at 11:13 PM, Julian Taylor
jtaylor.deb...@googlemail.com wrote:
 Package: python-numpy
 Version: 1:1.7.1-1
 Severity: important

 numpy includes one cython source which is not rebuilt during the package
 build, instead the upstream pregenerated source is used.

 the file can't be generated from the package source as numpy.pxd is missing.
 It can be found in upstreams git tree along with a generator script
 (./numpy/random/mtrand/generate_mtrand_c.py)

 I filed a bug upstream about the missing files:
 https://github.com/numpy/numpy/pull/3378

 ___
 Python-modules-team mailing list
 Python-modules-team@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team