How long can a package be in pending status?
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.sergiobelkin.com Watch More TV http://sebelk.blogspot.com LPIC-2 Certified - http://www.lpi.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How long can a package be in pending status?
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 wrong... > > Thanks in advance... It has been my experience that quite a lot of people like to have a few days off over the weekend. That also affects the not-fully-automated tasks like starting a repo compose. -- Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64 loadavg: 0.64 0.55 0.73 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 hope it gets fixed at some future point, but something should > probably be done in the short term. There is apparently a new release coming up with a fix: http://oss.codepoet.no/revelation/issue/61/file-format-magic-string-version-mismatch#comment-1584919 Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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. Can someone please do an independent confirmation that this actually fixes the underlying issues with the encryption weakness? There appears to be one potential regression in 0.14.3+ with searching...but I think its due to a change in gconf key layout. If you experience the search crash...logout/login or shutdown/restart and the problem appears to go away. I saw the crash last week on F16 and F17 while I was doing initial testing for 0.14.3 test packages that I rolled ahead of this security fix landing...but I could not duplicate the search traceback again after a system restart... making it a bit difficult to track down and squash. AnywaysI'm inclined to wait for the official release tarball to land from upstream tomorrow to push update packages into rawhide->F17,F16 testing for release 0.14.4 that rolls in the encryption changes. In the meantime anyone who is seriously concerned about this, please beat on the on the scratch build and make sure its actually a fix. -jef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 encryption format and requests
> me to resave to update the encryption.
>
> Can someone please do an independent confirmation that this actually
> fixes the underlying issues with the encryption weakness?
>
> There appears to be one potential regression in 0.14.3+ with
> searching...but I think its due to a change in gconf key layout. If
> you experience the search crash...logout/login or shutdown/restart
> and the problem appears to go away. I saw the crash last week on F16
> and F17 while I was doing initial testing for 0.14.3 test packages
> that I rolled ahead of this security fix landing...but I could not
> duplicate the search traceback again after a system restart... making
> it a bit difficult to track down and squash.
>
> AnywaysI'm inclined to wait for the official release tarball to
> land from upstream tomorrow to push update packages into
> rawhide->F17,F16 testing for release 0.14.4 that rolls in the
> encryption changes. In the meantime anyone who is seriously concerned
> about this, please beat on the on the scratch build and make sure its
> actually a fix.
>
> -jef
> --
Haven't checked the crypto changes, but I do notice this spew when I
try 'Edit->Preferences':
Traceback (most recent call last):
File "/usr/bin/revelation", line 206, in
action.connect("activate", lambda w: self.prefs())
File "/usr/bin/revelation", line 1527, in prefs
dialog.run_unique(Preferences, self, self.config)
File "/usr/lib64/python2.7/site-packages/revelation/dialog.py", line
1324, in run_unique
d = create_unique(dialog, *args)
File "/usr/lib64/python2.7/site-packages/revelation/dialog.py", line
1282, in create_unique
UNIQUE_DIALOGS[dialog] = dialog(*args)
File "/usr/bin/revelation", line 1623, in __init__
self.__init_section_password(self.page_general)
File "/usr/bin/revelation", line 1762, in __init_section_password
ui.config_bind(self.config, "passwordgen/punctuation",
self.check_punctuation_chars)
File "/usr/lib64/python2.7/site-packages/revelation/ui.py", line
182, in config_bind
id = cfg.monitor(key, cb_get, widget)
File "/usr/lib64/python2.7/site-packages/revelation/config.py", line
150, in monitor
callback(key, self.get(key), userdata)
File "/usr/lib64/python2.7/site-packages/revelation/config.py", line
129, in get
raise ConfigError
ConfigError
tom
--
Tom London
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 keys
for an app?
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..I'm all ears.
-jef
On Sun, Jun 24, 2012 at 12:17 PM, Tom London wrote:
> 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 encryption format and requests
>> me to resave to update the encryption.
>>
>> Can someone please do an independent confirmation that this actually
>> fixes the underlying issues with the encryption weakness?
>>
>> There appears to be one potential regression in 0.14.3+ with
>> searching...but I think its due to a change in gconf key layout. If
>> you experience the search crash...logout/login or shutdown/restart
>> and the problem appears to go away. I saw the crash last week on F16
>> and F17 while I was doing initial testing for 0.14.3 test packages
>> that I rolled ahead of this security fix landing...but I could not
>> duplicate the search traceback again after a system restart... making
>> it a bit difficult to track down and squash.
>>
>> AnywaysI'm inclined to wait for the official release tarball to
>> land from upstream tomorrow to push update packages into
>> rawhide->F17,F16 testing for release 0.14.4 that rolls in the
>> encryption changes. In the meantime anyone who is seriously concerned
>> about this, please beat on the on the scratch build and make sure its
>> actually a fix.
>>
>> -jef
>> --
>
> Haven't checked the crypto changes, but I do notice this spew when I
> try 'Edit->Preferences':
>
> Traceback (most recent call last):
> File "/usr/bin/revelation", line 206, in
> action.connect("activate", lambda w: self.prefs())
> File "/usr/bin/revelation", line 1527, in prefs
> dialog.run_unique(Preferences, self, self.config)
> File "/usr/lib64/python2.7/site-packages/revelation/dialog.py", line
> 1324, in run_unique
> d = create_unique(dialog, *args)
> File "/usr/lib64/python2.7/site-packages/revelation/dialog.py", line
> 1282, in create_unique
> UNIQUE_DIALOGS[dialog] = dialog(*args)
> File "/usr/bin/revelation", line 1623, in __init__
> self.__init_section_password(self.page_general)
> File "/usr/bin/revelation", line 1762, in __init_section_password
> ui.config_bind(self.config, "passwordgen/punctuation",
> self.check_punctuation_chars)
> File "/usr/lib64/python2.7/site-packages/revelation/ui.py", line
> 182, in config_bind
> id = cfg.monitor(key, cb_get, widget)
> File "/usr/lib64/python2.7/site-packages/revelation/config.py", line
> 150, in monitor
> callback(key, self.get(key), userdata)
> File "/usr/lib64/python2.7/site-packages/revelation/config.py", line
> 129, in get
> raise ConfigError
> ConfigError
>
> tom
> --
> Tom London
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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..I'm all ears. Replying to myself... it looks like the gconf schema handling scriptlets in this package has been busted for a long time. I'll spin up a new scratch build with adjusted scripted actions and see if that fixes the problem. Thanks for the breakage report Tom it helped point me in the correct direction. -jef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 scratch build. Logout/Login run revelation open edit/prefs No traceback. Tom can you confirm that the above works for you with the new test package? I suspect that we'll still get tracebacks unless the logout/login happens to restart gconf and have it look for the updated schema. I don't know how to have a running gconf "see" the schema updates introduced by a package install. -jef -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 is a packaging mechanism that I can use..I'm all ears. Replying to myself... it looks like the gconf schema handling scriptlets in this package has been busted for a long time. I'll spin up a new scratch build with adjusted scripted actions and see if that fixes the problem. Thanks for the breakage report Tom it helped point me in the correct direction. -jef I just wanted to say I'm glad someone is looking into updating Revelation and addressing these issues, as I've been using it for a long time and would like to continue doing so. -- Libre Video http://librevideo.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: How long can a package be in pending status?
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 testing) . It's not a reproach, only a question, if >> something is wrong... >> >> Thanks in advance... > > It has been my experience that quite a lot of people like to have a few > days off over the weekend. That also affects the not-fully-automated tasks > like starting a repo compose. Ok I am waiting :) > > -- > Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64 > loadavg: 0.64 0.55 0.73 > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel -- -- Sergio Belkin http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com LPIC-2 Certified - http://www.lpi.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] CANCELLED: 2012-06-25 Fedora QA Meeting
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 this 'recreation' I've heard about somewhere. It sounds terrible. This is what happens when no-one proposes agenda items! For the record, the two action items from last week were both for me, and they were: * adamw to start a list thread for further discussion of the blocker review meeting time topic * adamw to start a list thread about ways to analyze the corpus of blocker bugs Obviously, as you can see threads for both those things...I did them. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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/koji/taskinfo?taskID=4191873 > > > On local testing. > > Install the new scratch build. > Logout/Login > run revelation > open edit/prefs > No traceback. > > Tom can you confirm that the above works for you with the new test package? > > I suspect that we'll still get tracebacks unless the logout/login > happens to restart gconf and have it look for the updated schema. I > don't know how to have a running gconf "see" the schema updates > introduced by a package install. 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. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Revelation password manager issue
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 vetted as not "a bad thing" {tm} by the packaging thinktank?
-jef
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
