I would like to create an RPM package for our company's Fedora users which contains a bunch of company document templates. It looks like these need to live in /usr/lib64/libreoffice/share/ or /usr/lib/libreoffice/share/ depending on whether it's a 64-bit or 32-bit platform. Therefore I can't build an architecture-independent package; I have to build architecture-specific packages. With identical content. This makes me sad, and I think it probably violates the FHS. Isn't there a place in /usr/share that I can put templates in? If not, please *could* there be? cf. http://bugzilla.redhat.com/1092570
Hi David, One can add templates in an extension. And adding that extension unpacked in the folder libreofficeshare/extensions/ will ensure that the templates are available. HTH, Cor
(In reply to comment #1) > libreofficeshare/extensions/ libreoffice/share/extensions/ of course
(In reply to comment #1) > Hi David, > > One can add templates in an extension. > And adding that extension unpacked in the folder > libreofficeshare/extensions/ > will ensure that the templates are available. Hi Cor, you are missing the point here. The problem is that libreoffice/share/extensions _itself_ is in an architecture-dependent location in distribution builds. E.g., on Fedora, it is /usr/lib/libreoffice/share/extensions for 32-bit arch and /usr/lib64/libreoffice/share/extensions for 64-bit arch. That means that if one packages some templates (or a gallery, or a java extension, FWIW), one cannot make the rpm "noarch". Instead, one has to build it for all arches, even if it is no actual need for that. This request is for real arch-independent extension dir, e.g., /usr/share/libreoffice/extensions .
Hi David, (In reply to comment #3) > you are missing the point here. The problem is that > libreoffice/share/extensions _itself_ is in an architecture-dependent > location in distribution builds. E.g., on Fedora, it is > /usr/lib/libreoffice/share/extensions for 32-bit arch and Sorry for being toooo short in my comment. I meant <install>/libreoffice/share/extensions/ so that is in the package. Does that help?
(In reply to comment #4) > Hi David, > > (In reply to comment #3) > > > you are missing the point here. The problem is that > > libreoffice/share/extensions _itself_ is in an architecture-dependent > > location in distribution builds. E.g., on Fedora, it is > > /usr/lib/libreoffice/share/extensions for 32-bit arch and > > Sorry for being toooo short in my comment. > I meant <install>/libreoffice/share/extensions/ > so that is in the package. Does that help? You are still missing the point :-) It is not a problem to get the path to install the extension into on different platforms. The problem is that I have to build a separate package for every platform, even if there is nothing platform-dependent in the extension itself! There is no other way, as files in /usr/lib* are considered platform-dependent. Platform-independent data packages would normally go somewhere into /usr/share. But there is no possibility for that in libreoffice.
Yes, we really need to have libreoffice look in /usr/share/libreoffice for architecture content, and libreoffice itself should install architecure independent content there. We are discussion this in packaging guidelines for Fedora here https://fedorahosted.org/fpc/ticket/465 and this is a concern.
Moving this to NEW as DTardon is involved and knows what's up (I think :) ). Thanks all.
Still, when you deploy an .oxt as admin, you can place it in the programs path. So the same extension (.oxt) applies to all platforms.. That's what we use in e.g. LibreLex
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
(In reply to QA Administrators from comment #9) > Please DO NOT > Update the version field ... > 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; Well, it's assume that "setting" the version field as instructed is not the same as "updating" the version field, and do so despite the otherwise contradictory instructions. This is still an issue in current versions, it seems.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Alessandro-B in IRC confirmed this for 6.3.5 at least.
Dear David Woodhouse, 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