From: Luc Maisonobe <luc@spaceroots.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: libreoffice-common: libreoffice installs its own /ust/bin/soffice instead of using debian alternatives system Date: Fri, 14 Dec 2012 11:15:21 +0100 Package: libreoffice-common Version: 1:3.5.4+dfsg-4 Severity: normal Dear Maintainer, Since the fork between LibreOffice and OpenOffice.org (now Apache OpenOffice), both suites install /usr/bin/soffice directly. This completely prevents users to install both on the same computer, despite Debian does provide a fully mature way to support that: the alternatives. This is particularly annnoying since /usr/bin/soffice is already a link, so technically there is no point in forcing its destination at installation. With the current setting, attemptin to install the suite A when suite B has been installed beforehand fails (whatever are A and B, the problem is the same in both installation orders). The failure is that dpkg refuses to overwrite /usr/bin/soffce since it is own by the first package installed. Installation can be force using dpkg only using the --force-overwrite flag. This is really inconvenient and seems to contradict Debian installation rules. Even if people manage to install both packages using dpkg and --force-overwrite, upgrading also don't work and the same trick has to be reused to overwrite the link. LibreOffice (and Apache OpenOffice too) should use the alternative mechanism to set up the /usr/bin/soffice link.
Since the fork between LibreOffice and OpenOffice.org (now Apache OpenOffice), both suites install an /usr/bin/soffice link directly on Debian systems. This completely prevents users to install both on the same computer, despite Debian does provide a fully mature way to support that: the alternatives. This is particularly annnoying since /usr/bin/soffice is already a link, so technically there is no point in forcing its destination at installation. With the current setting, attempting to install the suite A when suite B has been installed beforehand fails (whatever are A and B, the problem is the same in both installation orders). The failure is that dpkg refuses to overwrite /usr/bin/soffice since it is owned by the first package installed. Installation can be force using dpkg only using the --force-overwrite flag. This is really inconvenient and seems to contradict Debian installation rules. Even if people manage to install both packages using dpkg and --force-overwrite, upgrading also don't work and the same trick has to be reused to overwrite the link. Apache OpenOffice (and LibreOffice too) should use the alternatives mechanism to set up the /usr/bin/soffice link on the Debian packaging system. Note that the same bug report has already been filed on the Debian bug tracker for LibreOffice (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695916).
There is no /usr/bin/soffice in the upstream packages. Btw, when you paste a bug description from the Debian bug tracker, could you remote any irrelevant parts?
> There is no /usr/bin/soffice in the upstream packages. Ok, it’s Debian specific also. > Btw, when you paste a bug description from the Debian bug tracker, > could you remote any irrelevant parts? I do not have any copied. Hard for me to really know what you need. I did not want to be stingy. Usually it is full rather that the report is succinct.
(In reply to Stéphane Aulery from comment #3) > > Btw, when you paste a bug description from the Debian bug tracker, > > could you remote any irrelevant parts? > > I do not have any copied. Hard for me to really know what you need. I did > not want to be stingy. Usually it is full rather that the report is succinct. We definitely do not need the e-mail header. Neither do we need the bug header (package, version, severity), becuase the info there is Debian-specific (version should be selected using the Version field).
How do i find my computer in windows 10,simple to type "my PC" in window search box https://mycomputerwindows10.com and easily to open my computer and search your any documents folder.