tags 639210 + wontfix thankyou Hi! Thank you for this bug report, but I won't add the PK GTK+2 module again. Reason for this is that it is already removed in the newest, still uneleased version of PK, so I would need to remove it again very soon and that it is not required by many applications. So yes, you should wait for applications to be ported to GTK+3. Applications, of course, can still access PackageKit through it's session DBus interface or through PK-Glib2. The GTK-module is only required to install missing GTK components using PackageKit, for example missing fonts. If you have an extremely good reason why we could need the GTK2 module, I will of course consier re-adding it, but to be honest I don't thing this reason exists :P Cheers, Matthias
On Thu, 25 Aug 2011 04:10:45 +0200, Petr Gajdůšek <gajdusek.p...@centrum.cz> wrote: > Package: packagekit > Version: 0.6.15-1 > Severity: normal > > Hello > Absence of gtk2 module renders packagekit worthless for many > applications, including i.e. rhythmbox or papref. > > Is it possible to build packagekit-gtk-module along with > packagekit-gtk3-module? Or should I wait till applications will be > rebuilt against gtk3 ? > > Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
