1:18 p.m.
Can somebody please reopen and appropriately mark the following bug for
EPEL7, so it doesn't get auto-closed on new Fedora releases? Thanks.
https://bugzilla.redhat.com/show_bug.cgi?id=1164414
6:30 p.m.
On Fri, Aug 19, 2016 at 12:18 PM, Christopher
<ctubbsii(a)fedoraproject.org> wrote:
Can somebody please reopen and appropriately mark the following bug
for
EPEL7, so it doesn't get auto-closed on new Fedora releases? Thanks.
https://bugzilla.redhat.com/show_bug.cgi?id=1164414
When product is changed to Fedora EPEL, there is no gnome-desktop
component option. Only gnome-desktop-sharp. There's also gnome-common.
--
Chris Murphy
6:37 p.m.
On Saturday, 20 August 2016 at 01:30, Chris Murphy wrote:
On Fri, Aug 19, 2016 at 12:18 PM, Christopher
<ctubbsii(a)fedoraproject.org> wrote:
> Can somebody please reopen and appropriately mark the following bug for
> EPEL7, so it doesn't get auto-closed on new Fedora releases? Thanks.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1164414
When product is changed to Fedora EPEL, there is no gnome-desktop
component option. Only gnome-desktop-sharp. There's also gnome-common.
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1164414#c2 ,
gnome-desktop exists in RHEL7/CentOS7 as gnome-desktop3. The report is
invalid and should be closed as such.
Regards,
Dominik
--
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
6:40 p.m.
On Fri, Aug 19, 2016 at 5:37 PM, Dominik 'Rathann' Mierzejewski
<dominik(a)greysector.net> wrote:
On Saturday, 20 August 2016 at 01:30, Chris Murphy wrote:
> On Fri, Aug 19, 2016 at 12:18 PM, Christopher
> <ctubbsii(a)fedoraproject.org> wrote:
> > Can somebody please reopen and appropriately mark the following bug for
> > EPEL7, so it doesn't get auto-closed on new Fedora releases? Thanks.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1164414
>
> When product is changed to Fedora EPEL, there is no gnome-desktop
> component option. Only gnome-desktop-sharp. There's also gnome-common.
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1164414#c2 ,
gnome-desktop exists in RHEL7/CentOS7 as gnome-desktop3. The report is
invalid and should be closed as such.
Ahh OK, so notabug? Invalid is not an option.
Chris Murphy
9:07 p.m.
On Fri, Aug 19, 2016 at 7:41 PM Chris Murphy <lists(a)colorremedies.com>
wrote:
On Fri, Aug 19, 2016 at 5:37 PM, Dominik 'Rathann'
Mierzejewski
<dominik(a)greysector.net> wrote:
> On Saturday, 20 August 2016 at 01:30, Chris Murphy wrote:
>> On Fri, Aug 19, 2016 at 12:18 PM, Christopher
>> <ctubbsii(a)fedoraproject.org> wrote:
>> > Can somebody please reopen and appropriately mark the following bug
for
>> > EPEL7, so it doesn't get auto-closed on new Fedora releases? Thanks.
>> >
>> > https://bugzilla.redhat.com/show_bug.cgi?id=1164414
>>
>> When product is changed to Fedora EPEL, there is no gnome-desktop
>> component option. Only gnome-desktop-sharp. There's also gnome-common.
>
> As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1164414#c2 ,
> gnome-desktop exists in RHEL7/CentOS7 as gnome-desktop3. The report is
> invalid and should be closed as such.
Ahh OK, so notabug? Invalid is not an option.
Ah, my mistake. I was under the impression that it was missing, because
related to gnome-python2-desktop (
https://bugzilla.redhat.com/show_bug.cgi?id=1177390) which
contains gnome-python2-gnomekeyring. Maybe gnome-python2-desktop can be
built with gnome-desktop3? Not sure I understand GNOME packaging
interdependencies yet, but I miss my old python keyring library.
7:15 a.m.
On Sat, 2016-08-20 at 02:07 +0000, Christopher wrote:
Ah, my mistake. I was under the impression that it was missing,
because
related to gnome-python2-desktop (
https://bugzilla.redhat.com/show_bug.cgi?id=1177390) which
contains gnome-python2-gnomekeyring. Maybe gnome-python2-desktop can
be
built with gnome-desktop3? Not sure I understand GNOME packaging
interdependencies yet, but I miss my old python keyring library.
Hi,
I'd never heard of it before now, but I looked into it briefly out of
curiosity. Turns out gnome-python2-desktop (called gnome-python-desktop
upstream) contains old-style manual Python bindings to various old
GNOME 2 stuff. These have all been obsoleted for a very long time by
PyGObject; the upstream git repo was archived five years ago. It's
totally unrelated to gnome-desktop3 (called gnome-desktop upstream),
which is an important GNOME module that just happens to have a
confusingly-similar name.
gnome-python2-gnomekeyring in particular contains old bindings for the
gnome-keyring library, which is also long deprecated. The modern way to
access the keyring is to use libsecret via PyGObject:
https://lazka.github.io/pgi-docs/#Secret-1
Michael
12:49 a.m.
On Sat, Aug 20, 2016 at 8:16 AM Michael Catanzaro <mcatanzaro(a)gnome.org>
wrote:
On Sat, 2016-08-20 at 02:07 +0000, Christopher wrote:
> Ah, my mistake. I was under the impression that it was missing,
> because
> related to gnome-python2-desktop (
> https://bugzilla.redhat.com/show_bug.cgi?id=1177390) which
> contains gnome-python2-gnomekeyring. Maybe gnome-python2-desktop can
> be
> built with gnome-desktop3? Not sure I understand GNOME packaging
> interdependencies yet, but I miss my old python keyring library.
Hi,
I'd never heard of it before now, but I looked into it briefly out of
curiosity. Turns out gnome-python2-desktop (called gnome-python-desktop
upstream) contains old-style manual Python bindings to various old
GNOME 2 stuff. These have all been obsoleted for a very long time by
PyGObject; the upstream git repo was archived five years ago. It's
totally unrelated to gnome-desktop3 (called gnome-desktop upstream),
which is an important GNOME module that just happens to have a
confusingly-similar name.
gnome-python2-gnomekeyring in particular contains old bindings for the
gnome-keyring library, which is also long deprecated. The modern way to
access the keyring is to use libsecret via PyGObject:
https://lazka.github.io/pgi-docs/#Secret-1
Michael
libsecret won't work. It's a higher level abstraction and I need to look at
the GnomeKeyring attributes directly. You can do this with the old
gnome-python2-gnomekeyring library, but the new GnomeKeyring
(python-gobject/python3-gobject) returns a GLib.Array object for the
attribute list, and I can't figure out any way to inspect the attributes
from that in python (and it looks like I'm not the only one[1]).
[1]: http://stackoverflow.com/a/25642221/196405
4:45 p.m.
On Sun, Aug 21, 2016 at 1:49 AM Christopher <ctubbsii(a)fedoraproject.org>
wrote:
On Sat, Aug 20, 2016 at 8:16 AM Michael Catanzaro
<mcatanzaro(a)gnome.org>
wrote:
> On Sat, 2016-08-20 at 02:07 +0000, Christopher wrote:
> > Ah, my mistake. I was under the impression that it was missing,
> > because
> > related to gnome-python2-desktop (
> > https://bugzilla.redhat.com/show_bug.cgi?id=1177390) which
> > contains gnome-python2-gnomekeyring. Maybe gnome-python2-desktop can
> > be
> > built with gnome-desktop3? Not sure I understand GNOME packaging
> > interdependencies yet, but I miss my old python keyring library.
>
> Hi,
>
> I'd never heard of it before now, but I looked into it briefly out of
> curiosity. Turns out gnome-python2-desktop (called gnome-python-desktop
> upstream) contains old-style manual Python bindings to various old
> GNOME 2 stuff. These have all been obsoleted for a very long time by
> PyGObject; the upstream git repo was archived five years ago. It's
> totally unrelated to gnome-desktop3 (called gnome-desktop upstream),
> which is an important GNOME module that just happens to have a
> confusingly-similar name.
>
> gnome-python2-gnomekeyring in particular contains old bindings for the
> gnome-keyring library, which is also long deprecated. The modern way to
> access the keyring is to use libsecret via PyGObject:
>
> https://lazka.github.io/pgi-docs/#Secret-1
>
> Michael
>
>
libsecret won't work. It's a higher level abstraction and I need to look
at the GnomeKeyring attributes directly. You can do this with the old
gnome-python2-gnomekeyring library, but the new GnomeKeyring
(python-gobject/python3-gobject) returns a GLib.Array object for the
attribute list, and I can't figure out any way to inspect the attributes
from that in python (and it looks like I'm not the only one[1]).
[1]: http://stackoverflow.com/a/25642221/196405
I don't suppose anybody here knows how to read the GArray in python to get
the attributes list for a keyring item in GnomeKeyring?
2821
days inactive
2831
days old
7 comments
4 participants
participants (4)
-
Chris Murphy -
Christopher -
Dominik 'Rathann' Mierzejewski -
Michael Catanzaro