[Top][All Lists]

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

Re: Shishi 0.0.26

From: Elrond
Subject: Re: Shishi 0.0.26
Date: Wed, 17 May 2006 00:15:29 +0200
User-agent: Mutt/1.5.9i

On Tue, May 16, 2006 at 10:35:40PM +0200, Simon Josefsson wrote:
> Simon Josefsson <address@hidden> writes:
> > Simon Josefsson <address@hidden> writes:
> >
> >> Maybe we can keep the postrm/prerm in the old shishid package?  I'm
> >> not sure if I got everything correct (I had troubles installing the
> >> 0.0.23 package at all), but dist-upgrade now seem to work.
> >
> > That wasn't really true...  I'm tweaking things further, but haven't
> > succeeded yet.  Stay tuned.
> The problem is, IIUC, that we can't use prerm/postinst to handle an
> old buggy shishid if we at the same time have a shishi-kdc do:
> Provides: shishid
> Conflicts: shishid
> Replaces: shishid
> When I run dist-upgrade, dpkg will use the prerm from the old shishid
> package, which fails, and there is no prerm from the "new" shishid,
> because there is no new shishid.
> One solution I see would be to provide an "empty" shishid with the
> prerm, that depends on shishi-kdc, and remove the above
> Provides/Conflicts/Replaces.

It should have
        Replaces: shishid (<= last-version-with-real-shishid)
        Conflicts: dito

At least that's my suggestion. Play with it, throw it in
the trash basket or do whatever you like.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]