Bug#894757: libmypaint-common: file conflict with mypaint-data

[Adrian Bunk <bunk@debian.org>]

Control: clone -1 -2
Control: close -1 1.3.0-2
Control: retitle -2 libmypaint-common needs solution to co-exist with mypaint-data
Control: severity -2 important

On Tue, Jun 12, 2018 at 10:28:04AM +0200, Bernhard Schmidt wrote:
> On Tue, Apr 03, 2018 at 05:43:10PM -0400, Jeremy Bicha wrote:
> 
> Hi Jeremy,
> 
> > Package: libmypaint-common
> > Version: 1.3.0-1
> > Severity: serious
> > Forwarded: https://github.com/mypaint/mypaint/issues/918
> > 
> > libmypaint-common ships some of the same file names as mypaint-data
> > (the libmypaint.mo files).
> > 
> > I'm going to go ahead and add "Conflicts: mypaint-data" now. The way
> > forward is to have mypaint use libmypaint. When that happens, we can
> > add "Replaces: mypaint-data" too and close this bug.
> 
> This bug is still open and preventing the migration of libmypaint and
> GIMP 2.10 to testing. As far as I can see you worked around this issue
> in 1.3.0-2, right? Setting this version as fixed would allow the stack
> to migrate.

I'm closing this bug, and cloning a second to track that a proper 
solution is still required.

> Bernhard

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed