digiKam no longer on Jekins?

[Veaceslav Munteanu-2]

Hello developers,

I saw that quite some tests are failing for a very long time.

I decided to fix what can be fixed, so we could take better advantage of jekins.
 However I am not able to find  digiKam anymore on build.kde.org

Does anybody knows anything?

[Gilles Caulier-4]

Hi Veaceslav,

This is a good question. Nobody touch Jenkins settings from here. All
is managed by KDE admin.

There is no reason to not see digiKam on Jenkins. It's certainly an
error somewhere...

I recommend to contact KDE admin through KDE Phabricator. There is a
way to report a dysfunction like this. An "admin task" must be open
(not a simple task). It's here :

https://phabricator.kde.org/

Best

Gilles

2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
> Hello developers,
>
> I saw that quite some tests are failing for a very long time.
>
> I decided to fix what can be fixed, so we could take better advantage of jekins.
>  However I am not able to find  digiKam anymore on build.kde.org
>
> Does anybody knows anything?

[Ben Cooksley]

On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
<[hidden email]> wrote:
> Hi Veaceslav,

Hi Gilles, Veaceslav,

>
> This is a good question. Nobody touch Jenkins settings from here. All
> is managed by KDE admin.
>
> There is no reason to not see digiKam on Jenkins. It's certainly an
> error somewhere...

It isn't an error. I have made repeated announcements on various
mailing lists over the past few weeks, including one last week to
kde-cvs-announce (which all Developers receive) concerning important
changes to the CI system.
One of these changes concerned the coverage of Extragear projects. All
of the emails had repeated notices saying your attention was required.
Nobody from Digikam responded to any of these.

I'd suggest you have a read of those emails.

>
> I recommend to contact KDE admin through KDE Phabricator. There is a
> way to report a dysfunction like this. An "admin task" must be open
> (not a simple task). It's here :
>
> https://phabricator.kde.org/
>
> Best
>
> Gilles

Cheers,
Ben

>
> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>> Hello developers,
>>
>> I saw that quite some tests are failing for a very long time.
>>
>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>  However I am not able to find  digiKam anymore on build.kde.org
>>
>> Does anybody knows anything?

[Gilles Caulier-4]

Hi Ben,

I just check my email history with Gmail search engine, and i cannot
find a message from you about the CI changes... I also take a look to
spam, in case of, and there is nothing about. This is why you never
recieve a message (:=)))...

Do you have a link to the original mail ?

Gilles Caulier

2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:

> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
> <[hidden email]> wrote:
>> Hi Veaceslav,
>
> Hi Gilles, Veaceslav,
>
>>
>> This is a good question. Nobody touch Jenkins settings from here. All
>> is managed by KDE admin.
>>
>> There is no reason to not see digiKam on Jenkins. It's certainly an
>> error somewhere...
>
> It isn't an error. I have made repeated announcements on various
> mailing lists over the past few weeks, including one last week to
> kde-cvs-announce (which all Developers receive) concerning important
> changes to the CI system.
> One of these changes concerned the coverage of Extragear projects. All
> of the emails had repeated notices saying your attention was required.
> Nobody from Digikam responded to any of these.
>
> I'd suggest you have a read of those emails.
>
>>
>> I recommend to contact KDE admin through KDE Phabricator. There is a
>> way to report a dysfunction like this. An "admin task" must be open
>> (not a simple task). It's here :
>>
>> https://phabricator.kde.org/
>>
>> Best
>>
>> Gilles
>
> Cheers,
> Ben
>
>>
>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>> Hello developers,
>>>
>>> I saw that quite some tests are failing for a very long time.
>>>
>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>
>>> Does anybody knows anything?

[Simon Frei]

Hi,

I don't find a link, but it is the message below. I wasn't aware of the
digiKam project using CI at the time, so I ignored it:

On 10/06/17 07:05, Ben Cooksley wrote:

