VDR developer version 1.3.48 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.48.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.47-48.diff
If there are no more serious bugs, this will become the final version 1.4.0 next weekend :-)
The changes since version 1.3.47:
- Updated the GPL copies (thanks to Ville Skyttä). - Fixed several spelling errors (thanks to Ville Skyttä). - Updated the Polish OSD texts (thanks to Jaroslaw Swierczynski). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Updated the French OSD texts (thanks to Pierre Briec). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Updated the Romanian OSD texts (thanks to Lucian Muresan). - Updated the Danish OSD texts (thanks to Mogens Elneff). - Updated the Russian OSD texts (thanks to Oleg Roitburd). - Updated the Slovenian OSD texts (thanks to Matjaz Thaler). - Fixed wrong credits for the patch that was used to implement cPlugin::Active(). - Simplified the 'grep|awk|sed' command to retrieve the VDR/APIVERSION to a single 'sed' call. - Updated the Swedish OSD texts (thanks to Tomas Prybil). - Modified the German OSD texts to be "less technical" (thanks to Andreas Brachold). - Extended the version number reported with the '-V' option to also show the current APIVERSION (suggested by Thomas Günther). - Fixed handling empty titles in cEvent::FixEpgBugs() (reported by Rolf Ahrenberg). - Fixed some missing '-' in the German OSD texts (thanks to Walter Koch). - Added an error message about plugins that don't honor APIVERSION in their Makefile (based on a suggestion by Udo Richter). - Fixed a format string in recording.c to avoid a compiler warning on 64bit systems (thanks to Christian Wieninger for reporting, and Werner Schweer for pointing out that the 'z' modifier should be used here). - Ignoring k_Repeat when deciding whether the same key has been pressed in string input fields (based on a patch from Marko Mäkelä).
Have fun!
Klaus
On 23 Apr 2006 Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
- Added an error message about plugins that don't honor APIVERSION in their Makefile (based on a suggestion by Udo Richter).
There is a small bug:
#make plugins /bin/sh: line 1: @noapiv=: command not found Plugin mp3: make[1]: Entering directory `/usr/local/source/VDR/vdr-1.3.48/PLUGINS/src/mp3-unstable' [...]
Fix:
--- Makefile.orig 2006-04-23 17:04:21.000000000 +0200 +++ Makefile 2006-04-23 17:06:07.000000000 +0200 @@ -176,7 +176,7 @@
plugins: include-dir @failed="";\ - @noapiv="";\ + noapiv="";\ for i in `ls $(PLUGINDIR)/src | grep -v '[^a-z0-9]'`; do\ echo "Plugin $$i:";\ if ! grep -q "$$(LIBDIR)/.*$$(APIVERSION)" "$(PLUGINDIR)/src/$$i/Makefile" ; then\
Regards.
Stefan Huelswitt wrote:
On 23 Apr 2006 Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
- Added an error message about plugins that don't honor APIVERSION in their Makefile (based on a suggestion by Udo Richter).
There is a small bug:
#make plugins /bin/sh: line 1: @noapiv=: command not found Plugin mp3: make[1]: Entering directory `/usr/local/source/VDR/vdr-1.3.48/PLUGINS/src/mp3-unstable' [...]
Fix:
--- Makefile.orig 2006-04-23 17:04:21.000000000 +0200 +++ Makefile 2006-04-23 17:06:07.000000000 +0200 @@ -176,7 +176,7 @@
plugins: include-dir @failed="";\
@noapiv="";\
noapiv="";\ for i in `ls $(PLUGINDIR)/src | grep -v '[^a-z0-9]'`; do\ echo "Plugin $$i:";\ if ! grep -q "\$$(LIBDIR)/.*\$$(APIVERSION)" "$(PLUGINDIR)/src/$$i/Makefile" ; then\
Yea, Ronny Kornexl was about 20 minutes faster than you in a private mail - so please don't wonder if he get's the credit for this ;-)
Too bad I missed this one - I just had eyes for the new error message and the summary line...
Klaus
Hi Klaus,
I've been taking little time off at vdr upgrades, but now that I tried the new version I've noticed some talked setbacks that new APIVERSION has.
I'm using Debian and those scripts that came with apt-get distributed vdr package, so there's problem with scripts to correctly identify vdr versio from APIVERSION. What I mean is it possible to separate them to different switches since now if I try running with those scripts I get this...
/etc/init.d/vdr start Starting Linux Video Disk Recorder: vdr Searching for plugins (VDR 1.3.48/1.3.47):find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name libvdr-*.so.1.3.48/1.3.47' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ libvdr-*.so.1.3.48/1.3.47'. sed: -e expression #1, char 47: unknown option to `s'
./vdr -V vdr (1.3.48/1.3.47) - The Video Disk Recorder
It take me for a while to identify where the problem was since those scripts are always worked perfectly, now they aren't :( It found out that plugin-loader.sh is effected from this change in vdr version x.x.xx/x.x.xx handling. I hope someone of Debian vdr package maintainer is reading this to be notified.
Although this can be fixed fiddling the script, I think they should be separated with different switches. But since vdr-1.4 is finally going to be released, this probably isn't gonna happen?
-Mikko
Mikko Salo wrote:
/etc/init.d/vdr start Starting Linux Video Disk Recorder: vdr Searching for plugins (VDR 1.3.48/1.3.47):find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name libvdr-*.so.1.3.48/1.3.47' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ libvdr-*.so.1.3.48/1.3.47'. sed: -e expression #1, char 47: unknown option to `s'
This problem is debian specific and will be fixed in the 1.3.48 release.
Use this patch:
--- vdr/vdr/trunk/debian/plugin-loader.sh 2006-04-23 14:58:18 UTC (rev 2475) +++ vdr/vdr/trunk/debian/plugin-loader.sh 2006-04-23 16:12:44 UTC (rev 2476) @@ -32,6 +32,7 @@ echo -ne "\nSearching for plugins (VDR $version):"
# find installed plugins + version=`echo "$version" | sed 's:.*/::'` plugins=(`find ${PLUGIN_DIR} -maxdepth 1 \ -name "${PLUGIN_PREFIX}*.so.${version}" | \ xargs -r dpkg -S 2>&1 | \
Tom
On Sun, 2006-04-23 at 21:13 +0200, Thomas Günther wrote:
Mikko Salo wrote:
/etc/init.d/vdr start Starting Linux Video Disk Recorder: vdr Searching for plugins (VDR 1.3.48/1.3.47):find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name libvdr-*.so.1.3.48/1.3.47' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ libvdr-*.so.1.3.48/1.3.47'. sed: -e expression #1, char 47: unknown option to `s'
This problem is debian specific and will be fixed in the 1.3.48 release.
Use this patch:
--- vdr/vdr/trunk/debian/plugin-loader.sh 2006-04-23 14:58:18 UTC (rev 2475) +++ vdr/vdr/trunk/debian/plugin-loader.sh 2006-04-23 16:12:44 UTC (rev 2476) @@ -32,6 +32,7 @@ echo -ne "\nSearching for plugins (VDR $version):"
# find installed plugins
- version=`echo "$version" | sed 's:.*/::'` plugins=(`find ${PLUGIN_DIR} -maxdepth 1 \ -name "${PLUGIN_PREFIX}*.so.${version}" | \ xargs -r dpkg -S 2>&1 | \
Thank you!
Working fine again, sorry for the trouble.
-Mikko
Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at ...
- Simplified the 'grep|awk|sed' command to retrieve the VDR/APIVERSION to a single 'sed' call.
(1) My sed does not accept lines like this: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h | sed: -e expression #1, char 47: Extra characters after command
This works: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/p; }' config.h | 1.3.47
(2) The newplugin script is broken: - references VDRVERSION, not APIVERSION - '' must be escaped - sed problem as above
Patches attached.
Oliver
Oliver Endriss wrote:
Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at ...
- Simplified the 'grep|awk|sed' command to retrieve the VDR/APIVERSION to a single 'sed' call.
(1) My sed does not accept lines like this: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h | sed: -e expression #1, char 47: Extra characters after command
This works: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/p; }' config.h | 1.3.47
(2) The newplugin script is broken:
- references VDRVERSION, not APIVERSION
- '' must be escaped
- sed problem as above
Just to make sure I don't make any stupid last minute error here's the complete change that resulted from this. Maybe somebody finds the time to look over this...
Klaus
Klaus Schmidinger wrote:
Just to make sure I don't make any stupid last minute error here's the complete change that resulted from this. Maybe somebody finds the time to look over this...
I gave everything a test run, seems to work. GNU-sed 4.1.2. Out of curiosity, I've tried solaris 5.6 sed of 1997 and AIX 5.2 sed, and they accepted it too.
Cheers,
Udo
Klaus Schmidinger wrote:
Oliver Endriss wrote:
Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at ...
- Simplified the 'grep|awk|sed' command to retrieve the
VDR/APIVERSION to a single 'sed' call.
(1) My sed does not accept lines like this: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h | sed: -e expression #1, char 47: Extra characters after command
This works: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/p; }' config.h | 1.3.47
(2) The newplugin script is broken:
- references VDRVERSION, not APIVERSION
- '' must be escaped
- sed problem as above
Just to make sure I don't make any stupid last minute error here's the complete change that resulted from this. Maybe somebody finds the time to look over this...
Klaus
Im trying to test this from the console and I seem to have a problem with the following command (using sed-4.1.4-7 from debian sid):
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$$/\1/; p }' config.h"
This returns nothing.
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h"
This returns:
1.3.48
Is that right? Removing one of the "$" seems to fix it..
BR.
Im trying to test this from the console and I seem to have a problem with the following command (using sed-4.1.4-7 from debian sid):
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$$/\1/; p }' config.h"
This returns nothing.
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h"
This returns:
1.3.48
Is that right? Removing one of the "$" seems to fix it..
Sorry, I meant to say this command returns nothing:
sed -ne '/define VDRVERSION/s/^.*"(.*)".*$$/\1/p' config.h
and this command works:
sed -ne '/define VDRVERSION/s/^.*"(.*)".*$/\1/p' config.h
BR.
C.Y.M wrote:
Klaus Schmidinger wrote:
Oliver Endriss wrote:
Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at ...
- Simplified the 'grep|awk|sed' command to retrieve the
VDR/APIVERSION to a single 'sed' call.
(1) My sed does not accept lines like this: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h | sed: -e expression #1, char 47: Extra characters after command
This works: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/p; }' config.h | 1.3.47
(2) The newplugin script is broken:
- references VDRVERSION, not APIVERSION
- '' must be escaped
- sed problem as above
Just to make sure I don't make any stupid last minute error here's the complete change that resulted from this. Maybe somebody finds the time to look over this...
Klaus
Im trying to test this from the console and I seem to have a problem with the following command (using sed-4.1.4-7 from debian sid):
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$$/\1/; p }' config.h"
This returns nothing.
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h"
This returns:
1.3.48
Is that right? Removing one of the "$" seems to fix it..
That's all right. The '$' needs to be doubled in the Makefile.
Klaus
On Tue, Apr 25, 2006 at 11:49:29PM -0700, C.Y.M wrote:
Klaus Schmidinger wrote:
Oliver Endriss wrote:
Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at ...
- Simplified the 'grep|awk|sed' command to retrieve the
VDR/APIVERSION to a single 'sed' call.
(1) My sed does not accept lines like this: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h | sed: -e expression #1, char 47: Extra characters after command
This works: | sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/p; }' config.h | 1.3.47
(2) The newplugin script is broken:
- references VDRVERSION, not APIVERSION
- '' must be escaped
- sed problem as above
Just to make sure I don't make any stupid last minute error here's the complete change that resulted from this. Maybe somebody finds the time to look over this...
Klaus
Im trying to test this from the console and I seem to have a problem with the following command (using sed-4.1.4-7 from debian sid):
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$$/\1/; p }' config.h"
This returns nothing.
"sed -ne '/define APIVERSION/ { s/^.*"(.*)".*$/\1/; p }' config.h"
This returns:
1.3.48
Is that right? Removing one of the "$" seems to fix it..
Hmm ... within Makefiles the first $ is readed by the make program and if there is no second $ you'll get the make variable $/ ...
Werner
Hi,
just a little hint. The regular expression in the VDR Makefile which detects if the APIVERSION is used in the plugins Makefile is not compatible with the grep version of linvdr 07 (grep version 2.4.2). Since i have updated grep to version 2.5.1 all works fine.
Greets Jörg Wendel
On Sonntag 23 April 2006 16:13, Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.48.tar.bz2A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.47-48.diffIf there are no more serious bugs, this will become the final version 1.4.0 next weekend :-)
The changes since version 1.3.47:
- Updated the GPL copies (thanks to Ville Skyttä).
- Fixed several spelling errors (thanks to Ville Skyttä).
- Updated the Polish OSD texts (thanks to Jaroslaw Swierczynski).
- Updated the Finnish OSD texts (thanks to Rolf Ahrenberg).
- Updated the French OSD texts (thanks to Pierre Briec).
- Updated the Estonian OSD texts (thanks to Arthur Konovalov).
- Updated the Romanian OSD texts (thanks to Lucian Muresan).
- Updated the Danish OSD texts (thanks to Mogens Elneff).
- Updated the Russian OSD texts (thanks to Oleg Roitburd).
- Updated the Slovenian OSD texts (thanks to Matjaz Thaler).
- Fixed wrong credits for the patch that was used to implement
cPlugin::Active(). - Simplified the 'grep|awk|sed' command to retrieve the VDR/APIVERSION to a single 'sed' call.
- Updated the Swedish OSD texts (thanks to Tomas Prybil).
- Modified the German OSD texts to be "less technical" (thanks to Andreas
Brachold). - Extended the version number reported with the '-V' option to also show the current APIVERSION (suggested by Thomas Günther).
- Fixed handling empty titles in cEvent::FixEpgBugs() (reported by Rolf
Ahrenberg). - Fixed some missing '-' in the German OSD texts (thanks to Walter Koch). - Added an error message about plugins that don't honor APIVERSION in their Makefile (based on a suggestion by Udo Richter).
- Fixed a format string in recording.c to avoid a compiler warning on 64bit
systems (thanks to Christian Wieninger for reporting, and Werner Schweer for pointing out that the 'z' modifier should be used here).
- Ignoring k_Repeat when deciding whether the same key has been pressed in
string input fields (based on a patch from Marko Mäkelä).
Have fun!
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Jörg Wendel wrote:
Hi,
just a little hint. The regular expression in the VDR Makefile which detects if the APIVERSION is used in the plugins Makefile is not compatible with the grep version of linvdr 07 (grep version 2.4.2). Since i have updated grep to version 2.5.1 all works fine.
A solution for this has already been posted earlier on this list. Please take a look at the 'vdr-1.3.48-apiversion.diff' I've posted, or the original posting by Oliver Endriss.
Klaus
On Montag 24 April 2006 22:36, Klaus Schmidinger wrote:
Jörg Wendel wrote:
Hi,
just a little hint. The regular expression in the VDR Makefile which detects if the APIVERSION is used in the plugins Makefile is not compatible with the grep version of linvdr 07 (grep version 2.4.2). Since i have updated grep to version 2.5.1 all works fine.
A solution for this has already been posted earlier on this list. Please take a look at the 'vdr-1.3.48-apiversion.diff' I've posted, or the original posting by Oliver Endriss.
I have seen this patch, but the problem with the old version of grep is the following line of the VDR makefile:
if ! grep -q "$$(LIBDIR)/.*$$(APIVERSION)" "$(PLUGINDIR)/src/$$i/Makefile" ; then\
and in the 'vdr-1.3.48-apiversion.diff' i can't see a change of this line.
Jörg
Hi again,
ok, sorry it is to late ;) I have applied the patch and tested again with the old version of grep and it works fine! The line with the expression isn't changed by the patch, but it works now. May be i can find the trick tomorrow ;)
Jörg
On Montag 24 April 2006 23:50, Jörg Wendel wrote:
On Montag 24 April 2006 22:36, Klaus Schmidinger wrote:
Jörg Wendel wrote:
Hi,
just a little hint. The regular expression in the VDR Makefile which detects if the APIVERSION is used in the plugins Makefile is not compatible with the grep version of linvdr 07 (grep version 2.4.2). Since i have updated grep to version 2.5.1 all works fine.
A solution for this has already been posted earlier on this list. Please take a look at the 'vdr-1.3.48-apiversion.diff' I've posted, or the original posting by Oliver Endriss.
I have seen this patch, but the problem with the old version of grep is the following line of the VDR makefile:
if ! grep -q "$$(LIBDIR)/.*$$(APIVERSION)" "$(PLUGINDIR)/src/$$i/Makefile" ; then\
and in the 'vdr-1.3.48-apiversion.diff' i can't see a change of this line.
Jörg
Am 23.04.2006 um 16:13 schrieb Klaus Schmidinger:
- Fixed a format string in recording.c to avoid a compiler warning
on 64bit systems
I get the following warning now with gcc 2.95
recording.c: In method `cIndexFile::cIndexFile(const char *, bool)': recording.c:1200: warning: unknown conversion type character `z' in format recording.c:1200: warning: format argument is not a pointer (arg 3)
Could this lead to problems for me?
Ciao, Dominique
On Tuesday 25 April 2006 13:58, Dominique Simon wrote:
I get the following warning now with gcc 2.95
am I right in believing that most 2.95 users come from linvr 0.7?
I also believe linvdr 0.8 is coming soon.
Maybe it is time to finally stop supporting compilation with 2.95?
I am sure somebody will provided necessary patches for 2.95
Dominique Simon wrote:
Am 23.04.2006 um 16:13 schrieb Klaus Schmidinger:
- Fixed a format string in recording.c to avoid a compiler warning on
64bit systems
I get the following warning now with gcc 2.95
recording.c: In method `cIndexFile::cIndexFile(const char *, bool)': recording.c:1200: warning: unknown conversion type character `z' in format recording.c:1200: warning: format argument is not a pointer (arg 3)
This format conversion specifier has been documented in the "GNU C Library Reference Manual" since at least 2001-07-06, so it's been there for quite a while - I guess it should be ok to use it ;-)
Could this lead to problems for me?
If you still want to use that old compiler, just remove the 'z' and you should be fine.
Klaus
Am 25.04.2006 um 23:31 schrieb Klaus Schmidinger:
If you still want to use that old compiler, just remove the 'z' and you should be fine.
I am using LinVDR 0.7, so i "have to" use gcc 2.95. Anyway, with the Release of VDR 1.4 there will hopefully be LinVDR 0.8 based on Debian Sarge very soon :)
Ciao, Dominique
On Sunday 23 April 2006 16:13, Klaus Schmidinger wrote:
VDR developer version 1.3.48 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.48.tar.bz2A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.47-48.diffIf there are no more serious bugs, this will become the final version 1.4.0 next weekend :-)
For those who want to test the release candidate on SUSE Linux I've updated the vdr13 packages in
ftp://ftp.suse.com/pub/suse/i386/supplementary/misc resp. ftp://ftp.suse.com/pub/suse/x86_64/supplementary/misc
to 1.3.48. They can savely be installed in parallel to the vdr 1.2.6 packages that ship with SUSE Linux.
cu Ludwig
-
C.Y.M -
Dominique Simon -
Dr. Werner Fink -
Jörg Wendel -
Klaus Schmidinger -
Ludwig Nussel -
Mikko Salo -
Oliver Endriss -
s.huelswitt＠gmx.de -
Thomas Günther -
Udo Richter -
Wolfgang Rohdewald