Right, i will prepare a Merge Request

Reviewing the logs I see the following typo:

LANGUAGES=en es fr nl uk_UA ca de it zh_CH pt_PT

Hi Ben,

As all work as expected, this file can be closed now.

Hi all,

Ok, i seen the problem.

I have now unprotected that Sysadmin ticket.

Hum, i don't have the right to access on T16059...

Sorry, wrong copy-and-paste: T16059

Hi Luigi,
T16036 ??? are you sure ?..

Please leave them there for now. See T16036.

Hi all,

Done with this commit https://invent.kde.org/documentation/digikam-doc/commit/22dfc978e6442ef34a0b5bea8a03fa4f2fc79634

The ticket can't be closed just yet: the new documentation is stated to be CC BY SA 4.0 but the text is mostly the same as the old one, which is GFDL 1.2. Unless a proper relicensing is documented, where all contributors agree (or have already agreed though FLA and or https://invent.kde.org/sdk/kde-dev-scripts/-/blob/master/relicensecheck.pl), the license must stay GFDL 1.2.

Yes, this is just the nature of the readthedocs theme. Not only Kdenlive all documentations using it, look like this.

That behaviour is governed by the Sphinx theme - you can see the exact same thing happening with Kdenlive.
Krita appears to be using a customised theme hence why they don't have the issue.

Hi all,

Hi all,

That will be due to the first run not being done - i've now done that.

The job https://binary-factory.kde.org/view/Websites/job/Website_docs-digikam-org/ is not triggered anymore automatically when a commit is done in git/master.

Hi Ben,

Hi all,

Thanks Luigi for the feedback. So i need to complete first the conversion and merge back sphinx branch to master, before to check the translations workflow.

In T16036#285444, @cgilles wrote:

Hi Luigi,

Hi all,

Hi Albert,

Same - if you start from the StaticMessages.sh script from the other repositories, it should be fine.

Personally i know 0 about how that works, but if you're doing the same as the two other places, i don't see why it wouldn't work.

The infrastructure of digiKam handbook is under migrating from DocBook to RestructuredText/Sphinx. It miss the i18n to enable.
I plan to complete the manual conversion before Christmas, as we have a group of people ready to work on ported documentation to create missing entry in the documentation.

Hi Ben,

Hi Julius,

ID 38 enable for stats.kde.org :

I've provisioned ID "38" for that now.