> Next week we will be introducing the new Continuous Integration system.
> It can currently be found at https://build-sandbox.kde.org/
>
> Prior to the switch over taking place, all developers are *strongly*
> encouraged to check the status of their builds and tests. You will
> also need to check the dependencies which have been installed.
>
> This can be done by reviewing the build logs and other information
> displayed by Jenkins for your project.
>
> If your project is in Extragear and you have not previously requested
> for your coverage to be continued then you will likely need to request
> this.
>
> Additionally, if you have previously requested for email alerts to be
> provided, these will need to be re-requested.
>
> The new system among other things has the option to provide both
> FreeBSD and Windows builds. If you are interested in this for your
> application, please file a Sysadmin request.
>
> Note that in the case of Windows builds you'll need to provide
> assistance in getting builds functional for everything above
> Frameworks to your application in the event it depends on other KDE
> software.
>
> In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
> 5 builds are supported from this point onward.
>
> Regards,
> Ben

On 26/06/17 11:08, Gilles Caulier wrote:

> Hi Ben,
>
> I just check my email history with Gmail search engine, and i cannot
> find a message from you about the CI changes... I also take a look to
> spam, in case of, and there is nothing about. This is why you never
> recieve a message (:=)))...
>
> Do you have a link to the original mail ?
>
> Gilles Caulier
>
> 2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:
>> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
>> <[hidden email]> wrote:
>>> Hi Veaceslav,
>> Hi Gilles, Veaceslav,
>>
>>> This is a good question. Nobody touch Jenkins settings from here. All
>>> is managed by KDE admin.
>>>
>>> There is no reason to not see digiKam on Jenkins. It's certainly an
>>> error somewhere...
>> It isn't an error. I have made repeated announcements on various
>> mailing lists over the past few weeks, including one last week to
>> kde-cvs-announce (which all Developers receive) concerning important
>> changes to the CI system.
>> One of these changes concerned the coverage of Extragear projects. All
>> of the emails had repeated notices saying your attention was required.
>> Nobody from Digikam responded to any of these.
>>
>> I'd suggest you have a read of those emails.
>>
>>> I recommend to contact KDE admin through KDE Phabricator. There is a
>>> way to report a dysfunction like this. An "admin task" must be open
>>> (not a simple task). It's here :
>>>
>>> https://phabricator.kde.org/
>>>
>>> Best
>>>
>>> Gilles
>> Cheers,
>> Ben
>>
>>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>>> Hello developers,
>>>>
>>>> I saw that quite some tests are failing for a very long time.
>>>>
>>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>>
>>>> Does anybody knows anything?

[Gilles Caulier-4]

Thanks Simon,

Voilà, Veaceslav, you have all info to continuous the game with
Jenkins (:=)))....

Gilles

2017-06-26 11:21 GMT+02:00 Simon Frei <[hidden email]>:

