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

Re: Broken Upgrade Path for trac from etch-backports to lenny



Hi Sebastian,

On Wednesday 25 February 2009, Sebastian Harl wrote:
> On Wed, Feb 25, 2009 at 12:57:58AM +0100, Jan Wagner wrote:
> > The problem is, that the python stuff change in lenny and the package
> > can't be removed cleanly on lenny.
>
> Is there no way to detect how to properly remove the package? Something
> like checking the version of Python or whatever (I don't know anything
> about how Python packages are handled and what kind of changes have been
> introduced in Lenny)? If that's possibly, I suggest to upload a "fixed"
> package to etch-backports.

sure, I can upload a version, which provides a fixed postrm script. But nobody 
knows, if everybody will update to the version _before_ upgrading to lenny.

With kind regards, Jan.
-- 
Never write mail to <waja@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: