On Sun, Jun 24, 2012 at 9:50 PM, Pierre-Yves Chibon wrote:
> I had a number of problem with guake and its gconf schema, so after
> discussion here I added this to the spec file:
>
> %posttrans
> killall -HUP gconfd-2 > /dev/null || :
>
> That pretty much forces gconf to reload.
Uhm has this been
On Sun, 2012-06-24 at 13:39 -0800, Jef Spaleta wrote:
> On Sun, Jun 24, 2012 at 12:17 PM, Tom London wrote:
>
> > Haven't checked the crypto changes, but I do notice this spew when I
> > try 'Edit->Preferences':
>
> Okay I think I have the GConf scriptlets fixed:
> http://koji.fedoraproject.org/
Don't say I didn't warn you...because I don't have anything for the
agenda, and no-one else suggested anything, no-one gets to have any fun
at the QA meeting tomorrow. It's cancelled. Yeah, you heard me -
cancelled. You'll just have to go and suffer somewhere else, doing
something horrible like thi
2012/6/24 Michael Schwendt :
> On Sun, 24 Jun 2012 14:09:34 -0300, Sergio Belkin wrote:
>
>> Hi,
>>
>> Just I am somewhat surprised that I submitted package cdw for testing
>> and still is in status
In Pending status I meant :)
(I remember in previous updates that in a few
>> hours it went to tes
On 06/24/2012 05:07 PM, Jef Spaleta wrote:
On Sun, Jun 24, 2012 at 12:45 PM, Jef Spaleta wrote:
Users with existing revelation configurations can blow away
.gconf/apps/revelation and relogin to avoid the errors and reconfig
revelation in the process. But clearly that is not optimal. If there
i
On Sun, Jun 24, 2012 at 12:17 PM, Tom London wrote:
> Haven't checked the crypto changes, but I do notice this spew when I
> try 'Edit->Preferences':
Okay I think I have the GConf scriptlets fixed:
http://koji.fedoraproject.org/koji/taskinfo?taskID=4191873
On local testing.
Install the new sc
On Sun, Jun 24, 2012 at 12:45 PM, Jef Spaleta wrote:
> Users with existing revelation configurations can blow away
> .gconf/apps/revelation and relogin to avoid the errors and reconfig
> revelation in the process. But clearly that is not optimal. If there
> is a packaging mechanism that I can use
this is part of the gconf drift introduced in 0.14.3.
See comments in related upstream report
http://oss.codepoet.no/revelation/issue/77/generating-password-on-rhel6-raises
A fresh test user wont experience the preference problem.
The question becomes how do we force gconf to load the new gconf
On Sun, Jun 24, 2012 at 12:57 PM, Jef Spaleta wrote:
> Rawhide target scratch build of the upstream tree with the fix.
>
> http://koji.fedoraproject.org/koji/taskinfo?taskID=4191839
>
> I have done a local build and test on an F16 system. Revelation
> informs me that the key file is an old encryp
Rawhide target scratch build of the upstream tree with the fix.
http://koji.fedoraproject.org/koji/taskinfo?taskID=4191839
I have done a local build and test on an F16 system. Revelation
informs me that the key file is an old encryption format and requests
me to resave to update the encryption.
On Thu, 2012-06-14 at 07:40 -0500, Josh Bressers wrote:
> Relevation password manager
> https://admin.fedoraproject.org/pkgdb/applications/Revelation Password
> Manager
>
> Has been found to be unsafe.
> http://knoxin.blogspot.co.uk/2012/06/revelation-password-manager-considered.html
>
> I would
On Sun, 24 Jun 2012 14:09:34 -0300, Sergio Belkin wrote:
> Hi,
>
> Just I am somewhat surprised that I submitted package cdw for testing
> and still is in status (I remember in previous updates that in a few
> hours it went to testing) . It's not a reproach, only a question, if
> something is wro
Hi,
Just I am somewhat surprised that I submitted package cdw for testing
and still is in status (I remember in previous updates that in a few
hours it went to testing) . It's not a reproach, only a question, if
something is wrong...
Thanks in advance...
--
--
Sergio Belkin http://www.sergiobe
13 matches
Mail list logo