> Hi,
>
> I don't find a link, but it is the message below. I wasn't aware of the
> digiKam project using CI at the time, so I ignored it:
>
> On 10/06/17 07:05, Ben Cooksley wrote:
>> Next week we will be introducing the new Continuous Integration system.
>> It can currently be found at https://build-sandbox.kde.org/
>>
>> Prior to the switch over taking place, all developers are *strongly*
>> encouraged to check the status of their builds and tests. You will
>> also need to check the dependencies which have been installed.
>>
>> This can be done by reviewing the build logs and other information
>> displayed by Jenkins for your project.
>>
>> If your project is in Extragear and you have not previously requested
>> for your coverage to be continued then you will likely need to request
>> this.
>>
>> Additionally, if you have previously requested for email alerts to be
>> provided, these will need to be re-requested.
>>
>> The new system among other things has the option to provide both
>> FreeBSD and Windows builds. If you are interested in this for your
>> application, please file a Sysadmin request.
>>
>> Note that in the case of Windows builds you'll need to provide
>> assistance in getting builds functional for everything above
>> Frameworks to your application in the event it depends on other KDE
>> software.
>>
>> In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
>> 5 builds are supported from this point onward.
>>
>> Regards,
>> Ben
>
>
> On 26/06/17 11:08, Gilles Caulier wrote:
>> Hi Ben,
>>
>> I just check my email history with Gmail search engine, and i cannot
>> find a message from you about the CI changes... I also take a look to
>> spam, in case of, and there is nothing about. This is why you never
>> recieve a message (:=)))...
>>
>> Do you have a link to the original mail ?
>>
>> Gilles Caulier
>>
>> 2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:
>>> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
>>> <[hidden email]> wrote:
>>>> Hi Veaceslav,
>>> Hi Gilles, Veaceslav,
>>>
>>>> This is a good question. Nobody touch Jenkins settings from here. All
>>>> is managed by KDE admin.
>>>>
>>>> There is no reason to not see digiKam on Jenkins. It's certainly an
>>>> error somewhere...
>>> It isn't an error. I have made repeated announcements on various
>>> mailing lists over the past few weeks, including one last week to
>>> kde-cvs-announce (which all Developers receive) concerning important
>>> changes to the CI system.
>>> One of these changes concerned the coverage of Extragear projects. All
>>> of the emails had repeated notices saying your attention was required.
>>> Nobody from Digikam responded to any of these.
>>>
>>> I'd suggest you have a read of those emails.
>>>
>>>> I recommend to contact KDE admin through KDE Phabricator. There is a
>>>> way to report a dysfunction like this. An "admin task" must be open
>>>> (not a simple task). It's here :
>>>>
>>>> https://phabricator.kde.org/
>>>>
>>>> Best
>>>>
>>>> Gilles
>>> Cheers,
>>> Ben
>>>
>>>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>>>> Hello developers,
>>>>>
>>>>> I saw that quite some tests are failing for a very long time.
>>>>>
>>>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>>>
>>>>> Does anybody knows anything?
>

[Veaceslav Munteanu-2]

I was not aware that digiKam was in extra-gear, so I also ignored the mail :))

I opened a new sysadmin task.

T6398

On Mon, Jun 26, 2017 at 11:27 AM, Gilles Caulier
<[hidden email]> wrote:

