John Molohan wrote:
> Hans Meine wrote:
>   
>> On Friday 29 September 2006 18:10, Duncan Webb wrote:
>>   
>>     
>>> I've put back the changes to freevo_config.py and xine_ivtv_tv, so only
>>> the recordserver needs to be worked on for the PRE/POST PADDING. Is the
>>> error in record server is due to python2.3/python2.4 changes?    
>>>       
>> I saw your error report in the bug report, but it is very unclear to me how 
>> that could happen - it looks entirely unrelated.  (You mean this, don't you:
>>
>> Unhandled exception in thread started by <bound method
>> Record_Thread.__bootstrap of <Record_Thread(Thread-1,
>> stopped daemon)>>
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.4/threading.py", line 427, in
>> __bootstrap
>>     _active_limbo_lock.acquire()
>> AttributeError: 'NoneType' object has no attribute 'acquire'
>>
>> Are you sure this is the first error message you get?)  But I will have a 
>> look 
>> at that later (problem is that my wife is watching movies ATM, so I must not 
>> fiddle around with the Freevo setup ;-/ ).
>>     
I know this problem. I'm pretty sure that was the first message. I'll
try again later and report back.
>> BTW: Am I the only one who dislikes all those bug report messages on the ML? 
>>  
>> For me, it would be nicer to have plain mailing list threads.  With the 
>> SourceForge-generated messages, KMail won't thread them properly (could 
>> probably be fixed on the SF side by adding reference mail headers), and I 
>> have to wad through a complete thread in each message, instead of simply 
>> reading the news quickly. :-(  
>>     
> You're certainly not the only one.
It's certainly useful to track the bugs on sourceforge, easy to track
and see the progress. Must admit I don't like double messages for one
bug report. However if you using procmail it's easy to put the messages
into separate folders. BTW Thunderbird handles the threads correctly. I
use these procmail rules for freevo mail:

:0:
* ^Subject: \[Freevo-devel\] \[ freevo-Bugs-
.Freevo.Bugs2/

:0:
* ^Subject: \[ freevo-Bugs.*
.Freevo.Bugs/

:0:
* ^Subject: .*\[Freevo-devel\]
.Freevo.Devel/

:0:
* ^Subject: .*\[Freevo-users\]
.Freevo.Users/

:0:
* ^Subject: \[Freevo-cvslog\]
.Freevo.Svn/

:0:
* ^Envelope-to: [EMAIL PROTECTED]
.Freevo/



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to