Bug 29812 - Update Request new release of Darktable 3.8 announced
Summary: Update Request new release of Darktable 3.8 announced
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2021-12-24 18:04 CET by Jose Manuel López
Modified: 2022-01-27 23:27 CET (History)
8 users (show)

See Also:
Source RPM: darktable-3.6.1-1.mga8.src.rpm
Status comment:

Darktable 3.8 spec for Mageia 8 (2.88 KB, text/plain)
2022-01-17 16:02 CET, Jose Manuel López
DT 3.8 spec used in MLO repo (6.27 KB, text/plain)
2022-01-23 19:14 CET, christian barranco

Description Jose Manuel López 2021-12-24 18:04:10 CET
Description of problem: New release of Darktable to 3.8 announced with a lot of improvements and bugfixes.

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

How reproducible: Check the announcement on: https://www.darktable.org/2021/12/darktable-3.8.0-released/

Steps to Reproduce:
1. Check the Darktable version of Mageia, is 3.6.1
2. Check the Darktable version in official site, is 3.8
3. The new version come with a lot of improvements and bugfixes.
Comment 1 Lewis Smith 2021-12-26 20:55:54 CET
Thank you for the prompt.

Version 3.8.0 has just been put into Cauldron by dlucio.

Assigning this akien who did the current Version 3.6.1; up to you whether you want to ask DanielL to push this on.

Assignee: bugsquad => rverschelde
Source RPM: Darktable => darktable-3.6.1-1.mga8.src.rpm

Comment 2 Jose Manuel López 2021-12-26 21:05:32 CET
I have managed to compile the new version from official git in Mageia 8, but I don't know still package to rpm for Mageia. 

For the moment, the new version compiled works fine. I have import image, and I have applicated various filters.

I hope this serves as an initial report that the new version works in Mageia 8.

I'll wait for the testing package for a finish report.
Comment 3 Morgan Leijström 2021-12-27 00:34:42 CET
@Jose: New packagers are much welcome :)
If you like to contribute packaging, speak up if you need a mentor

CC: (none) => fri

Comment 4 Jose Manuel López 2022-01-03 09:31:04 CET
I need a mentor. I want package for Mageia, but I learn some things.

I know how to package from srpm package, but I don't know how to package from source.

Comment 5 Jose Manuel López 2022-01-03 09:49:30 CET
I have tried the new version 3.8 in Cauldron. Works fine for me.

Import and export image, workflow ok, modules ok.

Thanks for your work!!
Jose Manuel López 2022-01-03 11:18:11 CET

Summary: Request new release of Darktable 3.8 announced => Update Request new release of Darktable 3.8 announced

Comment 6 Morgan Leijström 2022-01-03 12:07:52 CET
I sent a mentor request on dev mailing list, pointing to comment 4
Comment 7 Jose Manuel López 2022-01-04 13:02:21 CET
No one has spoken yet.
Comment 8 Nicolas Lécureuil 2022-01-04 16:51:22 CET
ok for me.

I will first clean my padawans, for 1 i need to commit 3 packages and ask for a full account.

Can i contact you around the middle of next week ?

CC: (none) => mageia

Comment 9 Jose Manuel López 2022-01-04 17:00:10 CET
For me ok.

Right now I am attemping understand how works the darktable.spec file

I have tried to build for mga8 but the spec file request me some dependencies that I don't see in mga8, for example "exiftool".  Although I see that I have installed the exif package.

Comment 10 Morgan Leijström 2022-01-04 17:04:53 CET
Thank you Nicolas for stepping in, and Jose for joining us  :)
Comment 11 Jose Manuel López 2022-01-04 19:03:20 CET
I have checked the srpm of version 3.6.1. I don't understand how when I try to package from there, it asks for some dependencies, which don't exist in Mageia 8, however, the .rpm package of version 3.6.1 is available in the Mageia repos. 

There's something wrong with me...

I refer to these dependencies:

[jose@localhost SPECS]$ rpmbuild -ba darktable.spec
error: Fallo al construir las dependencias:
        gnome-doc-utils es necesario por darktable-3.6.1-1.mga8.x86_64
        lua5.3-devel es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(GraphicsMagick) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(colord) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(colord-gtk) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(dbus-glib-1) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(flickcurl) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(libsecret-1) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(libsoup-2.4) es necesario por darktable-3.6.1-1.mga8.x86_64
        pkgconfig(osmgpsmap-1.0) es necesario por darktable-3.6.1-1.mga8.x86_64
[jose@localhost SPECS]$
Comment 12 Guillaume Rousse 2022-01-04 19:53:06 CET
Just because they are not installed on your build host doesn't mean they are not available. Just try to install them first:
$> sudo urpmi darktable.spec

BTW, when posting output messages here, or any other mailing list, actually, it would be easier for other people to force english language, as it is generally more understandable for other people. Just forcing environnment variable LC_ALL=C should work, for instance:
$> LC_ALL=C rpmbuild -ba darktable.spec

CC: (none) => guillomovitch

Comment 13 Jose Manuel López 2022-01-04 22:44:49 CET
[jose@localhost SPECS]$ LC_ALL=C rpmbuild -ba darktable.spec
error: Failed build dependencies:
        exiftool is needed by darktable-3.8.0-4.mga8.x86_64
        lua-devel is needed by darktable-3.8.0-4.mga8.x86_64
[jose@localhost SPECS]$
Comment 14 Jose Manuel López 2022-01-04 22:48:57 CET
This testing come frome darktable spec of cauldron
Comment 15 Jose Manuel López 2022-01-04 23:05:07 CET
I have managed to package Darktable 3.8 from the spec of version 3.6.1.

Attached are the files for review.

Thanks for your help.

I hope that this will serve to raise updates.

Comment 16 Jose Manuel López 2022-01-04 23:19:03 CET
I can't attach this files, I put on Megaupload:

Comment 17 Jose Manuel López 2022-01-04 23:39:42 CET
Tried in Mageia 8 X64 works fine for me. Filters, conf. import and export, all ok for the moment.
Comment 18 Morgan Leijström 2022-01-04 23:47:54 CET
Great, Jose

Your mentor, or the bug assignee, or another packager will review your work, then if all is OK they arrange it to get built on Mageia build system and get uploaded to updates_testing.

After that this bug will be assigned to QA for testing.

( That does not hinder any interested user reading this bug to use your packages from Mega :) )
Comment 19 Guillaume Rousse 2022-01-05 05:21:09 CET
There is no reason to issue an update here, as there is no bug, and no security issue involved. Otherwise, we might as well issue all new packages from cauldron as updates... A backport, eventually.
Comment 20 Jose Manuel López 2022-01-05 07:12:06 CET
I think that somebody that use this application will disagree with the comment 19.

This new version fix 19 importants bugs according to official announcement, and I suposse others minors bugs that haven't mentioned there.

So, I think that this application should go to updates. There are others applications with the same position.

One thing is that the application update is minor, and another is that as in this and other cases they improvements are added and errors that affect the user's workflow are corrected.
Comment 21 Rémi Verschelde 2022-01-05 09:33:27 CET
For darktable I usually provide minor versions as updates (see e.g. bug 29226). In general for leaf packages that's something that users appreciate and if both the package maintainer and QA are up for it, I see no reason to freeze Mageia 8 in time for leaf applications.

I could handle this update but since Jose got started and is getting trained as a packager this way, I'll leave it to you as a good opportunity. I don't expect any major difficulties in updating darktable (it's usually just a version bump).
Comment 22 Morgan Leijström 2022-01-05 11:45:19 CET
I agree with Jose and Remi.

Lets keep high end applications that users desire updated, to keep attracting normal users. Like Office applications, image processing, video, CAD...

Of course, security problems in web browsers, and kernel and other general parts should get speediest handling, but dont forget people also wish shiny efficient tools :)
Comment 23 Jose Manuel López 2022-01-17 16:02:07 CET
Created attachment 13090 [details]
Darktable 3.8 spec for Mageia 8

This is the spec file for update Darktable to 3.8 version on Mageia 8
Comment 24 Rémi Verschelde 2022-01-23 12:30:25 CET
Thanks for the spec and the testing. In the end I sync with Cauldron which had significant new changes from other packagers: http://svnweb.mageia.org/packages/updates/8/darktable/current/SPECS/darktable.spec?r1=1745543&r2=1769507


Updated darktable package provides new 3.8.0 release

  This update provides the recently released darktable 3.8.0, which is the new
  stable branch. It provides new features, fixes various bugs, and improves
  camera support.

  See the linked release notes for details.


 - https://github.com/darktable-org/darktable/releases/

SRPM in core/updates_testing:


RPM in core/updates_testing:


CC: (none) => rverschelde
Assignee: rverschelde => qa-bugs

