Hello community,

here is the log from the commit of package mpich for openSUSE:Factory checked 
in at 2011-11-24 12:36:19
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/mpich (Old)
 and      /work/SRC/openSUSE:Factory/.mpich.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "mpich", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/mpich/mpich.changes      2011-09-23 
02:13:30.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.mpich.new/mpich.changes 2011-11-24 
11:36:37.000000000 +0100
@@ -1,0 +2,5 @@
+Wed Nov 23 09:28:55 UTC 2011 - [email protected]
+
+- add libtool as buildrequire to avoid implicit dependency
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ mpich.spec ++++++
--- /var/tmp/diff_new_pack.rvMkYk/_old  2011-11-24 11:36:46.000000000 +0100
+++ /var/tmp/diff_new_pack.rvMkYk/_new  2011-11-24 11:36:46.000000000 +0100
@@ -1,7 +1,7 @@
 #
-# spec file for package mpich (Version 1.2.7p1)
+# spec file for package mpich
 #
-# 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
@@ -19,7 +19,7 @@
 
 
 Name:           mpich
-BuildRequires:  gcc-c++ gcc-fortran gdb
+BuildRequires:  gcc-c++ gcc-fortran gdb libtool
 BuildRequires:  fdupes
 License:        PERMISSIVE-OSI-COMPLIANT
 Group:          Development/Libraries/Parallel
@@ -49,7 +49,6 @@
 Patch15:        mpich-fix_headers.diff
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 Requires:       openssh, Modules
-AutoReqProv:    on
 %define _mpich_root       /opt/mpich
 %define gnu    1
 %define absoft 0

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

Reply via email to