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

Re: Very Large Package Set Upgrade, stage 1



On Monday 11 December 2006 09:15, Steve Langasek wrote:
> > sarge: aspell: Depends: aspell-bin, aspell-en | aspell6-dictionary
> > sarge: aspell-en: Depends: libaspell15 (>> 0.60)
> >
> > etch: aspell: Depends: libaspell15 (>= 0.60), libc6 (>= 2.3.6-6),
> > libgcc1 (>= 1:4.1.0), libncursesw5 (>= 5.4-5), libstdc++6 (>= 4.1.0),
> > libaspell15 (= 0.60.4-4), dictionaries-common (>> 0.40) etch:
> > aspell-en Depends: aspell (>= 0.60.3-2)
> >
> Looks like the new libaspell15 conflicts with aspell6-dictionary, which
> is the virtual package provided by the old aspell-$lang packages, and
> the new aspell doesn't depend on the new dictionaries, it only has a
> recommends on aspell-en | aspell-dictionary | aspell6a-dictionary.

Seems to me a bug in package management: aptitude should consider 
upgrading the individual dicts a better solution to resolve the conflict 
than removing them.

Having aspell depend on individual dicts is a no-op as you want to able 
able to choose which dicts to install.

> Do you think this warrants a bug on aspell?

Is there a way to resolve this in aspell packaging then?

Attachment: pgpmUbTGNJFSC.pgp
Description: PGP signature


Reply to: