Bug#972085: gtkam: Build-Depends on libexif-gtk, which is moving to GTK3
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
Bug#972085: gtkam: Build-Depends on libexif-gtk, which is moving to GTK3
Hi Adrian, 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. 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. If smcv does manage to remove GTK 2 during the next development cycle, however, we will need to revisit this bug. >
Bug#972085: gtkam: Build-Depends on libexif-gtk, which is moving to GTK3
On Mon, Oct 12, 2020 at 11:04:42PM +1100, Hugh McMaster wrote: >... > libexif-gtk is moving to GTK3 in response to #967573. > > gtkman also only supports GTK2, which means it blocks the introduction of > libexif-gtk built on GTK3. >... 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. > Thank you cu Adrian
Bug#972085: gtkam: Build-Depends on libexif-gtk, which is moving to GTK3
Source: gtkam Version: 1.0-3 Severity: serious Tags: ftbfs Justification: Policy 7.7 Dear Maintainer, libexif-gtk is moving to GTK3 in response to #967573. gtkman also only supports GTK2, which means it blocks the introduction of libexif-gtk built on GTK3. Upstream gtkam has seen no activity since October 2016 and appears dead. If this is not the case, please ask them to convert the source to GTK2. gtkam may need to be removed from Debian if no action is taken. Thank you -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
