Bug#894757: libmypaint-common: file conflict with mypaint-data
On Wed, Aug 15, 2018 at 11:15:22AM -0400, Jeremy Bicha wrote:
> On Mon, Aug 13, 2018 at 4:43 PM Adrian Bunk <bunk@debian.org> wrote:
> > I'm closing this bug, and cloning a second to track that a proper
> > solution is still required.
>
> Uh, respectfully, why did you do that? You could have just lowered the
> severity of this bug if you think it's not RC.
The bug was RC, and this was fixed in 1.3.0-2.
> But even there I
> disagree: it is clearly RC that gimp can't be co-installable with
> mypaint.
Feel free to change the severity of #906144.
> Your action allowed the new version of gimp to migrate to Testing
> which I know lots of people wanted, but I don't think it's a good idea
> to knowingly introduce this kind of bug to Testing.
No maintainer activity or answer to the suggestion for 4 months.
And several packages waiting for it. I actually started looking at this
for getting gmic from the autoremoval list.
Short-term the breakage isn't that bad, it mainly makes it impossible
for testing users who have both mypaint and gimp installed to upgrade
the affected packages.
> Thanks,
> Jeremy Bicha
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
Reply to: