Bug 17829

Summary:	Darktable 2.0.1 backport, new major stable branch
Product:	Mageia	Reporter:	Rémi Verschelde <rverschelde>
Component:	Backports	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	tarazed25, tmb
Version:	5	Keywords:	Backport
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA5-64-OK MGA5-32-OK
Source RPM:	darktable-2.0.1-1.mga5	CVE:
Status comment:

Description Rémi Verschelde 2016-02-27 14:31:17 CET

This package is proposed as a backport as it brings many new features that Darktable users might want, but being a new stable branch it does not fit our updates policy (we have 1.6.x in Core Release/Updates).

Here are the release announcements for 2.0 and 2.0.1:
- http://www.darktable.org/2015/12/darktable-2-0-released/
- http://www.darktable.org/2016/02/darktable-2-0-1-released/


RPM: (core/backports_testing)
====
darktable-2.0.1-1.mga6

SRPM: (core/backports_testing)
=====
darktable-2.0.1-1.mga6

Comment 1 Len Lawrence 2016-02-27 23:47:17 CET

mga5  x86_64  Mate

Installed darktable-2.0.1-1.mga6 then checked
# urpmi darktable
Package darktable-2.0.1-1.mga5.x86_64 is already installed
Requires were also installed.
- lib64osmgpsmap1.0_0-1.0.2-4.mga5.x86_64
- lib64pugixml1-1.4-5.mga5.x86_64

$ urpmq --whatrequires lib64pugixml1 | sort | uniq
lib64OpenImageIO1.2
lib64pugixml1
lib64pugixml-devel

lib64OpenImageIO1.2 was not already installed.
$ urpmq --conflicts lib64OpenImageIO1.2
$ urpmq --conflicts lib64pugixml1
No conflicts.
Showing these without really understanding what the conflicts tag actually means but trying to figure out whether this breaks backports policy or not.
I guess not because lib64pugixml1 is current in Core Updates.

The maintenance release version of darktable installed earlier pulled in lib64osmgpsmap2.
$ cd /usr/lib64
$ ls *osmgp*
libosmgpsmap-1.0.so.0      libosmgpsmap.so.2
libosmgpsmap-1.0.so.0.0.0  libosmgpsmap.so.2.0.1

Opened up the interface and found the collection already imported.  Moved to the darkroom to try out several of the functions.  Everything working properly.

CC: (none) => tarazed25

Len Lawrence 2016-02-27 23:58:56 CET

Keywords: (none) => Backport
Whiteboard: (none) => MGA5-64-OK

Comment 2 Len Lawrence 2016-02-29 23:22:09 CET

mga5  i586 in virtualbox  Mate

Updated the backport candidate and tried it out.  It seems to function alright in spite of the dire warnings about using a 32-bit build and in spite of the fact that this test ws executed in a vbox with restricted memory and cpu power.

Len Lawrence 2016-02-29 23:22:42 CET

Whiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK

Comment 3 Thomas Backlund 2016-03-27 00:29:48 CET

Moved to backports

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED