[SRU] Update digikam to 8.0.0-beta1 on Kinetic
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~
...
* 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~
[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:/
[2] https:/
[3] https:/
[4] https:/
Changed in digikam (Ubuntu Lunar): | |
status: | New → Fix Released |
Changed in digikam (Ubuntu Kinetic): | |
status: | New → Triaged |
description: | updated |
description: | updated |
Changed in digikam (Ubuntu Kinetic): | |
status: | Triaged → In Progress |
Note that I can sponsor my own upload, debdiff included only for reference.