--00000000000054a05805ffe3e60e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 7, 2023 at 5:31=E2=80=AFAM Friedrich W. H. Kossebau <kossebau@k=
de.org>
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
> >
> >  > from the CI system is obviously incomplete (or likely nonexistent).
> >
> > Isn=E2=80=99t that (among other things) the reason kexiv2 exists?
>
> Does not help if kexiv2 is not rebuilt and deployed as artifact when exiv=
2
> on
> the image changed in a incompatible version?
>

Correct.


>
> Triggered the needed manual rerun of kfilemetadata now, so the exiv plugi=
n
> artifact is updated to the match the current base image. Also reran the
> tellico jump afterwards, seems to pass now again.
>

Thanks for sorting that.


>
> Curious: are the images regenerated automatically or manually? in both
> cases,
> triggering also seed runs should be something part of that process? As we
> seem
> to run into such things again and again?
>

The images are only rebuilt manually, to ensure we control when changes
take place.

Unfortunately the build of the images took longer than I had anticipated
due to various issues, so sleep was required before it was completed
(meaning I couldn't hit start on the ci-management jobs)


>
> Cheers
> Friedrich
>

Cheers,
Ben

--00000000000054a05805ffe3e60e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jul 7, 2023 at 5:31=E2=80=AFAM Fr=
iedrich W. H. Kossebau &lt;<a href=3D"mailto:kossebau@kde.org">kossebau@kde=
.org</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Am Donnerstag, 6. Juli 2023, 18:43:50 CEST=
 schrieb Kai Uwe Broulik:<br>
&gt;=C2=A0 &gt; Probably libexiv2 on the CI host was updated to libexiv2 0.=
28, but<br>
&gt;=C2=A0 &gt; KFileMetaData was not rebuilt. Automatic dependency trackin=
g for<br>
&gt; <br>
&gt; artifacts<br>
&gt; <br>
&gt;=C2=A0 &gt; from the CI system is obviously incomplete (or likely nonex=
istent).<br>
&gt; <br>
&gt; Isn=E2=80=99t that (among other things) the reason kexiv2 exists?<br>
<br>
Does not help if kexiv2 is not rebuilt and deployed as artifact when exiv2 =
on <br>
the image changed in a incompatible version?<br></blockquote><div><br></div=
><div>Correct.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">
<br>
Triggered the needed manual rerun of kfilemetadata now, so the exiv plugin =
<br>
artifact is updated to the match the current base image. Also reran the <br=
>
tellico jump afterwards, seems to pass now again.<br></blockquote><div><br>=
</div><div>Thanks for sorting that.</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
<br>
Curious: are the images regenerated automatically or manually? in both case=
s, <br>
triggering also seed runs should be something part of that process? As we s=
eem <br>
to run into such things again and again?<br></blockquote><div><br></div><di=
v>The images are only rebuilt manually, to ensure we control when changes t=
ake place.</div><div><br></div><div>Unfortunately the build of the images t=
ook longer than I had anticipated due to various issues, so sleep was requi=
red before it was completed (meaning I couldn&#39;t hit start on the ci-man=
agement jobs)</div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">
<br>
Cheers<br>
Friedrich<br></blockquote><div><br></div><div>Cheers,</div><div>Ben=C2=A0</=
div></div></div>

--00000000000054a05805ffe3e60e--