Bug#991709: unblock: python-defaults/2.7.18-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-defaults (just uploaded, so needs few more days but hopefully it will make it into Bullseye) [ Reason ] pyclean and pycomile scripts (and debpython module stripped down to code needed by mentioned scripts) were accidentally removed in 2.7.18-1 from python2-minimal package. There's a fallback code in maintainer scripts (in python-foo packages) so nobody noticed for almost a year but fortunately Jakub Wilk pinged us about the problem. [ Impact ] We're almost done with removing Python 2.X stack, but these scripts are still used and cover few more cases than the fallback code. At least pyclean will be used a lot while removing old packages. unblock python-defaults/2.7.18-3 diff -Nru python-defaults-2.7.18/debian/changelog python-defaults-2.7.18/debian/changelog --- python-defaults-2.7.18/debian/changelog 2020-08-04 10:22:34.0 +0200 +++ python-defaults-2.7.18/debian/changelog 2021-07-28 13:17:06.0 +0200 @@ -1,3 +1,9 @@ +python-defaults (2.7.18-3) unstable; urgency=medium + + * Install pycompile and pyclean accidentally removed in -1 + + -- Piotr Ożarowski Wed, 28 Jul 2021 13:17:06 +0200 + python-defaults (2.7.18-2) unstable; urgency=medium * Don't ship a duplicate README.Debian in python2-doc. Closes: #966823. diff -Nru python-defaults-2.7.18/debian/rules python-defaults-2.7.18/debian/rules --- python-defaults-2.7.18/debian/rules 2020-08-04 10:20:50.0 +0200 +++ python-defaults-2.7.18/debian/rules 2021-07-28 13:16:09.0 +0200 @@ -112,6 +112,7 @@ dh_testroot # dh_installdirs -ppython usr/share/doc/python dh_install + DESTDIR=debian/python2-minimal PREFIX=/usr make install-runtime touch stamp-install signature.asc Description: PGP signature
Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1
Control: tags -1 - moreinfo > that's because Thomas overwrote my NMU with another upload, please give > me some time to talk with him Thomas added my changes back, all 3 OpenStack packages have ">=" dependency only (no "<<" anymore)
Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1
[Niels Thykier, 2017-04-03] > > unblock sqlalchemy/1.1.5+ds1-1 > > unblock murano/1:3.0.0-3.1 > > unblock ceilometer/1:7.0.1-1.1 > > unblock mistral/3.0.0-2 > > > > I cannot exactly say I am trilled with this change. But starting from > the bottom, something is definitely wrong. AFAICT, the latter 3 > packages in your unblock request fail piuparts tests because they cannot > be installed with the following: > > """ > The following packages have unmet dependencies: >piuparts-depends-dummy : Depends: python-sqlalchemy (< 1.1.0) but > 1.1.6+ds1-1 is to be installed > E: Unable to correct problems, you have held broken packages. > """ > > That suggests to me that this unblock request cannot succeed in its > current form. These 3 openstack packages have other bugs that would be > great to have fixed in testing (a nettools dependency issue), so I would > be glad if that part could get solved. that's because Thomas overwrote my NMU with another upload, please give me some time to talk with him
Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1
FYI: I plan to upload sqlalchemy 1.1.6+ds1-1 (i.e. a new upstream release in 1.1.X series). I assume if you will allow 1.1.5, then there's no reason to not allow 1.1.6 - i.e. next bug fix release in 1.1 series. Note that upstream already started working on 1.2 series which I'm not considering for Stretch - these one gets new features and f.e. drops Python 2.6 (which we don't support since a long time, but still) - my point is: upstream is sane. -- GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sqlalchemy 1.1 - it was in unstable for a very
long time and was my plan to ship it in Strech since the first beta
release of 1.1.0. Upstream author provides best unit test coverage I've
seen in an Open Source project and cares about stability and
compatibility a lot (+ provides very detailed migration guides).
A lot of packages needed an update for 1.1 but it was mostly a rebuild & check
(I was generating << X.Y+1 dependency for each package that depended on
X.Y release before 1.1 one), this work was done long before freeze.
It was supposed to be done even sooner, but I kept it in experimental
for over a month due to miscommunication with another developer.
I've missed few packages (and was busy with RL) so it didn't propagate
to testing on time. Packages that blocked the migration are: ceilometer,
murano, ceilometer and mistral - see below.
ceilometer and murano NMUs have just a requirements.txt tiny patch to
drop << 1.1 dependency. requirements.txt is used in Python world for
recommended env. (in contrast to setup.py's requires.txt which is
supposed to list minimum required dependencies) - unfortunately
OpenStack upstream decided to not bother with it and just copy
requirements.txt into requires.txt - a lot of OS packages were patched
for this reason (thanks to OS team!), unfortunately I've missed two.
mistral 3.0.0-2 was uploaded on 24 Oct 2016 with sqlalchemy >= 1.1
dependency so it didn't migrate to testing due to missing SA 1.1
All other python-sqlalchemy and python3-sqlalchemy rev. dependencies are
already in testing because, as I mentioned before, sqlalchemy no longer
generates (via dh_python{2,3}) <
signature.asc
Description: PGP signature
Re: Transition to SQLAlchemy 1.1.x
[Emilio Pozuelo Monfort, 2016-11-21] > Piotr, any comment on that? I'm done talking with Thomas, it's always either his way or nothing. The one and only reason I uploaded 1.1 to experimental was to make it easier to test Openstack. I completed the "transition" on Friday¹, I didn't even need the whole weekend. Sure, I wasn't able to test all of them as I didn't always really know how (like in this² case). Griffith, the app I'm a co-author, wasn't (unfortunately) updated in years... and it still works with each new X.Y SA release. SA has also the best unit tests I've seen in a Python library, so I'm pretty confident 1.1 is good enough for Stretch (that's why I want to update x.y.Z releases in stable, I was told not to do that in the past, I will ask again for Stretch). The only missing pieces for now are the ones from very cooperative Openstack Team. Since I feel very strongly about this (I feel deceived) I will let Thomas take it to the TC (if they want to take this package from me, so be it - I will not upload 1.0 to unstable again). Packages rebuild with 1.1 will migrate to testing even now, as they no longer have << 1.X dependency, so the new maintainer will not have to do much to revert to 1.0). In the meantime I will send patches to the Openstack packages that really need this (as I understand it, it's not only SQLAlchemy-migrate³, now, I will check if migrate is the reason 2 more showed up). [¹] there are still 2 PAPT packages that have new upstream releases and maintainer wanted to work on it in a week or so so I didn't upload those, I might soon if that's a problem. [²] https://lists.alioth.debian.org/pipermail/debian-med-packaging/2016-November/047994.html [³] I even recall helping Thomas to make it buildable again, once he told me it's failing to build (even with SA 1.0) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: Transition to SQLAlchemy 1.1.x
[Rene Engelhard, 2016-11-18] > > [...] > > To sum up: it's IMO really too late for such an upload, and it shouldn't > > be allowed, unless we don't care about OpenStack in Debian. > > Yup. Transition freeze was ~2 weeks ago, and this wasn't approved, so I've > no idea why this should be allowed... that's because: a) I consider SQLAlchemy new upstream releases stable now, so I dropped the << dependency in latest upload b) I wanted to upload it over a month ago. The << 1.1 dependency is mostly in OpenStack packages so I contacted Thomas back then. He asked me to wait 1 or 2 weeks because he's busy. I agreed to upload to experimental for now so that he can do tests and asked him to not complain later about library transition freeze (sic!). He didn't report back any problems except SQLAlchemy Migrate (about which he wanted to talk with SQLAlchemy's upstream author during OpenStack conference IIRC). I wanted to upload it later so I contacted him again, no response until yesterday when he told me I can go to hell basically. Most of packages are ready now, even without rebuild. I will rebuild all that are not in OpenStack team over the weekend. Rebuilt packages work fine with 1.0 an 1.1 (rebuild will simply remove << 1.1 dependency) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Bug#772070: unblock: pygments/2.0.1+dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package pygments This is upstream's final release (testing currently has release candidate + some additional commits from upstream repo) that contains fixes and lexer improvements only (default lexer encoding change from upstream changelog was already in Debian since a long time and I finally removed my patch) unblock pygments/2.0.1+dfsg-1 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash pygments.diff.xz Description: application/xz signature.asc Description: Digital signature
Bug#771963: unblock: python3-defaults/3.4.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python3-defaults
It cleans after bugs like 771095 or 769769 (in python3.4).
py_compile.py in python3.4 was already fixed upstream (see
http://bugs.python.org/issue22966) and in the Debian package (BTW, it
would be great if you could unblock python3.4 as well) but pyc files are
already there (not in stable, though, python3.2 is not affected) and
fixed python3.4 will not remove already generated files
unblock python3-defaults/3.4.2-2
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru python3-defaults-3.4.2/debian/changelog python3-defaults-3.4.2/debian/changelog
--- python3-defaults-3.4.2/debian/changelog 2014-10-08 15:43:43.0 +0200
+++ python3-defaults-3.4.2/debian/changelog 2014-11-29 18:36:28.0 +0100
@@ -1,3 +1,10 @@
+python3-defaults (3.4.2-2) unstable; urgency=medium
+
+ * py3clean: remove pyc files generated from files with dot in its name
+(workaraunds http://bugs.python.org/issue22966)
+
+ -- Piotr Ożarowski pi...@debian.org Sat, 29 Nov 2014 18:14:17 +0100
+
python3-defaults (3.4.2-1) unstable; urgency=medium
[ Scott Kitterman ]
diff -Nru python3-defaults-3.4.2/py3clean python3-defaults-3.4.2/py3clean
--- python3-defaults-3.4.2/py3clean 2012-12-12 00:33:09.0 +0100
+++ python3-defaults-3.4.2/py3clean 2014-11-29 18:34:17.0 +0100
@@ -97,13 +97,18 @@
# remove compiled files in __pycache__ directory
def find_files_to_remove(pyfile):
directory = join(dirname(pyfile), '__pycache__')
-fnames = %s.* % splitext(basename(pyfile))[0]
-for fn in glob1(directory, fnames):
+fname = splitext(basename(pyfile))[0]
+for fn in glob1(directory, %s.* % fname):
yield join(directory, fn)
# remove classic .pyc files as well
for filename in (%sc % pyfile, %so % pyfile):
if exists(filename):
yield filename
+# workaround for http://bugs.python.org/issue22966
+if '.' in fname:
+sane_fname = join(dirname(pyfile), fname.split('.', 1)[0])
+for fn in find_files_to_remove(sane_fname):
+yield join(directory, fn)
elif magic_tag is False:
# remove 3.1's .pyc files only
@@ -119,6 +124,11 @@
fname = splitext(basename(pyfile))[0]
for fn in glob1(directory, %s.%s.py[co] % (fname, magic_tag)):
yield join(directory, fn)
+# workaround for http://bugs.python.org/issue22966
+if '.' in fname:
+sane_fname = join(dirname(pyfile), fname.split('.', 1)[0])
+for fn in find_files_to_remove(sane_fname):
+yield join(directory, fn)
def myremove(fname):
remove(fname)
signature.asc
Description: Digital signature
Bug#769330: unblock: dh-python/1.20141111-2
Control: tags -1 -moreinfo The other change in this upload is to set binary package's Multi-Arch to foreign. This is a blocker; the bug is closes is normal, and we aren't accepting multi-arching now without exceptional circumstances. Can you prepare a package that doesn't include this please? done in -2 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141115120217.gc4...@sts0.p1otr.com
Bug#769330: unblock: dh-python/1.20141111-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dh-python
Python's Requires field can contain module names and hence
dh_python2/dh_python3 was generating incorrect dependencies while
guessing package name for modules with such requirements. See f.e.
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1389283
In 1.2014-1 upload I changed dh_python* to use pre-generated list of
all packages that ship Egg metadata (and not only those with unusual
names - this change makes this upload backwards compatible) and disabled
guessing for modules not available during build or on the fallback list.
In Jessie+1 I will add a code that searches also for modules (unless you
think such changes are acceptable for an unblock as well :).
guess_dependency() is used only in pydist.py and depends.py (both support
returning None in this function)
The other change in this upload is to set binary package's Multi-Arch to
foreign.
`debdiff dh-python_1.20141026-1.dsc dh-python_1.2014-1.dsc | filterdiff -x
'*_fallback'`
output attached (fallback files contain list of all packages with Egg
metadata)
unblock dh-python/1.2014-1
diff -Nru dh-python-1.20141026/debian/changelog
dh-python-1.2014/debian/changelog
--- dh-python-1.20141026/debian/changelog 2014-10-26 23:41:38.0
+0100
+++ dh-python-1.2014/debian/changelog 2014-11-11 21:23:22.0
+0100
@@ -1,3 +1,15 @@
+dh-python (1.2014-1) unstable; urgency=medium
+
+ * Set dh-python's Multi-Arch to foreign (closes: 767339)
+ * dist_fallback files now contain list of all packages that provide Egg
+metadata (i.e. not just packages that don't have sensible name)
+ * dh_python* no longer guesses dependency from requires.txt files nor
Requires
+fields. Dependencies are generated only if given requirement is available
+in dist_fallback file (generated at dh-python's build time) or if it's
+available at build time (hint: Build-Depends)
+
+ -- Piotr Ożarowski pi...@debian.org Tue, 11 Nov 2014 21:23:20 +0100
+
dh-python (1.20141026-1) unstable; urgency=medium
[ Stefano Rivera ]
diff -Nru dh-python-1.20141026/debian/control
dh-python-1.2014/debian/control
--- dh-python-1.20141026/debian/control 2014-10-26 23:41:17.0 +0100
+++ dh-python-1.2014/debian/control 2014-11-11 15:42:25.0 +0100
@@ -14,6 +14,7 @@
Package: dh-python
Architecture: all
+Multi-Arch: foreign
Depends: ${misc:Depends}, ${python3:Depends}
Breaks:
# due to /usr/bin/dh_python3 and debhelper files
diff -Nru dh-python-1.20141026/dhpython/pydist.py
dh-python-1.2014/dhpython/pydist.py
--- dh-python-1.20141026/dhpython/pydist.py 2014-10-26 23:41:41.0
+0100
+++ dh-python-1.2014/dhpython/pydist.py 2014-11-11 21:23:41.0
+0100
@@ -117,13 +117,14 @@
def guess_dependency(impl, req, version=None):
-log.debug('trying to guess dependency for %s (python=%s)',
+log.debug('trying to find dependency for %s (python=%s)',
req, version)
if isinstance(version, str):
version = Version(version)
# some upstreams have weird ideas for distribution name...
name, rest = re.compile('([^!= \(\)\[]+)(.*)').match(req).groups()
+# TODO: check stdlib and dist-packaged for name.py and name.so files
req = safe_name(name) + rest
data = load(impl)
@@ -154,7 +155,7 @@
else:
return item['dependency']
-# try dpkg -S
+# search for Egg metadata file or directory (using dpkg -S)
query = PYDIST_DPKG_SEARCH_TPLS[impl].format(ci_regexp(safe_name(name)))
log.debug(invoking dpkg -S %s, query)
@@ -175,13 +176,13 @@
else:
log.debug('dpkg -S did not find package for %s: %s', name, stderr)
-# fall back to python-distname
pname = sensible_pname(impl, name)
-log.info('Cannot find installed package that provides %s. '
- 'Using %s as package name. Please add %s correct_package_name '
- 'line to %s to override it IF this is incorrect.',
- name, pname, safe_name(name), PYDIST_OVERRIDES_FNAMES[impl])
-return pname
+log.info('Cannot find package that provides %s. '
+ 'Please add package that provides it to Build-Depends or '
+ 'add %s %s-fixme line to %s or add proper '
+ ' dependency to Depends by hand and ignore this info.',
+ name, safe_name(name), pname, PYDIST_OVERRIDES_FNAMES[impl])
+# return pname
def parse_pydep(impl, fname):
diff -Nru dh-python-1.20141026/.gitignore dh-python-1.2014/.gitignore
--- dh-python-1.20141026/.gitignore 2014-10-26 23:41:41.0 +0100
+++ dh-python-1.2014/.gitignore 2014-11-11 21:23:41.0 +0100
@@ -5,6 +5,7 @@
pydist/cache/
*\.1
*\.pyc
+*\.swp
*\.deb
*\.changes
*\.log
diff -Nru dh-python-1.20141026/pydist/cpython2_fallback
dh-python-1.2014
Re: SQLAlchemy 0.9.X in unstable
[Thomas Goirand, 2014-02-23] CC-ing the release team, since I think you should have coordinate with them here. dropping everyone else. I forgot to set MFT, my bad. On 02/23/2014 11:58 PM, Piotr Ożarowski wrote: Hi guys, I just uploaded sqlalchemy 0.9.3 to unstable Noo !!! Man, this is a COMPLETE DISASTER for me. Don't do this again without any coordination! Jessie will be released with 0.9.X, IIRC I told you that months ago, during DebConf. 0.8.X → 0.9.X changes are not that big and I even considered uploading 0.9.1 directly to unstable. I used experimental where you had more than a month to test it. This *will* break about everything in OpenStack. I'm just recovering from the last upload of SQLAlchemy 0.8.x which you did last July without recovering from artificial limits that I enforce on all python-sqlalchemy's reverse dependencies by generating X.Y dependency. I'm pretty sure that 99% of packages will need simple rebuild. Those who don't will block python-sqlalchemy's migration (they already have appropriate Depends line) any coordination, yet you're doing it again. It took about 7 months for upstream to do the switch, and during a full release cycle, I had lots and lots of troubles. I'm letting you know. You have just broke: - ceilometer - cinder - glance - heat - keystone - neutron - nova - trove - taskflow will you back this up with a traceback? (/me really wanted to say more here but will stop for now) [...] Please revert this upload immediately (with an EPOC) and until other packages have reasonable upstream support for it. I will not do that! -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140223191746.gm3...@sts0.p1otr.com
SQLAlchemy updates in stable
Hi guys, I want to start updating sqlalchemy source package in stable to the latest point release. Upstream is sane and makes sure 3rd party code doesn't break by 0.X.Y releases (every bug fix has a test case, testsuite is huge¹, changelog is very verbose², each 0.X→0.Y update is described in a migration guide³). Once 0.X+1 is released, 0.X.* versions get bug fixes mostly, sometimes additional features are also backported which makes debdiff not small (big enough to not call it release team friendly). My question is: is it worth my time or will you reject it basing on debdiff size? I can start with preparing 0.7.10 (released upstream in February) upload to stable [¹] http://sources.debian.net/src/sqlalchemy/latest/test [²] http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html [³] http://docs.sqlalchemy.org/en/latest/changelog/migration_08.html PS please CC me on replies -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131204122802.gp3...@sts0.p1otr.com
Re: Dropped binary package: python-aeidon
Hi, [Cyril Brulebois, 2013-10-06] it looks like src:gaupol dropped python-aeidon, which is apparently still needed by translate-toolkit; can you please sure this issue is tracked down, possibly by opening a bug report against translate-toolkit with appropriate instructions? http://lists.debian.org/debian-python/2013/06/msg00091.html -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#703803: unblock: griffith/0.13-2
[Adam D. Barratt, 2013-04-04] Control: tags -1 + moreinfo On Sun, 2013-03-24 at 11:47 +0100, Julien Cristau wrote: On Sat, Mar 23, 2013 at 22:30:59 +0100, Piotr Ożarowski wrote: Please unblock package griffith I fixed it looong time ago in the trunk. Restoring database from a backup is something I want to work in Debian stable. gutils.file_chooser appears to return False in some cases, at which point this patch would break? when someone will try to close a window (by pressing Esc or alt+f4) instead of clicking on OK or CANCEL button. It's still better than before - it wasn't working at all in -1 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130404200111.gu6...@piotro.eu
Bug#703803: unblock: griffith/0.13-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package griffith I fixed it looong time ago in the trunk. Restoring database from a backup is something I want to work in Debian stable. diff -Nru griffith-0.13/debian/changelog griffith-0.13/debian/changelog --- griffith-0.13/debian/changelog 2011-12-18 21:45:37.0 +0100 +++ griffith-0.13/debian/changelog 2013-03-23 22:22:22.0 +0100 @@ -1,3 +1,9 @@ +griffith (0.13-2) unstable; urgency=low + + * Fix restore function + + -- Piotr Ożarowski pi...@debian.org Sat, 23 Mar 2013 22:22:22 +0100 + griffith (0.13-1) unstable; urgency=low * New upstream release diff -Nru griffith-0.13/debian/patches/fix_restore_function.patch griffith-0.13/debian/patches/fix_restore_function.patch --- griffith-0.13/debian/patches/fix_restore_function.patch 1970-01-01 01:00:00.0 +0100 +++ griffith-0.13/debian/patches/fix_restore_function.patch 2013-03-23 22:21:21.0 +0100 @@ -0,0 +1,13 @@ +Index: griffith-0.13/lib/backup.py +=== +--- griffith-0.13.orig/lib/backup.py griffith-0.13/lib/backup.py +@@ -200,7 +200,7 @@ def restore(self, merge=False): + * SQLite3 *.db file + + # let user select a backup file +-filename = gutils.file_chooser(_(Restore Griffith backup), \ ++filename, path = gutils.file_chooser(_(Restore Griffith backup), \ + action=gtk.FILE_CHOOSER_ACTION_OPEN, backup=True, \ + buttons=(gtk.STOCK_CANCEL, gtk.RESPONSE_CANCEL, gtk.STOCK_OPEN, gtk.RESPONSE_OK)) + if not filename: diff -Nru griffith-0.13/debian/patches/series griffith-0.13/debian/patches/series --- griffith-0.13/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ griffith-0.13/debian/patches/series 2013-03-23 22:18:22.0 +0100 @@ -0,0 +1 @@ +fix_restore_function.patch unblock griffith/0.13-2 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130323213059.24525.69760.reportbug@hadar
Re: Bug#652653: python-virtualenv: insecure /tmp file handling
[Adam D. Barratt, 2011-12-19] I noticed that an upload which appears to fix this issue (although without reference the bug number) has appeared in p-u-NEW. Whilst sorry, I didn't notice a bug was reported that's an admirable turn-around :-) it really should have been discussed with the SRMs first, rather than simply uploading (I believe this is well documented enough by now - if not, please point out where and how we could make it clearer). ups, I assumed someone from SRMs is in the thread Looking at the diff, and the equivalent code in the unstable package, there seems to be a missing component - namely, that the directory created via mkdtemp() is never cleaned up. Am I missing something, or does fixing this issue result in orphaned temporary directories? the old code didn't do it as well, I can update the patch to remove it -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111220084454.gk27...@piotro.eu
it's Python time now
FYI: I plan to upload python-sphinx, python-defaults (without Python 2.5, with Python 2.7) and python3-defaults (with Python 3.2 instead of Python 3.2) tomorrow. Please report bug against tech-ctte and CC me if you think it's not a good idea. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330140256.gg30...@piotro.eu
Re: it's Python time now
[Julien Cristau, 2011-03-30] On Wed, Mar 30, 2011 at 16:02:56 +0200, Piotr Ożarowski wrote: FYI: I plan to upload python-sphinx, python-defaults (without Python 2.5, with Python 2.7) and python3-defaults (with Python 3.2 instead of Python 3.2) tomorrow. Please report bug against tech-ctte and CC me if s/3.2/3.1/ you think it's not a good idea. I think it's not a good idea. 3 days then (python-defaults didn't migrate to testing yet) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330142604.gh30...@piotro.eu
Re: it's Python time now
[Piotr Ożarowski, 2011-03-30] FYI: I plan to upload python-sphinx, python-defaults (without Python 2.5, with Python 2.7) and python3-defaults (with Python 3.2 instead of Python 3.2) tomorrow. Please report bug against tech-ctte and CC me if you think it's not a good idea. I know I shouldn't send this email, I usually try to wait 24h after writing, didn't do it this time. I already removed myself from python-defaults' Uploaders, though (but still plan to work on dh_python2). -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
python-defaults update in Squeeze
Hi,
I backported some changes in python-defaults, the pycompile one should
fix Lenny → Squeeze upgrades where administrator installed local
version of Python (without my py_compile.py changes backported from
Python 3.2 in Debian)
Can I upload it?
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
diff -Nru python-defaults-2.6.6/debian/changelog python-defaults-2.6.6/debian/changelog
--- python-defaults-2.6.6/debian/changelog 2011-01-11 23:07:28.0 +0100
+++ python-defaults-2.6.6/debian/changelog 2011-02-16 23:08:55.0 +0100
@@ -1,3 +1,15 @@
+python-defaults (2.6.6-3+squeeze6) stable; urgency=low
+
+ * pycompile:
+- use /usr/bin/pythonX.Y rather than pythonX.Y (to avoid /usr/local
+ interpreters and thus fix some Lenny → Squeeze upgrades)
+ * dh_python2:
+- add support for DH_OPTIONS env. variable
+- replace a file with a symlink also if there's a matching one in
+ pyshared directory already
+
+ -- Piotr Ożarowski pi...@debian.org Wed, 16 Feb 2011 20:33:27 +0100
+
python-defaults (2.6.6-3+squeeze5) unstable; urgency=low
* dh_python2: fix moving files from old debug locations
diff -Nru python-defaults-2.6.6/dh_python2 python-defaults-2.6.6/dh_python2
--- python-defaults-2.6.6/dh_python2 2011-01-11 22:16:07.0 +0100
+++ python-defaults-2.6.6/dh_python2 2011-02-16 22:48:12.0 +0100
@@ -26,7 +26,7 @@
import os
import re
import sys
-from filecmp import dircmp, cmpfiles
+from filecmp import dircmp, cmpfiles, cmp as fcmp
from optparse import OptionParser, SUPPRESS_HELP
from os.path import isdir, islink, exists, join
from shutil import rmtree, copy as fcopy
@@ -236,8 +236,12 @@
# do not touch symlinks created by previous loop or other tools
if dc and not islink(fpath1):
# replace with a link to pyshared
-os.rename(fpath1, fpath3)
-relative_symlink(fpath3, fpath1)
+if not exists(fpath3):
+os.rename(fpath1, fpath3)
+relative_symlink(fpath3, fpath1)
+elif fcmp(fpath3, fpath1, shallow=False):
+os.remove(fpath1)
+relative_symlink(fpath3, fpath1)
if dc is None: # guess/copy mode
if islink(fpath1):
# ralative links will work as well, it's always the same level
@@ -251,7 +255,8 @@
os.rename(fpath1, fpath3)
relative_symlink(fpath3, fpath1)
relative_symlink(fpath3, fpath2)
-else:
+elif exists(fpath2) and exists(fpath3) and \
+ fcmp(fpath2, fpath3, shallow=False):
os.remove(fpath2)
relative_symlink(fpath3, fpath2)
for dn, dc in common_dirs:
@@ -432,7 +437,8 @@
# ignore some debhelper options:
parser.add_option('-O', help=SUPPRESS_HELP)
-(options, args) = parser.parse_args()
+(options, args) = parser.parse_args(sys.argv[1:] + \
+ os.environ.get('DH_OPTIONS', '').split())
# regexpr option type is not used so lets check patterns here
for pattern in options.regexpr or []:
# fail now rather than at runtime
@@ -518,7 +524,7 @@
ext_for = details.get('public_ext')
if ext_for is None: # no extension
-if options.vrange:
+if options.vrange and options.vrange != (None, None):
args += -V %s % vrange_str(options.vrange)
elif False in ext_for: # extension's version not detected
if options.vrange and '-' not in vrange_str(options.vrange):
diff -Nru python-defaults-2.6.6/pycompile python-defaults-2.6.6/pycompile
--- python-defaults-2.6.6/pycompile 2011-01-11 22:54:09.0 +0100
+++ python-defaults-2.6.6/pycompile 2011-02-16 20:39:26.0 +0100
@@ -125,6 +125,9 @@
def get_exclude_patterns(directory='/', patterns=None, versions=None):
Return patterns for files that shouldn't be compiled in given dir.
+if versions is not None:
+# make sure it's a set (debsorted returns a list)
+versions = set(versions)
if patterns:
if versions is None:
versions = set(SUPPORTED)
@@ -169,7 +172,7 @@
def py_compile(version, optimize, workers):
if not isinstance(version, basestring):
version = vrepr(version)
-cmd = python%s%s -m py_compile - \
+cmd = /usr/bin/python%s%s -m py_compile - \
% (version, '' if (__debug__ or not optimize) else ' -O')
process = Popen(cmd, bufsize=1, shell=True,
stdin=PIPE, close_fds=True)
signature.asc
Description: Digital signature
Re: python-defaults update in Squeeze
[Julien Cristau, 2011-02-16] I backported some changes in python-defaults, the pycompile one should fix Lenny → Squeeze upgrades where administrator installed local version of Python (without my py_compile.py changes backported from Python 3.2 in Debian) Care to explain why this is needed? And what the other changes are about? There's no bug number, and the changelog doesn't really tell much. I was told there are many upgrade problems due to /usr/local/bin/python, like this one: http://paste.debian.net/107836/ -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#608937: unblock: phatch/0.2.7-3
[Mehdi Dogguy, 2011-01-07] On 01/04/2011 07:57 PM, Piotr Ożarowski wrote: Please unblock package phatch It was removed two days ago because Nautilus scripts didn't work, I removed phatch-nautilus binary package (Stani will change it a little bit in next upstream release) so please unblock phatch and let it propagate to testing again. Doesn't seem possible since #608952 is still open (and RC). I used wrong version number, should be fixed now -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110109161604.ga31...@piotro.eu
Bug#608937: unblock: phatch/0.2.7-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package phatch It was removed two days ago because Nautilus scripts didn't work, I removed phatch-nautilus binary package (Stani will change it a little bit in next upstream release) so please unblock phatch and let it propagate to testing again. unblock phatch/0.2.7-3 -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature
Bug#605500: unblock: python-defaults/2.6.6-3+squeeze2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package python-defaults These are two trivial fixes backported from 2.6.6-6 (which I will upload to experimental soon) unblock python-defaults/2.6.6-3+squeeze2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru python-defaults-2.6.6/debian/changelog python-defaults-2.6.6/debian/changelog --- python-defaults-2.6.6/debian/changelog 2010-10-18 19:14:11.0 +0200 +++ python-defaults-2.6.6/debian/changelog 2010-11-30 19:59:18.0 +0100 @@ -1,3 +1,14 @@ +python-defaults (2.6.6-3+squeeze2) unstable; urgency=low + + * pycompile: +- `pycompile $DESTDIR/usr/lib/python*` will recognize public + site-packages directories and use the right interpreter instead of + raising KeyError +- do not try to check if interpreter is present when version range is + empty (closes: 605356) + + -- Piotr Ożarowski pi...@debian.org Tue, 30 Nov 2010 19:57:51 +0100 + python-defaults (2.6.6-3+squeeze1) unstable; urgency=medium * pycompile: if installed Python is requested via -V option, use it even if diff -Nru python-defaults-2.6.6/pycompile python-defaults-2.6.6/pycompile --- python-defaults-2.6.6/pycompile 2010-10-18 19:08:20.0 +0200 +++ python-defaults-2.6.6/pycompile 2010-11-30 20:00:57.0 +0100 @@ -191,7 +191,13 @@ if exists(%sc % fn): continue for version in versions_to_compile: -pipe = STDINS[version] +try: +pipe = STDINS[version] +except KeyError: +# `pycompile /usr/lib/` invoked, add missing worker +pipe = py_compile(version, WORKERS) +pipe.next() +STDINS[version] = pipe pipe.send(fn) @@ -236,6 +242,7 @@ 'public modules to skip') if options.vrange and options.vrange[0] == options.vrange[1] and\ + options.vrange != (None, None) and\ exists(/usr/bin/python%d.%d % options.vrange[0]): # specific version requested, use it even if it's not in SUPPORTED versions = set(options.vrange[:1]) signature.asc Description: Digital signature
Bug#601282: unblock: paste/1.7.5.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package paste It's a bug fix release, also workarounds a problem with online debugger (libjs-mochikit moved to Recommeds, I will convert whole Pylons stack to dh_python2 in Wheezy) Upstream changelog: * Fix bug introduced in paste.auth.auth_tkt (with url_unquote) * Won’t install tests/ directory (also caused installation problems on some Mac systems). * Fixed problem with gzip middleware and zero-length responses. * Use X-Forwarded-For header in paste.translogger * Fixed problems with mimeparse code * Fixed some corner cases with CGI scripts * paste.auth.auth_tkt will URL-quote usernames, avoiding some errors with usernames with ! in them. * Improve handling of errors in fetching error pages in paste.errordocument. That's the only Pylons related package I want to be updated in Squeeze, new upstream releases of other Pylons related packages are uploaded to experimental or unstable, but I don't think changes are that important. unblock paste/1.7.5.1-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature
Bug#601284: unblock: griffith/0.12.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package griffith Works with python-sqlalchemy 0.6.* (the one in Squeeze). That's the version I wanted to release upstream short after DebConf10. unblock griffith/0.12.1-1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#600623: unblock: jinja2/2.5.4-1
retitle 600623 unblock: jinja2/2.5.5-1 thanks [Mehdi Dogguy, 2010-10-19] On 10/18/2010 07:48 PM, Piotr Ożarowski wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package jinja2 There is a _build directory in the tarball. I assume that its content is completely generated (please correct me if I'm wrong). What's the reason of having it in the source package? (except making the diff much bigger). ok, I uploaded 2.5.5 (the one without html files in upstream tarball), yes - I regenerate them at build time signature.asc Description: Digital signature
Bug#600746: unblock: python-support/1.0.11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package python-support Python 2.4 is no longer supported in Debian, 1.0.11 moves it to old versions. unblock python-support/1.0.11 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#600620: unblock: python-defaults/2.6.6-3+squeeze1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package python-defaults New interpreter will fail to install without this change if it uses pycompile in its maintainer scripts. See #600529 and #600536. unblock python-defaults/2.6.6-3+squeeze1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature
Bug#600623: unblock: jinja2/2.5.4-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package jinja2
fixes two important bugs, quote from upstream changelog:
- Fixed extensions not loading properly with overlays.
- Work around a bug in cpython for the debugger that causes segfaults
on 64bit big-endian architectures.
- fixed an operator precedence error introduced in 2.5.2. Statements
like -foo.bar had their implicit parentheses applied around the
first part of the expression ((-foo).bar) instead of the more
correct -(foo.bar).
from tests:
|def test_parse_unary(self):
|tmpl = env.from_string('{{ -foo[bar] }}')
|assert tmpl.render(foo={'bar': 42}) == '-42'
|tmpl = env.from_string('{{ -foo[bar]|abs }}')
|assert tmpl.render(foo={'bar': 42}) == '42'
the fix is very small, hint: filter out html docs from debdiff, upstream
removed them in 2.5.5 (I asked to not re-release the same version with
different tarball), I can upload 2.5.5-1 if you prefer
unblock jinja2/2.5.4-1
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
signature.asc
Description: Digital signature
Re: Python3 experimental packages with destination squeeze
[Sandro Tosi, 2010-09-16] Something I didn't find written anywhere and makes me wonder is: what's the gain for squeeze to have those new packages? is 3.1 being a supported version depending on those packages or viceversa? (after all, why have 3.1 as supported without any modules?) Please read PEP 3147 and PEP 3149 - that's what we'll have in Wheezy. 3149 (but *not* 3147) was partially backported to python3.1 so that both versions can share dist-packages directory. This means replacing 3.1 with 3.2 in Wheezy will be a lot easier and the toolchain will not have to support one exception¹ for Python 3.1 (3.0 was never supported by Debian). Few existing Squeeze packages that *do* support Python 3.1 right now would benefit from binNMU or few minor changes (changes in python3.1 are backwards compatible, BTW). We simply want to have toolchain ready in Squeeze, it has nothing to do with adding more python3-foo binary packages in Squeeze which is a separate thing. In Wheezy+1² we might have a problem with supporing more than one Python 3 version at the same time (in very rare cases where .py files cannot be shared or patched) but I'm convinced that by that time release managers will tell us about the freeze 6 months in advance and we'll figure something out with upstream. [¹] which would be a PITA, I removed like half of dh_python3 after moving files from /usr/lib/python3.1/dist-packages to /usr/lib/python3/dist-packages [²] yes, Wheezy+1, not Squeeze+1 -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100916181218.ga26...@piotro.eu
Bug#596549: unblock: phenny/2~hg28-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package phenny it fixes release critical bug (#596311) unblock phenny/2~hg28-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- mail to -announce 6 months before Debian freeze FTW! -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100912150032.ga31...@piotro.eu
Re: Python 3 support in Squeeze
[Neil McGovern, 2010-09-08] I'm slightly worried by: Sometimes 2to3 will find a place in your source code that needs to be changed, but 2to3 cannot fix automatically. In this case, 2to3 will print a warning beneath the diff for a file. You should address the warning in order to have compliant 3.x code. and: Note The lib2to3 API should be considered unstable and may change drastically in the future. once again, we are NOT going to add python3-foo binary packages for code not tested with Python 3 by upstream. I ask about packages for which upstream claims 2to3 did a good job or it wasn't needed at all. Adam: I uploaded my packages that support Python 3 (beaker and mako). Let me know if I will not waste my time and I will work on docutils, cython and lxml next. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100908131211.gg15...@piotro.eu
Re: Python 3 support in Squeeze
[Adam D. Barratt, 2010-09-06] So upstream have verified the result of 2to3 on their software? yes On a related note, will the build system allow for the result of 2to3 to be easily overridden? For example, if whilst building an update the security team discover that there's a problem with the 2to3-generated patch, will they be able to add a fixed patch to the package and have that used in preference? Most of the times (all of them?) it can be fixed in Python 2.x code. You can also extend 2to3 tool (see f.e. sqlalchemy's sa2to3 or jinja2's custom_fixers) -- /me wants time-based freezes -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100906205445.ga15...@piotro.eu
Re: Python 3 support in Squeeze
[Adam D. Barratt, 2010-09-03] On Sat, 2010-08-21 at 00:44 +0200, Piotr Ożarowski wrote: We plan to upload such NEW versions of Squeeze packages to experimental² (one of ftp-team members, who is a member of our team, will help us with that), test it there and if everything will be ok - upload to unstable and ask for freeze exception³. Has the initial side of that process begun yet (i.e. the preparation of the new packages and uploads to experimental)? I can have my packages ready really soon (I did some initial work). I can also prepare patches for the ones I listed previously (I took a look at them before sending my mail). Then I plan to write some instructions so that more people will join. Please note that in most (all?) cases 2to3 tool (which converts python2.X code to python3.X one) will have to be used (again, no new upstream versions) so patching the code in Squeeze (security bugs, etc.) will not have to be done twice (at least in most cases). Adding new packages at this stage of the release process obviously carries a certain degree of risk, and the auto-generated aspect of the code has the potential to add more. How confident are you in the code produced by 2to3? all packages I listed were checked by upstreams (and they claim 2to3 did a good job). I don't think it's a good idea to convert sources that upstream didn't test with Python 3 and I don't plan to convert such packages. If one of the packages involved needed a security update in stable, what are the chances that 2to3 would fail to convert the patched code, produce a script which doesn't run, doesn't work or (hopefully a very unlikely worst case) doesn't properly fix the bug? how about sending such patches to debian-pyt...@l.d.o? You can also ping me directly. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903185054.gb27...@piotro.eu
Bug#594423: unblock: mod-wsgi/3.3-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package mod-wsgi. It's a new upstream release with some
bug fixes backported from (unreleased) 4.0 branch (changelog is
available here¹). There are also some fixes in packaging (see
debian/changelog) including new binary package that will let users
choose Python 3 more easily (and is part of separate Python and Python
3 and increase Python 3 support in Squeeze goals).
unblock mod-wsgi/3.3-1
[¹] http://code.google.com/p/modwsgi/wiki/ChangesInVersion0303
--
Do you like the idea of time-based freezes?
Mention it in your signature in all mails to debian-rele...@l.d.o to
encourage Release Team!
diff -Nru mod-wsgi-3.2/debian/changelog mod-wsgi-3.3/debian/changelog
--- mod-wsgi-3.2/debian/changelog 2010-08-25 21:54:49.0 +0200
+++ mod-wsgi-3.3/debian/changelog 2010-08-25 21:54:50.0 +0200
@@ -1,3 +1,22 @@
+mod-wsgi (3.3-1) unstable; urgency=low
+
+ [ Sameer Rahmani ]
+ * watch file fixed.
+
+ [ Bernd Zeimetz ]
+ * Ensure that the mod-wsgi symlink is updated to the current default Python
+version while installing/upgrading the package. This is only necessary
+in rare cases (when the default Python version was updated after the last
+rebuild of mod-wsgi), but it needs to be handled properly.
+
+ [ Piotr Ożarowski ]
+ * New upstream release
+ * Move Python 3.X extension to new libapache2-mod-wsgi-py3 binary package
+ * Provide httpd-wsgi (see #588497)
+ * Bump Standards-Version to 3.9.1 (no changes needed)
+
+ -- Piotr Ożarowski pi...@debian.org Wed, 18 Aug 2010 23:40:10 +0200
+
mod-wsgi (3.2-2) unstable; urgency=low
* mod-wsgi needs to depend on libpython for Python 2.5.
diff -Nru mod-wsgi-3.2/debian/control mod-wsgi-3.3/debian/control
--- mod-wsgi-3.2/debian/control 2010-08-25 21:54:49.0 +0200
+++ mod-wsgi-3.3/debian/control 2010-08-25 21:54:50.0 +0200
@@ -5,7 +5,7 @@
Uploaders: Bernd Zeimetz b...@debian.org, Piotr Ożarowski pi...@debian.org
Build-Depends: debhelper (= 5), python-all-dev, python3-all-dev,
apache2-threaded-dev
Homepage: http://www.modwsgi.org/
-Standards-Version: 3.8.4
+Standards-Version: 3.9.1
Vcs-Svn: svn://svn.debian.org/python-modules/packages/mod-wsgi/trunk/
Vcs-Browser:
http://svn.debian.org/viewsvn/python-modules/packages/mod-wsgi/trunk/
@@ -13,9 +13,27 @@
Architecture: any
Depends: apache2, apache2.2-common, ${shlibs:Depends}, ${misc:Depends},
${python:Depends}
Suggests: apache2-mpm-worker | apache2-mpm-event
+Provides: httpd-wsgi
Description: Python WSGI adapter module for Apache
The mod_wsgi adapter is an Apache module that provides a WSGI (Web Server
Gateway Interface, a standard interface between web server software and
web applications written in Python) compliant interface for hosting Python
based web applications within Apache. The adapter provides significantly
better performance than using existing WSGI adapters for mod_python or CGI.
+ .
+ This package provides module for Python 2.X.
+
+Package: libapache2-mod-wsgi-py3
+Architecture: any
+Depends: apache2, apache2.2-common, ${shlibs:Depends}, ${misc:Depends},
${python3:Depends}
+Suggests: apache2-mpm-worker | apache2-mpm-event
+Conflicts: libapache2-mod-wsgi
+Provides: httpd-wsgi
+Description: Python 3 WSGI adapter module for Apache
+ The mod_wsgi adapter is an Apache module that provides a WSGI (Web Server
+ Gateway Interface, a standard interface between web server software and
+ web applications written in Python) compliant interface for hosting Python
+ based web applications within Apache. The adapter provides significantly
+ better performance than using existing WSGI adapters for mod_python or CGI.
+ .
+ This package provides module for Python 3.X.
diff -Nru mod-wsgi-3.2/debian/copyright mod-wsgi-3.3/debian/copyright
--- mod-wsgi-3.2/debian/copyright 2010-08-25 21:54:49.0 +0200
+++ mod-wsgi-3.3/debian/copyright 2010-08-25 21:54:50.0 +0200
@@ -9,7 +9,7 @@
Copyright:
-Copyright 2007-2009 GRAHAM DUMPLETON
+Copyright 2007-2010 GRAHAM DUMPLETON
License:
@@ -28,5 +28,5 @@
On Debian systems the full text of the Apache License, Version 2,
can be found in `/usr/share/common-licenses/Apache-2.0'.
-The Debian packaging is © 2007-2009, Bernd Zeimetz be...@bzed.de and
+The Debian packaging is © 2007-2010, Bernd Zeimetz be...@bzed.de and
is licensed under the Apache License, Version 2.0, see below.
diff -Nru mod-wsgi-3.2/debian/libapache2-mod-wsgi.postinst
mod-wsgi-3.3/debian/libapache2-mod-wsgi.postinst
--- mod-wsgi-3.2/debian/libapache2-mod-wsgi.postinst2010-08-25
21:54:49.0 +0200
+++ mod-wsgi-3.3/debian/libapache2-mod-wsgi.postinst2010-08-25
21:54:50.0 +0200
@@ -12,13 +12,23 @@
fi
}
+update_symlink() {
+wsgi_py=`readlink /usr/lib/apache2/modules/mod_wsgi.so | sed 's,.*-,,'`
+py_default=`dpkg -s python | grep
Bug#593943: unblock: python-virtualenv/1.4.9-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package python-virtualenv
version in Squeeze installs virtualenv module into wrong namespace
unblock python-virtualenv/1.4.9-3
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Do you like the idea of time-based freezes?
Mention it in your signature in all mails to debian-rele...@l.d.o to
encourage Release Team!
diff -Nru python-virtualenv-1.4.9/debian/changelog
python-virtualenv-1.4.9/debian/changelog
--- python-virtualenv-1.4.9/debian/changelog2010-06-18 19:59:19.0
+0200
+++ python-virtualenv-1.4.9/debian/changelog2010-08-22 15:55:50.0
+0200
@@ -1,3 +1,38 @@
+python-virtualenv (1.4.9-3) unstable; urgency=low
+
+ * Team upload.
+ * Update look_for_external_files.patch to use /usr/share/python-virtualenv
+
+ -- Piotr Ożarowski pi...@debian.org Sun, 22 Aug 2010 15:55:07 +0200
+
+python-virtualenv (1.4.9-2) unstable; urgency=low
+
+ * Team upload.
+
+ [ Carl Chenet ]
+ * Renamed README.source to README.Debian
+ * Added debian/patches/look_for_external_files
+- patch to store archives and eggs in /usr/share/python-virtualenv
+ * debian/control
+- bump to 3.9.0 (No changes needed)
+- moved python-pip to Recommends
+ * debian/rules
+- removed overrides
+- cleaning pysupport results
+ * debian/install
+- corrected path to virtualenv.py. Closes: #588179
+ * debian/python-virtualenv.lintian-overrides
+- modified paths to lintian-overrides
+
+ [ Piotr Ożarowski ]
+ * Install PIP tarball. Closes: 590824
+ * Add add_distribute.patch (based on Barry Warsaw's one from Ubuntu)
+ * Install scripts/virtualenv instead of the one generated by setuptools
+ * Install docs/news.txt file as upstream changelog
+ * Bump Standards-Version to 3.9.1 (no changes needed)
+
+ -- Piotr Ożarowski pi...@debian.org Sun, 22 Aug 2010 00:13:28 +0200
+
python-virtualenv (1.4.9-1) unstable; urgency=low
* New upstream version. Closes: #563993,#571411
diff -Nru python-virtualenv-1.4.9/debian/clean
python-virtualenv-1.4.9/debian/clean
--- python-virtualenv-1.4.9/debian/clean1970-01-01 01:00:00.0
+0100
+++ python-virtualenv-1.4.9/debian/clean2010-08-21 23:44:10.0
+0200
@@ -0,0 +1 @@
+virtualenv.egg-info/*
diff -Nru python-virtualenv-1.4.9/debian/control
python-virtualenv-1.4.9/debian/control
--- python-virtualenv-1.4.9/debian/control 2010-06-15 22:49:29.0
+0200
+++ python-virtualenv-1.4.9/debian/control 2010-08-22 00:05:11.0
+0200
@@ -8,12 +8,13 @@
Vcs-Browser:
http://svn.debian.org/wsvn/python-modules/packages/python-virtualenv/trunk/
Build-Depends: debhelper (= 7.0.50~), python
Build-Depends-Indep: python-support, python-setuptools
-Standards-Version: 3.8.4
+Standards-Version: 3.9.1
XS-Python-Version: all
Package: python-virtualenv
Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-pkg-resources,
python-setuptools, python-pip (= 0.7.2)
+Depends: ${misc:Depends}, ${python:Depends}, python-pkg-resources,
python-setuptools
+Recommends: python-pip (= 0.7.2)
XB-Python-Version: ${python:Versions}
Description: Python virtual environment creator
The virtualenv utility creates virtual Python instances, each invokable
diff -Nru python-virtualenv-1.4.9/debian/docs
python-virtualenv-1.4.9/debian/docs
--- python-virtualenv-1.4.9/debian/docs 2010-06-18 19:59:19.0 +0200
+++ python-virtualenv-1.4.9/debian/docs 2010-08-22 00:05:49.0 +0200
@@ -1,3 +1 @@
docs/index.txt
-docs/news.txt
-debian/README.source
diff -Nru python-virtualenv-1.4.9/debian/install
python-virtualenv-1.4.9/debian/install
--- python-virtualenv-1.4.9/debian/install 2010-06-15 22:49:29.0
+0200
+++ python-virtualenv-1.4.9/debian/install 2010-08-22 00:07:24.0
+0200
@@ -1,2 +1,3 @@
-virtualenv_support/ usr/share/pyshared/virtualenv/
-virtualenv.py usr/share/pyshared/virtualenv/
+virtualenv_support/*.tar.gz /usr/share/python-virtualenv/
+virtualenv_support/*.egg /usr/share/python-virtualenv/
+scripts/virtualenv /usr/bin/
diff -Nru python-virtualenv-1.4.9/debian/patches/add_distribute.patch
python-virtualenv-1.4.9/debian/patches/add_distribute.patch
--- python-virtualenv-1.4.9/debian/patches/add_distribute.patch 1970-01-01
01:00:00.0 +0100
+++ python-virtualenv-1.4.9/debian/patches/add_distribute.patch 2010-08-22
15:50:20.0 +0200
@@ -0,0 +1,54 @@
+Description: Add --distribute as an option in virtualenv.py
+ Enable --distribute by default in virtualenv.py but add --setuptools
+ and $VIRTUALENV_USE_SETUPTOOLS to fallback to the default upstream
+ behavior.
+Origin: vendor
Bug#593858: unblock: markupsafe/0.9.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package markupsafe 0.9.2-2 closes #591953 (+ some other minor packaging changes) unblock markupsafe/0.9.2-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Bug#593864: unblock: sqlalchemy/0.6.3-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package sqlalchemy
it closes 591954 (RC bug)
unblock sqlalchemy/0.6.3-2
diff -u sqlalchemy-0.6.3/debian/control sqlalchemy-0.6.3/debian/control
--- sqlalchemy-0.6.3/debian/control
+++ sqlalchemy-0.6.3/debian/control
@@ -4,10 +4,10 @@
Maintainer: Piotr Ożarowski pi...@debian.org
Uploaders: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Build-Depends: debhelper (= 5.0.38),
- python-all-dev (= 2.6.5-2~), python3-all-dev (= 3.1.2-1~),
+ python-all-dev (= 2.6.5-2~), python3-all-dev (= 3.1.2-6~),
python-setuptools (= 0.6b3-1~), python3-setuptools
Build-Depends-Indep: python-sphinx (= 0.6), python-mako
-Standards-Version: 3.9.0
+Standards-Version: 3.9.1
Homepage: http://www.sqlalchemy.org/
Vcs-Svn: svn://svn.debian.org/python-modules/packages/sqlalchemy/trunk
Vcs-Browser:
http://svn.debian.org/viewsvn/python-modules/packages/sqlalchemy/trunk/
@@ -85,7 +85,7 @@
Package: python3-sqlalchemy
Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
+Depends: ${python3:Depends}, ${misc:Depends}
Suggests: python-sqlalchemy-doc
Description: SQL toolkit and Object Relational Mapper for Python 3
SQLAlchemy is an SQL database abstraction library for Python.
diff -u sqlalchemy-0.6.3/debian/changelog sqlalchemy-0.6.3/debian/changelog
--- sqlalchemy-0.6.3/debian/changelog
+++ sqlalchemy-0.6.3/debian/changelog
@@ -1,3 +1,11 @@
+sqlalchemy (0.6.3-2) unstable; urgency=low
+
+ * Use ${python3:Depends} in python3-sqlalchemy package (closes: 591954)
+- minimum python3-all-dev version bumped to 3.1.2-6~
+ * Standards-Version bumped to 3.9.1 (no changes needed)
+
+ -- Piotr Ożarowski pi...@debian.org Sat, 21 Aug 2010 19:05:08 +0200
+
sqlalchemy (0.6.3-1) unstable; urgency=low
* New upstream release
signature.asc
Description: Digital signature
Python 3 support in Squeeze
Hi Release Team, [I asked you about this issue at DebConf10 and was told to ask via e-mail again, hence my mail] Squeeze will support Python 3.1 as the first Python 3.X version in Debian. Unfortunately, we didn't have much time to start preparing packages with 3rd party modules/extensions for Python 3.X (python2.6 transition was completed not that long ago). We still want to improve Python 3.1 stack in Squeeze by adding python3-foo binary packages to important packages¹ from testing (no new upstream versions!). We plan to upload such NEW versions of Squeeze packages to experimental² (one of ftp-team members, who is a member of our team, will help us with that), test it there and if everything will be ok - upload to unstable and ask for freeze exception³. Please note that in most (all?) cases 2to3 tool (which converts python2.X code to python3.X one) will have to be used (again, no new upstream versions) so patching the code in Squeeze (security bugs, etc.) will not have to be done twice (at least in most cases). [¹] I want at least 20 more python3-foo packages, hopefully more (f.e. Cython, docutils, Pygments [+Sphinx backport], Sip4, PyQt, Beaker, Mako, lxml, ...) [²] and thus we'll wait with adding Python 2.7 and later Python 3.2 to the supported Python versions in experimental [³] with a Py3 usertag/Subject tag (or something similar), to make it easier for you -- Do you like the idea of time-based freezes? Mention it in your signature in all mails to debian-rele...@l.d.o to encourage Release Team! signature.asc Description: Digital signature
Re: Freeze exception: python-defaults 2.6.5-13
[Adam D. Barratt, 2010-08-17] Let me know if you'd like to correct any or all of those in a -14 upload, otherwise I'll just unblock -13. please unblock it. It's fixed in bzr, but we'll wait for more changes before uploading... -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Freeze exception: python-defaults 2.6.5-13
Please unblock python-defaults 2.6.5-13. It fixes some important bugs related to dh_python2 and pycompile (+ some policy/docs changes) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Freeze exception: python3-defaults 3.1.2-6
Please unblock python3-defaults 3.1.2-6. It fixes some important bugs
related to dh_python3 and py3compile.
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
diff -Nru python3-defaults-3.1.2/debian/changelog
python3-defaults-3.1.2/debian/changelog
--- python3-defaults-3.1.2/debian/changelog 2010-07-28 22:49:13.0
+0200
+++ python3-defaults-3.1.2/debian/changelog 2010-08-13 23:29:29.0
+0200
@@ -1,3 +1,23 @@
+python3-defaults (3.1.2-6) unstable; urgency=low
+
+ [ Matthias Klose ]
+ * Substitution variables for control files always start with a `python3'
+prefix (python:Versions - python3:Versions, python:Provides -
+python3:Provides).
+ * Generate dependencies on python3 (= 3.1.2-6~).
+
+ [ Piotr Ożarowski ]
+ * py3compile: do not hang if interpreters are not started in the same order
+as they're used
+ * dh_python3: pass shallow=False to cmpfiles to make sure file comparison
+works as expected
+
+ [ Scott Kitterman ]
+ * Us X-Python3-Version for Python 3 instead of XS-Python-Version (which
+should just be used for Python)
+
+ -- Piotr Ożarowski pi...@debian.org Fri, 13 Aug 2010 23:27:45 +0200
+
python3-defaults (3.1.2-5) unstable; urgency=medium
* Add README.PyDist to python3-doc package
diff -Nru python3-defaults-3.1.2/debian/py3versions.py
python3-defaults-3.1.2/debian/py3versions.py
--- python3-defaults-3.1.2/debian/py3versions.py2010-06-07
21:58:26.0 +0200
+++ python3-defaults-3.1.2/debian/py3versions.py2010-08-13
23:27:05.0 +0200
@@ -164,8 +164,8 @@
pass
def extract_pyversion_attribute(fn, pkg):
-read the debian/control file, extract the XS-Python-Version
-field; check that XB-Python-Version exists for the package.
+read the debian/control file, extract the X-Python3-Version
+field.
version = None
sversion = None
@@ -180,21 +180,16 @@
section = 'Source'
elif line.startswith('Package: ' + pkg):
section = pkg
-elif line.startswith('XS-Python-Version:'):
+elif line.startswith('X-Python3-Version:'):
if section != 'Source':
-raise ValueError('attribute XS-Python-Version not in Source
section')
+raise ValueError('attribute X-Python3-Version not in Source
section')
sversion = line.split(':', 1)[1].strip()
-elif line.startswith('XB-Python-Version:'):
-if section == pkg:
-version = line.split(':', 1)[1].strip()
if section == None:
raise ControlFileValueError('not a control file')
if pkg == 'Source':
if sversion == None:
-raise MissingVersionValueError('missing XS-Python-Version in
control file')
+raise MissingVersionValueError('missing X-Python3-Version in
control file')
return sversion
-if version == None:
-raise MissingVersionValueError('missing XB-Python-Version for package
`%s' % pkg)
return version
def requested_versions_bis(vstring, version_only=False):
@@ -239,7 +234,7 @@
help='print the supported python3 versions',
action='store_true', dest='supported')
parser.add_option('-r', '--requested',
- help='print the python3 versions requested by a build;
the argument is either the name of a control file or the value of the
XS-Python-Version attribute',
+ help='print the python3 versions requested by a build;
the argument is either the name of a control file or the value of the
X-Python3-Version attribute',
action='store_true', dest='requested')
parser.add_option('-i', '--installed',
help='print the installed supported python3 versions',
@@ -276,7 +271,7 @@
% (program, fn))
sys.exit(1)
except MissingVersionValueError:
-sys.stderr.write(%s: missing XS-Python-Version in control
file, fall back to supported versions\n \
+sys.stderr.write(%s: missing X-Python3-Version in control
file, fall back to supported versions\n \
% program)
vs = supported_versions(opts.version_only)
else:
diff -Nru python3-defaults-3.1.2/debpython/debhelper.py
python3-defaults-3.1.2/debpython/debhelper.py
--- python3-defaults-3.1.2/debpython/debhelper.py 2010-07-25
16:19:18.0 +0200
+++ python3-defaults-3.1.2/debpython/debhelper.py 2010-08-13
23:42:02.0 +0200
@@ -80,7 +80,7 @@
elif line.startswith('Source:'):
self.source_name = line[7:].strip()
elif source_section and line.startswith('X-Python3-Version
Re: Freeze exception: python3-defaults 3.1.2-6
[Adam D. Barratt, 2010-08-17] On Tue, 2010-08-17 at 20:47 +0200, Piotr Ożarowski wrote: Please unblock python3-defaults 3.1.2-6. It fixes some important bugs related to dh_python3 and py3compile. debpython/debhelper.py appears to be continuing to fallback to XS-Python-Version if X-Python3-Version is not set. Is that intentional, given the changes to py3versions to make it ignore the older name? yes, that was the previous behaviour and I didn't want to break existing packages Also, dh_python3 has made --quiet off by default in this upload but I didn't spot this in the changelog. actually it's *on* by default now (--verbose is set to False by default) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100817193435.gf20...@piotro.eu
please unblock webhelpers 1.1-1
Hi, Please unblock webhelpers 1.1-1 for Squeeze. It's a new upstream version that fixes licensing problem (I've missed The Software shall be used for Good, not Evil. previously). There are no other upstream changes in the code (except removing one meaningless import line). -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 diff -Nru webhelpers-1.0/CHANGELOG webhelpers-1.1/CHANGELOG --- webhelpers-1.0/CHANGELOG2010-06-02 07:41:08.0 +0200 +++ webhelpers-1.1/CHANGELOG2010-08-10 02:48:14.0 +0200 @@ -6,6 +6,24 @@ No changes yet. +1.1 (2010-08-09) + + +* webhelpers.paginate: + + - Remove stray Routes import. (Other conditional Routes imports remain for +backward compatibility; see module docstring.) + +* webhelpers.pylonslib.minify: + + - Remove _jsmin module due to licensing issues. Details are in +webhelpers/pylonslib/_jsmin.py . You can install the jsmin package in +PyPI (which has the same license), and the helper will use it. If that +package is installed, the helper will use it. Otherwise the helper will +emit a warning and leave the Javascript unchanged. CSS minification is not +affected. + + 1.0 (2010-06-01) - diff -Nru webhelpers-1.0/debian/changelog webhelpers-1.1/debian/changelog --- webhelpers-1.0/debian/changelog 2010-08-13 19:44:07.0 +0200 +++ webhelpers-1.1/debian/changelog 2010-08-13 19:44:08.0 +0200 @@ -1,3 +1,13 @@ +webhelpers (1.1-1) unstable; urgency=low + + * New upstream release +- webhelpers.pylonslib._jsmin module removed due to licensing issues + * debian/copyright file updated + * Standards-Version bumped to 3.9.1: +- BSD license included directly in debian/copyright + + -- Piotr Ożarowski pi...@debian.org Fri, 13 Aug 2010 18:58:48 +0200 + webhelpers (1.0-1) unstable; urgency=low * New upstream release diff -Nru webhelpers-1.0/debian/control webhelpers-1.1/debian/control --- webhelpers-1.0/debian/control 2010-08-13 19:44:07.0 +0200 +++ webhelpers-1.1/debian/control 2010-08-13 19:44:08.0 +0200 @@ -5,7 +5,7 @@ Uploaders: Oleksandr Moskalenko ma...@debian.org, Piotr Ożarowski pi...@debian.org Build-Depends: debhelper (= 5) Build-Depends-Indep: python-all (= 2.5.4), python-support (= 0.6.4), python-setuptools (= 0.6b3) -Standards-Version: 3.8.4 +Standards-Version: 3.9.1 Vcs-Svn: svn://svn.debian.org/python-modules/packages/webhelpers/trunk/ Vcs-Browser: http://svn.debian.org/viewsvn/python-modules/packages/webhelpers/trunk/ Homepage: http://pylonshq.com/WebHelpers/ diff -Nru webhelpers-1.0/debian/copyright webhelpers-1.1/debian/copyright --- webhelpers-1.0/debian/copyright 2010-08-13 19:44:07.0 +0200 +++ webhelpers-1.1/debian/copyright 2010-08-13 19:44:08.0 +0200 @@ -13,36 +13,202 @@ License: - Most of this package is licensed under the 3-clause BSD License. - - On Debian GNU/Linux systems, the complete text of the BSD license can be - found in `/usr/share/common-licenses/BSD'. - - - JavaScript scripts in webhelpers/rails/javascripts/ are licensed under the - MIT license: - - Permission is hereby granted, free of charge, to any person obtaining - a copy of this software and associated documentation files (the - Software), to deal in the Software without restriction, including - without limitation the rights to use, copy, modify, merge, publish, - distribute, sublicense, and/or sell copies of the Software, and to - permit persons to whom the Software is furnished to do so, subject to - the following conditions: - - The above copyright notice and this permission notice shall be - included in all copies or substantial portions of the Software. - - THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, - EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF - MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND - NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE - LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION - OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION - WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + Copyright (c) 2005-2009 Ben Bangert, James Gardner, Philip Jenvey, + Mike Orr, Jon Rosenbaugh, Christoph Haas, + and other contributors. + All rights reserved. + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + 1. Redistributions of source code must retain the above copyright +notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright +notice, this list of conditions and the following disclaimer
Re: XSS in paste 1.7.1-1 and 1.7.3.1-1
Hi,
Could someone take a look at paste in stable-proposed-updates?
(sorry for not sending this mail to -release earlier, I was convinced
that uploading to stable/stable-proposed-updated is enough now, I
probably misread one of the mails on -release)
[Piotr Ożarowski, 2010-06-26]
Hi guys,
source package name: paste
binary package name: python-paste
affected versions: 1.7.1-1 (stable), 1.7.3.1-1 (testing)
fixed versions: 1.7.4-1 (unstable)
backported fix for 1.7.1-1 attached (patch and debdiff)
what it fixes:
URLs like http://foo.pl/--%0Dscriptalert('xss')/script
will no longer generate error pages where JavaScript can be executed
from upstream's changelog:
Fix XSS bug (security issue) with not found handlers for
:class:`paste.urlparser.StaticURLParser` and
:class:`paste.urlmap.URLMap`. If you ask for a path with
``/--script...`` that will be inserted in the error page and can
execute Javascript. Reported by Tim Wintle.
in paste 1.7.4-1 source package there are two tests, one in
tests/test_urlmap.py (test_404) and one in tests/test_urlparser.py
(test_xss)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
diff -u paste-1.7.1/debian/changelog paste-1.7.1/debian/changelog
--- paste-1.7.1/debian/changelog
+++ paste-1.7.1/debian/changelog
@@ -1,3 +1,11 @@
+paste (1.7.1-1+lenny1) stable; urgency=high
+
+ * Fix XSS bug (security issue) with not found handlers for
+paste.urlparser.StaticURLParser and paste.urlmap.URLMap
+(patch backported from version 1.7.4)
+
+ -- Piotr Ożarowski pi...@debian.org Fri, 25 Jun 2010 20:47:36 +0200
+
paste (1.7.1-1) unstable; urgency=low
* New upstream release
diff -u paste-1.7.1/debian/patches/00list paste-1.7.1/debian/patches/00list
--- paste-1.7.1/debian/patches/00list
+++ paste-1.7.1/debian/patches/00list
@@ -1,0 +2 @@
+xss_in_url.dpatch
only in patch2:
unchanged:
--- paste-1.7.1.orig/debian/patches/xss_in_url.dpatch
+++ paste-1.7.1/debian/patches/xss_in_url.dpatch
@@ -0,0 +1,74 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+##
+## DP: Fix XSS bug (security issue) with not found handlers for
+## DP: `paste.urlparser.StaticURLParser` and `paste.urlmap.URLMap`.
+## DP: If you ask for a path with `/--script...` that will be
+## DP: inserted in the error page and can execute Javascript.
+## DP: Reported by Tim Wintle.
+
+
+...@dpatch@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git'
'--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr'
paste-1.7.1~/paste/httpexceptions.py paste-1.7.1/paste/httpexceptions.py
+--- paste-1.7.1~/paste/httpexceptions.py 2008-06-13 18:41:58.0
+0200
paste-1.7.1/paste/httpexceptions.py2010-06-25 23:33:56.560406133
+0200
+@@ -77,7 +77,7 @@
+ from paste.wsgilib import catch_errors_app
+ from paste.response import has_header, header_value, replace_header
+ from paste.request import resolve_relative_url
+-from paste.util.quoting import strip_html, html_quote, no_quote
++from paste.util.quoting import strip_html, html_quote, no_quote, comment_quote
+
+ SERVER_NAME = 'WSGI Server'
+ TEMPLATE = \
+@@ -210,12 +210,12 @@
+
+ def plain(self, environ):
+ text/plain representation of the exception
+-body = self.make_body(environ, strip_html(self.template), no_quote)
++body = self.make_body(environ, strip_html(self.template),
comment_quote)
+ return ('%s %s\r\n%s\r\n' % (self.code, self.title, body))
+
+ def html(self, environ):
+ text/html representation of the exception
+-body = self.make_body(environ, self.template, html_quote, no_quote)
++body = self.make_body(environ, self.template, html_quote,
comment_quote)
+ return TEMPLATE % {
+'title': self.title,
+'code': self.code,
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git'
'--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr'
paste-1.7.1~/paste/urlmap.py paste-1.7.1/paste/urlmap.py
+--- paste-1.7.1~/paste/urlmap.py 2008-06-13 18:41:58.0 +0200
paste-1.7.1/paste/urlmap.py2010-06-25 23:33:56.560406133 +0200
+@@ -7,6 +7,7 @@
+ from UserDict import DictMixin
+ import re
+ import os
++import cgi
+ from paste import httpexceptions
+
+ __all__ = ['URLMap', 'PathProxyURLMap']
+@@ -105,7 +106,7 @@
+ extra += '\nHTTP_HOST: %r' % environ.get('HTTP_HOST')
+ app = httpexceptions.HTTPNotFound(
+ environ['PATH_INFO'],
+-comment=extra).wsgi_application
++comment=cgi.escape(extra)).wsgi_application
+ return app(environ, start_response)
+
+ def normalize_url(self, url, trim=True):
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git'
'--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr'
paste-1.7.1
Re: XSS in paste 1.7.1-1 and 1.7.3.1-1
[Adam D. Barratt, 2010-08-03] Have you discussed with the security team whether this is something they believe a DSA should be issued for? I backported the patch for Debian (stable and unbstable) few hours after upstream released new version (didn't know about the issue before) and mailed security team few hours later. They suggested to contact release team instead. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100802223354.gk20...@piotro.eu
Re: Re: Future requirements for specifying supported Python versionsand transition support
one thing that isn't clear for me, what is (or is there any) opinion from doko / POX on this? I proposed the (optional and stripped down) X-Python-Version / X-Python3-Version field. To be honest, all we want to know is if release team still wants the XS-P-V and XB-P-V fields, the rest is implementation details (about which we will not ask release team for opinions ;-P) PS Please CC me on replies -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Re: Bug#545848: python-enchant: Typo in method name in enchant/checker/__init__.py
fixed 545848 1.5.3-1 thanks bts [Tapio Lehtonen, 2009-09-09] from enchant.checker import SpellChecker checker = SpellChecker(ufi_FI) checker.add_to_personal(usomeword) Tapio: it's fixed in 1.5.x (currently in testing) Please use 'checker.dict.add(usomeword)' directly for now. Release managers: can I upload pyenchant 1.4.2-3+lenny1 with this patch: | --- enchant/checker/__init__.py.orig 2009-09-09 22:42:20.949143895 +0200 | +++ enchant/checker/__init__.py 2009-09-09 22:42:35.564143851 +0200 | @@ -284,7 +284,7 @@ | | if word is None: | word = self.word | -self.dict.add_to_personal(word) | +self.dict.add(word) | | def suggest(self,word=None): | Return suggested spellings for the given word. it's clearly a typo, version in stable returns: AttributeError: 'Dict' object has no attribute 'add_to_personal' -- -=[ Piotr Ożarowski ]=- -=[ http://www.ozarowski.pl ]=- signature.asc Description: Digital signature
Re: can we upload mod-wsgi 2.5-1~lenny1 to stable?
See below for upstream's response. If it's fine with you, we'll also
include this change in our upload:
| Index: mod_wsgi.c
| ===
| --- mod_wsgi.c (wersja 1351)
| +++ mod_wsgi.c (wersja 1352)
| @@ -1540,7 +1540,6 @@
|
| if (n == -1) {
| PyErr_SetString(PyExc_IOError, request data read error);
| -Py_DECREF(result);
| return NULL;
| }
(Graham mentions it in his mail)
[Graham Dumpleton, 2009-08-28]
2009/8/28 Piotr Ożarowski pi...@debian.org:
[Bernd Zeimetz, 2009-08-28]
Hi Graham,
I'm forwarding you a mail from our Debian release managers - could you
give a
comment on that?
/me is pretty sure it's a fix, but lets wait for Graham's response :)
[...]
that's in mod_wsgi.c, btw:
@@ -3538,7 +3583,7 @@
}
}
- Py_INCREF(m);
+ Py_XDECREF(m);
Py_INCREF(h);
This appears to be part of upstream r1244
(http://code.google.com/p/modwsgi/source/detail?r=1244path=/trunk/mod_wsgi/mod_wsgi.c)
for which the commit message is Protect against decrementing reference
count on
NULL pointer. The other two hunks of the commit do exactly that,
exchanging
Py_DECREF for Py_XDECREF, but replacing Py_INCREF with Py_XDECREF doesn't
seem
to make a lot of sense.
The original code, where it was doing:
Py_INCREF(m);
could technically cause a one off Python object memory leak as it
should have been decrementing instead of incrementing.
In the greater scheme of things it didn't matter though as it would
only cause a leak if the Python interpreter was destroyed within that
process and then reinitialised. For the process this was done in, that
never occurs as once Python interpreter is destroyed the process is
exited.
So, fixing a technical mistake in handling object reference counts,
but change is ultimately of no significance as wasn't causing a
problem.
The other changes in that change revision were again more
technicalities, as the thing on which reference count was being
decremented should always exist. If it didn't then Python would likely
have crashed before that point. So, again just making code technically
correct and not actually addressing a presenting problem.
Given this is a fix from mod_wsgi 2.4 and you are looking at getting
2.5 into stable tree, is this just someone reviewing the changes.
BTW, I have pending changes for mod_wsgi 2.6 as well. These are detailed at:
http://code.google.com/p/modwsgi/wiki/ChangesInVersion0206
There is though only one in there of any significance, ie., causes a
crash. This is:
3. Fixed bug where was decrementing Python object reference count on
NULL pointer, causing a crash. This was possibly only occuring in
embedded mode and only where closure of remote client connection was
detected before any request content was read. The issue may have been
more prevalent for a HTTPS connection from client.
The code change is a one line change at line 1543 in:
http://code.google.com/p/modwsgi/source/diff?spec=svn1351r=1352format=sidepath=/branches/mod_wsgi-2.X/mod_wsgi.c
If you look through that functions code you will see that result is
never set before that point. Don't know what your attitude is to back
porting obvious fixes from future versions.
I'll be releasing mod_wsgi 2.6 sometime soon, but when really depends
on when I sort out Python 3.X changes for mod_wsgi 3.0 and am ready
for that to also go out. Of course, mod_wsgi 2.6 still has to go
through the whole unstable, testing cycle etc.
Graham
--
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: can we upload mod-wsgi 2.5-1~lenny1 to stable?
[Adam D. Barratt, 2009-08-28] Yes, that's fine. Please go ahead. (fwiw, I almost requested that you backport some of the changes on top of 2.3 instead, but by the time I'd finished and looked at the few bits that had ended up being left out, it didn't seem worth the effort). If you're aiming for inclusion in 5.0.3, don't forget that p-u-new is being frozen during the course of this weekend in preparation for the release the week after. uploaded to stable, thanks -- -=[ Piotr Ożarowski ]=- -=[ http://www.ozarowski.pl ]=- signature.asc Description: Digital signature
can we upload mod-wsgi 2.5-1~lenny1 to stable?
Hi release team,
Debian Lenny was shipped with mod-wsgi v2.3. Upstream released two new
bug fix versions since then - 2.4 and 2.5 (with bug fixes mostly
backported from developement branch - 3.x). Since upstream changelog
mentions[1] also new features (also backported from 3.x), we (Bernd and I)
contacted upstream (who helped us a lot before) about these new features
and he told us that these features are actually a bug fixes as well
and he recommends not to strip them in an upload to Debian stable.
What do you think? Can we upload 2.5 to Debian stable?
Please note that I use (in place where I work) mod-wsgi 2.5 in
production since May and one of Debian servers (the one that hosts
wiki.debian.org) is using backported version as well.
I'm attaching the output of:
debdiff mod-wsgi_2.3-1.dsc mod-wsgi_2.5-1~lenny1.dsc | filterdiff -x
\*configure
diffstat:
README |2
configure | 2391 ++---
configure.ac | 105 -
debian/README.source |6
debian/changelog | 26
debian/control |4
debian/copyright |4
debian/libapache2-mod-wsgi.postrm |1
debian/patches/configure-apache-version.dpatch | 27
mod_wsgi.c | 412 +++-
10 files changed, 1426 insertions(+), 1552 deletions(-)
[1] http://code.google.com/p/modwsgi/wiki/ChangesInVersion0204
http://code.google.com/p/modwsgi/wiki/ChangesInVersion0205
--
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-
diff -Nru mod-wsgi-2.3/configure mod-wsgi-2.5/configure
diff -Nru mod-wsgi-2.3/configure.ac mod-wsgi-2.5/configure.ac
--- mod-wsgi-2.3/configure.ac 2008-01-24 11:19:14.0 +0100
+++ mod-wsgi-2.5/configure.ac 2009-04-15 01:06:28.0 +0200
@@ -1,6 +1,6 @@
dnl vim: set sw=4 expandtab :
dnl
-dnl Copyright 2007-2008 GRAHAM DUMPLETON
+dnl Copyright 2007-2009 GRAHAM DUMPLETON
dnl
dnl Licensed under the Apache License, Version 2.0 (the License);
dnl you may not use this file except in compliance with the License.
@@ -50,15 +50,18 @@
AC_SUBST(PYTHON)
-PYTHON_VERSION=`${PYTHON} -c 'from distutils import sysconfig; \
-print sysconfig.get_config_var(VERSION)'`
-
-CPPFLAGS1=`${PYTHON} -c 'from distutils import sysconfig; \
-print -I + sysconfig.get_config_var(INCLUDEPY)'`
-
-CPPFLAGS2=`${PYTHON} -c 'from distutils import sysconfig; \
-print .join(filter(lambda x: x.startswith(-D), \
-sysconfig.get_config_var(CFLAGS).split()))'`
+PYTHON_VERSION=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write((sysconfig.get_config_var(VERSION)))'`
+
+CPPFLAGS1=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write(-I + sysconfig.get_config_var(INCLUDEPY))'`
+
+CPPFLAGS2=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write( .join(filter(lambda x: x.startswith(-D), \
+sysconfig.get_config_var(CFLAGS).split('`
if test ${ENABLE_EMBEDDED} != yes; then
CPPFLAGS3=-DMOD_WSGI_DISABLE_EMBEDDED
@@ -66,40 +69,63 @@
CPPFLAGS3=
fi
-CPPFLAGS=${CPPFLAGS1} ${CPPFLAGS2} ${CPPFLAGS3}
+CPPFLAGS=${CPPFLAGS} ${CPPFLAGS1} ${CPPFLAGS2} ${CPPFLAGS3}
AC_SUBST(CPPFLAGS)
-PYTHONFRAMEWORKDIR=`${PYTHON} -c 'from distutils import sysconfig; \
-print sysconfig.get_config_var(PYTHONFRAMEWORKDIR)'`
-PYTHONFRAMEWORKPREFIX=`${PYTHON} -c 'from distutils import sysconfig; \
-print sysconfig.get_config_var(PYTHONFRAMEWORKPREFIX)'`
-PYTHONFRAMEWORK=`${PYTHON} -c 'from distutils import sysconfig; \
-print sysconfig.get_config_var(PYTHONFRAMEWORK)'`
+PYTHONLIBDIR=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write(sysconfig.get_config_var(LIBDIR))'`
+PYTHONCFGDIR=`${PYTHON} -c 'from sys import stdout; \
+import distutils.sysconfig; \
+stdout.write(distutils.sysconfig.get_python_lib(plat_specific=1, \
+standard_lib=1) +/config)'`
+PYTHONFRAMEWORKDIR=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write(sysconfig.get_config_var(PYTHONFRAMEWORKDIR))'`
+PYTHONFRAMEWORKPREFIX=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write(sysconfig.get_config_var(PYTHONFRAMEWORKPREFIX))'`
+PYTHONFRAMEWORK=`${PYTHON} -c 'from sys import stdout; \
+from distutils import sysconfig; \
+stdout.write(sysconfig.get_config_var(PYTHONFRAMEWORK))'`
if test ${PYTHONFRAMEWORKDIR} = no-framework; then
-LDFLAGS=`${PYTHON} -c 'import distutils.sysconfig; \
-print -L + distutils.sysconfig.get_python_lib(plat_specific=1, \
-standard_lib=1) +/config'`
+LDFLAGS1=-L${PYTHONLIBDIR}
+LDFLAGS2=-L${PYTHONCFGDIR}
LDLIBS1
unblock request for python-avc 0.6.1-1
Hi, Please unblock python-avc 0.6.1-1. Missing sources for PDF documentation were added in this release (no changes in the code) pgpMJYyrgFwqs.pgp Description: PGP signature
Re: Pre-approval for matplotlib/0.98.1-1+lenny4 upload to t-p-u
[Sandro Tosi, 2008-11-13] PS: I would like to kindly ask you to re-consider the possibility to accept 0.98.3 for lenny: it was already rejected once [1], but all the bugs fixed with t-p-u uploads were already fixed in 0.98.3 release. +1 please note that we can remove all the Debian specific changes (like new -dbg package) if it will allow us to have 0.98.3 in Lenny. Yeah, I know that there's lots of stuff to review in 0.98.3 but please note that matplotlib is the only package in our teams (DPMT and PAPT, 284 packages in total) which is blocking release of Lenny and we would love to have all the upstream fixes in Lenny. -- :wq! pgp5QNEJxRCh9.pgp Description: PGP signature
Re: please unblock phatch 0.1.6-1
[Neil McGovern, 2008-11-10] On Sun, Nov 09, 2008 at 10:10:43PM +0100, Piotr Ożarowski wrote: Please unblock phatch 0.1.6-1. What's: locale/.dropbox? hmm, it looks like serialized empty dictionary. It's probably a leftover from some kind of local test Stani forgot to remove. Anyway, it's not installed nor used. -- :wq! pgpUXBCHooG4A.pgp Description: PGP signature
please unblock phatch 0.1.6-1
Please unblock phatch 0.1.6-1.
It's a new upstream release but upstream (aka 5-euro guy[1] ;) is one
of the packagers and is aware of the freeze so only few lines of
code were changed (+translation updates), no new features (thanks
Stani), see attached debdiff
(`debdiff phatch_0.1.{5,6}-1.dsc | filterdiff -x '*/locale/*'`)
from debian/changelog:
|phatch (0.1.6-1) unstable; urgency=low
|
| [ Stani M ]
| * New upstream release (Closes LP: #288404, #277073, #260549)
|
| [ Emilio Pozuelo Monfort ]
| * Fix watch file.
|
| [ Sandro Tosi ]
| * debian/control
|- switch Vcs-Browser field to viewsvn
[1]
http://pythonide.blogspot.com/2008/10/how-to-make-money-with-free-software.html
diff -Nru phatch-0.1.5/debian/changelog phatch-0.1.6/debian/changelog
--- phatch-0.1.5/debian/changelog 2008-11-09 22:07:23.0 +0100
+++ phatch-0.1.6/debian/changelog 2008-11-09 22:07:23.0 +0100
@@ -1,3 +1,17 @@
+phatch (0.1.6-1) unstable; urgency=low
+
+ [ Stani M ]
+ * New upstream release (Closes LP: #288404, #277073, #260549)
+
+ [ Emilio Pozuelo Monfort ]
+ * Fix watch file.
+
+ [ Sandro Tosi ]
+ * debian/control
+- switch Vcs-Browser field to viewsvn
+
+ -- Piotr Ożarowski [EMAIL PROTECTED] Sun, 09 Nov 2008 21:43:23 +0100
+
phatch (0.1.5-1) unstable; urgency=medium
[ Stani M ]
diff -Nru phatch-0.1.5/debian/control phatch-0.1.6/debian/control
--- phatch-0.1.5/debian/control 2008-11-09 22:07:23.0 +0100
+++ phatch-0.1.6/debian/control 2008-11-09 22:07:23.0 +0100
@@ -6,7 +6,7 @@
Stani M [EMAIL PROTECTED], Piotr Ożarowski [EMAIL PROTECTED]
Standards-Version: 3.8.0
Homepage: http://photobatch.stani.be
-Vcs-Browser:
http://svn.debian.org/wsvn/python-apps/packages/phatch/trunk/?op=log
+Vcs-Browser: http://svn.debian.org/viewsvn/python-apps/packages/phatch/trunk/
Vcs-Svn: svn://svn.debian.org/python-apps/packages/phatch/trunk/
Build-Depends: debhelper (= 5.0.51),
cdbs (= 0.4.43),
diff -Nru phatch-0.1.5/debian/watch phatch-0.1.6/debian/watch
--- phatch-0.1.5/debian/watch 2008-11-09 22:07:23.0 +0100
+++ phatch-0.1.6/debian/watch 2008-11-09 22:07:23.0 +0100
@@ -1,3 +1,3 @@
version=3
opts=uversionmangle=s/.bzr/~bzr/ \
-http://sd-2986.dedibox.fr/photobatch/download/package/phatch-(.*)\.tar\.gz
+http://sd-2469.dedibox.fr/photobatch/download/package/phatch-(.*)\.tar\.gz
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/ar/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/ar/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/ar/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/ar/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/bg/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/bg/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/bg/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/bg/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/ca/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/ca/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/ca/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/ca/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/cs/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/cs/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/cs/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/cs/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/da/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/da/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/da/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/da/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/de/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/de/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/de/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/de/LC_MESSAGES/phatch.po
diff -Nru phatch-0.1.5/locale/.dropbox phatch-0.1.6/locale/.dropbox
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/el/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/el/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/el/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/el/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/en_GB/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/en_GB/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/en_GB/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/en_GB/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/es/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/es/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/es/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/es/LC_MESSAGES/phatch.po
Pliki binarne /tmp/ONPLW2UrbZ/phatch-0.1.5/locale/fa/LC_MESSAGES/phatch.mo i
/tmp/7d5p2UBV2h/phatch-0.1.6/locale/fa/LC_MESSAGES/phatch.mo się różnią
diff -Nru phatch-0.1.5/locale/fa/LC_MESSAGES/phatch.po
phatch-0.1.6/locale/fa/LC_MESSAGES/phatch.po
Pliki binarne /tmp
Re: enchant NMU
[ Paul Wise, 2008-09-30 ] Another two have different versions in sid/lenny, so will need multiple binNMUs: pyenchant_1.3.1-2 pyenchant_1.4.2-1 actually I planed to ask for a freeze exception for pyenchant 1.4.2-1 after having it in unstable for a while but then #499710 was reported. Since it's fixed now, do you think unblocking pyenchant 1.4.2-1 is still possible? Pyenchant is released simultaneously with Enchant (it even has the same upstream version). It was my fault why it wasn't in time in unstable - I prepared new version 5 months ago[1] but since it wasn't working correctly with Enchant 1.3, I didn't upload it to unstable (waiting for Enchant 1.4 to be uploaded first). Few months later Enchat 1.4 was uploaded but I've missed it. When I finally noticed it, it was too late... anyway, I removed some major changes I introduced in the meantime (like new -dbg package), created lenny branch[2] and uploaded it to unstable. Upstream bug tracker[3] doesn't contain any new bugs. [1] http://svn.debian.org/wsvn/python-modules/packages/pyenchant/trunk/debian/?op=logrev=0sc=0isdir=1 [2] http://svn.debian.org/wsvn/python-modules/packages/pyenchant/branches/lenny/debian/?op=logrev=0sc=0isdir=1 [3] http://sourceforge.net/tracker/?group_id=129919atid=716237 -- :wq! pgpgow0sHZb1u.pgp Description: PGP signature
Re: please unblock python-webob 0.9.3-1
[Neil McGovern, 2008-09-26] Can you explain what bugs are fixed please? * PUT requests with empty content-type are no longer considered form requests (Pylons applications will save some bandwidth) * it no longer raises ValueError if long timestamp is passed (can affects 64bit machines) * trailing semicolons in cookie headers are striped if python2.4 is used (python2.5 does that by default) -- :wq! pgpbPfJApjCk7.pgp Description: PGP signature
please unblock python-webob 0.9.3-1
Hi,
Please unblock python-webob 0.9.3-1. It's a new upstream but a bug fix
only release.
From upstream changelog:
* Fixed resp.set_cookie(max_age=timedelta(...))
* request.POST now supports PUT requests with the appropriate Content-Type.
It's in unstable since 10 days and no bugs has been reported against it.
Package has one[1] rev. dependency in Lenny: python-weberror and it
works fine with python-webob 0.9.3 (I'm [co-]maintaining all 3 mentioned
packages)
I'm attaching diffstat and
`debdiff python-webob_0.9.{2,3}-1.dsc | filterdiff -x '*/doc/*' -x '*/test/*'`
output.
TIA
[1] python-pylons 0.9.7~rc, which also depends on this package, is in
experimental for now
--
:wq!
PKG-INFO |2 -
WebOb.egg-info/PKG-INFO|2 -
WebOb.egg-info/SOURCES.txt |1
debian/changelog |6 +
docs/conf.py |2 -
docs/differences.txt |6 -
docs/file-example.txt |6 ++---
docs/index.txt |2 -
docs/news.txt |8 +++
docs/reference.txt | 42 +++-
docs/test-file.txt |1
setup.cfg |4 ++-
setup.py |4 +--
tests/test_request.py |2 -
tests/test_request.txt | 28 ++
tests/test_response.txt| 10 -
webob/__init__.py | 47 -
webob/multidict.py |4 +--
18 files changed, 114 insertions(+), 63 deletions(-)
diff -Nru python-webob-0.9.2/debian/changelog
python-webob-0.9.3/debian/changelog
--- python-webob-0.9.2/debian/changelog 2008-09-25 22:41:58.0 +0200
+++ python-webob-0.9.3/debian/changelog 2008-09-25 22:41:58.0 +0200
@@ -1,3 +1,9 @@
+python-webob (0.9.3-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Piotr Ożarowski [EMAIL PROTECTED] Mon, 15 Sep 2008 21:26:02 +0200
+
python-webob (0.9.2-1) unstable; urgency=low
* New upstream release
diff -Nru python-webob-0.9.2/docs/conf.py python-webob-0.9.3/docs/conf.py
diff -Nru python-webob-0.9.2/docs/differences.txt
python-webob-0.9.3/docs/differences.txt
diff -Nru python-webob-0.9.2/docs/file-example.txt
python-webob-0.9.3/docs/file-example.txt
diff -Nru python-webob-0.9.2/docs/index.txt python-webob-0.9.3/docs/index.txt
diff -Nru python-webob-0.9.2/docs/news.txt python-webob-0.9.3/docs/news.txt
diff -Nru python-webob-0.9.2/docs/reference.txt
python-webob-0.9.3/docs/reference.txt
diff -Nru python-webob-0.9.2/docs/test-file.txt
python-webob-0.9.3/docs/test-file.txt
diff -Nru python-webob-0.9.2/PKG-INFO python-webob-0.9.3/PKG-INFO
--- python-webob-0.9.2/PKG-INFO 2008-06-13 18:46:08.0 +0200
+++ python-webob-0.9.3/PKG-INFO 2008-09-15 04:30:33.0 +0200
@@ -1,6 +1,6 @@
Metadata-Version: 1.0
Name: WebOb
-Version: 0.9.2
+Version: 0.9.3
Summary: WSGI request and response object
Home-page: http://pythonpaste.org/webob/
Author: Ian Bicking
diff -Nru python-webob-0.9.2/setup.cfg python-webob-0.9.3/setup.cfg
--- python-webob-0.9.2/setup.cfg2008-06-13 18:46:08.0 +0200
+++ python-webob-0.9.3/setup.cfg2008-09-15 04:30:33.0 +0200
@@ -7,9 +7,11 @@
command_packages = buildutils.pudge_command, buildutils.publish_command
[nosetests]
-detailed-errors = True
doctest-extension = txt
+detailed-errors = True
with-doctest = True
+exclude = jsonrpc-example.txt
+include = docs
[publish]
doc-dest = scp://[EMAIL PROTECTED]/home/paste/htdocs/webob/
diff -Nru python-webob-0.9.2/setup.py python-webob-0.9.3/setup.py
--- python-webob-0.9.2/setup.py 2008-06-13 18:45:44.0 +0200
+++ python-webob-0.9.3/setup.py 2008-09-15 04:29:54.0 +0200
@@ -1,7 +1,7 @@
from setuptools import setup, find_packages
import sys, os
-version = '0.9.2'
+version = '0.9.3'
setup(name='WebOb',
version=version,
@@ -31,5 +31,5 @@
include_package_data=True,
zip_safe=True,
test_suite='nose.collector',
- tests_require=['dtopt', 'nose', 'webtest']
+ tests_require=['dtopt', 'nose', 'tempita', 'webtest', 'wsgiproxy']
)
diff -Nru python-webob-0.9.2/tests/test_request.py
python-webob-0.9.3/tests/test_request.py
diff -Nru python-webob-0.9.2/tests/test_request.txt
python-webob-0.9.3/tests/test_request.txt
diff -Nru python-webob-0.9.2/tests/test_response.txt
python-webob-0.9.3/tests/test_response.txt
diff -Nru python-webob-0.9.2/webob/__init__.py
python-webob-0.9.3/webob/__init__.py
--- python-webob-0.9.2/webob/__init__.py2008-06-13 18:45:44.0
+0200
+++ python-webob-0.9.3/webob/__init__.py2008-09-15 04:29:54.0
+0200
@@ -300,7 +300,7 @@
dt = dt.timetuple()
if isinstance(dt, (tuple, time.struct_time)):
dt = calendar.timegm(dt)
-if not isinstance(dt, (float, int)):
+if not isinstance(dt, (float, int, long)):
raise ValueError(
You must pass in a datetime, date, time
please unblock sqlalchemy 0.4.7p1-1
Hi,
Please unblock sqlalchemy 0.4.7p1-1. It's a new upstream release but only
3 lines of code[1] are changed (4 including version change).
Please note that 0.4.* releases are just a bug fix releases, development
version of SQLAlchemy (0.5.x series) is already in experimental.
I'm attaching diffstat and
`debdiff sqlalchemy_0.4.7{,p1}-1.dsc | filterdiff -x '*/doc/*' -x '*/test/*'`
output.
BTW: I'm using this version since 2008-08-01, I uploaded it to unstable
recently due to 0.4.7-1 transition.
[1] i.e. without docs/tests
--
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-
diff -Nru sqlalchemy-0.4.7/CHANGES sqlalchemy-0.4.7p1/CHANGES
--- sqlalchemy-0.4.7/CHANGES2008-07-26 18:43:59.0 +0200
+++ sqlalchemy-0.4.7p1/CHANGES 2008-07-31 17:08:36.0 +0200
@@ -1,6 +1,21 @@
===
CHANGES
===
+0.4.7p1
+=
+- orm
+- Added add() and add_all() to scoped_session
+ methods. Workaround for 0.4.7:
+
+from sqlalchemy.orm.scoping import ScopedSession,\
+instrument
+setattr(
+ScopedSession, add, instrument(add))
+setattr(
+ScopedSession, add_all, instrument(add_all))
+
+- Fixed non-2.3 compatible usage of set() and generator
+ expression within relation().
0.4.7
=
diff -Nru sqlalchemy-0.4.7/debian/changelog sqlalchemy-0.4.7p1/debian/changelog
--- sqlalchemy-0.4.7/debian/changelog 2008-08-10 21:57:39.0 +0200
+++ sqlalchemy-0.4.7p1/debian/changelog 2008-08-10 21:57:39.0 +0200
@@ -1,3 +1,9 @@
+sqlalchemy (0.4.7p1-1) unstable; urgency=low
+
+ * New upstream release
+
+ -- Piotr Ożarowski [EMAIL PROTECTED] Fri, 01 Aug 2008 19:43:14 +0200
+
sqlalchemy (0.4.7-1) unstable; urgency=low
* New upstream release
diff -Nru sqlalchemy-0.4.7/doc/copyright.html
sqlalchemy-0.4.7p1/doc/copyright.html
diff -Nru sqlalchemy-0.4.7/doc/dbengine.html
sqlalchemy-0.4.7p1/doc/dbengine.html
diff -Nru sqlalchemy-0.4.7/doc/docstrings.html
sqlalchemy-0.4.7p1/doc/docstrings.html
diff -Nru sqlalchemy-0.4.7/doc/documentation.html
sqlalchemy-0.4.7p1/doc/documentation.html
diff -Nru sqlalchemy-0.4.7/doc/index.html sqlalchemy-0.4.7p1/doc/index.html
diff -Nru sqlalchemy-0.4.7/doc/intro.html sqlalchemy-0.4.7p1/doc/intro.html
diff -Nru sqlalchemy-0.4.7/doc/mappers.html sqlalchemy-0.4.7p1/doc/mappers.html
diff -Nru sqlalchemy-0.4.7/doc/metadata.html
sqlalchemy-0.4.7p1/doc/metadata.html
diff -Nru sqlalchemy-0.4.7/doc/ormtutorial.html
sqlalchemy-0.4.7p1/doc/ormtutorial.html
diff -Nru sqlalchemy-0.4.7/doc/plugins.html sqlalchemy-0.4.7p1/doc/plugins.html
diff -Nru sqlalchemy-0.4.7/doc/pooling.html sqlalchemy-0.4.7p1/doc/pooling.html
diff -Nru sqlalchemy-0.4.7/doc/session.html sqlalchemy-0.4.7p1/doc/session.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_access.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_access.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_firebird.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_firebird.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_maxdb.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_maxdb.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_mssql.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_mssql.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_mysql.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_mysql.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_oracle.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_oracle.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_postgres.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_postgres.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_sqlite.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_sqlite.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_databases_sybase.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_databases_sybase.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_engine_default.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_engine_default.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_engine.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_engine.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_engine_strategies.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_engine_strategies.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_engine_threadlocal.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_engine_threadlocal.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_engine_url.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_engine_url.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_exceptions.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_exceptions.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_ext_associationproxy.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_ext_associationproxy.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_ext_declarative.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_ext_declarative.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_ext_orderinglist.html
sqlalchemy-0.4.7p1/doc/sqlalchemy_ext_orderinglist.html
diff -Nru sqlalchemy-0.4.7/doc/sqlalchemy_ext_sqlsoup.html
sqlalchemy-0.4.7p1/doc
any chance to unblock jinja2 2.0-1 ?
Hi, I uploaded jinja2 (jinja successor, doesn't conflict with jinja package) on 2008-07-20 (before the freeze) but it stuck in NEW for some time. Is there any chance to unblock this package or is it too late? [Please CC me on replies] -- :wq! pgpsozuTQrLmW.pgp Description: PGP signature
Re: Please allow sphinx 0.4.2-1 into testing
I agree with Mikhail that all changes from 0.4.2 should appear in Lenny. I'm attaching complete debdiff and a debdiff without documentation/tests changes - the second one is not really that big and changes looks sane to me. -- :wq! sphinx.debdiff.gz Description: application/gunzip sphinx_code.debdiff.gz Description: application/gunzip pgpXvZK0Zk2bK.pgp Description: PGP signature
Re: Please allow sphinx 0.4.2-1 into testing
[Marc 'HE' Brockschmidt, 2008-08-01] Piotr =?utf-8?Q?O=C5=BCarowski?= [EMAIL PROTECTED] writes: I agree with Mikhail that all changes from 0.4.2 should appear in Lenny. I'm attaching complete debdiff and a debdiff without documentation/tests changes - the second one is not really that big and changes looks sane to me. God, how hard is it to understand what No new upstream release means? Rejected. [no sarcasm, just a question] Is it a general rule? The no new upstream release one?. I plan to upload sqlalchemy 0.4.7p1-1 with 3 lines of code changed soon[1]. Do I really have to prepare 0.4.7-2 with changes moved from upstream sources to debian/patches? What does it change (besides avoiding big debdiff due to lots of date stamps in documentation / new regression test files)? If it's not a general rule, what's a sane debdiff size? [1] I'm waiting for 0.4.7-1 to propagate to testing -- :wq! pgpCbZoRSkHVD.pgp Description: PGP signature
Re: Bugs that'll block python 2.5
[Raphael Hertzog, 2008-04-15 09:31]
On Mon, 14 Apr 2008, Adeodato Simó wrote:
Finally, and quite importantly, there is what to do with modules that
have been added to the standard library in 2.5 (ctypes, celementtree,
wgsiref). These use either pycentral or pysupport, and since they mark
themselves as for python 2.5 only, the dependency generated is on
python ( 2.5), rendering them uninstallable.
I think they should simply be updated to not use ${python:Depends}.
I wonder if that should be replaced by some custom dependency however.
Probably not. There's no reason to depend on python-2.4... that's the
job of packages containing python scripts requiring 2.4.
I guess my mail from yesterday didn't make it... anyway, ctypes and wgsiref
are already fixed (I will file bugs against python-support and python-central
later) and celementtree should be fixed by binNMU (it worked on my
desktop)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Request for binNMU of gnome-python-extras
Please binNMU gnome-python-extras package on all architectures (rebuild will add support for python2.5) gnome-python-extras-2.14.3, Rebuild to get python2.5 extensions, 1, alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc m68k -- :wq! pgphulDeuFlLT.pgp Description: PGP signature
Request for binNMU of gnome-python
Please binNMU gnome-python package on all architectures (rebuild will add support for python2.5) gnome-python-2.18.2-1, Rebuild to get python2.5 extensions, 1, alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc m68k -- :wq! pgpvxd1cRBsvD.pgp Description: PGP signature
Request for binNMUs of pycairo, pygobject and pybluez
Please binNMU these packages on all architectures (rebuild will add support for python2.5): pycairo_1.4.0-2, 1, Rebuild to get python2.5 extensions, alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc m68k pygobject_2.12.3-2, 1, Rebuild to get python2.5 extensions, alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc m68k pybluez_0.9.1-1, 1, Rebuild to get python2.5 extensions, alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc m68k -- :wq! pgpwZba1eQOg4.pgp Description: PGP signature
