<?xml version="1.0" encoding="UTF-8"?>
<!--PATCHINFO id="60a7834f2879272b930fd2a0a3ef0377"!-->
<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="sdkp1-libzypp-4907"
    timestamp="1199990140"
    engine="1.0">
  <yum:name>sdkp1-libzypp</yum:name>
  <summary lang="en">Recommended update for libzypp</summary>
  <summary lang="de">Recommended update for libzypp</summary>
  <description lang="en">The following bugs are fixed by the update:

188409 Auto install reports &quot;Array index is out of range&quot;
in stage 2 using FTP:

When there was &quot;..&quot; in the installation source url, &quot;rug
sub &lt;url&gt;&quot; was throwing this error. Modified rug to
specially handle &quot;..&quot; in the installation source.

203051 Online update of kernel should force reboot: Reboot
of the system is required after installation of kernel
patch. From the kernel patch this information was being put
into zmd.db and then retrieved by ZMD correctly, but this
information was not being passed onto rug/zen-updater
client properly. Added a new interface to ZMD to provide
access this information and modified rug and zen-updater to
use the new ZMD interface and reboot the system after
kernel patch update.

254496 log rotation file not included in binary RPM:
Although logrotate file was present with the ZMD package,
ZMD was not using it. ZMD's log4net logger was using its
own RollingFileAppender which in turn was not rotating the
logs properly. Modified ZMD to use simple FileAppender in
stead of RollingFileAppender and rotating of logs will now
be taken care by logrotate.

269514 Unable to update the iprint client (packages already
exist): Modified zen-installer not to follow best package
approach when rpm files are directly installed by clicking
on it or by some other application. In this case now
zen-installer will request the backend to install the exact
version of the rpm.

275170 installation of a package failed with dependencies:
This happening for some installation sources which can be
added as both YUM and ZYPP services. User can add both
services with two different aliases but same url. But the
backend uses the url as distinct catalog name in ZMD DB.
Since url is same for both YUM and ZYPP services, the
resolvables of the first service are overwritten by the
resolvables of second service. So the subsequent problem
happens.

As part of fix, added &quot;YUM@&quot; pattern to the beginning of
the url that is passed as catalog name to backend and this
distinguishing it from the ZYPP catalog name.

293073 rug up: List has changed: This error was originally
thrown by Mono when an element from a arraylist was deleted
inside the for loop body while looping on the array.
Modified rug to make a copy of the array. Loop on one array
and delete from the other array.

288422 - using rug to update to SP1 makes the wifi to
disapear and the smp kernel not installed (still using
default)

Automatic installation of hardware specific packages, like
kernel drivers, is based on 'hardware dependencies'
expressed by the respective package. This kind of
dependency information was not properly stored in the
ZENworks Daemon (zmd) database, resulting in missing
drivers after the SP1 upgrade.


This fix corrects the handling of 'hardware dependencies'
within the ZENworks software management stack.

295894 - rug in: ERROR: Cannot create channel sink to
connect to URL ... If a restart of ZMD is scheduled,
initiating a transaction via rug can lead to this problem.
The ZMD process now handles the situation gracefully.

270836 - &quot;yast sw_single&quot; dies with DiskUsageCounter.cc
errors

There is a bug in yast2-ncurses disk space calculation
which causes a floating point exception for partitions with
zero size (e.g. nfs shares, mounted cluster volumes). This
bugfix solves also this problem.

298731 - zypper do not support non interactive mode: The
zypper command line tool now offers options for running
fully in non-interactive mode.

301843 - building kiwi image with zypper as backand end
with error: libzypp and zypper are able now to work in a
chroot environment.

308235 - libzypp package requires gpg

238165 - Fix restoring of Sources if root prefix is used

325556 - Correctly handle file-descriptors, umask and call
of setgid

248300 - Do not log YCP clients arguments in (yast2-core)
</description>
  <description lang="de">The following bugs are fixed by the update:

188409 Auto install reports &quot;Array index is out of range&quot;
in stage 2 using FTP:

When there was &quot;..&quot; in the installation source url, &quot;rug
sub &lt;url&gt;&quot; was throwing this error. Modified rug to
specially handle &quot;..&quot; in the installation source.

203051 Online update of kernel should force reboot: Reboot
of the system is required after installation of kernel
patch. From the kernel patch this information was being put
into zmd.db and then retrieved by ZMD correctly, but this
information was not being passed onto rug/zen-updater
client properly. Added a new interface to ZMD to provide
access this information and modified rug and zen-updater to
use the new ZMD interface and reboot the system after
kernel patch update.

254496 log rotation file not included in binary RPM:
Although logrotate file was present with the ZMD package,
ZMD was not using it. ZMD's log4net logger was using its
own RollingFileAppender which in turn was not rotating the
logs properly. Modified ZMD to use simple FileAppender in
stead of RollingFileAppender and rotating of logs will now
be taken care by logrotate.

269514 Unable to update the iprint client (packages already
exist): Modified zen-installer not to follow best package
approach when rpm files are directly installed by clicking
on it or by some other application. In this case now
zen-installer will request the backend to install the exact
version of the rpm.

275170 installation of a package failed with dependencies:
This happening for some installation sources which can be
added as both YUM and ZYPP services. User can add both
services with two different aliases but same url. But the
backend uses the url as distinct catalog name in ZMD DB.
Since url is same for both YUM and ZYPP services, the
resolvables of the first service are overwritten by the
resolvables of second service. So the subsequent problem
happens.

As part of fix, added &quot;YUM@&quot; pattern to the beginning of
the url that is passed as catalog name to backend and this
distinguishing it from the ZYPP catalog name.

293073 rug up: List has changed: This error was originally
thrown by Mono when an element from a arraylist was deleted
inside the for loop body while looping on the array.
Modified rug to make a copy of the array. Loop on one array
and delete from the other array.

288422 - using rug to update to SP1 makes the wifi to
disapear and the smp kernel not installed (still using
default)

Automatic installation of hardware specific packages, like
kernel drivers, is based on 'hardware dependencies'
expressed by the respective package. This kind of
dependency information was not properly stored in the
ZENworks Daemon (zmd) database, resulting in missing
drivers after the SP1 upgrade.


This fix corrects the handling of 'hardware dependencies'
within the ZENworks software management stack.

295894 - rug in: ERROR: Cannot create channel sink to
connect to URL ... If a restart of ZMD is scheduled,
initiating a transaction via rug can lead to this problem.
The ZMD process now handles the situation gracefully.

270836 - &quot;yast sw_single&quot; dies with DiskUsageCounter.cc
errors

There is a bug in yast2-ncurses disk space calculation
which causes a floating point exception for partitions with
zero size (e.g. nfs shares, mounted cluster volumes). This
bugfix solves also this problem.

298731 - zypper do not support non interactive mode: The
zypper command line tool now offers options for running
fully in non-interactive mode.

301843 - building kiwi image with zypper as backand end
with error: libzypp and zypper are able now to work in a
chroot environment.

308235 - libzypp package requires gpg

238165 - Fix restoring of Sources if root prefix is used

325556 - Correctly handle file-descriptors, umask and call
of setgid

248300 - Do not log YCP clients arguments in (yast2-core)
</description>
  <yum:version ver="4907" rel="0"/>
  <rpm:requires>
    <rpm:entry kind="atom" name="libzypp-devel" epoch="0" ver="2.16.2" rel="0.2" flags="EQ"/>
    <rpm:entry kind="atom" name="yast2-core-devel" epoch="0" ver="2.13.41" rel="0.3" flags="EQ"/>
    <rpm:entry kind="atom" name="zmd-devel" epoch="0" ver="7.2.0.0" rel="0.24" flags="EQ"/>
  </rpm:requires>
  <category>recommended</category>
  <atoms>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>libzypp-devel</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.16.2" rel="0.2"/>
      <checksum type="sha" pkgid="YES">2883a3160fb00924a0d1bd4c0e568dea4ff105c9</checksum>
      <time file="1200330574" build="1199990140"/>
      <size package="4404470" installed="47831187" archive="48530020"/>
      <location xml:base="media://#1" href="suse/x86_64/libzypp-devel-2.16.2-0.2.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="libzypp-devel" epoch="0" ver="2.16.2" rel="0.2" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="libzypp-devel"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>yast2-core-devel</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="2.13.41" rel="0.3"/>
      <checksum type="sha" pkgid="YES">0dc08674548a96aca2d3a9a351b99602067156a5</checksum>
      <time file="1200330576" build="1199731422"/>
      <size package="2582267" installed="20000864" archive="20378508"/>
      <location xml:base="media://#1" href="suse/x86_64/yast2-core-devel-2.13.41-0.3.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="yast2-core-devel" epoch="0" ver="2.13.41" rel="0.3" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="yast2-core-devel"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>zmd-devel</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="7.2.0.0" rel="0.24"/>
      <checksum type="sha" pkgid="YES">e07c5bdf9c49bc4eb4dd437881f8f00b1497f259</checksum>
      <time file="1200330581" build="1200076997"/>
      <size package="37925" installed="3432" archive="4124"/>
      <location xml:base="media://#1" href="suse/x86_64/zmd-devel-7.2.0.0-0.24.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="zmd-devel" epoch="0" ver="7.2.0.0" rel="0.24" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="zmd-devel"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
  </atoms>
</patch>