The commented Matomo tracking code need to be re-enabled. A new ID must be used (actually it's 34 for KDenlive);

Hi Ben,

The Binary Factory job to build the site has now been provisioned: https://binary-factory.kde.org/job/Website_docs-digikam-org/1/console
It fails however, likely because Digikam is not mirroring the format that Kdenlive and Krita have chosen. You need to match how they have their setup i'm afraid.

Hi Ben,

I start to back-port KDenlive implementations:

Thanks Ben. I will backport and configure KDenlive files in "sphinx" branch from digiKam documentation repository.

The system has flexibility as to the branch that we use.

Ok, Must i use master or a devel branch in git repository ?

As stated previously, the initial work for Sphinx to be able to run must be in place within the repository first before anything from a Sysadmin perspective can be actioned.

Hi Ben,

Thanks Julius for this excellent feedback. Now i know how to start with the migration.

Hi Gilles,

Hi Wolthera,

Thanks Eugen,

I think Julius can advise for the technical part: migrate from docBook -> Sphinx (we migrated from KDE-UserBase-Wiki to Sphinx).

As you works on the KDenlive Documentation repository, Perhaps you can guide us a little bit on the currrent digiKam DocBook repository to Sphinx migration ?

digiKam git documentation based on DocBook is now tagged with v7.9.0:

I'm afraid we don't do the work of preparing the repository - that will need to be something undertaken by the >Digikam team (it was done by Kdenlive/Krita folks for theirs).

I'm afraid we don't do the work of preparing the repository - that will need to be something undertaken by the DIgikam team (it was done by Kdenlive/Krita folks for theirs).

Hi Ben,

Ah thanks Ben for the explanations.

This was a restriction imposed by another admin following the various adjustments you were making to .gitlab-ci.yml to disable Gitlab CI jobs because the "functionality was provided elsewhere".
Please note that both build.kde.org and binary-factory.kde.org will be going away, being replaced by native Gitlab CI in the future.

Hi Ben,

The system has no support for differentiating between Qt 5 and Qt 6 i'm afraid.

Hi Ben ,

Hi Ben,

The job in that case is complaining that KSane does not exist for that platform/branch combination.

Hi Ben,

At this time expansion of additional targets on build.kde.org is no longer supported as build.kde.org is in the process of being sunset.
Please configure Gitlab CI instead.

The linking problem is the same under MacOS. All is installed into /opt/digikam, and when lqr-1 dependency is installed digiKam do not link as under FreeBSD
Gilles Caulier

yes, sure. Fell free to patch cmake file in digiKam repository.

I think it would be preferable if the cmake were fixed to properly respect the values read via the find package call. It's an easy fix after all.

What's about if you disable liblqr-1 detection under FREEBSD. In fact it's only used with one plugin (liquid-rescale) which represent 0.1 % of code.

Yes, all the patch-* in the files direcotry in the above link get applied before building.

Your lqr-1 patch is applied while digiKam is compiled for freebsd ?

As this is all sorted out now from a CI Infrastructure point of view, going to unsubscribe myself and Sysadmin.
Let us know if anything further needs to be sorted out.

We have it fixed like so in the tree:
https://github.com/freebsd/freebsd-ports-kde/blob/master/graphics/digikam/files/patch-core_CMakeLists.txt

03:32:36 [ 42%] Linking CXX shared library libdigikamcore.so
03:32:36 ld: error: unable to find library -llqr-1
03:32:36 ld: error: unable to find library -lglib-2.0
03:32:36 ld: error: unable to find library -lintl
03:32:36 ld: error: unable to find library -llqr-1
03:32:36 ld: error: unable to find library -lglib-2.0
03:32:36 ld: error: unable to find library -lintl
03:32:36 c++: error: linker command failed with exit code 1 (use -v to see invocation)
03:32:36 gmake[2]: * [core/app/CMakeFiles/digikamcore.dir/build.make:1279: core/app/libdigikamcore.so.7.0.0] Error 1
03:32:36 gmake[1]: * [CMakeFiles/Makefile2:6377: core/app/CMakeFiles/digikamcore.dir/all] Error 2
03:32:36 gmake[1]: *** Waiting for unfinished jobs....

@cgilles https://build.kde.org/job/Extragear/job/digikam/job/kf5-qt5%20FreeBSDQt5.13/8/console opencv has been installed -- failures are now the missing link directories (basically -L/usr/local/lib)

Sure, I'll do that later today.

Tobias and Adriaan, could we get OpenCV added to the FreeBSD images please?

FreeBSD build fail due to missing OpenCV dependency...

This task was briefly discussed at today's Dolphin BoF at Akademy. It was pointed out that the QGraphicsView dependency of the custom view-engine cannot go away, as that would not be worth the effort.

digiKam is crashing when Colors channel is selected and we change the curve type.
I have tried other methods also like (channel < ColorChannels) in setCurveType function but it doesn't work.
What is the issue?

I think that my image should fail. If it works with you with the original image from the camera it is fine. If a lens is present in the metadata (wherever she comes from) if only a lens in the list, should only come out with a partial match.
For me, the patch is fine.

digikam.dimg: Search for camera "SONY" - "DSC-RX100M4" ==> true
digikam.dimg: Camera maker : "Sony"
digikam.dimg: Camera model : "DSC-RX100M4"
digikam.dimg: * Check for lens by direct query ( "Sony 24-70mm F1.8-2.8" : 0 )
digikam.dimg: * Check for no maker lens ( "Sony 24-70mm F1-2" : 0 )
digikam.dimg: lens matches : NOT FOUND
digikam.dimg: Focal Length : 25.7
digikam.dimg: Aperture : 5.6
digikam.dimg: Subject dist. : NOT FOUND : Use default value.
digikam.dimg: Subject dist. : 1000
digikam.dimg: Metadata match : "Partial Match"

In D20966#459650, @mqualmann wrote:

I only used a test sample from the web of the camera for the test, there is also only one lens in the list. But the BQM fails here despite patch because of missing lens.

Maik

I only used a test sample from the web of the camera for the test, there is also only one lens in the list. But the BQM fails here despite patch because of missing lens.