Hello community,

here is the log from the commit of package vdr for openSUSE:Factory checked in 
at 2015-01-07 09:39:11
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/vdr (Old)
 and      /work/SRC/openSUSE:Factory/.vdr.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "vdr"

Changes:
--------
--- /work/SRC/openSUSE:Factory/vdr/vdr.changes  2014-08-03 15:36:58.000000000 
+0200
+++ /work/SRC/openSUSE:Factory/.vdr.new/vdr.changes     2015-01-07 
09:39:16.000000000 +0100
@@ -1,0 +2,6 @@
+Tue Sep  3 14:32:23 UTC 2014 - [email protected]
+
+- fixed wrong writing of SUSE 
+- added template for SuSEfirewall2
+
+-------------------------------------------------------------------

Old:
----
  README.SuSE-vdr.html
  README.SuSE-vdr.txt

New:
----
  README.SUSE-vdr.html
  README.SUSE-vdr.txt
  vdr.firewall

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ vdr.spec ++++++
--- /var/tmp/diff_new_pack.UscO5k/_old  2015-01-07 09:39:18.000000000 +0100
+++ /var/tmp/diff_new_pack.UscO5k/_new  2015-01-07 09:39:18.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package vdr
 #
-# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2015 SUSE LINUX Products GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -50,10 +50,11 @@
 Source6:        openvt.diff
 Source7:        vdr-genindex.c
 Source10:       vdr.macros
+Source11:       vdr.firewall
 Source42:       msgmerge
 # generated from wiki page
-Source90:       README.SuSE-vdr.txt
-Source91:       README.SuSE-vdr.html
+Source90:       README.SUSE-vdr.txt
+Source91:       README.SUSE-vdr.html
 Source92:       greenish.css
 Source93:       vdr-fetchwikipage
 Source94:       vdr-renderwikipage
@@ -164,8 +165,8 @@
 #
 # docu
 #
-cp %{SOURCE90} README.SuSE
-cp %{SOURCE91} README.SuSE.html
+cp %{SOURCE90} README.SUSE
+cp %{SOURCE91} README.SUSE.html
 cp %{SOURCE92} .
 #
 install -d -m 755 %{buildroot}%{_datadir}/susehelp/meta/Manuals/Productivity
@@ -197,13 +198,16 @@
 #
 # msgmerge helper for plugins
 install -m 0755 msgmerge %{buildroot}%{_datadir}/vdr/msgmerge
+#
+# firewall config
+install -m 644 -D %{SOURCE11} 
%{buildroot}/%{_sysconfdir}/sysconfig/SuSEfirewall2.d/services/%{name}
 
 %pre
 /usr/sbin/useradd -r -d %{vdr_videodir} -s /bin/false -c "Video Disk Recorder" 
-g video vdr 2> /dev/null || :
 
 %files
 %defattr(-,root,root)
-%doc README.SuSE README.SuSE.html greenish.css
+%doc README.SUSE README.SUSE.html greenish.css
 %doc %{_datadir}/susehelp
 %doc COPYING README* UPDATE* CONTRIBUTORS HISTORY
 %doc MANUAL channels.conf.* PLUGINS.html plugins
