On 08.10.2010 10:59, Adam D. Barratt wrote:
On Fri, October 8, 2010 09:38, Matthias Klose wrote:
On 07.10.2010 21:20, Adam D. Barratt wrote:
On Fri, 2010-09-24 at 20:14 +0100, Adam D. Barratt wrote:
On Thu, 2010-09-23 at 21:42 +0200, Matthias Klose wrote:
python-stdlib-extensions (2.6.6-1) unstable; urgency=low
* Bump the package version to 2.6.6.
Possibly a silly question, but... why?
Ping?
same for python-profiler.
That has other changes (and no unblock request, afaics).
then please consider this request for python-profiler too.
Python 2.6 is split in more than one source package
for packaging and license reasons.
Indeed.
The only change in python-stdlib-extensions appears to be the version
number, so I was simply querying whether there was some reason I'd missed
that it was technically necessary for all of the involved packages to have
exactly the same version number if there was no functional change between
2.6.5-1 and 2.6.6-1.
No, I don't know of any functional change. I'm just waiting for the first bug
report that the version numbers don't match.
The only package I know that depends on the subminor version number is the
apache plugin. But I assume that somebody did take care of this when approving
the migration of 2.6.6 to testing.
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
