Hello community, here is the log from the commit of package sblim-cmpi-base for openSUSE:Factory checked in at 2012-12-08 15:53:21 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/sblim-cmpi-base (Old) and /work/SRC/openSUSE:Factory/.sblim-cmpi-base.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "sblim-cmpi-base", Maintainer is "VDziewiecki@suse.com" Changes: -------- --- /work/SRC/openSUSE:Factory/sblim-cmpi-base/sblim-cmpi-base.changes 2012-02-08 17:20:40.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.sblim-cmpi-base.new/sblim-cmpi-base.changes 2012-12-08 15:53:23.000000000 +0100 @@ -1,0 +2,10 @@ +Fri Nov 30 08:10:29 UTC 2012 - kkaempf@suse.com + +- Update to 1.6.2 + Bugs Fixed: + - 3275169 bash error reported in provider bootstrap scripts + - 3306580 wrong OperatingSystem.Version prop value on RHEL6 + - 3424288 Underlinked libcmpiOSBase_ProcessorProvider.so + - 3582069 Linux_UnixProcess command injection vulnerability + +------------------------------------------------------------------- Old: ---- sblim-cmpi-base-1.6.1-methods-enable.patch sblim-cmpi-base-1.6.1-missing-fclose.patch sblim-cmpi-base-1.6.1.tar.bz2 New: ---- sblim-cmpi-base-1.6.2-methods-enable.patch sblim-cmpi-base-1.6.2-missing-fclose.patch sblim-cmpi-base-1.6.2.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ sblim-cmpi-base.spec ++++++ --- /var/tmp/diff_new_pack.2RauZA/_old 2012-12-08 15:53:24.000000000 +0100 +++ /var/tmp/diff_new_pack.2RauZA/_new 2012-12-08 15:53:24.000000000 +0100 @@ -15,6 +15,7 @@ # Please submit bugfixes or comments via http://bugs.opensuse.org/ # + Name: sblim-cmpi-base BuildRequires: gcc-c++ BuildRequires: libtool @@ -22,10 +23,11 @@ BuildRequires: sblim-indication_helper-devel BuildRequires: sblim-sfcb BuildRequires: sblim-testsuite -Version: 1.6.1 +Version: 1.6.2 Release: 0 BuildRoot: %{_tmppath}/%{name}-%{version}-build -Requires: cim-server cim-schema +Requires: cim-schema +Requires: cim-server Url: http://sblim.wiki.sourceforge.net/ Source0: http://prdownloads.sourceforge.net/sblim/%{name}-%{version}.tar.bz2 Source1: sblim-cmpi-base-rpmlintrc ++++++ sblim-cmpi-base-1.6.1-methods-enable.patch -> sblim-cmpi-base-1.6.2-methods-enable.patch ++++++ ++++++ sblim-cmpi-base-1.6.1-missing-fclose.patch -> sblim-cmpi-base-1.6.2-missing-fclose.patch ++++++ ++++++ sblim-cmpi-base-1.6.1.tar.bz2 -> sblim-cmpi-base-1.6.2.tar.bz2 ++++++ ++++ 62442 lines of diff (skipped) ++++ retrying with extended exclude list diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/ChangeLog new/sblim-cmpi-base-1.6.2/ChangeLog --- old/sblim-cmpi-base-1.6.1/ChangeLog 2010-12-21 04:10:32.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/ChangeLog 2012-11-29 08:12:13.000000000 +0100 @@ -1,3 +1,33 @@ +2012-11-02 Tyrel Datwyler <tyreld@us.ibm.com> + + * NEWS, OSBase_UnixProcess.c: + + Fixed 3582069: Linux_UnixProcess command injection vulnerability + +2012-02-07 Tyrel Datwyler <tyreld@us.ibm.com> + + * Makefile.am, NEWS: + + Fixed 3424288: Underlinked libcmpiOSBase_ProcessorProvider.so + +2011-05-23 Tyrel Datwyler <tyreld@us.ibm.com> + + * NEWS, OSBase_OperatingSystem.c: + + Fixed 3306580: wrong OperatingSystem.Version prop value on RHEL6 + +2011-05-23 Tyrel Datwyler <tyreld@us.ibm.com> + + * NEWS, test/test-cmpi-base.sh: + + Fixed 3275169: bash error reported in provider bootstrap scripts + +2011-01-04 Tyrel Datwyler <tyreld@us.ibm.com> + + * ChangeLog, NEWS, configure.ac: + + Update release info for 1.6.1 + 2010-12-20 Tyrel Datwyler <tyreld@us.ibm.com> * NEWS, OSBase_Processor.c, OSBase_Processor.h, @@ -322,7 +352,7 @@ [ 1395363 ] Providers' postinstall step location dependent. Fixed Makefile and updated autoconf/deployment files from cmpi-samples. -2006-01-23 Lynn Moss +2006-01-23 Lynn Moss <lynn@us.ibm.com> * Makefile.am: @@ -1555,7 +1585,7 @@ Updated setting.cmpi to support Pegasus -2003-03-25 Adrian Schuur +2003-03-25 Adrian Schuur <schuur@de.ibm.com> * cimibase.h: diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/INSTALL new/sblim-cmpi-base-1.6.2/INSTALL --- old/sblim-cmpi-base-1.6.1/INSTALL 2008-06-06 21:56:23.000000000 +0200 +++ new/sblim-cmpi-base-1.6.2/INSTALL 2011-02-19 03:47:06.000000000 +0100 @@ -2,18 +2,24 @@ ************************* Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, -2006, 2007 Free Software Foundation, Inc. +2006, 2007, 2008, 2009 Free Software Foundation, Inc. -This file is free documentation; the Free Software Foundation gives -unlimited permission to copy, distribute and modify it. + Copying and distribution of this file, with or without modification, +are permitted in any medium without royalty provided the copyright +notice and this notice are preserved. This file is offered as-is, +without warranty of any kind. Basic Installation ================== -Briefly, the shell commands `./configure; make; make install' should + Briefly, the shell commands `./configure; make; make install' should configure, build, and install this package. The following more-detailed instructions are generic; see the `README' file for -instructions specific to this package. +instructions specific to this package. Some packages provide this +`INSTALL' file but do not implement all of the features documented +below. The lack of an optional feature in a given package is not +necessarily a bug. More recommendations for GNU packages can be found +in *note Makefile Conventions: (standards)Makefile Conventions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses @@ -42,7 +48,7 @@ you want to change it or regenerate `configure' using a newer version of `autoconf'. -The simplest way to compile this package is: + The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. @@ -53,12 +59,22 @@ 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with - the package. + the package, generally using the just-built uninstalled binaries. 4. Type `make install' to install the programs and any data files and - documentation. + documentation. When installing into a prefix owned by root, it is + recommended that the package be configured and built as a regular + user, and only the `make install' phase executed with root + privileges. + + 5. Optionally, type `make installcheck' to repeat any self-tests, but + this time using the binaries in their final installed location. + This target does not install anything. Running this target as a + regular user, particularly if the prior `make install' required + root privileges, verifies that the installation completed + correctly. - 5. You can remove the program binaries and object files from the + 6. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is @@ -67,15 +83,22 @@ all sorts of other programs in order to regenerate files that came with the distribution. - 6. Often, you can also type `make uninstall' to remove the installed - files again. + 7. Often, you can also type `make uninstall' to remove the installed + files again. In practice, not all packages have tested that + uninstallation works correctly, even though it is required by the + GNU Coding Standards. + + 8. Some packages, particularly those that use Automake, provide `make + distcheck', which can by used by developers to test that all other + targets like `make install' and `make uninstall' work correctly. + This target is generally not run by end users. Compilers and Options ===================== -Some systems require unusual options for compilation or linking that the -`configure' script does not know about. Run `./configure --help' for -details on some of the pertinent environment variables. + Some systems require unusual options for compilation or linking that +the `configure' script does not know about. Run `./configure --help' +for details on some of the pertinent environment variables. You can give `configure' initial values for configuration parameters by setting variables in the command line or in the environment. Here @@ -88,25 +111,41 @@ Compiling For Multiple Architectures ==================================== -You can compile the package for more than one kind of computer at the + You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their own directory. To do this, you can use GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the -source code in the directory that `configure' is in and in `..'. +source code in the directory that `configure' is in and in `..'. This +is known as a "VPATH" build. With a non-GNU `make', it is safer to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use `make distclean' before reconfiguring for another architecture. + On MacOS X 10.5 and later systems, you can create libraries and +executables that work on multiple system types--known as "fat" or +"universal" binaries--by specifying multiple `-arch' options to the +compiler but only a single `-arch' option to the preprocessor. Like +this: + + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CPP="gcc -E" CXXCPP="g++ -E" + + This is not guaranteed to produce working output in all cases, you +may have to build one architecture at a time and combine the results +using the `lipo' tool if you have problems. + Installation Names ================== -By default, `make install' installs the package's commands under + By default, `make install' installs the package's commands under `/usr/local/bin', include files under `/usr/local/include', etc. You can specify an installation prefix other than `/usr/local' by giving -`configure' the option `--prefix=PREFIX'. +`configure' the option `--prefix=PREFIX', where PREFIX must be an +absolute file name. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you @@ -117,16 +156,47 @@ In addition, if you use an unusual directory layout you can give options like `--bindir=DIR' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories -you can set and what kinds of files go in them. +you can set and what kinds of files go in them. In general, the +default for these options is expressed in terms of `${prefix}', so that +specifying just `--prefix' will affect all of the other directory +specifications that were not explicitly provided. + + The most portable way to affect installation locations is to pass the +correct locations to `configure'; however, many packages provide one or +both of the following shortcuts of passing variable assignments to the +`make install' command line to change installation locations without +having to reconfigure or recompile. + + The first method involves providing an override variable for each +affected directory. For example, `make install +prefix=/alternate/directory' will choose an alternate location for all +directory configuration variables that were expressed in terms of +`${prefix}'. Any directories that were specified during `configure', +but not in terms of `${prefix}', must each be overridden at install +time for the entire installation to be relocated. The approach of +makefile variable overrides for each directory variable is required by +the GNU Coding Standards, and ideally causes no recompilation. +However, some platforms have known limitations with the semantics of +shared libraries that end up requiring recompilation when using this +method, particularly noticeable in packages that use GNU Libtool. + + The second method involves providing the `DESTDIR' variable. For +example, `make install DESTDIR=/alternate/directory' will prepend +`/alternate/directory' before all installation names. The approach of +`DESTDIR' overrides is not required by the GNU Coding Standards, and +does not work on platforms that have drive letters. On the other hand, +it does better at avoiding recompilation issues, and works well even +when some directory options were not specified in terms of `${prefix}' +at `configure' time. + +Optional Features +================= If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. -Optional Features -================= - -Some packages pay attention to `--enable-FEATURE' options to + Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The @@ -138,14 +208,53 @@ you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. + Some packages offer the ability to configure how verbose the +execution of `make' will be. For these packages, running `./configure +--enable-silent-rules' sets the default to minimal output, which can be +overridden with `make V=1'; while running `./configure +--disable-silent-rules' sets the default to verbose, which can be +overridden with `make V=0'. + +Particular systems +================== + + On HP-UX, the default C compiler is not ANSI C compatible. If GNU +CC is not installed, it is recommended to use the following options in +order to use an ANSI C compiler: + + ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" + +and if that doesn't work, install pre-built binaries of GCC for HP-UX. + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot +parse its `<wchar.h>' header file. The option `-nodtk' can be used as +a workaround. If GNU CC is not installed, it is therefore recommended +to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" + + On Solaris, don't put `/usr/ucb' early in your `PATH'. This +directory contains several dysfunctional programs; working variants of +these programs are available in `/usr/bin'. So, if you need `/usr/ucb' +in your `PATH', put it _after_ `/usr/bin'. + + On Haiku, software installed for all users goes in `/boot/common', +not `/usr/local'. It is recommended to use the following options: + + ./configure --prefix=/boot/common + Specifying the System Type ========================== -There may be some features `configure' cannot figure out automatically, -but needs to determine by the type of machine the package will run on. -Usually, assuming the package is built to be run on the _same_ -architectures, `configure' can figure that out, but if it prints a -message saying it cannot guess the machine type, give it the + There may be some features `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the `--build=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name which has the form: @@ -153,7 +262,8 @@ where SYSTEM can have one of these forms: - OS KERNEL-OS + OS + KERNEL-OS See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't @@ -171,9 +281,9 @@ Sharing Defaults ================ -If you want to set default values for `configure' scripts to share, you -can create a site shell script called `config.site' that gives default -values for variables like `CC', `cache_file', and `prefix'. + If you want to set default values for `configure' scripts to share, +you can create a site shell script called `config.site' that gives +default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. @@ -182,7 +292,7 @@ Defining Variables ================== -Variables not defined in a site shell script can be set in the + Variables not defined in a site shell script can be set in the environment passed to `configure'. However, some packages may run configure again during the build, and the customized values of these variables may be lost. In order to avoid this problem, you should set @@ -201,11 +311,19 @@ `configure' Invocation ====================== -`configure' recognizes the following options to control how it operates. + `configure' recognizes the following options to control how it +operates. `--help' `-h' - Print a summary of the options to `configure', and exit. + Print a summary of all of the options to `configure', and exit. + +`--help=short' +`--help=recursive' + Print a summary of the options unique to this package's + `configure', and exit. The `short' variant lists options used + only in the top level, while the `recursive' variant lists options + also present in any nested packages. `--version' `-V' @@ -232,6 +350,16 @@ Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. +`--prefix=DIR' + Use DIR as the installation prefix. *note Installation Names:: + for more details, including other options available for fine-tuning + the installation locations. + +`--no-create' +`-n' + Run the configure checks, but stop before creating any output + files. + `configure' also accepts some other, not widely useful, options. Run `configure --help' for more details. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/Makefile.am new/sblim-cmpi-base-1.6.2/Makefile.am --- old/sblim-cmpi-base-1.6.1/Makefile.am 2009-07-25 02:37:30.000000000 +0200 +++ new/sblim-cmpi-base-1.6.2/Makefile.am 2012-11-29 07:22:20.000000000 +0100 @@ -1,4 +1,4 @@ -# $Id: Makefile.am,v 1.17 2009/07/25 00:37:30 tyreld Exp $ +# $Id: Makefile.am,v 1.19 2012/11/29 06:22:20 tyreld Exp $ # ================================================================== # (C) Copyright IBM Corp. 2005, 2009 # @@ -14,6 +14,7 @@ # Description: Automake input file for OS Base Providers # ================================================================== +AUTOMAKE_OPTIONS = no-dist-gzip dist-bzip2 # SBLIM Include Directory sblimincdir = $(includedir)/sblim @@ -93,7 +94,7 @@ cmpiOSBase_ProcessorProvider.c \ cmpiOSBase_Processor.c \ OSBase_Processor.c -libcmpiOSBase_ProcessorProvider_la_LIBADD = -lcmpiOSBase_Common +libcmpiOSBase_ProcessorProvider_la_LIBADD = -lcmpiOSBase_Common -lpthread libcmpiOSBase_ProcessorProvider_la_LDFLAGS = -avoid-version # Base Board diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/NEWS new/sblim-cmpi-base-1.6.2/NEWS --- old/sblim-cmpi-base-1.6.1/NEWS 2010-12-21 03:53:43.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/NEWS 2012-11-29 08:22:26.000000000 +0100 @@ -1,3 +1,12 @@ +Changes in Version 1.6.2 +======================== + +Bugs Fixed: +- 3275169 bash error reported in provider bootstrap scripts +- 3306580 wrong OperatingSystem.Version prop value on RHEL6 +- 3424288 Underlinked libcmpiOSBase_ProcessorProvider.so +- 3582069 Linux_UnixProcess command injection vulnerability + Changes in Version 1.6.1 ======================== diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/OSBase_OperatingSystem.c new/sblim-cmpi-base-1.6.2/OSBase_OperatingSystem.c --- old/sblim-cmpi-base-1.6.1/OSBase_OperatingSystem.c 2009-07-25 02:37:30.000000000 +0200 +++ new/sblim-cmpi-base-1.6.2/OSBase_OperatingSystem.c 2011-05-24 03:36:29.000000000 +0200 @@ -143,7 +143,7 @@ _OSBASE_TRACE(4,("--- _init_os_distro() called : init")); - rc = runcommand( "find /etc/ -type f -maxdepth 1 -name *release* 2>/dev/null" , NULL , &hdout , NULL ); + rc = runcommand( "find /etc/ -maxdepth 1 -type f -name *release 2>/dev/null" , NULL , &hdout , NULL ); if( rc == 0 && *hdout != NULL) { while (hdout[j] && hdout[j][0]) { if (strstr(hdout[j],"lsb-release") && hdout[j+1] && hdout[j+1][0]) { diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/OSBase_UnixProcess.c new/sblim-cmpi-base-1.6.2/OSBase_UnixProcess.c --- old/sblim-cmpi-base-1.6.1/OSBase_UnixProcess.c 2009-07-25 02:37:30.000000000 +0200 +++ new/sblim-cmpi-base-1.6.2/OSBase_UnixProcess.c 2012-11-02 23:24:03.000000000 +0100 @@ -86,21 +86,28 @@ char * cmd = NULL; char * str = NULL; char * ptr = NULL; - DIR * dpid = NULL; + char buf[256]; + int len = 0; int i = 0; int rc = 0; _OSBASE_TRACE(3,("--- get_process_data() called")); - cmd = (char*)malloc((strlen(pid)+100)); - sprintf(cmd, "ps -p %s --no-headers -eo pid,ppid,tty,pri,nice,uid,gid,pmem,pcpu,cputime,session,state,args",pid); - rc = runcommand( cmd , NULL, &hdout, NULL ); + sscanf(pid, "%[0-9] %n", buf, &len); + if (len != strlen(pid)) { + _OSBASE_TRACE(3,("--- get_process_data() failed : PID %s not valid", pid)); + return -1; + } + + cmd = (char*)malloc(len + 100); + sprintf(cmd, "ps -p %s --no-headers -o pid,ppid,tty,pri,nice,uid,gid,pmem,pcpu,cputime,session,state,args",buf); + rc = runcommand( cmd , NULL, &hdout, NULL ); if (rc == 0) { while( hdout[i] ) { if((ptr=strchr(hdout[i], '\n'))) { *ptr = '\0'; } str = hdout[i]; while( *str == ' ' ) { str = str+1; } - if( strncmp( str,pid,strlen(pid)) == 0 ) { + if( strncmp( str,buf,len) == 0 ) { rc = _process_data( hdout[i], sptr ); break; } @@ -108,7 +115,6 @@ } free ( cmd ); freeresultbuf( hdout ); - closedir(dpid); } else { _OSBASE_TRACE(3,("--- get_process_data() failed : PID %s not valid",pid)); diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/config.h.in new/sblim-cmpi-base-1.6.2/config.h.in --- old/sblim-cmpi-base-1.6.1/config.h.in 2010-12-21 04:11:29.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/config.h.in 2012-11-29 08:24:29.000000000 +0100 @@ -107,6 +107,9 @@ */ #undef HAVE_SYS_NDIR_H +/* Define to 1 if you have the <sys/param.h> header file. */ +#undef HAVE_SYS_PARAM_H + /* Define to 1 if you have the <sys/stat.h> header file. */ #undef HAVE_SYS_STAT_H @@ -137,6 +140,10 @@ /* Define to 1 if `vfork' works. */ #undef HAVE_WORKING_VFORK +/* Define to the sub-directory in which libtool stores uninstalled libraries. + */ +#undef LT_OBJDIR + /* Name of package */ #undef PACKAGE @@ -152,6 +159,9 @@ /* Define to the one symbol short name of this package. */ #undef PACKAGE_TARNAME +/* Define to the home page for this package. */ +#undef PACKAGE_URL + /* Define to the version of this package. */ #undef PACKAGE_VERSION diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/configure.ac new/sblim-cmpi-base-1.6.2/configure.ac --- old/sblim-cmpi-base-1.6.1/configure.ac 2010-12-21 04:06:15.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/configure.ac 2012-11-29 08:22:37.000000000 +0100 @@ -2,7 +2,7 @@ # Process this file with autoconf to produce a configure script. AC_PREREQ(2.59) -AC_INIT(SBLIM BaseOS Providers Base, 1.6.1, sblim-devel@lists.sourceforge.net,sblim-cmpi-base) +AC_INIT(SBLIM BaseOS Providers Base, 1.6.2, sblim-devel@lists.sourceforge.net,sblim-cmpi-base) AC_CONFIG_SRCDIR([OSBase_Common.c]) AC_CONFIG_HEADER([config.h]) AM_INIT_AUTOMAKE diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/missing new/sblim-cmpi-base-1.6.2/missing --- old/sblim-cmpi-base-1.6.1/missing 2008-06-06 21:56:23.000000000 +0200 +++ new/sblim-cmpi-base-1.6.2/missing 2011-02-19 03:47:07.000000000 +0100 @@ -1,10 +1,10 @@ #! /bin/sh # Common stub for a few missing GNU programs while installing. -scriptversion=2006-05-10.23 +scriptversion=2009-04-28.21; # UTC -# Copyright (C) 1996, 1997, 1999, 2000, 2002, 2003, 2004, 2005, 2006 -# Free Software Foundation, Inc. +# Copyright (C) 1996, 1997, 1999, 2000, 2002, 2003, 2004, 2005, 2006, +# 2008, 2009 Free Software Foundation, Inc. # Originally by Fran,cois Pinard <pinard@iro.umontreal.ca>, 1996. # This program is free software; you can redistribute it and/or modify @@ -18,9 +18,7 @@ # GNU General Public License for more details. # You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA -# 02110-1301, USA. +# along with this program. If not, see <http://www.gnu.org/licenses/>. # As a special exception to the GNU General Public License, if you # distribute this file as part of a program that contains a @@ -89,6 +87,9 @@ tar try tar, gnutar, gtar, then tar without non-portable flags yacc create \`y.tab.[ch]', if possible, from existing .[ch] +Version suffixes to PROGRAM as well as the prefixes \`gnu-', \`gnu', and +\`g' are ignored when checking the name. + Send bug reports to <bug-automake@gnu.org>." exit $? ;; @@ -106,15 +107,22 @@ esac +# normalize program name to check for. +program=`echo "$1" | sed ' + s/^gnu-//; t + s/^gnu//; t + s/^g//; t'` + # Now exit if we have it, but it failed. Also exit now if we # don't have it and --version was passed (most likely to detect -# the program). +# the program). This is about non-GNU programs, so use $1 not +# $program. case $1 in - lex|yacc) + lex*|yacc*) # Not GNU programs, they don't have --version. ;; - tar) + tar*) if test -n "$run"; then echo 1>&2 "ERROR: \`tar' requires --run" exit 1 @@ -138,7 +146,7 @@ # If it does not exist, or fails to run (possibly an outdated version), # try to emulate it. -case $1 in +case $program in aclocal*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if @@ -148,7 +156,7 @@ touch aclocal.m4 ;; - autoconf) + autoconf*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if you modified \`${configure_ac}'. You might want to install the @@ -157,7 +165,7 @@ touch configure ;; - autoheader) + autoheader*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if you modified \`acconfig.h' or \`${configure_ac}'. You might want @@ -187,7 +195,7 @@ while read f; do touch "$f"; done ;; - autom4te) + autom4te*) echo 1>&2 "\ WARNING: \`$1' is needed, but is $msg. You might have modified some files without having the @@ -210,7 +218,7 @@ fi ;; - bison|yacc) + bison*|yacc*) echo 1>&2 "\ WARNING: \`$1' $msg. You should only need it if you modified a \`.y' file. You may need the \`Bison' package @@ -240,7 +248,7 @@ fi ;; - lex|flex) + lex*|flex*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if you modified a \`.l' file. You may need the \`Flex' package @@ -263,7 +271,7 @@ fi ;; - help2man) + help2man*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if you modified a dependency of a manual page. You may need the @@ -277,11 +285,11 @@ else test -z "$file" || exec >$file echo ".ab help2man is required to generate this page" - exit 1 + exit $? fi ;; - makeinfo) + makeinfo*) echo 1>&2 "\ WARNING: \`$1' is $msg. You should only need it if you modified a \`.texi' or \`.texinfo' file, or any other file @@ -310,7 +318,7 @@ touch $file ;; - tar) + tar*) shift # We have already tried tar in the generic part. @@ -363,5 +371,6 @@ # eval: (add-hook 'write-file-hooks 'time-stamp) # time-stamp-start: "scriptversion=" # time-stamp-format: "%:y-%02m-%02d.%02H" -# time-stamp-end: "$" +# time-stamp-time-zone: "UTC" +# time-stamp-end: "; # UTC" # End: diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/sblim-cmpi-base.spec new/sblim-cmpi-base-1.6.2/sblim-cmpi-base.spec --- old/sblim-cmpi-base-1.6.1/sblim-cmpi-base.spec 2011-01-05 00:20:49.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/sblim-cmpi-base.spec 2012-11-29 08:24:27.000000000 +0100 @@ -8,7 +8,7 @@ Summary: SBLIM Base Providers Name: sblim-cmpi-base -Version: 1.6.1 +Version: 1.6.2 Release: 1 Group: Systems Management/Base URL: http://www.sblim.org diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/sblim-cmpi-base-1.6.1/test/test-cmpi-base.sh new/sblim-cmpi-base-1.6.2/test/test-cmpi-base.sh --- old/sblim-cmpi-base-1.6.1/test/test-cmpi-base.sh 2007-01-04 10:07:16.000000000 +0100 +++ new/sblim-cmpi-base-1.6.2/test/test-cmpi-base.sh 2011-05-24 02:31:40.000000000 +0200 @@ -10,7 +10,7 @@ #******************************************************************************# -declare -a CLASSNAMES[]; +declare -a CLASSNAMES; CLASSNAMES=([0]=Linux_ComputerSystem [1]=Linux_OperatingSystem \ [2]=Linux_UnixProcess [3]=Linux_Processor \ [4]=Linux_RunningOS [5]=Linux_OSProcess [6]=Linux_CSProcessor \ -- To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-commit+help@opensuse.org