@@ -220,6 +224,7 @@
 %{_bindir}/*
 %{vdr_libdir}/*
 %{_mandir}/man?/*
+%config(noreplace) %attr(0644,root,root) 
%{_sysconfdir}/sysconfig/SuSEfirewall2.d/services/%{name}
 
 %files devel
 %defattr(-,root,root)
@@ -231,4 +236,5 @@
 %{_datadir}/vdr/msgmerge
 
 %files lang -f %{name}.lang
+
 %changelog

++++++ README.SUSE-vdr.html ++++++
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" href="./greenish.css" type="text/css" />
<title>VDR</title>
</head>
<body>
<h1>VDR - Video Disk Recorder</h1>
<p><a href='http://www.tvdr.de/'>VDR</a> (Video Disk Recorder) is a video 
playing and recording
application for DVB (Digital Video Brodcast) cards.</p>
<a name='File%20system%20layout'></a><h2>File system layout</h2>

<p>The vdr package is adapted to fit seamlessy into the openSUSE
filesystem hierarchy:</p>
<ul>
<li>/etc/vdr contains configuration files that you might want to modify to 
suite your needs (e.g. channels.conf). See man 5 vdr for the syntax of those 
files.</li>
<li>/var/spool/video is the place where recordings are stored. If you are low 
on space you should consider putting this on a separate partition. Recordings 
can take up several Gigabytes.</li>
<li>/usr/lib/vdr contains shared libraries for plugins. If you compile you own 
plugins you need to put them there. </li>
<li>/usr/include/vdr contains header files necessary to compile plugins.</li>
</ul>
<a name='Start%20scripts'></a><h2>Start scripts</h2>

<p>You almost never want to run the vdr binary itself. Use /etc/init.d/vdr to
start vdr as daemon on console 9 or runvdr to start it in the current terminal.
You can configure several parameters for these scripts in 
/etc/sysconfig/vdr.</p>
<p>Note: vdr as packaged on openSUSE does not run as root but under a special 
vdr user
account to reduce the risk of damage to the system in case of (security-)bugs.
Do not try to re-use the vdr start scripts for a self-compiled version without
applying the necessary patches!</p>
<a name='Setting%20up%20the%20channel%20list'></a><h2>Setting up the channel 
list</h2>

<p>vdr as packaged on openSUSE contains a minimal /etc/vdr/channels.conf for
Astra-19.2E (DVB-S). You can create you own using dvbscan. For example if you
live in Nuernberg, Germany and want to create a channels.conf for DVB-T you
would run</p>
<pre> scan -o vdr /usr/share/dvb/scan/dvb-t/de-Nuernberg &gt; 
/etc/vdr/channels.conf
</pre>
<a name='Using%20vdr%20with%20a%20TV%20set%20attached'></a><h2>Using vdr with a 
TV set attached</h2>

<p>If you have a full-featured card and intend to run vdr on a dedicated machine
just like a regular VCR, you probably want also use a remote control unit to
control vdr. Unfortunately, the remote control unit shipped with the popular
Hauppauge DVB cards is not supported out of the box. You need to install the
Remote Control-Plugin contained in the vdr-plugins package. For home-brew
hardware or if you also have an analogue card with remote you might want to use
lirc. Use the yast runlevel editor or chkconfig to have dvb, lirc and vdr
started during boot.</p>
<a name='Using%20vdr%20on%20a%20desktop%20machine'></a><h2>Using vdr on a 
desktop machine</h2>

<p>With a full-featured card you can use xawtv for watching TV on your desktop.
You should append /usr/share/doc/packages/xawtv/vdr.config to your ~/.xawtv
file to control vdr from within xawtv.</p>
<a name='Using%20vdr%20on%20budget%20cards'></a><h2>Using vdr on budget 
cards</h2>

<p>Budget cards do not have an mpeg decoder so you can't connect a TV set to 
them
nor use v4l applications like xawtv to watch TV. Instead you may use
the xine-plugin for vdr (package vdr-plugin-xine). To tell vdr to use
this plugin set the following values in /etc/sysconfig/vdr:</p>
<pre> VDR_PLUGINS=&quot;xine&quot;
 VDR_PLUGIN_ARGS_xine=&quot;-r&quot;
</pre>
<p>When vdr is running press the &quot;VDR&quot; button in xine (package 
xine-ui) to get the
live TV picture. Instead of xine-ui you can also use any xine based
media player like kaffeine by opening the url
vdr://var/lib/vdr-xine/stream#demux:mpeg_pes</p>
<p>You may need to install additional codec packages to be able to view
mpeg streams like the one from the dvb card.</p>
<a name='Compiling%20your%20own%20plugins'></a><h2>Compiling your own 
plugins</h2>

<p>See also <a 
href='http://en.opensuse.org/openSUSE%3APackaging_vdr'>openSUSE:Packaging_vdr</a>
 for instructions how to properly package vdr plugins to fit into package 
management.</p>
<p>Normally, vdr plugins expect to be compiled inside the vdr source directory.
This is of course not possible with a prebuilt package. Fortunately, most
plugins can still be easily compiled using the following command:</p>
<pre> make VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr 
LOCALEDIR=/usr/share/vdr/locale all
</pre>
<p>If you add the plugin name to VDR_PLUGINS in /etc/sysconfig/vdr, it will be
loaded automatically when vdr starts. Please read the associated comment in
that file for details. Some plugins require additional treatment because vdr is
not running as root. The osd-teletext plugin for example wants to put files
into /vtx. You have to create that directory yourself and change it's owner to
vdr. Other plugins like the dvd plugin open device files, you need to adjust
permissions for these as well.</p>
<a name='Updated%20Packages'></a><h2>Updated Packages</h2>

<p>Packages for the most recent stable vdr version are available via the
<a href='http://download.opensuse.org/repositories/vdr/'>openSUSE build 
service</a></p>
</html></body>
++++++ README.SUSE-vdr.txt ++++++
VDR - Video Disk Recorder

VDR (Video Disk Recorder) is a video playing and recording application for DVB
(Digital Video Brodcast) cards.

File system layout

The vdr package is adapted to fit seamlessy into the openSUSE filesystem
hierarchy:

  • /etc/vdr contains configuration files that you might want to modify to
    suite your needs (e.g. channels.conf). See man 5 vdr for the syntax of
    those files.
  • /var/spool/video is the place where recordings are stored. If you are low
    on space you should consider putting this on a separate partition.
    Recordings can take up several Gigabytes.
  • /usr/{lib,lib64}/vdr contains shared libraries for plugins. If you compile
    you own plugins you need to put them there.
  • /usr/include/vdr contains header files necessary to compile plugins.

Start scripts

You almost never want to run the vdr binary itself. Use /etc/init.d/vdr to
start vdr as daemon on console 9 or runvdr to start it in the current terminal.
You can configure several parameters for these scripts in /etc/sysconfig/vdr.

Note: vdr as packaged on openSUSE does not run as root but under a special vdr
user account to reduce the risk of damage to the system in case of (security-)
bugs. Do not try to re-use the vdr start scripts for a self-compiled version
without applying the necessary patches!

Setting up the channel list

vdr as packaged on openSUSE contains a minimal /etc/vdr/channels.conf for
Astra-19.2E (DVB-S). You can create you own using dvbscan. For example if you
live in Nuernberg, Germany and want to create a channels.conf for DVB-T you
would run

 scan -o vdr /usr/share/dvb/scan/dvb-t/de-Nuernberg > /etc/vdr/channels.conf

Using vdr with a TV set attached

If you have a full-featured card and intend to run vdr on a dedicated machine
just like a regular VCR, you probably want also use a remote control unit to
control vdr. Unfortunately, the remote control unit shipped with the popular
Hauppauge DVB cards is not supported out of the box. You need to install the
Remote Control-Plugin contained in the vdr-plugins package. For home-brew
hardware or if you also have an analogue card with remote you might want to use
lirc. Use the yast runlevel editor or chkconfig to have dvb, lirc and vdr
started during boot.

Using vdr on a desktop machine

With a full-featured card you can use xawtv for watching TV on your desktop.
You should append /usr/share/doc/packages/xawtv/vdr.config to your ~/.xawtv
file to control vdr from within xawtv.

Using vdr on budget cards

Budget cards do not have an mpeg decoder so you can't connect a TV set to them
nor use v4l applications like xawtv to watch TV. Instead you may use the
xine-plugin for vdr (package vdr-plugin-xine). To tell vdr to use this plugin
set the following values in /etc/sysconfig/vdr:

 VDR_PLUGINS="xine"
 VDR_PLUGIN_ARGS_xine="-r"

When vdr is running press the "VDR" button in xine (package xine-ui) to get the
live TV picture. Instead of xine-ui you can also use any xine based media
player like kaffeine by opening the url vdr://var/lib/vdr-xine/stream#
demux:mpeg_pes

You may need to install additional codec packages to be able to view mpeg
streams like the one from the dvb card.

Compiling your own plugins

See also openSUSE:Packaging_vdr for instructions how to properly package vdr
plugins to fit into package management.

Normally, vdr plugins expect to be compiled inside the vdr source directory.
This is of course not possible with a prebuilt package. Fortunately, most
plugins can still be easily compiled using the following command:

 make VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr 
LOCALEDIR=/usr/share/vdr/locale all

If you add the plugin name to VDR_PLUGINS in /etc/sysconfig/vdr, it will be
loaded automatically when vdr starts. Please read the associated comment in
that file for details. Some plugins require additional treatment because vdr is
not running as root. The osd-teletext plugin for example wants to put files
into /vtx. You have to create that directory yourself and change it's owner to
vdr. Other plugins like the dvd plugin open device files, you need to adjust
permissions for these as well.

Updated Packages

Packages for the most recent stable vdr version are available via the openSUSE
build service

++++++ vdr-doc.desktop ++++++
--- /var/tmp/diff_new_pack.UscO5k/_old  2015-01-07 09:39:18.000000000 +0100
+++ /var/tmp/diff_new_pack.UscO5k/_new  2015-01-07 09:39:18.000000000 +0100
@@ -1,4 +1,4 @@
 [Desktop Entry]
 Name=vdr
 Comment=Video Disk Recorder
-DocPath=/usr/share/doc/packages/vdr/README.SuSE.html
+DocPath=/usr/share/doc/packages/vdr/README.SUSE.html

++++++ vdr.firewall ++++++
# Do not edit this file as it's just a template and will be
# overwritten on package updates! Copy to a new file instead.
# Fill in the required variables and delete the unused ones.
# If in doubt ask [email protected]
#
# Only the variables TCP, UDP, RPC, IP, BROADCAST, RELATED and
# MODULES are allowed. More may be supported in the future.
#
# For a more detailed description of the individual variables see
# the comments for FW_SERVICES_*_EXT in /etc/sysconfig/SuSEfirewall2
#

## Name: VDR
## Description: Opens ports for vdr in order to accept SVDRP commands.

# space separated list of allowed TCP ports
TCP="svdrp"

# space separated list of allowed UDP ports
UDP=""

# space separated list of allowed RPC services
RPC=""

# space separated list of allowed IP protocols
IP=""

# space separated list of allowed UDP ports that accept broadcasts
BROADCAST=""

### variables below are only needed in very special cases

# space separated list of net,protocol[,sport[,dport]]
# see FW_SERVICES_ACCEPT_RELATED_EXT
# net 0/0 means IPv4 and IPv6. If this sevice should only work for
# IPv4 use 0.0.0.0/0
RELATED=""

# additional kernel modules needed for this service
# see FW_LOAD_MODULES
MODULES=""
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to