On Dec 23, 2017, at 10:26, Jonas Meurer wrote:
>
> we - the Debian Mailman3 maintainers - would like to backport the latest
> versions of flufl.i18n and flufl.lock from sid/testing to
> stretch-backports. They're required as dependencies for the Mailman3
> packages to be
On May 08, 2017, at 10:16 AM, Mickael Viey wrote:
>After a python3-virtualenv fresh install. The package is installed on
>/usr/lib/python3/dist-packages, but doesn't provide any entry point to invoke
>virtualenv:
That's correct. python3-virtualenv is just the library. Install the
`virtualenv`
Source: pycxx
Version: 7.0.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just noticed this over in Ubuntu, where pycxx 7.0.1-1 is failing its
autopkgtest, which prevents it from getting promoted out of
zesty-proposed. Retested on unstable, in a sid chroot, the exact
On Jan 31, 2017, at 09:43 AM, Eli Collins wrote:
>Passlib 1.7.1 is out, which should fix #852289; I'll try to keep an eye on
>the reproducible build status for a bit in case there's any other hiccups.
Thanks! I'm working on the new upstream in git right now. It looks like we
can also drop the
On Jan 30, 2017, at 08:21 AM, Simon McVittie wrote:
>Thanks for letting me know, I'll mark it as unmaintained. Would you like
>your other packages to be marked as unmaintained too?
>
>Sorry, I am not intending to adopt python-whoosh: I'm only fixing it
>because removing it from testing would be
Maybe, create a python{,3}-pyside-common package that only contains the
.egg-info and then have all subpackages depend on that?
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
I have no objections, but I don't have time right now to do it. Piotr did the
1.7.0-1 upload so please verify with him.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
Are you sure that link actually exists?
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
On Nov 17, 2016, at 11:17 PM, Nelson A. de Oliveira wrote:
>Since we are installing pip from a Debian package, shouldn't we have it
>using "--disable-pip-version-check" by default, to avoid this?
Yes, I think we should.
___
Python-modules-team mailing
On Nov 13, 2016, at 10:14 PM, Arthur de Jong wrote:
>I just ran into this today and I can confirm that the above fix allows
>me to move forward with a Python 2.6 virtualenv. Can you fix this for
>unstable?
Yes, I'll upload this fix to unstable momentarily.
pgpd6xRk84j_A.pgp
Description:
Hi. I'm not sure that's a reasonable thing to support, especially now that
stretch is the next version. So much has changed in pip in the meantime, that
I think it will be too difficult to backport or otherwise make unstable's pip
work in any older versions.
Sorry for not getting to this bug in
On Mon, 31 Oct 2016 18:25:16 -0400 Barry Warsaw <ba...@debian.org> wrote:
> Thanks for the bug report. I plan on fixing this in 8.1.2-3 but I think the
> shebang should be /usr/bin/python2 for /usr/bin/pip2. Can you think of a
> reason not to do this?
Well, one reason is that i
Thanks for the bug report. I plan on fixing this in 8.1.2-3 but I think the
shebang should be /usr/bin/python2 for /usr/bin/pip2. Can you think of a
reason not to do this?
___
Python-modules-team mailing list
How would we do that? I'm not particularly fond of debian/control.in files.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Package: python-pip
Version: 8.1.2-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
There are some latent autopkgtest failures now, as originally
described in LP: #1626258, which also contains a debdiff. As per
usual, this should be fixed in Debian and
On Oct 08, 2016, at 04:58 PM, Ben Finney wrote:
>When attempting to create a new virtualenv, Pip crashes with an error:
I can't reproduce this on unstable.
% python2 -m pip --version
pip 8.1.2 from /usr/lib/python2.7/dist-packages (python 2.7)
% python2 -m virtualenv --version
15.0.3
% python2
It's difficult to figure out the copyrights on many of the files in examples.
I've asked upstream for details.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
On Jul 27, 2016, at 05:06 PM, Matijs van Zuijlen wrote:
>virtualenv allows specifying the python version to use. However, when
>doing so I get the following output:
>
> $ virtualenv -p /usr/bin/python3 --system-site-packages .venv
> Already using interpreter /usr/bin/python3
> [..]
>
On Jul 12, 2016, at 05:41 PM, Daniel Holth wrote:
>The problem is that Debian patched pip to make the --user option the
>default.
In talking with Donald, we all agree that we need to move forward on the
upstream switch to --user by default. I don't have time right now to continue
working on
On Jul 04, 2016, at 04:52 PM, Olivier Berger wrote:
>Unfortunately, I'm no longer able to dedicate time to help maintaining
>the html5lib package.
Thanks so much for your past work on it!
>Thus I'm requesting that anyone uploading the next version as part of
>the team, please remove me from the
I don't know how to use targetcli. I tried the simple command you gave in
your bug report, but that failed for other reasons (some kind of input file is
missing).
In any case, I just uploaded pyparsing 2.1.4+dfsg1-1 which has a number of bug
fixes. Please try that. If it works for you, great!
On Apr 30, 2016, at 07:21 PM, Ondrej Novy wrote:
>announced before:
>http://lists.alioth.debian.org/pipermail/python-modules-team/2016-March/030256.html
Thanks! I must have missed it, but you did the right thing.
-Barry
PS: why do we have two mailing lists?! :( :(
pgp3FKxlJshFs.pgp
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? Which change do you
have a problem with? I genuinely want to know because I do think we need to
have
I'll have a fix uploaded momentarily.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Can you please report the output of `dpkg-query -W python-pip-whl`, both if
virtualenv works and doesn't work for you?
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
On Mar 24, 2016, at 10:06 AM, Joel Cross wrote:
>Ddoes this mean that if I need to use the Python 2 version of Flake8 (for
>instance, for linting my Python 2 files), that I will need to install my own
>binary? It seems to me that if the package is missing a binary, and that
>binary isn't
I just tried this on a fully dist-upgraded sid machine:
@chemistry[~:1005]% virtualenv -p python3.5 /tmp/p35
Running virtualenv with interpreter /usr/bin/python3.5
Using base prefix '/usr'
New python executable in /tmp/p35/bin/python3.5
Also creating executable in /tmp/p35/bin/python
Installing
I think this should now all be sorted out with python-virtualenv 15.0.0+ds-1
and python-pip 8.1.0-1. I'm going to close this bug but if you're still
having a problem with those new versions, please reopen it.
___
Python-modules-team mailing list
Does this problem happen on Stretch/unstable?
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
On Feb 15, 2016, at 10:23 PM, Sebastian Ramacher wrote:
>Yes, it's a bug and it will be fixed shortly. It's a serious bug in Ubuntu,
>but it's nowhere near serious in Debian. Python 3.4 is still supported. Once
>we start the transition to remove Python 3.4 from the supported set and are
>left
Please be aware that this bug makes the package completely unusable for Python
3 users on such systems as described here. Thus I think serious is a valid
severity. I'll stop complaining once this bug is fixed though. Thanks.
___
Python-modules-team
Source: pytest
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
The change uploaded in 2.8.7-3 that closes #814622 and reverts the
change from 2.8.7-2 causes a critical regression in the DEP-8 tests on
Ubuntu, where only Python 3.5 exists. Once Debian drops
On Feb 15, 2016, at 08:06 PM, Sebastian Ramacher wrote:
>This is just not true. python3.m5 -m pytest works just fine. If not, please
>file a proper bug report.
The fix you uploaded introduces a regression, albeit in Ubuntu only right now,
but it will show up in Debian once Python 3.4 is dropped.
The reversion of 2.8.7-2 is not correct. It breaks the DEP-8 tests in Ubuntu
where there is only Python 3.5 (and will break Debian as soon as Python 3.4 is
dropped).
By reverting this, you find that there is no Python 3 module in python3-pytest
and `python3.5 -m pytest` fails. Please restore
On Feb 15, 2016, at 11:37 AM, Matthias Klose wrote:
>No, in the first place it's a bug to not declare a proper Breaks/Replaces.
Well, in the meantime, you uploaded a new version of python-setuptools, so the
Breaks/Replaces that already exists in python-pip is now out of date. But if
you agree
On Feb 13, 2016, at 07:27 AM, Ralf Treinen wrote:
>Here is a list of files that are known to be shared by both packages
>(according to the Contents file for sid/amd64, which may be
>slightly out of sync):
>
> /usr/share/python-wheels/setuptools-20.0-py2.py3-none-any.whl
>
>This bug has been
On Feb 12, 2016, at 01:11 PM, Andreas Beckmann wrote:
>the Breaks+Replaces against python-six-whl are insufficiently versioned,
>that package was removed in six 1.10.0-3, it is still present in -2.
I'm not sure I can make piuparts cooperate for me locally, but it's obvious
the Replaces/Breaks
On Feb 11, 2016, at 09:09 AM, Ross Gammon wrote:
>I was working last night on fixing the RC bug for tweepy, but got myself
>in a muddle with git-dpm.
Yep, git-dpm will do this some times. :/
>Tweepy is currently 3.4.0 & 3.5.0 is a new available release. I cloned,
>fixed the bug (just disabling
Since upstream hasn't changed the default yet, and for understandable reasons
it isn't high on their priority list, and because I'm tired of carrying the
Ubuntu delta that switches to --user by default, I am going to port the Ubuntu
patch to the Debian version. This will let me resync to Debian
On Feb 10, 2016, at 11:43 AM, Donald Stufft wrote:
>Can we at least ensure that $HOME/.local/bin is on the $PATH by default if
>you’re going to do that?
How can we do that? Not in python-pip certainly. Users control their own
$PATH so I'm not sure how we can enforce that. I'm not sure what
On Feb 08, 2016, at 10:51 AM, Colin Watson wrote:
>Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813399, but
>more of the same. Barry, shouldn't you be doing something like
>"python-six-whl (<< 1.10.0+)", rather than these sketchy <= dependencies
>on specific packaging revisions
On Feb 01, 2016, at 04:24 PM, Andreas Beckmann wrote:
>during a test with piuparts I noticed your package fails to upgrade from
>'testing'.
>It installed fine in 'testing', then the upgrade to 'sid' fails
>because it tries to overwrite other packages files without declaring a
>Breaks+Replaces
Hi Sebastian,
On Jan 30, 2016, at 01:34 AM, Sebastian Ramacher wrote:
>This was an upgrade and python-pip-whl version 1.5.6-7 is installed.
You definitely need python-pip-whl 8.0.2-1
Did that not install when you upgraded?
pgpPAmE6Gucb1.pgp
Description: OpenPGP digital signature
On Jan 30, 2016, at 01:07 AM, Sebastian Ramacher wrote:
>After installing python3-cachecontrol, python3-lockfile, python3-packaging,
>python3-progress and python3-retrying, pip3 no longer fails with ImportErrors.
Those shouldn't be necessary. Was this an upgrade or a fresh install of these
Ultimately, this is a bug in Cython, which upstream is aware of and should fix
by Python 3.6. I reverted the change in upstream Python 3.5 (and 2.7) since
it's technically a regression. Matthias has cherry picked the fix for
Ubuntu's Python 3.5; I assume but am not sure if he's also done the
On Jan 04, 2016, at 10:43 AM, Carl Chenet wrote:
>We have a RC bug for Tweepy in Debian because the unittest2 and/or vcr
>Python modules are not packaged for Debian
Not correct. Both packages are in Debian for both Python 2 and 3.
We have unittest2 1.1.0-6 and vcr 1.7.3-1
There must be some
On Dec 23, 2015, at 07:20 PM, Tristan Seligmann wrote:
>If you want to run pytest with a particular version of python, then
>"pythonX.Y -m pytest" is a much better way than relying on the py.test-X.Y
>scripts.
Sorry, I've had no time to respond in detail, but in general I agree with
this. It's
On Nov 25, 2015, at 06:09 PM, Brian May wrote:
>Looks like the referenced ticket contains old information.
>
>https://github.com/django/django/commit/d27085b02d58ecf8b72e7189b6a5feaf634ec977
This is great news. I just built the 1.8.5-2ubuntu1 version in Xenial, which
runs the test suite under
Hi guys, apologies for any duplicate emails.
I really appreciate all the great work y'all have done to get us on Django
1.8. I was hoping that this would give us Python 3.5 support, but as you
know, upstream's documentation is incorrect about this, and then there's issue
25502 tracking *actual*
Source: numpydoc
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
debian/copyright produces a bunch of lintian warnings:
W: numpydoc source: empty-short-license-in-dep5-copyright (paragraph at line 5)
W: numpydoc source: empty-short-license-in-dep5-copyright
I think the best we can do is add a Conflicts between the two packages. The
contents of the conflicting directories are different. Personally, I think
it's a bug that the two upstreams install these into the top-level namespace,
but given the nature of the packages, I can see why they did it
core.zip location.
+ * debian/watch: Use the pypi.debian.net redirector.
+
+ -- Barry Warsaw <ba...@debian.org> Thu, 10 Sep 2015 15:25:31 -0400
+
python-babel (1.3+dfsg.1-5) unstable; urgency=medium
* Team upload.
Index: debian/c
Source: cssutils
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cssutils 1.0-2 fails to build from source with Python 3.5.
The upstream bug report is here:
https://bitbucket.org/cthedot/cssutils/issues/52/bad-octal-escape-blows-up-on-python-35b3
- -- System Information:
Source: genshi
Severity: important
Owner: !
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
genshi 0.7-3 currently FTBFS with Python 3.5. Upstream ticket is
http://genshi.edgewall.org/ticket/602 which contains a patch, although
this doesn't completely solve the problem for me. This is a
Hi Sandro,
On Jul 14, 2015, at 02:59 PM, Sandro Tosi wrote:
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?
I'm planning on updating unstable to 1.0.1 today, but I'm not sure
Oops, of course I forgot to mention the change to d/rules in the changelog
entry, but you can fix that. :)
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
+- 05_upstream_devendorize.patch: Upstream's pull request to better
+ support the devendorizing of urllib3 and chardet.
+
+ -- Barry Warsaw ba...@debian.org Wed, 10 Jun 2015 12:28:58 -0400
+
requests (2.7.0-2) unstable; urgency=medium
* Upload to unstable.
Index: debian/patches
This is almost certainly related to the distlib 0.2.0 update which manifest in
bug #785787 (and was fixed there for that example). We'll keep running into
these until I can finish the pip 7 work.
pgpk_T7EaHdb3.pgp
Description: OpenPGP digital signature
@Felix: Actually the pip_util.diff is only relevant for bug #758787. I've
tested what will be pip 1.5.6-6 with that patch and it isn't relevant for bug
#786440 afaict.
I'm inclined not to fix this for the 1.5.6 series, and just concentrate on
getting (now) pip 7 into Debian.
pgptAmkmY7fko.pgp
ScottK and I discussed this and we agreed that the change is necessary, and
that the severity of this bug should be bumped to serious. We also need to
make a change to Debian Python Policy to more accurately reflect the
restriction on wheel files. I will handle both of these changes.
I have committed a fix for this to python-pip's svn and sent a message with
the relevant details to debian-python@. The bug and its fix are pretty
simple. Instead of only putting the .whl files early on sys.path when inside
a venv, we should be doing that in all cases. The only inside/outside
On Dec 02, 2014, at 10:38 PM, Scott Kitterman wrote:
Speaking only for myself, I think that sounds reasonable.
It's well established I believe in Debian Python usage that if a user
installs packages in /usr/local and break their system, they are on their
own, so I'm not particularly worried
On Dec 03, 2014, at 03:20 PM, Piotr Ożarowski wrote:
IMO we should patch pip to *not* touch (install, upgrade, uninstall,
etc.) anything in /usr directory (or /) except /usr/local. Our Python
interpreter already installs to /usr/local and so should pip.
+1
This way:
* pip doesn't need to
I hope you don't mind if I beat you to it? ;)
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
The weird package relationships are due to the interaction between historical
baggage, Debian Python policy, and the port of the cli to Python 3.
python-foo should only be for Python 2 compatible libraries, while python3-foo
is for the Python 3 compatible libraries. Back when python-virtualenv
On Nov 18, 2014, at 09:39 AM, Brian May wrote:
For another solution, have a look at django-admin, provided by the
django-common package. You can call it using any of the following ways:
brian@aquitard:~$ django-admin# run as sh; autodetect python
Yep, that autodetect is clever. Such a
On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote:
From upstream point of view, ZODB3 (aka python-zodb in Debian) used to
include persistent, BTrees, ZODB and ZEO modules. However, since ZODB3
3.11.0a1, upstream has split it up into 4 distinct packages (one for
each module), bump the
Source: genshi
Version: Re-enable genshi support for Python 3.4
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
We previously had to deliberately disable python3-genshi support for
Python 3.3 because upstream was not compatible. This was
implemented in the form of an
On Jun 30, 2014, at 11:18 AM, Thorsten Alteholz wrote:
in debian/README.source you wrote that the docs directory has been
removed. But it is still available in the source tarball. There might
have gone something wrong ...
Hi Thorsten, thanks for the report.
I think this may be due to a
On Jun 30, 2014, at 10:21 PM, Thorsten Alteholz wrote:
On Mon, 30 Jun 2014, Barry Warsaw wrote:
I suppose it would be best to reject the NEW python-pyramid package,
ok, done
New version uploaded. Hopefully I got it right this time.
Cheers,
-Barry
signature.asc
Description: PGP signature
On Jun 30, 2014, at 10:21 PM, Thorsten Alteholz wrote:
On Mon, 30 Jun 2014, Barry Warsaw wrote:
I suppose it would be best to reject the NEW python-pyramid package,
ok, done
Darn, the new upload was rejected.
On Jun 30, 2014, at 09:56 PM, Debian FTP Masters wrote:
python-pyramid_1.5.1+dfsg
On Jun 17, 2014, at 08:52 AM, Raphael Hertzog wrote:
(CCing Barry who expressed interested in python3-django as well)
I started a *very* minimal branch for adding Python 3 packaging to
python-django 1.6, although 1.6.5 is the latest on PyPI (and in Debian).
There's really not much to my branch
easy_install isn't the right way to install packages into the virtualenv
anymore. Please use pip, which should be installed in venv/bin
automatically now. I cannot reproduce the traceback you're seeing.
___
Python-modules-team mailing list
I've not been able to reproduce this. I find it strange that the requests
package didn't get installed automatically as a dependency. In any case,
please try again with the upcoming pip 1.5.6 upload.
___
Python-modules-team mailing list
Switching to --user by default is being actively discussed upstream:
https://github.com/pypa/pip/issues/1668
In the meantime, I plan on updating the manpage to describe --user and any
other missing options.
___
Python-modules-team mailing list
Package: python-webob
Version: 1.3.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
The source package generates a lintian warning
W: python-webob source: missing-license-paragraph-in-dep5-copyright
mit (paragraph at line 6)
I think this is because the
Note that in Python 3.4, we have the stdlib ensurepip module which exposes the
exact same probably there. See bug #732703 for details. I am in the process
of uploading a Debian policy compliant solution, even though it's rather
complex. The same solution could be shared by the standalone
Source: python-psutil
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
psutil 2.0.0 was just announced.
https://pypi.python.org/pypi/psutil/2.0.0
Please update to the new version. There are some API changes, but it
seems easy to port to the new version.
-
On Dec 16, 2013, at 12:41 PM, Arnaud Fontaine wrote:
I see that you're shipping a -doc package, and it looks like
you're not rebuilding docs from a quick scan of rules.
Please re-build docs at build-time, don't ship pre-built
output of sources.
Could you please elaborate?
Actually, this
On Dec 14, 2013, at 05:23 PM, Paul Richards Tagliamonte wrote:
I see that you're shipping a -doc package, and it looks like
you're not rebuilding docs from a quick scan of rules.
Please re-build docs at build-time, don't ship pre-built
output of sources.
Bug #732148
Cheers,
-Barry
I just updated svn for pytest 2.5.0, which depends on python-py 1.4.19. I
updated the d/control version dependency as per this bug.
python-py's maintainer has just uploaded 1.4.19 so we should wait on uploading
pytest 2.5.0 until that's landed.
___
Package: python-psutil
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
There's a new upstream version available (1.1.3 as of this writing).
It should be as easy as bumping d/changelog. I've tested it locally
and it seems fine.
- -- System Information:
Debian
Package: python-pip
Version: 1.4.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
Since SSL certificate checks are now on by default, we really need
ca-certificates to be available for pip to be functional. I propose
to move it from Recommends to Depends.
On Jul 27, 2013, at 11:42 PM, Paul Richards Tagliamonte wrote:
Heyya Barry,
The correct term for that license is `Expat', it'd be nice to change that
in d/copyright!
I changed that in svn for the `Files: *` and License section, but not for
`Files: debian/*` section. I didn't want to do that
Please consider uploading pytest 2.3.4 to experimental soonish. I would like
to update tox to 1.3.4, but this is blocked on a newer pytest. I've updated
alioth pytest svn to the new version, but it currently ftbfs.
___
Python-modules-team mailing list
Package: python3-requests
Version: 0.12.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
Latest upstream version on PyPI is 0.14.2.
I am in the process of upgrading the Ubuntu 13.04 version of the
package (LP: #1076107) and will add a patch when that's
are now required
+ (i.e. Depends instead of Recommends).
+
+ -- Barry Warsaw ba...@ubuntu.com Thu, 01 Nov 2012 14:56:00 +0100
+
requests (0.12.1-1ubuntu6) quantal; urgency=low
* debian/control: Resolve Depends misspelling of python-urllib3.
=== modified file 'debian/control'
--- debian
On Nov 08, 2012, at 12:04 AM, Daniele Tricoli wrote:
Hello Barry,
On Wednesday 07 November 2012 21:18:27 Barry Warsaw wrote:
Attached is the diff against the Ubuntu version of the package. You
should be able to extract the relevant changes for the Debian version,
but because you might
the Python 3 version of the package.
+
+ -- Barry Warsaw ba...@python.org Wed, 18 Apr 2012 15:07:31 -0400
+
pyopenssl (0.13-1) unstable; urgency=low
* New upstream release
=== modified file 'debian/control'
--- debian/control 2011-08-15 18:44:39 +
+++ debian/control 2012-04-18 19:39:17 +
I noticed this same failure when I tried to build the package for Ubuntu.
However, what was weird was that it succeeded for amd64 but failed for i386.
https://launchpad.net/ubuntu/+source/cssutils/0.9.8-1build1
Same results in my PPA:
https://launchpad.net/~barry/+archive/python/+packages
I
Duh. arch: all so nevermind.
signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Package: python-psutil
Version: 0.2.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Sandro. This patch switches python-psutil to dh_python2.
Cheers.
*** /tmp/tmpEEDKld
In
Updated svn in r17925, including Breaks. ScottK is going to review and upload.
signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
Package: pyicu
Version: 1.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
python-support is now officially deprecated in Debian:
On Jul 20, 2011, at 11:05 PM, Jakub Wilk wrote:
* Barry Warsaw ba...@python.org, 2011-07-20, 16:18:
Also note that with the current rules file mod_python does not seem to be
buildable with more than one version of Python, so in converting to
dh_python2, I set X-Python-Version: = 2.7.
Err
On Jul 20, 2011, at 05:16 PM, Barry Warsaw wrote:
Maybe it's better to not include an X-Python-Version header and use
PYVER=$(shell pyversions -d)
instead?
Close. If you remove the X-Python-Version header, you need to add
--no-guessing-versions to the dh_python2 call.
Cheers,
-Barry
Package: libapache2-mod-python
Version: 3.3.1-9
Followup-For: Bug #616858
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As the bug report states, python-central is officially deprecated. This patch
completes the
Hi folks,
I spent about a day and a half tracking down a problem with virtualenv. As of
virtualenv 1.6 (which is in wheezy), it *should* be possible to use python3 as
a -p target. This fails because the way virtualenv re-invokes itself does not
play nicely with our symlink farm.
All the gory
it permanently.
+Author: Barry Warsaw ba...@python.org
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625784
+Forwarded: not-needed
+--- a/virtualenv.py
b/virtualenv.py
+@@ -469,6 +469,14 @@
+ project_name = 'distribute'
+ bootstrap_script = DISTRIBUTE_SETUP_PY
+ try
Package: python-virtualenv
Version: 1.4.9-3ubuntu1
Severity: important
On Wheezy, which has virtualenv 1.6, the following should work:
$ virtualenv -p python3 /tmp/xx
but it fails with this traceback:
-snip snip-
Traceback (most recent call last):
File
1 - 100 of 101 matches
Mail list logo