On Fri, Jul 7, 2023 at 5:31 AM Friedrich W. H. Kossebau
wrote:
> 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
On Fri, Jul 7, 2023 at 3:53 AM Stefan Brüns
wrote:
> 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
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 nonexistent)
> 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
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
>
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 https://invent.kde.org/office/tellico/-/j
