Bug 14752 - New Version of darktable 1.6
Summary: New Version of darktable 1.6
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-08 15:01 CET by Magnus Rasche
Modified: 2015-01-10 10:32 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Magnus Rasche 2014-12-08 15:01:17 CET 
Description of problem:
Is it possible to let the newest version of darktable in?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
David Walser 2014-12-10 22:14:09 CET

Component: New RPM package request => RPM Packages
Assignee: bugsquad => remi
Severity: normal => enhancement

Comment 1 Rémi Verschelde 2014-12-11 00:07:00 CET 
Looking into it :-)
Comment 2 Rémi Verschelde 2014-12-11 00:33:05 CET 
Magnus, could you test this updated package and check that there are no visible regressions compared to the 1.4.2 version?

http://remi.verschelde.fr/files/packages/mga5/darktable-1.6.0-1.mga5.x86_64.rpm

Tell me if you need a 32bit build.

If you can test it succesfully (I'm also testing it here), I'll ask for a freeze push to hopefully get it included in Mageia 5.
Comment 3 Magnus Rasche 2014-12-11 07:30:22 CET 
Thanks Remi.
Installation and first start ok.

Will do more tests in the evening.

Office is calling
Comment 4 Magnus Rasche 2014-12-11 21:40:52 CET 
Hallo Remi,
I have made some function tests with raw pictures and I saw no errors.

The new version also recognized the old database from the last version.
So you can use all the work from the past
Comment 5 Rémi Verschelde 2015-01-10 10:32:21 CET 
1.6.0 is in cauldron, and I asked for a freeze push for 1.6.1.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.