Re: Migrating a package from from python-central: cleaning up

2009-03-11 Thread Piotr Ożarowski
[Piotr Ożarowski, 2009-03-09]
   I'm a little bit busy these days (so I didn't check pycentral's
   code... yet), but isn't this bug fixed already (probably in 0.6.9
   aka 0.6.10)?

it's not fixed

I was also hit by another upgrade related bug recently - upgrading from
one pycentral based version to another can be broken as well if new
package provides different files. I needed to use rm -rf to clean all
the files (hint: make sure some other packages are not using the same
namespace before removing whole directory)

Here's my preinst file:

| #!/bin/sh
| # remove this file after releasing Squeeze
| set -e
| if [ $1 = upgrade ]  dpkg --compare-versions $2 lt VERSION
| then
|   pycentral pkgremove python-MODULE
|   # if pycentral doesn't remove all files, use below lines
|   rm -rf /usr/lib/python2.4/site-packages/MODULE/
|   rm -rf /usr/lib/python2.5/site-packages/MODULE/
| fi
|
| #DEBHELPER#

VERSION - the one where preinst file is introduced
MODULE - module name that package is providing
python-MODULE is package name

-- 
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpBx1HuS5LIP.pgp
Description: PGP signature


Re: Migrating a package from from python-central: cleaning up (was: Piotrek's new preferred helper tool - (unfair) decision)

2009-03-09 Thread Piotr Ożarowski
[Ben Finney, 2009-03-04]
 As noted elsewhere, this is to overcome behaviour (discussed in
 URL:http://bugs.debian.org/479852)

I'm a little bit busy these days (so I didn't check pycentral's code...
yet), but isn't this bug fixed already (probably in 0.6.9 aka 0.6.10)?
(yeah, I was the one who mentioned it in the first place, one week after
0.6.10 was uploaded)
-- 
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpUvwlfDjr5J.pgp
Description: PGP signature


Re: Migrating a package from from python-central: cleaning up

2009-03-09 Thread Ben Finney
Piotr Ożarowski pi...@debian.org writes:

 [Ben Finney, 2009-03-04]
  As noted elsewhere, this is to overcome behaviour (discussed in
  URL:http://bugs.debian.org/479852)
 
 I'm a little bit busy these days (so I didn't check pycentral's
 code... yet), but isn't this bug fixed already (probably in 0.6.9
 aka 0.6.10)?

(I'm confused by that last part. “aka” is “also known as”. Are you
saying that 0.6.9 and 0.6.10 are just alternate names for the same
version?)

I have ‘python-central’ 0.6.11 installed fron ‘testing’, and the
manual page for ‘dh_pycentral(1)’ still details the behaviour
described in that bug report.

-- 
 \  “One time a cop pulled me over for running a stop sign. He |
  `\said, ‘Didn't you see the stop sign?’ I said, ‘Yeah, but I |
_o__)don't believe everything I read.’” —Steven Wright |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Migrating a package from from python-central: cleaning up

2009-03-09 Thread Piotr Ożarowski
[Ben Finney, 2009-03-09]
 Piotr Ożarowski pi...@debian.org writes:
 
  [Ben Finney, 2009-03-04]
   As noted elsewhere, this is to overcome behaviour (discussed in
   URL:http://bugs.debian.org/479852)
  
  I'm a little bit busy these days (so I didn't check pycentral's
  code... yet), but isn't this bug fixed already (probably in 0.6.9
  aka 0.6.10)?
 
 (I'm confused by that last part. “aka” is “also known as”. Are you
 saying that 0.6.9 and 0.6.10 are just alternate names for the same
 version?)

0.6.9 was never released in Debian, all changes from this version are
in 0.6.10

 I have ‘python-central’ 0.6.11 installed fron ‘testing’, and the
 manual page for ‘dh_pycentral(1)’ still details the behaviour
 described in that bug report.

that manual is outdated at least in one other place (the one mentioning
/usr/share/pycentral), but I don't care anymore, all I want now is to
have python-support in a good shape
-- 
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgp2qwPiIgczt.pgp
Description: PGP signature


Migrating a package from from python-central: cleaning up (was: Piotrek's new preferred helper tool - (unfair) decision)

2009-03-03 Thread Ben Finney
Piotr Ożarowski pi...@debian.org writes:

 PS while converting [from use of ‘python-central’ to use of
 ‘python-support’], remember to add to preinst something like these 3
 lines:
 
 | if [ $1 = upgrade ]  dpkg --compare-versions $2 lt 1.2.3-4; then
 | pycentral pkgremove python-foo
 | fi

As noted elsewhere, this is to overcome behaviour (discussed in
URL:http://bugs.debian.org/479852) that is the default for
‘dh_pycentral’: “create symlinks on postinst, don't clean up on
prerm”. Because it is the default, this likely plagues a significant
portion of ‘python-central’-based packages already installed out
there.

The approaches suggested in the ‘dh_pycentral(1)’ manpage are:

This can be disabled by setting the environment varibale
DH_PYCENTRAL to a string containing the string noprepare. If the
newer version of a package needs to remove the symlinked files on
upgrade, either the package needs to take care of the removal by
calling pycentrel pkgremove in the new preinst, or leaving a file
/var/lib/pycentral/package.pkgremove and using pycentral 0.6.7
or later for the old package version.

I, like Piotr, am now preparing to migrate my Python packages to use
‘python-support’ (once the new version that stops using ‘/var/lib/’
hits ‘testing’). What is my best approach for preparing to do this? As
I see it, the existing documentation suggests one of:

  * Leave the package for now depending on ‘python-central’, set
‘DH_PYCENTRAL = noprepare’ in my existing packages's
‘debian/rules’, then build and upload a new release; or

  * Migrate the package immediately to use ‘python-support’, put the
call to ‘pycentral pkgremove foopackage’ in ‘preinst’ as shown
above by Piotr, then build and upload a new release; or

  * Migrate the package immediately to use ‘python-support’, create an
empty ‘${DESTDIR}/var/lib/pycentral/foopackage.pkgremove’, then
build and upload a new release; or

  * Something else (please specify).

Which of the above is best in general? What reasons would I have for
not doing the same thing to every affected package? How long should I
leave these measures in place before removing all mention of
‘python-central’ from a new release?

-- 
 \   “When I get new information, I change my position. What, sir, |
  `\ do you do with new information?” —John Maynard Keynes |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org