Bug#938027: python-pip: Python2 removal in sid/bullseye

Hi Sandro. Honestly, I have not contributed to Debian in a couple of years, and I don’t see that changing any time soon. Best to contact Matthias, the Python Team, or just do whatever you think is best. Cheers, -Barry > On Mar 13, 2020, at 12:32, Sandro Tosi wrote: > > On Fri, 30 Aug 2019

Bug#890621: forwarded python3.6 issue (bpo-32305 causing regressions)

On Feb 19, 2018, at 04:08, Matthias Klose wrote: > > This is https://bugs.python.org/issue32305, apparently intentional and will be > in 3.7. So better fix the packages itself. Not sure if that really should be > backported. Thanks for the forward. The fix is for third party

Bug#859421: python-tz orphaning

On Apr 07, 2017, at 02:47 AM, Matthias Klose wrote: >I think it's safe to go forward with this. Maybe keep the zope team (or the >individual uploaders) as an uploader for a while, but I think the zope team >is a little bit dead at this point ... I really think we should pull the zope library

Bug#812768: [Python-modules-team] Bug#812768: python-whoosh: diff for NMU version 2.7.0-1.1

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

Bug#851649: (no subject)

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.

Bug#844943: python-bleach: FTBFS: Tests failures

On Jan 13, 2017, at 09:16 PM, Pirate Praveen wrote: >I would prefer this approach as I prefer to avoid maintaining two >versions if possible. I cloned html5lib.git repo, but found recent tags >missing there. Can you push them? Apologies. Tags pushed. Let me know when you have a repo or branch

Bug#844943: python-bleach: FTBFS: Tests failures

Here's another thought. What if we upload a new html5lib source package containing seven-9's? I know we're in freeze, but this may make the most sense. Then, packages which need the old version like bleach can depend on the seven-9's version and that won't affect packages which require the

Bug#844943: python-bleach: FTBFS: Tests failures

On Jan 10, 2017, at 09:37 AM, Pirate Praveen wrote: >bleach and other projects using html5lib seems to have locked the version of >html5lib to the one with 7 nines. Can we also go back to the older version >which works? I had a conversation with the upstream pip maintainer. In theory it may be

Bug#835437: (no subject)

I can't reproduce the build failures reported here even with dpkg-buildpackage -A. However, I am going to add the discard-port proxies to d/rules that pybuild normally adds by default (this package doesn't use pybuild). That at least will prevent the tests from *actually* hitting the internet.

Bug#835437: pycurl: FTBFS too much often (failing tests)

On Nov 03, 2016, at 08:32 PM, Santiago Vila wrote: >My recommendation: Please find the way to disable any tests which >perform network access, I have the strong feeling that the build would >never hang if those tests are disabled. +1 - unfortunately I just don't have any spare cycles right now.

Bug#835437: pycurl: FTBFS too much often (failing tests)

On Nov 03, 2016, at 02:03 PM, Sandro Tosi wrote: >Hey Barry, did you have a chance to look at this? might be also just >forward it upstream and see how that goes. Thanks! I'm sorry, I haven't. :( pgpI4eitBenxl.pgp Description: OpenPGP digital signature

Bug#840847: (no subject)

Any chance this fix can get uploaded soon-ish? gtimelog build depends on it so it's marked for autoremoval because of this bug. Thanks!

Bug#838531: nose2: FTBFS in testing (failing tests)

On Sep 24, 2016, at 03:47 PM, Chris Lamb wrote: >> nose2: FTBFS in testing (failing tests) > >This is somewhat mind-bending to debug: > > AssertionError: Regex didn't match: > 'FAILED \\(failures=5, errors=1, skipped=1\\)' not found in > […] FAILED (failures=1, errors=1, skipped=1)\n'

Bug#828883: (no subject)

This actually turns out to be a bug in pybuild (dh-python). In zope.interface's d/control file we have: Build-Depends: debhelper (>= 9), dh-python, dpkg-dev (>= 1.16.1~), libpython-all-dbg, libpython-all-dev,

Bug#830712: marked as pending

f290d362a8d9767fb18687442d21f25980877481 Author: Barry Warsaw <ba...@python.org> Date: Wed Jul 13 10:11:03 2016 -0400 New upstream release. * New upstream release. * d/control: Add `Breaks: python-enum` to ensure that package (since removed from the archive) gets uninstalled when python-

Bug#828094: python3-coverage: Missing JavaScript dependency: jquery.debounce.min.js

On Jul 03, 2016, at 09:04 PM, Ben Finney wrote: >I can work to package the library dependency; would you be interested >in sponsoring it into the archive? Yes, for sure! pgpYTQQt9NOGZ.pgp Description: OpenPGP digital signature

Bug#828094: python3-coverage: Missing JavaScript dependency: jquery.debounce.min.js

Package: python3-coverage Version: 4.1+dfsg.1-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, Apparently python-coverage has gained a dependency on jquery.debounce.min.js but this isn't available in the archive afaict.

Bug#824566: (no subject)

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!

Bug#817936: roger-router: Please add libpeas-1.0-0-python2loader to Depends

On May 13, 2016, at 08:51 AM, Rolf Leggewie wrote: >Ubuntu is still unchanged both in Xenial and Yakkety. I'm currently in the process of resyncing the libpeas stack in Debian back to Yakkety. It's slow going because the python2/3 loader issue isn't the only delta from Debian in these packages.

Bug#820312: marked as pending

d0dc602f58cb2e04a0b559e79285e646d4bc2f26 Author: Barry Warsaw <ba...@python.org> Date: Wed May 11 14:39:40 2016 -0400 New upstream release. * New upstream release. - Closes: #793506 - Closes: #820312 diff --git a/debian/changelog b/debian/changelog index db49fb4..f84459b 100644 --- a/

Bug#821223: [Python-modules-team] Bug#821223: Unable to create a virtualenv: invalid requirement: '_markerlib'

I'll have a fix uploaded momentarily.

Bug#821223: (no subject)

Can you please report the output of `dpkg-query -W python-pip-whl`, both if virtualenv works and doesn't work for you?

Bug#820195: (no subject)

FWIW, attached is the patch in Ubuntu which fixes the FTBFS. This comes from 0.6-1ubuntu1. Description: Adapt tests to changes in NumPy 1.10 Default casting rule Origin: Upstream (commit 9b91b1789c8dc81e84c0a8691febbd1e242a81d1) --- pint/testsuite/helpers.py | 8 +++-

Bug#815294: marked as pending

d861abd6921e13b2d07f6b482fdb2a7e2bad8909 Author: Barry Warsaw <ba...@python.org> Date: Mon Apr 11 16:42:14 2016 -0400 Fix FTBFS, bump Standards-Version, add DEP-8 tests. * d/rules: override_dh_auto_test: Don't run the test suite at build time since upstream's tests/ directory

Bug#804582: (no subject)

Okay, so I think the locale changes are enough to fix the FTBFS. I retried building in an Ubuntu PPA and the build succeeded. The timeout failure must just have been a problem with my local sbuild.

Bug#804582: (no subject)

It's a locale problem. This fixes most of the problems: diff --git a/debian/rules b/debian/rules index 9c04662..6130dc4 100755 --- a/debian/rules +++ b/debian/rules @@ -1,6 +1,8 @@ #!/usr/bin/make -f export PYBUILD_NAME=paramiko +export PYBUILD_VERBOSE=1 +export DH_VERBOSE=1 %: dh

Bug#804582: (no subject)

I haven't quite fixed it yet, but it's almost certainly related to FOLDER in test_sftp.py. When the tests, such as test_K_utf8() fail, it's because the folder isn't empty so the os.rmdir() fails. Quickly I tried to add a TEST_FOLDER=`mktemp -d` to the test command but that didn't quite work. I

Bug#804582: (no subject)

On Apr 08, 2016, at 10:59 AM, Jeremy T. Bouse wrote: >Yes, I'd taken a slightly different approach but got to the same results >that you are currently getting. I have included your approach as it is >much cleaner than what I'd hacked together. > >Still trying to get to the bottom of those

Bug#804582: (no subject)

I'm running across this too now. I think part of the problem is that pybuild invokes unittest discover by default, but this isn't how paramiko's test suite is actually run, at least if you go by what's in the tox.ini file. This gets me closer: diff --git a/debian/rules b/debian/rules index

Bug#807351: (no subject)

I just ran across this bug too, but not until I worked out a different patch. ;) I'd be fine with Neil's patch, or deleting the test entirely. In the attached, I only assert that the SystemError is raised, but not what the exception message is. The other change is to close a small (possibly

Bug#815864: (no subject)

debugging when the +ensurepip command fails. + * d/patches/ensurepip-wheels.diff: Update for compatibility with latest +python-pip packages. + * d/control.in: Update python-pip-whl dependency version. + + -- Barry Warsaw <ba...@debian.org> Wed, 09 Mar 2016 16:23:54 -0500 + python3.5 (3

Bug#813571: (no subject)

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.

Bug#815864: (no subject)

/control.in: Update python-pip-whl version dependency. + + -- Barry Warsaw <ba...@ubuntu.com> Mon, 29 Feb 2016 16:45:06 -0500 + python3.5 (3.5.1-6ubuntu2) xenial; urgency=medium * python3.5-venv: Drop the dependency on python-pip-whl, depend on diff --git a/debian/control.in b/debian/cont

Bug#815864: (no subject)

more debugging when the +ensurepip command fails. + * d/patches/ensurepip-wheels.diff: Update for compatibility with latest +python-pip packages. + * d/control.in: Add virtualenv to Depends of pythonX.Y-venv. + + -- Barry Warsaw <ba...@ubuntu.com> Mon, 29 Feb 2016 16:45:06

Bug#814622: [Python-modules-team] Bug#814622: (no subject)

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.

Bug#814622: (no subject)

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

Bug#814571: marked as pending

e33082b7e0da3202e43005e71e323c699b589086 Author: Barry Warsaw <ba...@python.org> Date: Mon Feb 15 13:12:00 2016 -0500 d/control: Update the python-setuptools-whl Breaks/Replaces versions. (Closes: #814571) diff --git a/debian/changelog b/debian/changelog index e64086c..5c534f9 100644 --- a/debian/cha

Bug#814571: [Python-modules-team] Bug#814571: python-setuptools-whl and python-pip-whl: error when trying to install together

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

Bug#814571: [Python-modules-team] Bug#814571: python-setuptools-whl and python-pip-whl: error when trying to install together

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

Bug#813399: [Python-modules-team] Bug#813399: python-pip-whl: fails to upgrade from 'testing' - trying to overwrite /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl

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

Bug#813399: marked as pending

7994a7639100ece279608917e1fb1867cb103d83 Author: Barry Warsaw <ba...@python.org> Date: Fri Feb 12 14:24:07 2016 -0500 d/control: Fix Breaks/Replaces version on python-six-whl. (Closes: #813399) diff --git a/debian/changelog b/debian/changelog index 423a15c..e64086c 100644 --- a/debian/changelog

Bug#814069: python-six-whl and python-pip-whl: error when trying to install together

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

Bug#813399: [Python-modules-team] Bug#813399: python-pip-whl: fails to upgrade from 'testing' - trying to overwrite /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl

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

Bug#813399: marked as pending

af4faa13f52f7c14b5a06c77a5ff2aad20164fce Author: Barry Warsaw <ba...@python.org> Date: Mon Feb 1 13:09:38 2016 -0500 d/control: Fix Breaks/Depends for python-pip-whl. (Closes: #813399) diff --git a/debian/changelog b/debian/changelog index 686617a..6c49120 100644 --- a/debian/changelog +++ b/

Bug#813162: [Python-modules-team] Bug#813162: python3-pip: missing dependencies

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? pgpxoVou06iwX.pgp Description: OpenPGP digital signature

Bug#813162: [Python-modules-team] Bug#813162: python3-pip: missing dependencies

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

Bug#813162: marked as pending

b17ccb1c0f4bed16364605f7f9945854c3fd5877 Author: Barry Warsaw <ba...@python.org> Date: Fri Jan 29 21:44:08 2016 -0500 d/control: Add binary version dependency. (Closes: #813162) diff --git a/debian/changelog b/debian/changelog index 90d8104..2744c8c 100644 --- a/debian/changelog +++ b/debian/cha

Bug#810139: (no subject)

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

Bug#808843: marked as pending

52a8f944af07a44758c6f5b8f815856d77787b59 Author: Barry Warsaw <ba...@ubuntu.com> Date: Mon Jan 4 13:42:53 2016 -0500 New upstream release. * Team upload. * New upstream release. (Closes: #808843) * d/watch: Adjust filenamemangle to account for seemingly recent uscan behavior

Bug#804558: [Python-modules-team] Bug#804558: tweepy: FTBFS: ImportError: No module named {unittest2, vcr}

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

Bug#808763: [Python-modules-team] Bug#808763: Running pytest

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

Bug#795216: marked as pending

319ab86dbeef788318c674e4e862019d50e99e6f Author: Barry Warsaw <ba...@python.org> Date: Fri Nov 20 17:03:35 2015 -0500 d/copyright: Added missing licenses. (Closes: #795216) diff --git a/debian/changelog b/debian/changelog index 55fb182..3ebc010 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,

Bug#802141: (no subject)

A better way to skip trying to run the nonexistent upstream test suite is to add this to d/rules: export PYBUILD_DISABLE=test

Bug#802145: marked as pending

8b1eec6402bfe18f0c92f5d094a1ea467917c205 Author: Barry Warsaw <ba...@python.org> Date: Tue Oct 27 16:20:02 2015 -0400 * Non-maintainer upload. * Add python-requests to Build-Depends. (Closes: #802145) * Removed some underscores from long description. (Closes: #799531) diff --git a/

Bug#802145: Attached debdiff for NMU - please commit to packaging Git

On Oct 26, 2015, at 11:04 AM, Andreas Tille wrote: >I took the freedom to fix the minor bug in addition to the serious >one. Please add the debdiff to your packaging git. Done, and thanks!

Bug#802130: (no subject)

https://github.com/malthe/chameleon/issues/206 pgpqR6mDavIMd.pgp Description: OpenPGP digital signature

Bug#789670: (no subject)

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

Bug#795594: (no subject)

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

Bug#796898: python-pykmip: Remove Depends and Build-Depends on python3-enum34

Source: python-pykmip Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, python-pykmip currently includes Depends and Build-Depends on python3-enum34. This package is incompatible with Python 3.5 and unnecessary for Python 3.4 since the stdlib already contains

Bug#796909: python3-pies: Don't Depend on python3-enum34

Package: python3-pies Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, python3-enum34 binary package has been removed from the archive, because all supported versions of Python 3 already include the stdlib enum package, and enum34 is no longer compatible with

Bug#744145: (no subject)

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. -- To

Bug#774213: (no subject)

Something else must still be going on. I have the following zope packages installed: % aptitude search zope | grep ^i i python-zope.component - Zope Component Architecture i python-zope.configuration - Zope Configuration Markup Language (ZCML) i

Bug#774213: zope2.13: import zope.security._proxy - SystemError: dynamic module not initialized properly

On Dec 30, 2014, at 02:32 PM, Kirill Smelkov wrote: Package: zope2.13 Version: 2.13.22-1 Severity: grave Justification: renders package unusable With zope2.13 I've tried to create a (user) instance and start it, but a `SystemError: dynamic module not initialized properly` is raised while zopectl

Bug#768286: marked as done (python{, 3}-zope.interface-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

On Dec 28, 2014, at 11:48 PM, Ivo De Decker wrote: On Sun, Dec 28, 2014 at 05:31:59PM -0500, Barry Warsaw wrote: Would you please attach a debdiff against 4.1.1-3 so it's easier for me to make sure that a future release from alioth vcs doesn't regress? Sure. Attached. Thanks, applied

Bug#767554: python-persistent and python-zodb: error when trying to install together

On Dec 08, 2014, at 01:47 PM, Arnaud Fontaine wrote: Arnaud Fontaine wrote (26 Nov 2014 09:03:09 GMT) : Really sorry about that. FTR, I have not uploaded anything yet because the release team would prefer to avoid the Conflicts if possible and make python-zodb depends upon

Bug#771794: pip silently removes/updates system provided python packages

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

Bug#771794: [Python-modules-team] Bug#771794: pip silently removes/updates system provided python packages

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

Bug#771794: (no subject)

For reference: https://github.com/pypa/pip/issues/1668 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767554: python-persistent and python-zodb: error when trying to install together

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

Bug#752078: (no subject)

I think it's better to prune the files in that directory from the orig tarball, using a Files-Excluded header in d/copyright. The reason for this is that, even though the package does not currently contain the documentation, if it ever does, it's better to rebuild the docs from scratch using

Bug#751804: (no subject)

Are you reporting a packaging bug or an upstream bug? I ask because 1.7.1-1 doesn't explicitly set $HOME any more. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#719767: (no subject)

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

Bug#731299: (no subject)

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. -- To UNSUBSCRIBE, email to

Bug#707086: (no subject)

This is caused by the ancient version of zope.interface in sid/jessie. We need to get z.i 4.0.5 (the latest upstream release) and then this bug will fix itself wink. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#572072: (no subject)

For all intents and purposes, computer-janitor is abandonware. https://bugs.launchpad.net/ubuntu/+source/computer-janitor/+bug/1050071 signature.asc Description: PGP signature

Bug#661441: (no subject)

I added a merge proposal on the Ubuntu bug which fixes the FTBFS (and adds the `set -x` flag in d/rules). I'm not sure upstream would approve of the patch, since it's not clear to me whether the bogus SCRIPT tag should be entirely stripped or not. But in the absence of upstream response to their

Bug#679968: in ipython shell -- inserts history substitution before the prompt line -- renders python-mode interactive use with ipython unusable

On Jul 02, 2012, at 04:45 PM, Yaroslav Halchenko wrote: if python-mode.el is affected, please open a ticket also at https://bugs.launchpad.net/python-mode isn't python-mode.el belonging to python-mode package the one responsible for setting up ipython shell comint mode??? (sorry, I just do not

Bug#646464: (no subject)

to run autogen.sh after applying the + configure.ac patches. + + -- Barry Warsaw ba...@ubuntu.com Wed, 22 Feb 2012 17:14:50 -0500 + smc (1.9-4ubuntu1) oneiric; urgency=low * Update 02_binutils-gold.patch to properly use LDADD. Fixes FTBFS. === modified file 'debian/control' --- debian

Bug#642660: (no subject)

Attached is the fix I applied on Ubuntu, which builds fgfs-atlas from CVS. Cheers. === modified file 'debian/control' --- debian/control 2009-10-17 02:27:02 + +++ debian/control 2012-02-14 21:45:12 + @@ -1,14 +1,17 @@ Source: fgfs-atlas Section: games Priority: extra -Maintainer: Ove

Bug#658787: (no subject)

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

Bug#658787: (no subject)

Duh. arch: all so nevermind. signature.asc Description: PGP signature

Bug#651996: (no subject)

/changelog2012-01-03 18:08:38 + @@ -1,3 +1,11 @@ +cython (0.15.1-2) UNRELEASED; urgency=low + + * debian/patches/python27-testsuite-fix.patch: +Fix test suite for Python 2.7 change. Patch comes from Cython +upstream, post 0.15.1 release. (Closes: #651996) + + -- Barry Warsaw ba

Bug#642601: (no subject)

Yep, we fixed this in Ubuntu back in November. Here's the merge proposal at the time: https://code.launchpad.net/~barry/update-manager/673297-py27/+merge/40510 And the patch we applied (omitting debian/changelog): === modified file 'UpdateManager/Core/utils.py' --- UpdateManager/Core/utils.py

Bug#638953: (no subject)

I'm testing this patch in Ubuntu (which has the same ftbfs): https://github.com/nipy/nipype/commit/33db6f6bff3d0b554037e0169d17a14b7ff66f89 signature.asc Description: PGP signature

Bug#638953: (no subject)

ftbfs due to ImportError. This patch contains the + upstream git pull request fixing the import. +Origin: + https://github.com/nipy/nipype/commit/33db6f6bff3d0b554037e0169d17a14b7ff66f89 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nipype/+bug/835008 +Forwarded: not-needed +Author: Barry

Bug#638953: (no subject)

On Sep 22, 2011, at 02:26 PM, Yaroslav Halchenko wrote: eh -- we crossed in hyperspace -- I called mine up_recent_nipy_reference and didn't include all the nice headers... do you have a helper script for this DEP-3-friendliness? Nope, just quick Emacs fingers. But I always have to lookup DEP-3

Bug#632225: Cod review

Hi Jelmer, On Sep 19, 2011, at 11:22 PM, Jelmer Vernooij wrote: client.c:318 client_set_notify_funct() where notify_baton2 has inconsistent refcounting between the if-clause and else-clause. When you go through the if-clause, notify_baton2 steals a reference to Py_None, which is going to

Bug#632225: Cod review

I did a very quick review of the C code here (branched from debianlp:subvertpy on Launchpad, so should be the sid package), and found a number of questionable things. I don't know the library code or the svn API very well, so it's entirely possible that some or all of these are false alarms.

Bug#634107: (no subject)

I had a problem with pbuilder on wheezy. This Launchpad bug might be related: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/805886 I tested this fix in the Debian package for util-linux: https://code.launchpad.net/~pr0gg3d/ubuntu/oneiric/util-linux/bug-805886/+merge/70680 and it

Bug#634860: (no subject)

Updated svn in r17925, including Breaks. ScottK is going to review and upload. signature.asc Description: PGP signature

Bug#623165: FTBFS w/ Python 2.7 enabled

Here is the bug report for graphviz failure against Python 2.7 in Ubuntu Natty: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/683182/+index Here's the debdiff I applied to our package to get it to build:

Bug#568674: (no subject)

This is on our (upstream's) radar: http://bugs.python.org/issue7755 signature.asc Description: PGP signature