Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4
On 8/13/06, Stone <[EMAIL PROTECTED]> wrote: After updating to maintenance 4, I am getting the following error message when starting vdr:Aug 13 04:28:53 sid vdr: [16474] ERROR: plugin '' called cPlugin::ConfigDirectory(), which is not thread safe! Am I missing something? Do all of the plugins have to be modified now to not use "cPlugin::ConfigDirectory"? What is the alternative call?Sorry, I understand now what the problem is. One of my plugins was calling cPlugin::ConfigDirectory from the same thread. Best Regards ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4
Stone wrote: After updating to maintenance 4, I am getting the following error message when starting vdr: Aug 13 04:28:53 sid vdr: [16474] ERROR: plugin '' called cPlugin::ConfigDirectory(), which is not thread safe! Am I missing something? Do all of the plugins have to be modified now to not use "cPlugin::ConfigDirectory"? What is the alternative call? Check your log file to see which thread has pid 16474. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4
After updating to maintenance 4, I am getting the following error message when starting vdr:Aug 13 04:28:53 sid vdr: [16474] ERROR: plugin '' called cPlugin::ConfigDirectory(), which is not thread safe! Am I missing something? Do all of the plugins have to be modified now to not use "cPlugin::ConfigDirectory"? What is the alternative call?Best Regards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4
Anssi Hannula wrote: Klaus Schmidinger wrote: VDR maintenance patch 1.4.1-4 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-4.diff This is a 'diff' against version 1.4.1-3 (which is the official version 1.4.1, patched with ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff, ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-2.diff and ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-3.diff). Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch and report whether it works (or if it causes any new problems). This version requires plugins to be recompiled. Yet you didn't change APIVERSION. I see your problem, you already raised it to 1.4.2, and don't want APIVERSION go to 1.4.3 even before 1.4.2 is released. I would recommend having an independent version numbering for APIVERSION, without relation to the VDR version. It was probably a big mistake to introduce APIVERSION in the first place. I'm already regretting I've ever let myself be talked into doing this... APIVERSION is only incremented in levels of official VDR releases. During maintenance patches it may at some point be incremented to the next official release version, but that's it. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4
Klaus Schmidinger wrote: > VDR maintenance patch 1.4.1-4 is now available at > > ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-4.diff > > This is a 'diff' against version 1.4.1-3 (which is the official > version 1.4.1, patched with > ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff, > ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-2.diff and > ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-3.diff). > > > Small fixes to the officially released VDR versions will be first > made available as "maintenance patches" in the Developer directory, > so that they can be reviewed and tested before a new official > release is published. > > So please apply the above patch and report whether it works (or > if it causes any new problems). > > This version requires plugins to be recompiled. > Yet you didn't change APIVERSION. I see your problem, you already raised it to 1.4.2, and don't want APIVERSION go to 1.4.3 even before 1.4.2 is released. I would recommend having an independent version numbering for APIVERSION, without relation to the VDR version. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
