Bug#799691: zope.i18n: Use of python3-all-dev build-depends excessive
I have committed a fix, but don't have the rights to upload it.
Bug#788697: Rebuild needed
Now that Bug#779324 is fixed, a simple rebuild would to fix the FTBFS. -- Gediminas
Bug#793319: FTBFS: ImportError: cannot import name component_re
Now that Bug#779324 is fixed, a simple rebuild would fix the problem.
2015-07-22 22:58 GMT+03:00 Chris West (Faux) solo-debianb...@goeswhere.com
:
Source: zope.sqlalchemy
Version: 0.6.1-2
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
pydeb: Working on python distribution zope.sqlalchemy
Traceback (most recent call last):
File /usr/bin/van-pydeb, line 9, in module
load_entry_point('van.pydeb==1.3.3', 'console_scripts', 'van-pydeb')()
File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line
552, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line
2672, in load_entry_point
return ep.load()
File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line
2345, in load
return self.resolve()
File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line
2351, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File /usr/lib/python2.7/dist-packages/van/pydeb/__init__.py, line 20,
in module
from pkg_resources import component_re # Is this a public interface?
ImportError: cannot import name component_re
pydeb: Working on binary package
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/zope.sqlalchemy.html
Probably related:
https://bugs.debian.org/788697
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-22-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
___
pkg-zope-developers mailing list
pkg-zope-develop...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers
--
Gediminas
Bug#767554: python-persistent and python-zodb: error when trying to install together
2014-11-14 11:43 GMT+02:00 Arnaud Fontaine ar...@debian.org: Barry Warsaw ba...@debian.org writes: 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 version to 4.0 and made ZODB3 a metapackage depending on all of them. It looks like Debian still has zodb 3.9.7, right? Unfortunately, yes. As of fixing this RC bug for Jessie: Among the four, only persistent package is currently available in Debian, so there is no way to get rid of ZODB3 (at least for Jessie). Barry: If persistent = 4.0 Debian package is useful on its own to anyone (and thus should not be removed From testing), then can I add a Conflict on both packages and upload them to fix this bug? IIRC, I needed to update python-persistent for the Python 3 zope.component transition, as it's a build-dep. There are no other reverse dependencies that I know of. I think a Conflicts is the right way to handle this for now, given where we are in the Jessie release cycle. Arnaud, thanks for handling this! If that's ok with you, I'm going to upload both packages to fix this bug: * python-persistent: Conflicts: python-zodb ( 3.11.0~) * python-zodb: Conflicts: python-persistent Since ZODB3 before the split included persistent, it should provide it: Provides: python-persistent One package that Build-Depends on python-persistent but should be installable with only python-zodb is zope.component. -- Gediminas
Bug#753404: zope.security: Port python-zope.security-untrustedpython from Ubuntu
2014-07-01 18:52 GMT+03:00 Barry Warsaw ba...@debian.org: On Jul 01, 2014, at 05:24 PM, Brian Sutherland wrote: The reason it was not added in Debian is because it requires the RestrictedPython package: https://pypi.python.org/pypi/RestrictedPython That has security implications, and no-one wanted to take responsibility for that. I don't blame them. As it turns out, I'd forgotten that I already sync'd zope.security into Ubuntu, so already dropped this package. This will break a few reverse dependencies which only exist in Ubuntu: Reverse-Depends === * python-zope.app.pagetemplate * python-zope.browserpage * python-zope.pagetemplate * python-zope.ptresource Still, I don't want to block on updating this stack. If no one steps up to take this on in Debian, and it's a critical need in Ubuntu, we'll deal with it there. I've merged zope.security to Ubuntu a few times, keeping the delta. The code requiring RestrictedPython was extracted to a separate package. Newer zope.pagetemplate lists this as an optional dependency and only on python 2. 4.0.2 (2013-02-22) -- - Migrated from ``zope.security.untrustedpython`` to ``zope.untrustedpython``. - Made ``zope.untrustedpython`` an extra dependency. Without it, python expressions are not protected, even though path expressions are still security wrapped. zope.browserpage 4.1.0a1 is updated for this split and requires plain zope.security zope.ptresource 4.0.0a1 too. zope.app.pagetemplate needs a similar change to dependencies upstream. I will deal with this in Ubuntu and upstream if necessary. To keep the same functionality, a new source package zope.untrustedpython should be added to Ubuntu. But can live without it. -- Gediminas
Bug#747845: Daemon running beyond package build
Confirmed. This is caused by running tests during build. Latest version (4.0.0) does not cleanup tests either, reported a bug upstream https://github.com/zopefoundation/zdaemon/issues/7 -- Gediminas
Bug#732421: python-zc.buildout: requires setuptools=0.7 which is not in wheezy
Buildout itself does not require a newer version of setuptools, 0.6c11 is
enough. But the init command bootstraps a new buildout by downloading the
newest version of distribute and this fails. This started happening when
setuptools/distribute merged and setuptools 0.7 was released.
buildout init only creates an empty buildout.cfg file. It's not very useful.
The recommended way is to write the buildout.cfg, create a virtualenv and
bootstrap a self-contained buildout:
virtualenv sandbox
wget http://downloads.buildout.org/1/bootstrap.py
python bootstrap.py
bin/buildout
I never use the system buildout.
2013/12/17 Ryan Nowakowski r...@keyingredient.com
Package: python-zc.buildout
Version: 1.5.2-1
Severity: normal
It seems that buildout 1.5.2 requires setuptools=0.7 which is not is
wheezy:
tubaman@cuisine:~/myproj$ buildout2.7 init
Creating '/home/tubaman/myproj/buildout.cfg'.
Creating directory '/home/tubaman/myproj/bin'.
Creating directory '/home/tubaman/myproj/parts'.
Creating directory '/home/tubaman/myproj/eggs'.
Creating directory '/home/tubaman/myproj/develop-eggs'.
Getting distribution for 'distribute'.
warning: install_lib: 'build/lib.linux-x86_64-2.7' does not exist -- no
Python modules to install
Got distribute 0.7.3.
Getting distribution for 'zc.buildout'.
Got zc.buildout 2.2.1.
While:
Bootstrapping.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/zc/buildout/buildout.py, line
1805, in main
getattr(buildout, command)(args)
File /usr/lib/python2.7/dist-packages/zc/buildout/buildout.py, line
393, in bootstrap
ws.require('zc.buildout')
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 686, in
require
needed = self.resolve(parse_requirements(requirements))
File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 584, in
resolve
raise DistributionNotFound(req)
DistributionNotFound: setuptools=0.7
tubaman@cuisine:~/myproj$
-- System Information:
Debian Release: 7.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-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
Versions of packages python-zc.buildout depends on:
ii python2.7.3-4+deb7u1
ii python-pkg-resources 0.6.24-1
ii python2.6 2.6.8-1.1
ii python2.7 2.7.3-6
python-zc.buildout recommends no packages.
python-zc.buildout suggests no packages.
-- no debconf information
___
pkg-zope-developers mailing list
pkg-zope-develop...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers
--
Gediminas
Bug#697883: Update supervisor to 3.0b2
Tags: patch
I have updated supervisor to the latest version available, 3.0b2, and updated
packaging for the moved source files and heavily updated python packaging
guidelines since the last upload a long time ago.
This was done for Ubuntu, the UDD branch (source with packaging) is available at
https://code.launchpad.net/~menesis/ubuntu/raring/supervisor/raring
and a package was built for several Ubuntu releases in a PPA:
https://launchpad.net/~schooltool-owners/+archive/dev/
Attached is a diff of debian/ , solving this and many other Debian bugs
regarding supervisor.
=== renamed file 'debian/README.conf' = 'debian/README'
=== modified file 'debian/changelog'
--- debian/changelog 2011-05-08 16:45:52 +
+++ debian/changelog 2013-07-22 13:35:52 +
@@ -1,3 +1,34 @@
+supervisor (3.0b2-1) unstable; urgency=low
+
+ * New upstream release. (Closes: #697883)
+- fixes parsing of environment option (Closes: #700370)
+ * debian/control:
+- remove python-support from Build-Depends
+- requires Python = 2.4
+- bump Standards-Version to 3.9.4
+- replace Depends with dh_python2's substvars
+- drop Depends on python-medusa because a patched version is included
+ in the tarball.
+- fix lintian warnings in description (Closes: #697622)
+ * debian/rules:
+- replace everything by dh --with python2
+- install test files
+- do not install medusa/debian subdirectory
+ * debian/supervisor.install: install conffiles, remove dirs installed by
+default.
+ * debian/supervisor.dirs: create etc/supervisor/conf.d
+ * debian/supervisor.pyinstall: add to install version.txt
+ * debian/supervisor.init: fix restart (Closes: #609457)
+ * debian/supervisor.examples, debian/supervisor.docs: update for renamed
+source files.
+ * debian/watch: download from PyPI, there are no files at supervisord.org
+ * Switch to 3.0 (quilt) source format.
+ * debian/patches/read-version.txt.patch: add to fix finding the version.txt file
+ * debian/patches/etc-supervisor.patch: add /etc/supervisor/supervisord.conf
+to config file search path.
+
+ -- Gediminas Paulauskas mene...@pov.lt Wed, 05 Jun 2013 18:47:18 +0300
+
supervisor (3.0a8-1.1) unstable; urgency=low
* Non-maintainer upload.
=== modified file 'debian/control'
--- debian/control 2009-11-07 13:06:00 +
+++ debian/control 2013-07-22 13:35:50 +
@@ -2,19 +2,19 @@
Section: admin
Priority: extra
Maintainer: Anders Hammarquist i...@debian.org
-Build-Depends: debhelper (= 7), python-setuptools (= 0.6c7), python-support, python-all (= 2.3.5-7)
-XS-Python-Version: = 2.3
-Standards-Version: 3.8.3
+Build-Depends: debhelper (= 7.0.50~), python-setuptools, python-all (= 2.6.6-3~)
+XS-Python-Version: = 2.4
+Standards-Version: 3.9.4
Homepage: http://supervisord.org/
Package: supervisor
Architecture: all
-Depends: python (= 2.3), python-medusa (= 0.5.4), python-meld3, python-pkg-resources (= 0.6c7), ${python:Depends}
-Description: A system for controlling process state
+Depends: ${python:Depends}, ${misc:Depends}
+Description: System for controlling process state
Supervisor is a system for controlling and maintaining process state,
similar to what init does, but not intended as an init replacement.
.
- It will manage individual processess or groups of processes that
+ It will manage individual processes or groups of processes that
need to be started and stopped in order, and it is possible to
- control individual process state via an rpc mechanism, thus allowing
+ control individual process state via an RPC mechanism, thus allowing
ordinary users to restart processes.
=== added directory 'debian/patches'
=== added file 'debian/patches/etc-supervisor.patch'
--- debian/patches/etc-supervisor.patch 1970-01-01 00:00:00 +
+++ debian/patches/etc-supervisor.patch 2013-06-07 18:05:20 +
@@ -0,0 +1,14 @@
+Index: supervisor/supervisor/options.py
+===
+--- supervisor.orig/supervisor/options.py
supervisor/supervisor/options.py
+@@ -99,7 +99,8 @@ class Options:
+ searchpaths = [os.path.join(here, 'etc', 'supervisord.conf'),
+os.path.join(here, 'supervisord.conf'),
+'supervisord.conf', 'etc/supervisord.conf',
+- '/etc/supervisord.conf']
++ '/etc/supervisord.conf',
++ '/etc/supervisor/supervisord.conf']
+ self.searchpaths = searchpaths
+
+ def default_configfile(self):
=== added file 'debian/patches/read-version.txt.patch'
--- debian/patches/read-version.txt.patch 1970-01-01 00:00:00 +
+++ debian/patches/read-version.txt.patch 2013-06-06 21:43:52 +
@@ -0,0 +1,15 @@
+Index: supervisor/supervisor/options.py
+===
+--- supervisor.orig/supervisor/options.py
supervisor/supervisor/options.py
+@@ -51,9 +51,7 @@ from supervisor import loggers
Bug#697883: Full debian.tar.gz of updated package
The patch in previous message is a `bzr diff`, adds new files and renames others. For convenience, I attach all the packaging files, made with `bzr bd -S`. supervisor_3.0b2-1.debian.tar.gz Description: Binary data -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 3.0 (quilt) Source: supervisor Binary: supervisor Architecture: all Version: 3.0b2-1 Maintainer: Anders Hammarquist i...@debian.org Homepage: http://supervisord.org/ Standards-Version: 3.9.4 Build-Depends: debhelper (= 7.0.50~), python-setuptools, python-all (= 2.6.6-3~) Package-List: supervisor deb admin extra Checksums-Sha1: f82bc5ff15390dc754570643aa5f1167793f56a7 458264 supervisor_3.0b2.orig.tar.gz 131f175fb769aa7a40a939669506cde3a84c729e 7413 supervisor_3.0b2-1.debian.tar.gz Checksums-Sha256: 3cb0e1d8ce4e4feb8c27923ca996ad7ba725f9d6300b8f8dfd2dbac4998575ed 458264 supervisor_3.0b2.orig.tar.gz abb206d002f5c443fd2d07ba098499fcc3ec83ec7f72c977291f8f288ad10960 7413 supervisor_3.0b2-1.debian.tar.gz Files: e2557853239ee69955f993091b0eddc4 458264 supervisor_3.0b2.orig.tar.gz 463b43a884ee0354badd3e4e6d1dd6ca 7413 supervisor_3.0b2-1.debian.tar.gz Python-Version: = 2.4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHtOxIACgkQvH8GqcmRrccKDACfY8ez8eHfNiyEQ84WhDAaU1bF dEQAn1hF25/s/7Xs5HQS2LgpJsP+gUES =Uvyr -END PGP SIGNATURE- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 05 Jun 2013 18:47:18 +0300 Source: supervisor Binary: supervisor Architecture: source Version: 3.0b2-1 Distribution: unstable Urgency: low Maintainer: Anders Hammarquist i...@debian.org Changed-By: Gediminas Paulauskas mene...@pov.lt Description: supervisor - System for controlling process state Closes: 609457 697622 697883 700370 Changes: supervisor (3.0b2-1) unstable; urgency=low . * New upstream release. (Closes: #697883) - fixes parsing of environment option (Closes: #700370) * debian/control: - remove python-support from Build-Depends - requires Python = 2.4 - bump Standards-Version to 3.9.4 - replace Depends with dh_python2's substvars - drop Depends on python-medusa because a patched version is included in the tarball. - fix lintian warnings in description (Closes: #697622) * debian/rules: - replace everything by dh --with python2 - install test files - do not install medusa/debian subdirectory * debian/supervisor.install: install conffiles, remove dirs installed by default. * debian/supervisor.dirs: create etc/supervisor/conf.d * debian/supervisor.pyinstall: add to install version.txt * debian/supervisor.init: fix restart (Closes: #609457) * debian/supervisor.examples, debian/supervisor.docs: update for renamed source files. * debian/watch: download from PyPI, there are no files at supervisord.org * Switch to 3.0 (quilt) source format. * debian/patches/read-version.txt.patch: add to fix finding the version.txt file * debian/patches/etc-supervisor.patch: add /etc/supervisor/supervisord.conf to config file search path. Checksums-Sha1: 8092d50c4cb295108e90ca813a752db18eb107d0 1145 supervisor_3.0b2-1.dsc f82bc5ff15390dc754570643aa5f1167793f56a7 458264 supervisor_3.0b2.orig.tar.gz 131f175fb769aa7a40a939669506cde3a84c729e 7413 supervisor_3.0b2-1.debian.tar.gz Checksums-Sha256: 2dd3781c35c326d9b8b4483401f7f34f4808b7e9ddf4f51fef7f961d472816d3 1145 supervisor_3.0b2-1.dsc 3cb0e1d8ce4e4feb8c27923ca996ad7ba725f9d6300b8f8dfd2dbac4998575ed 458264 supervisor_3.0b2.orig.tar.gz abb206d002f5c443fd2d07ba098499fcc3ec83ec7f72c977291f8f288ad10960 7413 supervisor_3.0b2-1.debian.tar.gz Files: 7b4b9c9e3cba95ae14b07bdc74861dae 1145 admin extra supervisor_3.0b2-1.dsc e2557853239ee69955f993091b0eddc4 458264 admin extra supervisor_3.0b2.orig.tar.gz 463b43a884ee0354badd3e4e6d1dd6ca 7413 admin extra supervisor_3.0b2-1.debian.tar.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHtOxMACgkQvH8GqcmRrcdIqgCfdcpzrt6zcWmahVdK4+n/cXZ8 ySwAnRrhD8gA51KKzuKCtp/AW1HW2GHs =S4PC -END PGP SIGNATURE-
Bug#555436:
tag 555436 - wontfix + fixed-upstream thanks zope.testing 4 has removed the included doctest module.
Bug#555436:
tags 555436 - wontfix + fixed-upstream thanks zope.testing 4 has removed the included doctest module.
Bug#707893: a newer version packaged
There is a newer version of zc.buildout 1.7.1 with packaging updates from Ubuntu committed to http://anonscm.debian.org/viewvc/pkg-zope/zc.buildout/ . There is also a tag, but it has not been uploaded in fact. Uploading it will remove the binary dependency on python2.6
Bug#700429: Info received (webbrowser additions breaks with chrome)
The Chrome failure was reported as #703872 and fixed in 2.7.4~rc1-3 2013/3/25 Debian Bug Tracking System ow...@bugs.debian.org: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Matthias Klose d...@debian.org If you wish to submit further information on this problem, please send it to 700...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 700429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Gediminas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700429: webbrowser additions breaks with chrome
I get an exception when webbrowser module is used. I have google-chrome installed. The patch does not define a Chrome class. Traceback... ... File /home/menesis/src/schooltool/flourish/src/schooltool-justas/src/schooltool/testing/functional.py, line 28, in module from zope.testing.server import startServer File /home/menesis/.buildout/eggs/zope.testing-3.10.3-py2.7.egg/zope/testing/server.py, line 26, in module import webbrowser File /usr/lib/python2.7/webbrowser.py, line 505, in module register_X_browsers() File /usr/lib/python2.7/webbrowser.py, line 489, in register_X_browsers register(browser, None, Chrome(browser)) NameError: global name 'Chrome' is not defined
Bug#684560: [gaphor] gaphor requires python-setuptools
2012/8/25 Jakub Wilk jw...@debian.org: * Arnaud Fontaine ar...@debian.org, 2012-08-25, 17:05: After investigating a bit this issue, it seems that both zope.component and its requirement, zope.interface, does 'install_requires' setuptools because pkg_resources is required for zope namespace, but after install requires.txt ends up with setuptools. One solution would be to patch setup.py to remove the install_requires line for setuptools, but it will be required in a lot of packages, so I'm wondering if dh_python2 should handle that automatically or with a specific option? What do you think? Thanks! The current behviour of dh_python2 is IMHO errant. It should either 1) translate setuptools in requires.txt into dependency on python-setuptools or 2) remove setuptools from requires.txt when translating it into dependency on python-pkg-resources. dh_python2 does 2) for a year already: python-defaults (2.7.2-2) experimental; urgency=low [ Piotr Ożarowski ] * dh_python2: ... - remove setuptools from requires.txt (it is replaced with python-pkg-resources Debian dependency) ... Most likely the packages mentioned have not been rebuild since then. Or they use dh_pydeb (from python-van.pydeb) that does not remove setuptools from requires.txt Looking at the problem with other side: should setuptools be in requires.txt in the first place if the package uses only pkg_resources? pkg_resources is _the_ thing that checks these requirements after all. I mean, it's like adding dpkg to Depends because you can't install the package without dpkg... :) Most zope packages depend on setuptools. You are right that it is not really needed, but for historical reasons it is there upstream for many packages. -- Gediminas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
2011/9/17 Arnaud Fontaine ar...@debian.org: Hi, I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Indeed, I was waiting for Gediminas to confirm that there is no problem with updating the packages in pkg-zope SVN repository (which includes pytz) to ZTK 1.1.2 before uploading these packages... Gediminas: have you had time to look at that? While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). I would like all the work that is already done uploaded first, and only then look what is not up-to-date with ZTK 1.1 pytz is not even part of ZTK, and should always be the latest, so this discussion did not need to happen. I can update the ZTK myself, and the bump of pytz version would be one I would worry the least about. It is best to match the tzdata version, because python-tz package uses that data instead of the included one. tzdata in sid is already at 2011j. -- Gediminas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617139:
This has been done in this upload: van.pydeb (1.3.2-1) unstable; urgency=low [ Gediminas Paulauskas ] * New upstream release. * Do not add provides for metapackages, because it contains only itself. [ Matthias Klose ] * Build using dh_python2 instead of dh_pycentral. [ Brian Sutherland ] * require python-setuptools, our command line scripts don't work without it. [ Arnaud Fontaine ] * debian/control: + Add Vcs-Browser and rename XS-Vcs-Svn to Vcs-Svn (now supported by dpkg). + Bump Standards-Version to 3.9.2. No changes needed. + Build-Depends on python-all rather than python-all-dev as there is no extension to build. + Remove deprecated XB-Python-Version. + Rename deprecated XS-Python-Version to X-Python-Version and specify the minimum Python version supported as all is deprecated. + Add Homepage field. -- Arnaud Fontaine ar...@debian.org Sun, 01 May 2011 17:06:31 +0900 Closes: #617139 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617162:
tag pending thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630502: python-defaults: dh_python2 does not detect pydeb extension
Package: python-defaults
Severity: normal
Tags: patch
dh_python2 can guess dependencies. But van.pydeb, as used by Debian Zope Team,
has more features. Supposedly, if van.pydeb is used, dh_python2 should not do
dependency guessing.
But the detection only works with complete rules. The more common case now is to
use dh 7 sequencer:
dh --with python2 --with pydeb $@
Such usage should also be detected. Patch attached.
=== modified file 'dh_python2'
--- dh_python2 2011-01-11 14:45:20 +
+++ dh_python2 2011-06-10 18:59:31 +
@@ -486,7 +486,9 @@
except IOError:
log.warning('cannot open debian/rules file')
else:
-if re.compile('\n\s*dh_pydeb').search(fp.read()):
+rules = fp.read()
+if (re.search('\n\s*dh_pydeb', rules) or
+re.search('\n\s*dh\s+[^#]*--with\s+pydeb', rules)):
log.warning('dh_pydeb detected, PyDist feature disabled')
options.guess_deps = False
Bug#463201: Wrong dependencies
One of the major changes in Trac 0.11 is the migration to a new template language, Genshi. Thus the dependencies are wrong The versions from http://trac.edgewall.org/wiki/TracInstall would be Depends: python-genshi (= 0.5) Recommends: python-docutils (= 0.3.9 ), python-pygments | enscript, python-tz Suggests: python-clearsilver (= 0.9.3) I have listed only the packages which should be changed, others are OK AFAICS. Except I have no idea why trac package Suggests: php5-cli. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463201: Wrong dependencies
One of the major changes in Trac 0.11 is the migration to a new template language, Genshi. Thus the dependencies are wrong The versions from http://trac.edgewall.org/wiki/TracInstall would be Depends: python-genshi (= 0.5) Recommends: python-docutils (= 0.3.9 ), python-pygments | enscript, python-tz Suggests: python-clearsilver (= 0.9.3) I have listed only the packages which should be changed, others I have not looked at. Except I have no idea why trac package Suggests: php5-cli. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
