Hello community,

here is the log from the commit of package doomsday for openSUSE:Factory 
checked in at 2014-05-02 10:52:59
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/doomsday (Old)
 and      /work/SRC/openSUSE:Factory/.doomsday.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "doomsday"

Changes:
--------
--- /work/SRC/openSUSE:Factory/doomsday/doomsday.changes        2014-01-13 
10:52:53.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.doomsday.new/doomsday.changes   2014-05-02 
10:53:07.000000000 +0200
@@ -1,0 +2,25 @@
+Thu May  1 13:03:03 UTC 2014 - [email protected]
+
+- Update to new upstream release 1.14.1, which fixes:
+* particles were shut off shortly after level start
+* flickering light decoration on moving platform
+* letterboxed/pillarboxed drawing of the game was broken
+* Heretic ghost mummies' floating spirits were not disappearing
+  after death
+* Shift key state was not recognized by bindings when typing in
+  console
+* Multiplayer weapons were not remaining in play
+* Gracefully abort if OpenGL version is not sufficient
+
+-------------------------------------------------------------------
+Wed Apr 23 21:44:28 UTC 2014 - [email protected]
+
+- Update to new upstream release 1.14
+* It adds bloom to Doomsday's visual features. The last of the
+  old UI has been replaced, and now MP games and save games, due
+  to a new save game format, from all games can be accessed from
+  the taskbar or home screen (formerly Ring Zero). New alert and
+  tutorial notifications have been added to inform users of any
+  important engine, map and resource errors and about the UI.
+
+-------------------------------------------------------------------

Old:
----
  doomsday-1.13.1.tar.xz

New:
----
  doomsday-1.14.1.tar.gz

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

Other differences:
------------------
++++++ doomsday.spec ++++++
--- /var/tmp/diff_new_pack.Mw1DUw/_old  2014-05-02 10:53:08.000000000 +0200
+++ /var/tmp/diff_new_pack.Mw1DUw/_new  2014-05-02 10:53:08.000000000 +0200
@@ -17,9 +17,9 @@
 
 
 Name:           doomsday
-Version:        1.13.1
+Version:        1.14.1
 Release:        0
-%define rver   1.13.1
+%define rver   1.14.1
 Summary:        The Doomsday Engine: DOOM/Hertic/Hexen port with pretty 
graphics
 License:        GPL-2.0+ and GPL-2.0
 Group:          Amusements/Games/3D/Shoot
@@ -28,8 +28,7 @@
 
 #Git-Web:      https://github.com/skyjake/Doomsday-Engine
 #Git-Clone:    git://github.com/skyjake/Doomsday-Engine
-#DL-URL:       http://downloads.sf.net/deng/doomsday-1.13.1.tar.gz
-Source:         %name-%rver.tar.xz
+Source:         http://downloads.sf.net/deng/%name-%rver.tar.gz
 Source2:        %name-rpmlintrc
 
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
@@ -41,7 +40,6 @@
 BuildRequires:  libqt4-devel >= 4.6
 BuildRequires:  ncurses-devel
 BuildRequires:  xorg-x11-devel
-BuildRequires:  xz
 BuildRequires:  zlib-devel
 
 %if 0%{?suse_version}
@@ -54,9 +52,11 @@
 Provides:       deng = %version-%release
 
 # Doomsday 1.12 needs OpenGL 2.x, which Mesa 9.0 (as shipped in openSUSE 12.3)
-# does not have. As far as RPM is concerned, 3rd party GL drivers can coexist
-# with Mesa-libGL1 as they are located in a separate directory, which means
-# that having the Mesa require is always acceptable.
+# does not have.
+# For the situation in openSUSE 13.1+, as far as RPM is concerned, 3rd party
+# GL drivers can coexist with Mesa-libGL1 as they are located in a separate
+# directory, which means that having the following Mesa require is always
+# acceptable.
 Requires:       Mesa-libGL1 >= 9.2
 
 %description
@@ -108,7 +108,7 @@
 pushd doomsday/;
 make install INSTALL_ROOT="$b";
 mkdir -p "$b/%_libexecdir/%name";
-mv "$b/%_bindir"/{md2tool,texc} "$b/%_libexecdir/%name/";
+mv "$b/%_bindir"/{md2tool,savegametool,texc} "$b/%_libexecdir/%name/";
 popd;
 
 mkdir -p "$b/%_sysconfdir/doomsday";

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

Reply via email to