[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#793117: marked as done (jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1)

Your message dated Sun, 21 Feb 2016 10:33:22 +0000
with message-id <20160221103322.GD6200@betterave.cristau.org>
and subject line Re: Bug#793117: jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1
has caused the Debian Bug report #793117,
regarding jessie-pu: package python-memcache/1.53+2014.06.08.git.918e88c496-1+deb8u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
793117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793117
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org@packages.debian.org
Usertags: pu

Hi,

I would like to propose a stable upload for python-memcache. 

python-memcache's version currently in stable (1.53+2014.06.08.git.918e88c496-1)
is building python3-memcache though its code isn't fully python3
compatible. This python3 package is unusuable and shouldn't exist[0].

The upstream code have been ported to python3 in sid, but this fix 
shouldn't probably be backported since it would require an upstream code 
upgrade from 1.53 to 1.54 in Jessie.

The easiest solution is to make python-memcache stops building
python3-memcache in Jessie. This can be done with the attached fix.

The diff against 1.53+2014.06.08.git.918e88c496-1+deb8u1 is attached.

Best Regards,
 Hugo

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788561

-- 
      Hugo Lefeuvre (hugo6390)    |    www.hugo6390.org
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E

--- a/debian/changelog	2015-07-13 11:00:34.426439594 +0200
+++ b/debian/changelog	2015-07-13 11:00:49.106419709 +0200
@@ -1,3 +1,12 @@
+python-memcache (1.53+2014.06.08.git.918e88c496-1+deb8u1) jessie; urgency=medium
+
+  * Team upload.
+  * debian/control, debian/rules:
+   - Don't build python3-memcache anymore, upstream's Python3 support
+     is too incomplete (Closes: #788561).
+
+ -- Hugo Lefeuvre <hugo6390@orange.fr>  Sun, 12 Jul 2015 22:22:34 +0200
+
 python-memcache (1.53+2014.06.08.git.918e88c496-1) unstable; urgency=medium
 
   * New upstream release.
--- a/debian/control	2015-07-13 11:00:34.426439594 +0200
+++ b/debian/control	2015-07-13 11:00:34.422439599 +0200
@@ -5,9 +5,7 @@
 Uploaders: Carl Chenet <chaica@ohmytux.com>, Thomas Goirand <zigo@debian.org>
 Build-Depends: debhelper (>= 9),
                python-all (>= 2.6.6-3),
-               python-setuptools,
-               python3-all,
-               python3-setuptools
+               python-setuptools
 Standards-Version: 3.9.5
 Homepage: http://www.tummy.com/Community/software/python-memcached/
 Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/python-memcache/trunk/
@@ -23,14 +21,3 @@
  one or more, possibly remote, memcached servers.
  .
  This package contains the Python 2.x module.
-
-Package: python3-memcache
-Architecture: all
-Depends: python3-six, ${misc:Depends}, ${python3:Depends}
-Suggests: memcached
-Description: pure python memcached client - Python 3.x
- This software is a 100% Python interface to the memcached memory cache daemon.
- It is the client side software which allows storing values in one or more,
- possibly remote, memcached servers.
- .
- This package contains the Python 3.x module.
--- a/debian/rules	2015-07-13 11:00:34.426439594 +0200
+++ b/debian/rules	2015-07-13 11:00:34.422439599 +0200
@@ -1,22 +1,17 @@
 #!/usr/bin/make -f
 
 PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
 
 UPSTREAM_GIT = git://github.com/linsomniac/python-memcached.git
 
 %:
-	dh $@ --buildsystem=python_distutils --with python2,python3
+	dh $@ --buildsystem=python_distutils --with python2
 
 override_dh_install:
 	set -e && for pyvers in $(PYTHONS); do \
 		python$$pyvers setup.py install --install-layout=deb \
 			--root $(CURDIR)/debian/python-memcache; \
 	done
-	set -e && for pyvers in $(PYTHON3S); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python3-memcache; \
-	done
 
 override_dh_clean:
 	dh_clean -O--buildsystem=python_distutils

--- End Message ---
--- Begin Message --- 
On Sat, Jul 25, 2015 at 17:34:13 +0100, Adam D. Barratt wrote:

> Control: tags -1 + moreinfo
> 
> On Tue, 2015-07-21 at 15:04 +0200, Hugo Lefeuvre wrote:
> > python-memcache's version currently in stable (1.53+2014.06.08.git.918e88c496-1)
> > is building python3-memcache though its code isn't fully python3
> > compatible. This python3 package is unusuable and shouldn't exist[0].
> > 
> > The upstream code have been ported to python3 in sid, but this fix 
> > shouldn't probably be backported since it would require an upstream code 
> > upgrade from 1.53 to 1.54 in Jessie.
> > 
> > The easiest solution is to make python-memcache stops building
> > python3-memcache in Jessie. This can be done with the attached fix.
> 
> python3-memcache has a reverse-dependency in stable, which would need to
> be fixed first:
> 
> Will remove the following packages from stable:
> 
> python3-memcache | 1.53+2014.06.08.git.918e88c496-1 | all
> 
> Maintainer: Debian Python Modules Team
> <python-modules-team@lists.alioth.debian.org>
> 
> ------------------- Reason -------------------
> 
> ----------------------------------------------
> 
> Checking reverse dependencies...
> # Broken Depends:
> celery: python3-celery
> 
> # Broken Build-Depends:
> celery: python3-memcache
> 
> Dependency problem found.
> 
> (and python3-celery also has an r-dep, python3-django-celery, which
> would again need fixing)
> 
No reply since July, closing.

Cheers,
Julien

--- End Message ---
Reply to: