Hello community,
here is the log from the commit of package sound-theme-freedesktop for openSUSE:Factory checked in at 2012-10-03 10:40:26
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/sound-theme-freedesktop (Old)
and /work/SRC/openSUSE:Factory/.sound-theme-freedesktop.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "sound-theme-freedesktop", Maintainer is "gnome-maintainers@suse.de"
Changes:
--------
--- /work/SRC/openSUSE:Factory/sound-theme-freedesktop/sound-theme-freedesktop.changes 2011-09-23 12:46:40.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.sound-theme-freedesktop.new/sound-theme-freedesktop.changes 2012-10-03 10:40:28.000000000 +0200
@@ -1,0 +2,6 @@
+Tue Sep 25 21:39:14 UTC 2012 - dimstar@opensuse.org
+
+- Update to version 0.8:
+ + Change default bell sound.
+
+-------------------------------------------------------------------
Old:
----
sound-theme-freedesktop-0.7.tar.bz2
New:
----
sound-theme-freedesktop-0.8.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ sound-theme-freedesktop.spec ++++++
--- /var/tmp/diff_new_pack.VESaBM/_old 2012-10-03 10:40:29.000000000 +0200
+++ /var/tmp/diff_new_pack.VESaBM/_new 2012-10-03 10:40:29.000000000 +0200
@@ -1,7 +1,7 @@
#
-# spec file for package sound-theme-freedesktop (Version 0.7)
+# spec file for package sound-theme-freedesktop
#
-# Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2012 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
@@ -16,16 +16,15 @@
#
-
Name: sound-theme-freedesktop
-Version: 0.7
-Release: 1
+Version: 0.8
+Release: 0
# For details on the licenses used, see README
-License: GPL-2.0+
Summary: freedesktop.org sound theme
-Url: http://0pointer.de/public/sound-theme-freedesktop.tar.gz
+License: GPL-2.0+
Group: System/Libraries
-Source: %{name}-%{version}.tar.bz2
+Url: http://0pointer.de/public/sound-theme-freedesktop.tar.gz
+Source: http://people.freedesktop.org/~mccann/dist/%{name}-%{version}.tar.bz2
BuildRequires: fdupes
BuildRequires: glib2-devel
BuildRequires: intltool
++++++ sound-theme-freedesktop-0.7.tar.bz2 -> sound-theme-freedesktop-0.8.tar.bz2 ++++++
++++ 10118 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/sound-theme-freedesktop-0.7/CREDITS new/sound-theme-freedesktop-0.8/CREDITS
--- old/sound-theme-freedesktop-0.7/CREDITS 1970-01-01 01:00:00.000000000 +0100
+++ new/sound-theme-freedesktop-0.8/CREDITS 2012-06-26 19:35:06.000000000 +0200
@@ -0,0 +1,77 @@
+alarm-clock-elapsed
+ Copyright: Tim/corsica_s
+ URL: http://www.freesound.org/samplesViewSingle.php?id=67091
+ License: CC-BY-SA (relicensed with permission from author)
+
+audio-channel-front-center
+audio-channel-front-left
+audio-channel-front-right
+audio-channel-rear-center
+audio-channel-rear-left
+audio-channel-rear-right
+audio-channel-side-left
+audio-channel-side-right
+audio-test-signal
+ Copyright: The ALSA developers
+ URL: http://git.alsa-project.org/?p=alsa-utils.git;a=tree;f=speaker-test/samples;...
+ License: GPLv2+
+
+audio-volume-change
+ Copyright: Lucas McCallister
+ URL: http://www.freesound.org/samplesViewSingle.php?id=67091
+ License: CC-BY-SA (relicensed with permission from author)
+
+trash-empty
+ Copyright: Dr. Richard Boulanger et al
+ URL: http://www.archive.org/details/Berklee44v10
+ License: CC-BY Attribution 3.0 Unported
+
+complete
+ Copyright: Dr. Richard Boulanger et al
+ URL: http://www.archive.org/details/Berklee44v11
+ License: CC-BY Attribution 3.0 Unported
+
+bell
+ Copyright: Dr. Richard Boulanger et al
+ URL: http://www.archive.org/details/Berklee44v12
+ License: CC-BY Attribution 3.0 Unported
+
+
+camera-shutter
+screen-capture
+ Copyright: freesound user horsthorstensen
+ URL: http://www.freesound.org/samplesViewSingle.php?id=72714
+ License: CC-BY-SA (relicensed with permission from author)
+
+device-added
+device-removed
+power-plug
+power-unplug
+network-connectivity-established
+network-connectivity-lost
+message
+dialog-information
+dialog-warning
+ Copyright: Ivica Bukvic
+ URL: http://gnome-look.org/content/show.php/%22Borealis%22+sound+theme?content=12...
+ License: CC-BY-SA
+
+
+message-new-instant
+
+phone-incoming-call
+phone-outgoing-busy
+phone-outgoing-calling
+ Copyright: Damien Sandras
+ URL: http://git.gnome.org/cgit/ekiga/tree/sounds
+ License: GPLv2+
+
+service-login
+service-logout
+ Copyright: The Pidgin developers
+ License: GPLv2
+
+suspend-error
+ Created by Richard Hughes
+ Copyright: Red Hat, Inc.
+ License: CC-BY-SA
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/sound-theme-freedesktop-0.7/INSTALL new/sound-theme-freedesktop-0.8/INSTALL
--- old/sound-theme-freedesktop-0.7/INSTALL 2009-08-23 20:20:43.000000000 +0200
+++ new/sound-theme-freedesktop-0.8/INSTALL 2012-09-25 22:19:10.000000000 +0200
@@ -1,19 +1,25 @@
Installation Instructions
*************************
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006, 2007 Free Software Foundation, Inc.
+Copyright (C) 1994-1996, 1999-2002, 2004-2011 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,58 @@
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.
+
+ HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved. Use GNU `make'
+instead.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `