[ANNOUNCE] ExtP-NG für VDR-1.7.13/14/15/16

can't find file to patch at input line 5582
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruN vdr-1.7.15/po/de_DE.po vdr-1.7.15.patched/po/de_DE.po
|--- vdr-1.7.15/po/de_DE.po     2010-06-06 14:03:58.000000000 +0200
|+++ vdr-1.7.15.patched/po/de_DE.po     2010-06-11 18:17:56.921659743 +0200
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
6 out of 6 hunks ignored

dpkg-buildpackage: setze CFLAGS auf Standardwert: -g -O2
dpkg-buildpackage: setze CPPFLAGS auf Standardwert:
dpkg-buildpackage: setze LDFLAGS auf Standardwert:
dpkg-buildpackage: setze FFLAGS auf Standardwert: -g -O2
dpkg-buildpackage: setze CXXFLAGS auf Standardwert: -g -O2
dpkg-buildpackage: Quellpaket vdr
dpkg-buildpackage: Quellversion 1.7.15-1devel1
dpkg-buildpackage: Quellen geändert durch Thomas Günther <tom@toms-cafe.de>
dpkg-buildpackage: Host-Architektur i386
 make-special-vdr clean
/usr/bin/make-special-vdr clean SPECIAL_VDR_SUFFIX='devel' NO_CHECKBUILDDEPS=''
 make-special-vdr build
/usr/bin/make-special-vdr build SPECIAL_VDR_SUFFIX='devel' NO_CHECKBUILDDEPS=''
prepare: save all in subdirectory .save
prepare_common: substitute vdr -> vdrdevel
prepare_vdr: prevent conflict to standard vdr
patching file debian/vdrdevel.links
patching file debian/vdrdevel.postinst
prepare_vdr: add debconf question which vdr variation should start automatically
patching file debian/rules
Hunk #1 succeeded at 173 (offset 43 lines).
patching file debian/vdrdevel.config
patching file debian/vdrdevel.postinst
patching file debian/vdrdevel.prerm
patching file debian/vdrdevel.templates
patching file debian/commands.switch-vdr.conf
patching file debian/commands.switch-vdrdevel.conf
patching file debian/vdrdevel.install
prepare_vdr: set links to use logos and addons from standard packages
patching file debian/commands-loader.sh
patching file debian/vdrdevel.links
prepare_vdr: add hint to the plugin debianizer script
patching file debian/debianize-vdrdevelplugin
prepare_vdr: adapt patchcheck script
patching file debian/patchcheck.py
python debian/patchcheck.py -c -p multipatch
cmp -s debian/patches/00list.multipatch debian/patches/00list || \
          cp -b --suffix=.save debian/patches/00list.multipatch debian/patches/00list
test -d debian/patched || install -d debian/patched
dpatch  apply-all
applying patch 04_newplugin to ./ ... ok.
applying patch 06_default_svdrdevelp_port_0 to ./ ... ok.
applying patch 11_sortrecordings to ./ ... ok.
applying patch 12_osdbase-maxitems to ./ ... ok.
applying patch 16_channels.conf.terr-fix to ./ ... ok.
applying patch 81_Make_config to ./ ... ok.
applying patch 82_valgrind to ./ ... ok.
applying patch 99_ncursesw-include to ./ ... ok.
applying patch 99_vdrdevel-workaround-broken-sys-capability to ./ ... ok.
applying patch opt-20_liemikuutio to ./ ... failed.
make: *** [patch-stamp] Fehler 1
dpkg-buildpackage: Fehlschlag: make-special-vdr build gab Fehler-Exitstatus 2

COMMANDS
       The file commands.conf contains the definitions of commands that can be executed from the vdr main menu's "Commands" option.  Each line contains one command  definition
       in the following format:


       title : command


       where  title  is  the string that will be displayed in the "Commands" menu, and command is the actual command string that will be executed when this option is selected.
       The delimiting ':' may be surrounded by any number of white space characters. If title ends with the character '?', there will be a confirmation prompt before  actually
       executing the command. This can be used for commands that might have serious results (like deleting files etc) to make sure they are not executed inadvertently.


       Everything following (and including) a '#' character is considered to be comment.


       You can have nested layers of command menus by surrounding a sequence of commands with '{'...'}' and giving it a title, as in


       My Commands {
         First list {
           Do something: some command
           Do something else: another command
           }
         Second list {
           Even more: yet another command
           So much more: and yet another one
           }
         }


       Command lists can be nested to any depth.


       By  default the menu entries in the "Commands" menu will be numbered '1'...'9' to make them selectable by pressing the corresponding number key. If you want to use your
       own numbering scheme (maybe to skip certain numbers), just precede the titles with the numbers of your choice. vdr will suppress its automatic numbering  if  the  first
       entry in commands.conf starts with a digit in the range '1'...'9', followed by a blank.


       In  order  to avoid error messages to the console, every command should have stderr redirected to stdout. Everything the command prints to stdout will be displayed in a
       result window, with title as its title.


       Examples:


       Check for new mail?: /usr/local/bin/checkmail 2>&1
       CPU status: /usr/local/bin/cpustatus 2>&1
       Disk space: df -h | grep '/video' | awk '{ print 100 - $5 "% free"; }'
       Calendar: date;echo;cal


       Note that the commands 'checkmail' and 'cpustatus' are only examples!  Don't send emails to the author asking where to find these ;-)
       The '?' at the end of the "Check for new mail?" entry will prompt the user whether this command shall really be executed.