Package: python-pytest
Version: 2.2.4-2
Severity: grave
Justification: renders package unusable
With latest python3-pytest from sid, I get
# py.test-3.3
Traceback (most recent call last):
File /usr/bin/py.test-3.3, line 5, in module
sys.exit(load_entry_point('pytest==2.4.2',
Package: sphinx-common
Version: 1.1.3+dfsg-4
Severity: normal
File: /usr/bin/dh_sphinxdoc
For the s3ql-beta package (not yet uploaded), dh_sphinxdoc fails with:
dh_installdocs
dh_sphinxdoc
dh_sphinxdoc: error: unknown JavaScript code:
On 06/15/2013 03:51 PM, Nikolaus Rath wrote:
On 06/15/2013 03:38 PM, Jakub Wilk wrote:
* Nikolaus Rath nikol...@rath.org, 2013-06-15, 14:26:
For the s3ql-beta package (not yet uploaded),
(And it build-depends on packages not in the archive, so I can't
test-build it myself...)
Yes, sorry
On 06/15/2013 03:38 PM, Jakub Wilk wrote:
* Nikolaus Rath nikol...@rath.org, 2013-06-15, 14:26:
For the s3ql-beta package (not yet uploaded),
(And it build-depends on packages not in the archive, so I can't
test-build it myself...)
Yes, sorry. I can try to create a minimalistic debian/rules
On 05/04/2011 03:12 AM, Sandro Tosi wrote:
On Tue, May 3, 2011 at 20:33, Nikolaus Rath nikol...@rath.org wrote:
Hello,
Can you tell me what needs to happen for matplotlib 1.0 from
experimental to enter unstable and (eventually) testing? Are there any
critical showstoppers?
http
On 05/04/2011 09:27 AM, Sandro Tosi wrote:
On Wed, May 4, 2011 at 15:18, Nikolaus Rath nikol...@rath.org wrote:
On 05/04/2011 03:12 AM, Sandro Tosi wrote:
On Tue, May 3, 2011 at 20:33, Nikolaus Rath nikol...@rath.org wrote:
Hello,
Can you tell me what needs to happen for matplotlib 1.0 from
Hello,
Can you tell me what needs to happen for matplotlib 1.0 from
experimental to enter unstable and (eventually) testing? Are there any
critical showstoppers?
Can I safely download the source package and build it for my testing system?
Thanks for all your great Python packaging work!
Best,
7 matches
Mail list logo
