Bug 20690 - rawtherapee 5
Summary: rawtherapee 5
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: Mageia 6
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-17 16:10 CEST by Thierry Houx
Modified: 2017-08-29 13:51 CEST (History)
2 users (show)

See Also:
Source RPM: rawtherapee
CVE:
Status comment:


Attachments

Description Thierry Houx 2017-04-17 16:10:25 CEST
Description of problem:
The last version of rawtherapee is 5 and include important bug fixes and features; these are necessary for recent cameras

Version-Release number of selected component (if applicable):
rawtherapee-4.2-1.mga6.x86_64.rpm (cauldron)
rawterapee is actually at 5.0.3 r1

How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Thierry Houx 2017-04-17 16:13:20 CEST
I'm french, so my english is not necessary good, sorry.

Target Milestone: --- => Mageia 6

Comment 2 Marja Van Waes 2017-04-17 22:12:15 CEST
(In reply to Thierry Houx from comment #0)
> Description of problem:
> The last version of rawtherapee is 5 and include important bug fixes and
> features; these are necessary for recent cameras
> 
> Version-Release number of selected component (if applicable):
> rawtherapee-4.2-1.mga6.x86_64.rpm (cauldron)
> rawterapee is actually at 5.0.3 r1
> 

Assinging to all packagers collectively, since there is no registered rawtherapee maintainer.

CC: sysadmin-bugs => marja11
Assignee: bugsquad => pkg-bugs
Summary: ratherapee 5 => rawtherapee 5
Component: Release (media or process) => RPM Packages

Comment 3 Mike Rambo 2017-08-29 13:51:20 CEST
rawtherapee for cauldron was updated to version 5.2 on July 31st and has been above version 5 for some time before that. The target milestone, Mageia 6, was updated to 5.1 back in June. This bug is thus satisfied.

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


Note You need to log in before you can comment on or make changes to this bug.