> Thanks Simon,
>
> Voilà, Veaceslav, you have all info to continuous the game with
> Jenkins (:=)))....
>
> Gilles
>
> 2017-06-26 11:21 GMT+02:00 Simon Frei <[hidden email]>:
>> Hi,
>>
>> I don't find a link, but it is the message below. I wasn't aware of the
>> digiKam project using CI at the time, so I ignored it:
>>
>> On 10/06/17 07:05, Ben Cooksley wrote:
>>> Next week we will be introducing the new Continuous Integration system.
>>> It can currently be found at https://build-sandbox.kde.org/
>>>
>>> Prior to the switch over taking place, all developers are *strongly*
>>> encouraged to check the status of their builds and tests. You will
>>> also need to check the dependencies which have been installed.
>>>
>>> This can be done by reviewing the build logs and other information
>>> displayed by Jenkins for your project.
>>>
>>> If your project is in Extragear and you have not previously requested
>>> for your coverage to be continued then you will likely need to request
>>> this.
>>>
>>> Additionally, if you have previously requested for email alerts to be
>>> provided, these will need to be re-requested.
>>>
>>> The new system among other things has the option to provide both
>>> FreeBSD and Windows builds. If you are interested in this for your
>>> application, please file a Sysadmin request.
>>>
>>> Note that in the case of Windows builds you'll need to provide
>>> assistance in getting builds functional for everything above
>>> Frameworks to your application in the event it depends on other KDE
>>> software.
>>>
>>> In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
>>> 5 builds are supported from this point onward.
>>>
>>> Regards,
>>> Ben
>>
>>
>> On 26/06/17 11:08, Gilles Caulier wrote:
>>> Hi Ben,
>>>
>>> I just check my email history with Gmail search engine, and i cannot
>>> find a message from you about the CI changes... I also take a look to
>>> spam, in case of, and there is nothing about. This is why you never
>>> recieve a message (:=)))...
>>>
>>> Do you have a link to the original mail ?
>>>
>>> Gilles Caulier
>>>
>>> 2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:
>>>> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
>>>> <[hidden email]> wrote:
>>>>> Hi Veaceslav,
>>>> Hi Gilles, Veaceslav,
>>>>
>>>>> This is a good question. Nobody touch Jenkins settings from here. All
>>>>> is managed by KDE admin.
>>>>>
>>>>> There is no reason to not see digiKam on Jenkins. It's certainly an
>>>>> error somewhere...
>>>> It isn't an error. I have made repeated announcements on various
>>>> mailing lists over the past few weeks, including one last week to
>>>> kde-cvs-announce (which all Developers receive) concerning important
>>>> changes to the CI system.
>>>> One of these changes concerned the coverage of Extragear projects. All
>>>> of the emails had repeated notices saying your attention was required.
>>>> Nobody from Digikam responded to any of these.
>>>>
>>>> I'd suggest you have a read of those emails.
>>>>
>>>>> I recommend to contact KDE admin through KDE Phabricator. There is a
>>>>> way to report a dysfunction like this. An "admin task" must be open
>>>>> (not a simple task). It's here :
>>>>>
>>>>> https://phabricator.kde.org/
>>>>>
>>>>> Best
>>>>>
>>>>> Gilles
>>>> Cheers,
>>>> Ben
>>>>
>>>>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>>>>> Hello developers,
>>>>>>
>>>>>> I saw that quite some tests are failing for a very long time.
>>>>>>
>>>>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>>>>
>>>>>> Does anybody knows anything?
>>

[Gilles Caulier-4]

Ben,

The current Jenkins is broken due to Exiv2 dependency. digiKam now
require at lease last 0.26 which introduce more than 200 bugfixes
after 2 years of development. Please update Exiv2 on CI computers...

Best

Gilles Caulier

2017-06-26 12:15 GMT+02:00 Veaceslav Munteanu <[hidden email]>:

