[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Tellico failing CI with exiv2 error
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-07-07 11:25:58
Message-ID: CA+XidOFZ-jzOtxpFnaoxpUqNgNQuKS7KDayMo9G1uNcpzc7LzA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jul 7, 2023 at 5:31 AM Friedrich W. H. Kossebau <kossebau@kde.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't that (among other things) the reason kexiv2 exists?
>
> Does not help if kexiv2 is not rebuilt and deployed as artifact when exiv2
> on
> the image changed in a incompatible version?
>

Correct.


>
> Triggered the needed manual rerun of kfilemetadata now, so the exiv plugin
> 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

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Fri, Jul 7, 2023 at 5:31 AM Friedrich W. H. \
Kossebau &lt;<a href="mailto:kossebau@kde.org">kossebau@kde.org</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Am Donnerstag, 6. Juli 2023, 18:43:50 CEST schrieb \
Kai Uwe Broulik:<br> &gt;   &gt; Probably libexiv2 on the CI host was updated to \
libexiv2 0.28, but<br> &gt;   &gt; KFileMetaData was not rebuilt. Automatic \
dependency tracking for<br> &gt; <br>
&gt; artifacts<br>
&gt; <br>
&gt;   &gt; from the CI system is obviously incomplete (or likely nonexistent).<br>
&gt; <br>
&gt; Isn't 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>  </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-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>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> <br>
Curious: are the images regenerated automatically or manually? in both cases, <br>
triggering also seed runs should be something part of that process? As we seem <br>
to run into such things again and again?<br></blockquote><div><br></div><div>The \
images are only rebuilt manually, to ensure we control when changes take \
place.</div><div><br></div><div>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&#39;t hit start on the ci-management jobs)</div><div>  \
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
Cheers<br>
Friedrich<br></blockquote><div><br></div><div>Cheers,</div><div>Ben  \
</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]