https://bugs.kde.org/show_bug.cgi?id=526377

            Bug ID: 526377
           Summary: Build is not reproducible
    Classification: Plasma
           Product: Plasma Keyboard
      Version First unspecified
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

SUMMARY

Ideally, building the project twice on equivalent systems should result in the
same bit-by-bit result. This helps verify there's been no compromise of build
systems, especially when the project is part of a larger aggregate. You can
read more about this at https://reproducible-builds.org/.

plasma-keyboard seems quite close to being reproducible, but to suffer from an
issue similar to https://qt-project.atlassian.net/browse/QTBUG-137440:
potentially a missing explicit library dependency in the CMakeLists.txt of a
project using qml leads to a nondeterminism in what code is generated for it.

This issue was identified while reproducing the NixOS graphical installation
issue, and is tracked there as https://github.com/NixOS/nixpkgs/issues/566885

STEPS TO REPRODUCE

Build plasma-keyboard in an 'essentially equivalent' environment, but for
example varying the parallelism between '4' and '16'. 

OBSERVED RESULT

Different generated code / output.

Specifically,  the generated
build/src/styles/.rcc/qmlcache/breezestyle_breeze_style_qml.cpp from
./src/styles/breeze/style.qml is different. For 6.7.5, the expression not
consistently generated is for `aspectRatio at line 57, column 5`.

I'm not familiar enough with QML to go from here to actually figuring out what
might cause the nondeterminism - I'd be happy to test further if you can point
me in the right direction!

EXPECTED RESULT

The same generated code / output

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to