Bug 29226 - Update candidate: darktable 3.6.0
Summary: Update candidate: darktable 3.6.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, has_procedure, validated_update
Depends on:
Blocks:
 
Reported: 2021-07-05 14:56 CEST by Rémi Verschelde
Modified: 2021-07-21 14:19 CEST (History)
4 users (show)

See Also:
Source RPM: darktable-3.4.1-1.mga8
CVE:
Status comment:


Attachments

Description Rémi Verschelde 2021-07-05 14:56:24 CEST
Advisory:
=========

Updated darktable package provides new 3.6 feature release

  This is a feature and bugfix update for darktable, bringing the Mageia package
  from version 3.4.1 to 3.6.0.

  The release includes numerous new features, enhancements and bugfixes which
  are outlined in the referenced release notes.

  Important: Upgrading from darktable 3.4 to 3.6 will imply upgrading the data
  and library databases in a non backward compatible way (so downgrading is not
  easily possible).
  
  The pre-upgrade databases will be saved as `.pre-3.6.0` files in
  `~/.config/darktable/`. You can also back up the whole `~/.config/darktable/`
  folder prior to upgrading in case any issue is encountered during the upgrade.


Reference:

 - https://github.com/darktable-org/darktable/releases/tag/release-3.6.0


SRPM in core/updates_testing:
=============================

darktable-3.6.0-1.mga8

RPM in core/updates_testing:
============================

darktable-3.6.0-1.mga8


Testing procedure:
==================

As outlined in the advisory, darktable uses database files for its data and library, and this file format gets upgraded automatically when opening the new
version with pre-existing data.

Until we (and other upstream users) have tested this sufficiently to be confident about the upgrade, I would advise testers who use darktable personally to back up their `~/.config/darktable/` folder before testing the update.

While QA testing can be done right now, I would suggest waiting a few days before validating the update, just to see if there's any issue with the 3.6.0 release reported upstream that would push them to release a 3.6.1 bugfix.
Rémi Verschelde 2021-07-05 14:57:18 CEST

Keywords: (none) => has_procedure

Comment 1 Rémi Verschelde 2021-07-05 15:03:25 CEST
I pushed a new package with a patch fixing one upstream bug (crash) reported against 3.6.0: https://github.com/darktable-org/darktable/issues/9403


SRPM in core/updates_testing:
=============================

darktable-3.6.0-1.1.mga8

RPM in core/updates_testing:
============================

darktable-3.6.0-1.1.mga8
Comment 2 Jose Manuel López 2021-07-05 17:01:38 CEST
Hi, here works fine in Mga 8 Plasma for the moment. 

I was looking forward to this update, I was just going to report this afternoon for Mageia. Thanks for the speed to the developers!

It is an application that I use almost daily.

CC: (none) => joselp

Comment 3 Aurelien Oudelet 2021-07-10 21:03:45 CEST
MGA8 x64 Plasma

Saving ~/.config/darktable/ before.

This works ok.
Update well over existing installation.
Library migrated well.

No 3.6.1 issued. I don't know if there is well-know issues upstream for Linux.

CC: (none) => ouaurelien

Comment 4 Thomas Andrews 2021-07-20 02:22:08 CEST
mga8 x64 Plasma. No installation issues. Database is tiny,(I don't use this as a rule), and updated without incident. No issues noted.

It's been two weeks since this bug was filed, and darktable.org still has not announced a 3.6.1 release. Since Jose uses it "almost daily" and hasn't reported any issues, I think we can send this on.

Validating. Advisory in Comment 0, with the updated srpm in Comment1.

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

Aurelien Oudelet 2021-07-20 23:12:26 CEST

Keywords: (none) => advisory

Comment 5 Mageia Robot 2021-07-21 14:19:27 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0158.html

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


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