> I was not aware that digiKam was in extra-gear, so I also ignored the mail :))
>
> I opened a new sysadmin task.
>
> T6398
>
> On Mon, Jun 26, 2017 at 11:27 AM, Gilles Caulier
> <[hidden email]> wrote:
>> Thanks Simon,
>>
>> Voilà, Veaceslav, you have all info to continuous the game with
>> Jenkins (:=)))....
>>
>> Gilles
>>
>> 2017-06-26 11:21 GMT+02:00 Simon Frei <[hidden email]>:
>>> Hi,
>>>
>>> I don't find a link, but it is the message below. I wasn't aware of the
>>> digiKam project using CI at the time, so I ignored it:
>>>
>>> On 10/06/17 07:05, Ben Cooksley wrote:
>>>> Next week we will be introducing the new Continuous Integration system.
>>>> It can currently be found at https://build-sandbox.kde.org/
>>>>
>>>> Prior to the switch over taking place, all developers are *strongly*
>>>> encouraged to check the status of their builds and tests. You will
>>>> also need to check the dependencies which have been installed.
>>>>
>>>> This can be done by reviewing the build logs and other information
>>>> displayed by Jenkins for your project.
>>>>
>>>> If your project is in Extragear and you have not previously requested
>>>> for your coverage to be continued then you will likely need to request
>>>> this.
>>>>
>>>> Additionally, if you have previously requested for email alerts to be
>>>> provided, these will need to be re-requested.
>>>>
>>>> The new system among other things has the option to provide both
>>>> FreeBSD and Windows builds. If you are interested in this for your
>>>> application, please file a Sysadmin request.
>>>>
>>>> Note that in the case of Windows builds you'll need to provide
>>>> assistance in getting builds functional for everything above
>>>> Frameworks to your application in the event it depends on other KDE
>>>> software.
>>>>
>>>> In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
>>>> 5 builds are supported from this point onward.
>>>>
>>>> Regards,
>>>> Ben
>>>
>>>
>>> On 26/06/17 11:08, Gilles Caulier wrote:
>>>> Hi Ben,
>>>>
>>>> I just check my email history with Gmail search engine, and i cannot
>>>> find a message from you about the CI changes... I also take a look to
>>>> spam, in case of, and there is nothing about. This is why you never
>>>> recieve a message (:=)))...
>>>>
>>>> Do you have a link to the original mail ?
>>>>
>>>> Gilles Caulier
>>>>
>>>> 2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:
>>>>> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
>>>>> <[hidden email]> wrote:
>>>>>> Hi Veaceslav,
>>>>> Hi Gilles, Veaceslav,
>>>>>
>>>>>> This is a good question. Nobody touch Jenkins settings from here. All
>>>>>> is managed by KDE admin.
>>>>>>
>>>>>> There is no reason to not see digiKam on Jenkins. It's certainly an
>>>>>> error somewhere...
>>>>> It isn't an error. I have made repeated announcements on various
>>>>> mailing lists over the past few weeks, including one last week to
>>>>> kde-cvs-announce (which all Developers receive) concerning important
>>>>> changes to the CI system.
>>>>> One of these changes concerned the coverage of Extragear projects. All
>>>>> of the emails had repeated notices saying your attention was required.
>>>>> Nobody from Digikam responded to any of these.
>>>>>
>>>>> I'd suggest you have a read of those emails.
>>>>>
>>>>>> I recommend to contact KDE admin through KDE Phabricator. There is a
>>>>>> way to report a dysfunction like this. An "admin task" must be open
>>>>>> (not a simple task). It's here :
>>>>>>
>>>>>> https://phabricator.kde.org/
>>>>>>
>>>>>> Best
>>>>>>
>>>>>> Gilles
>>>>> Cheers,
>>>>> Ben
>>>>>
>>>>>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>>>>>> Hello developers,
>>>>>>>
>>>>>>> I saw that quite some tests are failing for a very long time.
>>>>>>>
>>>>>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>>>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>>>>>
>>>>>>> Does anybody knows anything?
>>>

[Ben Cooksley]

On Thu, Jun 29, 2017 at 5:33 AM, Gilles Caulier
<[hidden email]> wrote:
> Ben,

Hi Gilles,

>
> The current Jenkins is broken due to Exiv2 dependency. digiKam now
> require at lease last 0.26 which introduce more than 200 bugfixes
> after 2 years of development. Please update Exiv2 on CI computers...

I'm aware of that. Note that you are building on an openSUSE
Tumbleweed image, which is a *rolling* distribution and therefore
quite up to date so this is quite an aggressive requirement.
I raised this with the SUSE packagers yesterday.

As a general rule (as agreed with the wider community) you are
required to give 2 weeks notice of system dependency bumps.

>
> Best
>
> Gilles Caulier

Regards,
Ben

