This issue isn't happening on macOS (old Bash) or the LibreOffice build bots. They may not be using this file Module_helpcontent2.mk.
I do not know if this would be helpful, but do you know which shell the build system is using? Either the find command is not finding the file or it is failing silently, or ln -sf is failing silently. Could you try putting set -xv at the top of bin/unpack-sources and getting the output? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1936254 Title: [snap] 7.2.0.1 build from tarball fails to find modules Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: The LO snap builds from the upstream tarballs. In this case, we're building from (in the snapcraft.yaml): http://download.documentfoundation.org/libreoffice/src/7.2.0/libreoffice-7.2.0.1.tar.xz The snap repo commit being built: https://git.launchpad.net/~hellsworth/+git/libreoffice- snap/commit/?id=d8a871e0d330928885201dcaafdec30dfb0c7b61 The build failure: https://launchpadlibrarian.net/548455036/buildlog_snap_ubuntu_focal_amd64_libreoffice-7.2-wip_BUILDING.txt.gz Locally, I've reproduced this failure and the modules are there, just not in the expected place. snapcraft-libreoffice # find . -name Module_helpcontent2.mk ./parts/libreoffice/build/src/libreoffice-help-7.2.0.1/helpcontent2/Module_helpcontent2.mk Looking through the libreoffice source changes, I believe this commit is the culprit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=f3b7dc649bc384be6000d98a87763cab26fe3f32 Reverting this commit in a patch gets past the issue and the build resumes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1936254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
