Hi all,
Can anyone help with a failing CI test for Tellico? It just started
recently, and looks to be due to kfilemetadata not finding the libexiv2
library. I'm not sure what might have changed. Nothing in recent Tellico
commits seems to be related.
>From
On Donnerstag, 6. Juli 2023 17:43:11 CEST Robby Stephenson wrote:
> Hi all,
>
> Can anyone help with a failing CI test for Tellico? It just started
> recently, and looks to be due to kfilemetadata not finding the libexiv2
> library. I'm not sure what might have changed. Nothing in recent Tellico
Am Donnerstag, 6. Juli 2023, 18:43:50 CEST schrieb Kai Uwe Broulik:
> > Probably libexiv2 on the CI host was updated to libexiv2 0.28, but
> > KFileMetaData was not rebuilt. Automatic dependency tracking for
>
> artifacts
>
> > from the CI system is obviously incomplete (or likely
> Probably libexiv2 on the CI host was updated to libexiv2 0.28, but
> KFileMetaData was not rebuilt. Automatic dependency tracking for
artifacts
> from the CI system is obviously incomplete (or likely nonexistent).
Isn’t that (among other things) the reason kexiv2 exists?
Cheers
Kai Uwe
The problem you are describing is because of the evaluative nature of
the current setup, where I was asked to force the entire system to
have limited exposure. In full rollout every report that the user
manually writes in drkonqi will also end up on sentry. Every
additional crash also, so long as