>
> 2017-06-26 12:15 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>> I was not aware that digiKam was in extra-gear, so I also ignored the mail :))
>>
>> I opened a new sysadmin task.
>>
>> T6398
>>
>> On Mon, Jun 26, 2017 at 11:27 AM, Gilles Caulier
>> <[hidden email]> wrote:
>>> Thanks Simon,
>>>
>>> Voilà, Veaceslav, you have all info to continuous the game with
>>> Jenkins (:=)))....
>>>
>>> Gilles
>>>
>>> 2017-06-26 11:21 GMT+02:00 Simon Frei <[hidden email]>:
>>>> Hi,
>>>>
>>>> I don't find a link, but it is the message below. I wasn't aware of the
>>>> digiKam project using CI at the time, so I ignored it:
>>>>
>>>> On 10/06/17 07:05, Ben Cooksley wrote:
>>>>> Next week we will be introducing the new Continuous Integration system.
>>>>> It can currently be found at https://build-sandbox.kde.org/
>>>>>
>>>>> Prior to the switch over taking place, all developers are *strongly*
>>>>> encouraged to check the status of their builds and tests. You will
>>>>> also need to check the dependencies which have been installed.
>>>>>
>>>>> This can be done by reviewing the build logs and other information
>>>>> displayed by Jenkins for your project.
>>>>>
>>>>> If your project is in Extragear and you have not previously requested
>>>>> for your coverage to be continued then you will likely need to request
>>>>> this.
>>>>>
>>>>> Additionally, if you have previously requested for email alerts to be
>>>>> provided, these will need to be re-requested.
>>>>>
>>>>> The new system among other things has the option to provide both
>>>>> FreeBSD and Windows builds. If you are interested in this for your
>>>>> application, please file a Sysadmin request.
>>>>>
>>>>> Note that in the case of Windows builds you'll need to provide
>>>>> assistance in getting builds functional for everything above
>>>>> Frameworks to your application in the event it depends on other KDE
>>>>> software.
>>>>>
>>>>> In regards to Qt 4 support, this has been discontinued. Only KF5 / Qt
>>>>> 5 builds are supported from this point onward.
>>>>>
>>>>> Regards,
>>>>> Ben
>>>>
>>>>
>>>> On 26/06/17 11:08, Gilles Caulier wrote:
>>>>> Hi Ben,
>>>>>
>>>>> I just check my email history with Gmail search engine, and i cannot
>>>>> find a message from you about the CI changes... I also take a look to
>>>>> spam, in case of, and there is nothing about. This is why you never
>>>>> recieve a message (:=)))...
>>>>>
>>>>> Do you have a link to the original mail ?
>>>>>
>>>>> Gilles Caulier
>>>>>
>>>>> 2017-06-26 0:20 GMT+02:00 Ben Cooksley <[hidden email]>:
>>>>>> On Mon, Jun 26, 2017 at 9:50 AM, Gilles Caulier
>>>>>> <[hidden email]> wrote:
>>>>>>> Hi Veaceslav,
>>>>>> Hi Gilles, Veaceslav,
>>>>>>
>>>>>>> This is a good question. Nobody touch Jenkins settings from here. All
>>>>>>> is managed by KDE admin.
>>>>>>>
>>>>>>> There is no reason to not see digiKam on Jenkins. It's certainly an
>>>>>>> error somewhere...
>>>>>> It isn't an error. I have made repeated announcements on various
>>>>>> mailing lists over the past few weeks, including one last week to
>>>>>> kde-cvs-announce (which all Developers receive) concerning important
>>>>>> changes to the CI system.
>>>>>> One of these changes concerned the coverage of Extragear projects. All
>>>>>> of the emails had repeated notices saying your attention was required.
>>>>>> Nobody from Digikam responded to any of these.
>>>>>>
>>>>>> I'd suggest you have a read of those emails.
>>>>>>
>>>>>>> I recommend to contact KDE admin through KDE Phabricator. There is a
>>>>>>> way to report a dysfunction like this. An "admin task" must be open
>>>>>>> (not a simple task). It's here :
>>>>>>>
>>>>>>> https://phabricator.kde.org/
>>>>>>>
>>>>>>> Best
>>>>>>>
>>>>>>> Gilles
>>>>>> Cheers,
>>>>>> Ben
>>>>>>
>>>>>>> 2017-06-25 21:12 GMT+02:00 Veaceslav Munteanu <[hidden email]>:
>>>>>>>> Hello developers,
>>>>>>>>
>>>>>>>> I saw that quite some tests are failing for a very long time.
>>>>>>>>
>>>>>>>> I decided to fix what can be fixed, so we could take better advantage of jekins.
>>>>>>>>  However I am not able to find  digiKam anymore on build.kde.org
>>>>>>>>
>>>>>>>> Does anybody knows anything?
>>>>