Temporary files written to predetermined location during build
Michael Stahl
mstahl at redhat.com
Wed Aug 9 12:35:40 UTC 2017
On 09.08.2017 14:27, Paul Menzel wrote:
>> Building LibreOffice 5.4.0.3 with one user, and then building it with another
>> user shows that it tries to write to the same paths in the temporary directory,
>> which of course fails.
>>
>> ```
>> […]
>> ------------------------------------
>> ... languages de_en-US ...
>> ... analyzing files ...
>> ... analyzing files with flag FILELIST ...
>> filelist
>> /dev/shm/bee-root/libreoffice/libreoffice-5.4.0.3-0/build/workdir/Package/xmlsec.filelist
>> is empty
>> ... analyzing files with flag SCPZIP_REPLACE ...
>> ... analyzing all directories for this product ...
>> ... analyzing links ...
>> ... analyzing unix links ...
>> ... creating profiles ...
>> fatal: Not a git repository (or any parent up to mount point /dev)
>> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
>> ERROR: Failure in installer.pm
>> ERROR: ERROR: Cannot open file
>> /tmp/LibreOffice//profiles/de_en-US/gid_Brand_Profile_Bootstrap_Ini/bootstraprc
>> for writing at
>> /dev/shm/bee-root/libreoffice/libreoffice-5.4.0.3-0/source/solenv/bin/modules/installer/files.pm
>> line 85.
that definitely looks like a bug, it should create that inside some
random subdirectory...
>> ... cleaning the output tree ...
>> ... removing directory /tmp/ooopackaging6idOna/i_647771502279265 ...
... like ^ this one ...
the bug must be somewhere in solenv/bin/modules/...
although i don't think i've ever seen a failure like this, and i build
multiple release branches concurrently every day... maybe it happens
only if you have translations enabled or something like that?
More information about the LibreOffice
mailing list