Description: Since LibO 6.2, LibO deb packages install the main libreoffice executable in /usr/local/bin rather than in /usr/bin as LibO 6.1.x deb packages were doing. This is a regression and a reopening of bug 89963 that had first been introduced with the packaging of LibO 4.4 and then fixed (notwithstanding the closing of that bug as invalid). Packages to be installed by means of the OS package manager (either provided as part of the OS distribution or externally) should not touch the local hierarchy. That is for the system administrator to deal with autonomously with no risk that any software installation/upgrade/removal done by system tools touches it at all, changing what the administrator had done in unexpected ways. Furthermore, on some systems /usr/local will be mounted read only or mounted from the network (being shared with other hosts). This is clarified in the debian and ubuntu policy documents. Section 9.1.2. says: "packages must not place any files in /usr/local, either by putting them in the file system archive to be unpacked by dpkg or by manipulating them in their maintainer scripts" and "because /usr/local and its contents are for exclusive use of the local administrator, a package must not rely on the presence or absence of files or directories in /usr/local for normal operation" The filesystem hierarchy standard Section 4.9 says: "The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be *safe from being overwritten* when the system software is updated. It may be used for programs and data that are shareable amongst a group of hosts". Please, build policy compliant deb files, to avoid breaking systems where: - /usr/local is readonly - /usr/local is shared among multiple hosts and local root cannot write it - /usr/local/bin is used to contain custom wrappers to libreoffice because of some local needs. There should be no negative consequence of putting libreoffice6.2 in /usr/bin given that the document foundation provided LibO debs will anyway need not to be installed side-to-side or mixed-with the debian/ubununtu provided LibO debs. The issue is also present with LibO 6.3.0 beta 1. Steps to Reproduce: See description Actual Results: See description Expected Results: See description Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: StartModule [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
Since this is debian specific, I'm wondering if this should be reported to the debian bugtracker instead ? @Rene, what is your opinion here ?
No, the debian bug tracker is not for the Deb files you ship....
Fwiw: https://packages.debian.org/experimental/arm64/libreoffice-core/filelist (or -common, &writer etc). And we don't ship a 6.2 anywhere (anymore, right now) except on https://people.debian.org/~rene/libreoffice/6.2/ ...
Taking a look here: https://packages.debian.org/search?keywords=libreoffice I see 6.2 only for Sparc64 in experimental Sergio: what's your processor? What's Debian verison do you use? How did you get deb files?
Sorry, my fault... I meant the deb packages built by TDF for debian and ubuntu...
In this case, it can be a pb with a dependency. I don't know if it can be considered as a bug.
I don't see how moving executables from /usr/bin/ to /usr/local/bin/ has anything to do with dependency. Are the TDF .deb packaging details (the debian/ subdirectory under source tree) avaiable anywhere public?
Can’t help here, uncc myself
Hello Sergio Callegari, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear sergio.callegari, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear sergio.callegari, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp
Sorry for missing a notification that action was required on my side. The issue is still present in fresh (LibO 6.4.4.1).
Dear sergio.callegari, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Issue still present in 7.3.2