Comment 25 Thomas Andrews 2022-01-23 17:17:43 CET
(In reply to Guillaume Rousse from comment #19)
> There is no reason to issue an update here, as there is no bug, and no
> security issue involved. Otherwise, we might as well issue all new packages
> from cauldron as updates... A backport, eventually.

Bug and security fixes aren't the only reasons we do updates. 

We often do updates when the version we have is no longer being supported with those bug and/or security fixes. Firefox ESR is a good example of that.

Another reason, typically when Cauldron gets farther along than it is now, is to facilitate upgrade installs between releases.

CC: (none) => andrewsfarm

Comment 26 Thomas Andrews 2022-01-23 17:52:15 CET
I am not an experienced Darktable user, so a thorough test is beyond my capabilities. However, that doesn't stop me from testing for installation issues or a few basic functions.

Darktable already installed from previous tests. Used qarepo to download the darktable package. Updating with MCC appeared to draw in a new dependency:

The following 2 packages are going to be installed:

- darktable-3.8.0-1.mga8.x86_64
- perl-Image-ExifTool-12.0.0-1.1.mga8.noarch

No installation issues. Launched it from the Plasma menu, and was greeted with a message asking permission to apply configuration upgrades. (A nice touch.) I allowed it, and the program came up in Lightable mode, with two images displayed. Leftovers from that last test. I selected an image and went to Darkroom mode, where lots of buttons for various functions were displayed. I played with a few, and while I knew little of what I was doing, nothing crashed.

Going to call this good enough, and give it an OK. Validating. Advisory in Comment 24.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA8-64-OK

Comment 27 christian barranco 2022-01-23 19:14:22 CET
Created attachment 13100 [details]
DT 3.8 spec used in MLO repo

CC: (none) => chb0

Comment 28 christian barranco 2022-01-23 19:16:25 CET
Upon request on MLO forum, I built a package as well a few days ago and it is being tested.
Next time, I will do a more thorough search here...

Anyway, it was interesting to dig into this.

Based on comment 24, it might be so another spec is now used, compared to the one provide with comment 23.

I'd like then to share what I have done, for me to learn and to enrich the work done, if relevant. 

*lua version: 
** DT 3.8 requires lua 5.4. Cauldron spec provides lua 5.3.3 instead. After a discussion on IRC with DT dev, they seemed strong on the 5.4 requirement for DT 3.8 stability. Hence, I built the package with lua 5.4 coming from the DT version and it is provided as a bundle. What is the strategy used for MGA8?

*rawspeed: it looks like it might bring more speed in some cases. I bundled it as well. What do you think?

*noise tools: it is an additional tool I provide as an additional package; as done by Fedora. Do you think it is a good idea?

To make a bit clearer my comments, I attached the spec with comment #27

Looking forward to getting your feedback.
Comment 29 christian barranco 2022-01-23 19:45:54 CET
additional comment: this spec / package has been tested by an advanced DT user on MLO and he is satisfied. 

His comment:
"Neat installation, preserving my .config/darktable. I had backed it up though, to stay on the safe side. So far, no bugs have been noticed. Compared to 3.6.1, final jpeg export is notably faster and smoother. Hence, nothing to warn about so far."
Comment 30 Rémi Verschelde 2022-01-23 22:19:06 CET
Thanks, I'll take this update back and assess your proposed changes before pushing to stable.

Assignee: qa-bugs => rverschelde
Keywords: validated_update => (none)

Comment 31 Jose Manuel López 2022-01-24 16:57:07 CET

I have tried the package uploaded to testing repositories. Works fine for me. Import and export images, new modules ok, all ok for the moment in Mga 8 x86_64 real install.

Thanks for upload it to testing repos!

Comment 32 Rémi Verschelde 2022-01-25 16:35:15 CET
I had a quick look at Christian's proposed changes in comment 27 and comment 28, there's interesting new features but a lot to unpack and I'll need some time to review/cleanup.

I suggest opening a new bug report about adding these new features, which are not directly related to this 3.8 update and shouldn't be blocking for it.

Re-validating the current version which was tested in comment 26 and comment 31.

Assignee: rverschelde => qa-bugs
Keywords: (none) => validated_update

Dave Hodgins 2022-01-27 21:25:46 CET

CC: (none) => davidwhodgins
Keywords: (none) => advisory

Comment 33 Mageia Robot 2022-01-27 23:27:54 CET
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

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