etags 547835 + patch thanks Hi!
As such, I don't think any problem should exist in pygopherd with respect to a python 2.6 transition, since the site-packages reference in the postrm was something to do with python2.2. However, I have just made a few changes to be sure. Please find attached a patch containing the same. HTH, and thanks! Kumar
diff -Nru --exclude changelog pygopherd-2.0.18.3/debian/rules pygopherd-2.0.18.3+nmu1/debian/rules --- pygopherd-2.0.18.3/debian/rules 2008-08-05 08:46:33.000000000 -0500 +++ pygopherd-2.0.18.3+nmu1/debian/rules 2009-10-12 22:03:19.000000000 -0500 @@ -59,7 +59,7 @@ # Add here commands to install the package into debian/pygopherd. #$(MAKE) install DESTDIR=$(CURDIR)/debian/pygopherd - $(PYTHON) setup.py install --root=`pwd`/debian/$(PACKAGE) --no-compile + $(PYTHON) setup.py install --root=`pwd`/debian/$(PACKAGE) --no-compile --install-layout=deb # Build architecture-dependent files here.
