Hello community,

here is the log from the commit of package glibc for openSUSE:Factory
checked in at Wed Jun 29 14:06:03 CEST 2011.



--------
--- glibc/glibc.changes 2011-06-27 14:20:26.000000000 +0200
+++ /mounts/work_src_done/STABLE/glibc/glibc.changes    2011-06-28 
14:51:41.000000000 +0200
@@ -1,0 +2,6 @@
+Tue Jun 28 12:30:34 UTC 2011 - [email protected]
+
+- Only apply glibc-2.10.99-ia64-include.diff on SLE but not on
+  openSUSE.
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


Old:
----
  minmem

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

Other differences:
------------------
++++++ glibc.spec ++++++
--- /var/tmp/diff_new_pack.HYniDg/_old  2011-06-29 14:05:33.000000000 +0200
+++ /var/tmp/diff_new_pack.HYniDg/_new  2011-06-29 14:05:33.000000000 +0200
@@ -79,7 +79,7 @@
 Obsoletes:      glibc-32bit
 %endif
 Version:        2.13
-Release:        15
+Release:        17
 Url:            http://www.gnu.org/software/libc/libc.html
 Source:         glibc-%{version}-996cf2ef0727.tar.bz2
 Source2:        http://ftp.gnu.org/gnu/glibc/glibc-ports-2.13.tar.bz2
@@ -165,7 +165,7 @@
 Patch40:        libm-x86-64-exceptions.diff
 # PATCH-MISSING-TAG -- See 
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
 Patch41:        glibc-uio-cell.diff
-# PATCH-MISSING-TAG -- See 
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
+# PATCH-FIX-SLE -- Do not assume statfs64 exists for ia64's ia32 layer 
bnc#534828
 Patch42:        glibc-statfs64-ia64.diff
 # PATCH-MISSING-TAG -- See 
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
 Patch43:        missing-include-build-fix.diff
@@ -416,7 +416,10 @@
 %patch39
 %patch40
 %patch41 -p1
+%if 0%{?sles_version}
+# Only apply for x86 on SLES
 %patch42
+%endif
 %patch43 -p1
 %patch44 -p1
 %patch45


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



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to