<?xml version="1.0" encoding="UTF-8"?>
<!--PATCHINFO id="d4b5e6b2cb4bfe8b96734b6e113a9656"!-->
<patch
    xmlns="http://novell.com/package/metadata/suse/patch"
    xmlns:yum="http://linux.duke.edu/metadata/common"
    xmlns:rpm="http://linux.duke.edu/metadata/rpm"
    xmlns:suse="http://novell.com/package/metadata/suse/common"
    patchid="sdkp2-yast2-slp-server-5413"
    timestamp="1215523745"
    engine="1.0">
  <yum:name>sdkp2-yast2-slp-server</yum:name>
  <summary lang="en">Recommended update for yast2-slp-server</summary>
  <summary lang="de">Recommended update for yast2-slp-server</summary>
  <description lang="en">User sets up SLP  in YaST and it enters all parameters in
lower case in the /etc/slp.conf file.  This causes the slpd
to ignore those parameters and use the default values.

Example parameters:

net.slp.usescopes net.slp.isda net.slp.daaddresses

They should be:

net.slp.useScopes net.slp.isDA net.slp.DAAddresses

Use the default /etc/slp.conf file from the openslp package
to view the correct case for each and all of the parameters.

This is causing SLP configuration to keep default
settings.  So if the user wants to configure SLP to an
SLPDA, the OES2 server will not because the parameter is in
lower case and it is not recognized.  Like wise, they are
unable to use scope names other than DEFAULT and are not
able to setup the OES2 server as an SLPDA server.

We can workaround the issue by manually editing the
/etc/slp.conf file and changing the parameters to their
proper case and restarting the slp daemon.  The problem
with this is that the parameters get changed back after
running the SLP server plugin again, even if no changes are
made.
</description>
  <description lang="de">User sets up SLP  in YaST and it enters all parameters in
lower case in the /etc/slp.conf file.  This causes the slpd
to ignore those parameters and use the default values.

Example parameters:

net.slp.usescopes net.slp.isda net.slp.daaddresses

They should be:

net.slp.useScopes net.slp.isDA net.slp.DAAddresses

Use the default /etc/slp.conf file from the openslp package
to view the correct case for each and all of the parameters.

This is causing SLP configuration to keep default
settings.  So if the user wants to configure SLP to an
SLPDA, the OES2 server will not because the parameter is in
lower case and it is not recognized.  Like wise, they are
unable to use scope names other than DEFAULT and are not
able to setup the OES2 server as an SLPDA server.

We can workaround the issue by manually editing the
/etc/slp.conf file and changing the parameters to their
proper case and restarting the slp daemon.  The problem
with this is that the parameters get changed back after
running the SLP server plugin again, even if no changes are
made.
</description>
  <yum:version ver="5413" rel="0"/>
  <rpm:requires>
    <rpm:entry kind="atom" name="yast2-slp-server" epoch="0" ver="2.13.11" rel="0.4" flags="EQ"/>
  </rpm:requires>
  <category>recommended</category>
  <atoms>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>yast2-slp-server</name>
      <arch>noarch</arch>
      <version epoch="0" ver="2.13.11" rel="0.4"/>
      <checksum type="sha" pkgid="YES">0e798844f68e5f5acd689b9816a1d9261c24241c</checksum>
      <time file="1215732533" build="1215523745"/>
      <size package="34168" installed="151865" archive="156968"/>
      <location xml:base="media://#1" href="suse/noarch/yast2-slp-server-2.13.11-0.4.noarch.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="yast2-slp-server" epoch="0" ver="2.13.11" rel="0.4" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="yast2-slp-server"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
  </atoms>
</patch>
