Bug#972085: gtkam: Build-Depends on libexif-gtk, which is moving to GTK3

[Adrian Bunk <bunk@debian.org>]

Control: forcemerge 967485 -1

On Wed, Nov 18, 2020 at 12:09:30AM +1100, Hugh McMaster wrote:
> Hi Adrian,

Hi Hugh,

> On Tue, 17 Nov 2020 at 03:53, Adrian Bunk wrote:
> 
> > What is the point of moving libexif-gtk to GTK3 when the only package
> > using it does not support it?
> >
> > This sounds like a mistake that should be reverted.
> 
> 
> I already have. When I realised gtkam was an issue, I updated libexif-gtk
> to build both GTK 2 and 3.

thanks, and sorry that I missed that.

> Unfortunately, gtkam is dead upstream, so nothing will change there.
> However, several good alternatives exist.
> 
> The Debian QA team is also reluctant to remove gtkam due to its popcon
> installation numbers.
> 
> That said, as libexif-gtk will have GTK 2 support for some time, this bug
> severity can probably be downgraded.

I am merging this with the "depends on deprecated GTK 2" bug for gtkam.

> If smcv does manage to remove GTK 2 during the next development cycle,
> however, we will need to revisit this bug.

>From his "depends on deprecated GTK 2" bugs:

  GTK 2 is used by some important productivity applications like GIMP, 
  and has also historically been a popular UI toolkit for proprietary 
  software that we can't change, so perhaps removing GTK 2 from Debian 
  will never be feasible.


cu
Adrian