FFe: darktable 2.6.3 in focal needs update to 3.0.1

Bug #1871049 reported by layingback
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
darktable (Ubuntu)
Fix Released
High
Unassigned

Bug Description

This is a request to update darktable deb to match the snap ;)

The biggest new features to warrant it:
- UI rework; everything is now themable, and it works properly on high-DPI screens
- 'filmic RGB' module as a new option to old global tone-mapping modules
- a new culling mode

and more, full release notes at
https://github.com/darktable-org/darktable/releases/tag/release-3.0.0

This also pulls in the first bugfix release, plus a couple of commits from git to fix some minor regressions found since.

--- original description: ---

Ubuntu 20.04 Focal Fossa LTS still only has darktable 2.6.3 in the official repositories.

darktable 3.0.0 was released Dec 24, 2019, and darktable 3.0.1 was released March 09 2020.

( darktable feature releases are traditionally released each Christmas. )

Please note that darktable 3.x is NOT backward compatible with darktable 2.6.3. So there is no way for a user of a more current version of darktable to even use darktable 2.6.3. A supplement problem is that running 2.6.3 when you have a 3.0.x db (eg. if upgrading Ubuntu to 20.04 in place) results in a totally silent fail at load. Only if run from a terminal do you see the '... db is too new ... Aborting ...' message.

I'll submit a post to <email address hidden> re this

affects: ubuntu-mate → darktable (Ubuntu)
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Darktable is a package that is synced from upstream Debian. Even if 3.0.1 were to land in Debian today, we would need a Feature Freeze Exception (it contains new features) and a Sync Request in order to get it into the repo in time. Unfortunately, that's not likely to happen.

Long story short, it's too late to get it into Focal.

I *might* be able to get it in the Ubuntu Studio Backports PPA, but I'll admit, that's not a priority right now.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

you can find dt 3.0.1 plus fixes on my ppa:
https://launchpad.net/~tjaalton/+archive/ubuntu/ppa

maybe there's still a chance to get it in focal

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in darktable (Ubuntu):
status: New → Confirmed
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

@tjaalton if you can do the upgrade, be my guest. In other words:

As flavor lead of Ubuntu Studio, I approve this exception.

summary: - Welcome: darktable 2.6.3 in focal needs update to 3.0.1
+ FFe: darktable 2.6.3 in focal needs update to 3.0.1
Timo Aaltonen (tjaalton)
Changed in darktable (Ubuntu):
status: Confirmed → New
assignee: nobody → Timo Aaltonen (tjaalton)
Timo Aaltonen (tjaalton)
description: updated
Timo Aaltonen (tjaalton)
description: updated
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Removed assignee as tjaalton has already uploaded this.

Changed in darktable (Ubuntu):
importance: Undecided → High
assignee: Timo Aaltonen (tjaalton) → nobody
Changed in darktable (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package darktable - 3.0.1-0ubuntu1

---------------
darktable (3.0.1-0ubuntu1) focal; urgency=medium

  * New upstream release. (LP: #1871049)
  * 3.0.x-fixes.diff: Pull fixes from upstream as of 20200323.

 -- Timo Aaltonen <email address hidden> Mon, 23 Mar 2020 16:30:41 +0200

Changed in darktable (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Simon Iremonger (ubuntu-iremonger) wrote :

FWIW, Upstream and Debian-"unstable" have now released 3.0.2 ...
May be worth Updating now, in any-case keep an eye on upstream bug-fixes ongoing...

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

At this point, it is impossible to get an update to 3.0.2 into the Ubuntu archives. Final Freeze happened on Thursday, which means nothing enters or leaves the archives aside minor bugfixes for known bugs. This "update" also includes some new features (meaning the version bump should've been more significant than a meer bugfix "point release"), meaning it would absolutely not be allowed as Feature Freeze Exceptions aren't allowed after Final Freeze.

I'm afraid that due to the new features, even a Stable Release Update is out of the question as those are simply for bugfixes. That said, I might be able to backport it into the Ubuntu Studio Backports PPA.

Revision history for this message
Simon Iremonger (ubuntu-iremonger) wrote :

Thankyou for helpful answer, from what I can see new-features are minor, and there are likely to be many significant bugfixes ongoing that will need including one way or another.

In any case, I note neither focal 3.0.1-0ubuntu1 package, nor debian-unstable 3.0.2-1 package succeed in compiling atop bionic18.04 system... In both cases all the apparent dependencies can be satisfied (e.g. backported debhelper, likely nothing else apparently needing backporting).

Definitely worth making some PPAs with a view to bionic-backports in my view!. Can create a separate bug-report if needbe.

With many thanks,

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.