[Parl-devel] Bug#910589: myspell-ca: should be in package section oldlibs

[Agustin Martin]

Control: reassign -1 myspell-ca
Control: retitle -1 myspell-ca: obsolete hunspell-ca_3.0.2+repack1-1 has wrong section for it.
Control: severity -1 minor
Control: affects 910617 myspell-ca

On Mon, Oct 08, 2018 at 08:43:07PM +0200, Jonas Smedegaard wrote:
> Quoting Agustin Martin (2018-10-08 20:24:50)
> > Control: reassign -1 parl-desktop-world
> > Control: retitle -1 parl-desktop-world: Needs to depend on hunspell-ca instead of myspell-ca.
> > Control: severity -1 important
> > 
> > On Mon, Oct 08, 2018 at 07:20:22PM +0200, Agustin Martin wrote:
> > > Control: reassign -1 ftp.debian.org
> > > Control: retitle -1 RM: hunspell-ca_3.0.2+repack1-1 -- RoM; This particular version does not belong to any release.
> > > Control: severity -1 normal
> > > 
> > > --------------------------------------------------------------------------
> > > Note for ftpmasters: 
> > > 
> > > archive seems to still contain hunspell-ca_3.0.2+repack1-1 version, but
> > > it does not belong to any release
> > 
> > Hi all,
> > 
> > Just noticed why this ancient version is still there. Sorry for the noise,
> > ftpmasters.
> > 
> > $ apt-cache rdepends myspell-ca
> > 
> > parl-desktop-world: Depends: myspell-ca
> > ... Some suggests, recomends and "or'ed" dependencies.
> > 
> > Unfortunately, this hard rdepends went unnoticed when dropping myspell-ca.
> > Will look at other rdepends in case there is another pending hard-depends.
> > There are a couple of Recommends (testing's firefox-esr-l10n-ca and
> > task-catalan-desktop)
> > 
> > I am reassigning this bug report to parl-desktop-world.
> 
> Reassigning?  parl-desktop-world cannot make myspell-ca change section.

myspell-ca is only there because of parl-desktop-world, there is no point in
changing its section. Problem will go as soon as fixed parl-desktop-world is
accepted. That is why I did things this way.

> File a separate bugreport about parl-desktop-world depending on a 
> transitional package, and tag this bug as affected by the new one.

No problem. Doing things this other way. I'd prefer a block, but using
affects.

Regards,

-- 
Agustin