On Wed, Apr 22, 2020 at 7:01 PM Friedrich W. H. Kossebau
<kosse...@kde.org> wrote:
>
> Hi Dag,

Hi all,

>
> Am Mittwoch, 22. April 2020, 08:20:25 CEST schrieb Dag:
> > A few days ago CI build started to fail with this message:
> >
> > /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
> > /home/jenkins/install-prefix/lib64/libKF5XmlGui.so.5.70.0: undefined
> > reference to `QSystemLocale::QSystemLocale()@Qt_5.12.7_PRIVATE_API'
> > 08:34:10  collect2: error: ld returned 1 exit status
> > 08:34:10  make[2]: ***
> > [sheets/tests/CMakeFiles/BenchmarkPointStorage.dir/build.make:119:
> > sheets/tests/BenchmarkPointStorage] Error 1
> > 08:34:10  make[1]: *** [CMakeFiles/Makefile2:9166:
> > sheets/tests/CMakeFiles/BenchmarkPointStorage.dir/all] Error 2
> >
> > See:
> > https://build.kde.org/job/Calligra/job/calligra/job/kf5-qt5%20SUSEQt5.12/125
> > /console
> >
> > Any pointers?
>
> Needs a rerun of the respective dependencies build to resolve.
>
> Reason is that kxmlgui makes use of private Qt API (due to some needs). And
> the base image "SUSEQt5.12" had been updated to Qt 5.12.8 in the last days,
> but the set of dependenccies for the product "Calligra kf5-qt5 SUSEQt5.12"
> since then had not yet seen the weekly automatic build (or any manual) against
> the new base image, so the kxmlgui version part of the set of dependencies was
> still a one linking to private API version of Qt 5.12.7.
>
> I just started manually a build of that Dependencies set now:
> https://build.kde.org/job/Administration/job/
> Dependency%20Build%20Calligra%20kf5-qt5%20SUSEQt5.12/
> Once done will also trigger the respective calligra build,, which then
> hopefully no longer fails over that.
>
> From the build history dates it looks like Ben had tried to cover that before,
> but seems somehow the respective dependencies build still catched the old base
> image? At least I hit the same problem with "Applications" product before.

I've had a look and it seems the SUSE images were rebuilt on April 20,
while the dependencies build was done on April 19, which explains why
it used the old image.

We had previously rebuilt the image just 4 days earlier so I hadn't
expected any BIC issues :(

>
> Cheers
> Friedrich
>
>

Cheers,
Ben

Reply via email to