Hello community,

here is the log from the commit of package glibc for openSUSE:Factory
checked in at Sat Sep 3 23:06:05 CEST 2011.



--------
--- glibc/glibc.changes 2011-09-01 22:59:06.000000000 +0200
+++ /mounts/work_src_done/STABLE/glibc/glibc.changes    2011-09-03 
21:43:26.000000000 +0200
@@ -1,0 +2,5 @@
+Sat Sep  3 19:39:03 UTC 2011 - [email protected]
+
+- Revert last change, it caused some breakage.
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


Old:
----
  glibc-2.15-vsyscall.patch
  minmem

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

Other differences:
------------------
++++++ glibc.spec ++++++
--- /var/tmp/diff_new_pack.GplNir/_old  2011-09-03 23:04:56.000000000 +0200
+++ /var/tmp/diff_new_pack.GplNir/_new  2011-09-03 23:04:56.000000000 +0200
@@ -79,7 +79,7 @@
 %endif
 AutoReqProv:    on
 Version:        2.14
-Release:        9
+Release:        11
 Url:            http://www.gnu.org/software/libc/libc.html
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 Source:         glibc-%{version}-4eddf93f5cc2.tar.bz2
@@ -200,8 +200,6 @@
 Patch68:        glibc-fix-lookup-crash.patch
 # PATCH-FIX-UPSTREAM Fix fopen("non-existing-file", "re") errno bnc#713146 
[email protected]
 Patch69:        fopen-close-exec.patch
-# PATCH-FIX-UPSTREAM Use ifuncs for time and gettimeofday on x86-64 - 
[email protected]
-Patch70:        glibc-2.15-vsyscall.patch
 # PATCH-FEATURE-OPENSUSE -- add sha support to crypt_blowfish [email protected]
 Patch80:        crypt_blowfish-1.2-sha.diff
 # PATCH-FEATURE-OPENSUSE -- use separate symbol version for Owl extensions - 
[email protected]
@@ -437,7 +435,6 @@
 %patch67 -p1
 %patch68 -p1
 %patch69 -p1
-%patch70 -p1
 
 #
 # Inconsistency detected by ld.so: dl-close.c: 719: _dl_close: Assertion 
`map->l_init_called' failed!



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



Remember to have fun...

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

Reply via email to