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

Re: aspell upgrade woes

On Wed, Jul 20, 2005 at 09:52:13AM +0200, Goswin von Brederlow wrote:
> Brian Nelson <pyro@debian.org> writes:
> > However, that fix is not in the stable package of aspell.  In stable,
> > aspell-bin just depends on libaspell15 (>= 0.60), so a partial upgrade
> > of just libaspell15 would break aspell-bin.  I suppose I could make the
> > new libaspell15 conflict with the old aspell-bin, but that's rather
> > clumsy and could make upgrades even more awkward.
> Why? This is exactly what a versioned conflict is for. The packages
> have to be upgraded as pair and apt/dpkg will hapily do that. 

Policy does not recommend it:

  A Conflicts entry should almost never have an "earlier than" version
  clause. This would prevent dpkg from upgrading or installing the
  package which declared such a conflict until the upgrade or removal of
  the conflicted-with package had been completed.

> Having libaspell15c2 conflict libaspell15 makes it no easier than
> having libaspell15 conflict the old aspell-bin.

Well, libaspell15c2 conflicts/replaces with libaspell15, which dpkg may
handle differently than a pure conflicts.

Society is never going to make any progress until we all learn to
pretend to like each other.

Reply to: