[SRU] Update digikam to 8.0.0-beta1 on Kinetic

Bug #2000490 reported by Erich Eickmeyer
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Fix Released
Undecided
Unassigned
Kinetic
Fix Released
Undecided
Unassigned
Lunar
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

 * digiKam on Kinetic got stuck in an awkward position due to the update to ffmpeg 5.0 which caused a complete FTBFS (LP: #1982775). To figure out what to do with this, Rik Mills, Steve Langasek, and I decided to go with git snapshots of the digiKam repository hoping that digiKam would release at least a beta release prior to the release of 22.10. That did not happen.

 * The version of digiKam stuck in 22.10's repositories is a git snapshot of that which was available as of 02 October 2022. This was noted in Ubuntu Studio's Release Notes for 22.10 [1] with the hope and expectation that an update to a beta release would happen. Note that Ubuntu Studio is the only flavor that seeds digiKam.

 * As of 11 December 2022, the digiKam developers released 8.0.0-beta1.

[Test Case]

 * In 22.10 Kinetic Kudu:

$ apt info digikam

Package: digikam
Version: 4:8.0.0~git20221002-0ubuntu1
...

 * This should be updated to a version similar to that in Lunar, using my upload:

$ apt info digikam

Package: digikam
Version: 4:8.0.0~+beta1-0ubuntu0.22.10.1

[What could go wrong]

 * This beta release contains numerous bugfixes, but no new major features. Information about these bugfixes can be found in the NEWS file [2]

 * There still be unknown bugs as this is a beta release, but since this is no longer a development snapshot, this is much better than what exists in our repository.

 * This is also tested in my personal PPA and builds quite well against Kinetic. [3]

[Other Information]

 * As this is moving from a development snapshot to a beta release, I believe this justifies an exception from or meets the requirements of the microrelease policy. However, do note that the digiKam team decided to move their test suite into an entirely separate git repository which downloads at build time. I brought this problem to their attention [4] to which the reply was to simply disable the test suite. My reply to that was that it put us in a problematic position with an inability for our systems to run their tests.

 * Additionally, this should also justify a movement from beta to final release in the future should that happen significantly prior to 23.04's release, otherwise we should simply encourage users to upgrade to 23.04 for the final release of digiKam 8.0.0.

 * The versioning uses a ~+ since the prior version was ~git which is a newer version than ~beta as far as our versioning is concerned. Therefore, in order to supersede the git version, I had to use a +beta while keeping the ~ to keep it a lower version than the final 8.0.0 release will be. I do realize that this would cause a problem if Debian were to release an 8.0.0-beta1, but I highly doubt they will since the maintainer has already mentioned they wish to stick to final releases. When they do release a new version of a package at 8.0.0 final, I'm happy to sync and overwrite my entire delta which, at this point, has no functional significance.

[1] https://ubuntustudio.org/ubuntu-studio-22-10-release-notes/
[2] https://invent.kde.org/graphics/digikam/-/raw/32899a31edfa223faf99b012c03190c5260efb82/NEWS
[3] https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+packages
[4] https://bugs.kde.org/show_bug.cgi?id=463439

Changed in digikam (Ubuntu Lunar):
status: New → Fix Released
Changed in digikam (Ubuntu Kinetic):
status: New → Triaged
description: updated
description: updated
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Note that I can sponsor my own upload, debdiff included only for reference.

Changed in digikam (Ubuntu Kinetic):
status: Triaged → In Progress
Revision history for this message
Chris Halse Rogers (raof) wrote :

Woof. That's a *lot* of diffstat. At least most of it is translations.

I'm sympathetic to the "upgrade from random git snapshot" rationale. It's unfortunate that the tests are disabled, though - how hard would it be to we include the test data in the source package so that the tests can remain enabled?

Revision history for this message
Chris Halse Rogers (raof) wrote : Proposed package upload rejected

An upload of digikam to kinetic-proposed has been rejected from the upload queue for the following reason: "Please re-upload with the test-suite enabled, as discussed in #ubuntu-release".

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

Hi Chris,

I have just reuploaded with the test suite reenabled and included as we discussed.

Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Erich, or anyone else affected,

Accepted digikam into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/digikam/4:8.0.0~+beta1-0ubuntu0.22.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in digikam (Ubuntu Kinetic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-kinetic
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Tested in Kinetic by enabling proposed and installing digikam 8.0.0~+beta1-0ubuntu0.22.10.1 and the corresponding showfoto version. Everything appears to work as expected.

tags: added: verification-done verification-done-kinetic
removed: verification-needed verification-needed-kinetic
Revision history for this message
Graeme Hewson (ghewson) wrote :

digikam crashes with illegal instruction on AMD Athlon II (bug 2000718).

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

Graeme, this will hopefully fix that bug as this is an update in the Proposed pocket that is a beta release of digikam as opposed to the git snapshot that you filed the bug against.

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

Graeme, a follow-up. Reading your other bug report, it won't, but since this doesn't necessarily cause a regression, this update will proceed as planned. In the meantime, I'll work with you in the other bug report to get it filed upstream.

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

This bug was fixed in the package digikam - 4:8.0.0~+beta1-0ubuntu0.22.10.1

---------------
digikam (4:8.0.0~+beta1-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream beta release (LP: #2000490)
  * Include test suite in included-binaries
  * Patch to disable git checkout of test suite
  * Re-enable test suite using included-binaries
  * Refreshed patches

 -- Erich Eickmeyer <email address hidden> Thu, 26 Jan 2023 16:53:18 -0800

Changed in digikam (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for digikam has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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.