Hello community,

here is the log from the commit of package mcelog for openSUSE:Factory
checked in at Thu Jun 16 10:53:22 CEST 2011.



--------
--- mcelog/mcelog.changes       2010-10-25 15:51:12.000000000 +0200
+++ /mounts/work_src_done/STABLE/mcelog/mcelog.changes  2011-06-07 
11:53:11.000000000 +0200
@@ -1,0 +2,5 @@
+Tue Jun  7 09:51:57 UTC 2011 - [email protected]
+
+- Remove test email address from config
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


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

Other differences:
------------------
++++++ mcelog.spec ++++++
--- /var/tmp/diff_new_pack.c6FMCO/_old  2011-06-16 10:51:53.000000000 +0200
+++ /var/tmp/diff_new_pack.c6FMCO/_new  2011-06-16 10:51:53.000000000 +0200
@@ -1,7 +1,7 @@
 #
-# spec file for package mcelog (Version 1.0pre3.6363f5b719e9)
+# spec file for package mcelog
 #
-# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2011 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
@@ -22,7 +22,7 @@
 License:        GPLv2+
 Summary:        Log Machine Check Events
 Version:        1.0pre3.6363f5b719e9
-Release:        1
+Release:        6
 AutoReqProv:    on
 ExclusiveArch:  x86_64
 BuildRequires:  libesmtp-devel

++++++ mcelog.sysconfig ++++++
--- /var/tmp/diff_new_pack.c6FMCO/_old  2011-06-16 10:51:53.000000000 +0200
+++ /var/tmp/diff_new_pack.c6FMCO/_new  2011-06-16 10:51:53.000000000 +0200
@@ -7,4 +7,4 @@
 # ECC errors), processor or other HW are sent with a detailed description
 # to this address. Also read README.email_setup for further details.
 #
-MCELOG_ADMIN_EMAIL="[email protected]"
+MCELOG_ADMIN_EMAIL=""


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



Remember to have fun...

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

Reply via email to