Intentamos instalar Open365 en Ubuntu 16.04 sin éxito.
Al intentar instalar a través de dpkg obtenemos el siguiente error:
sudo dpkg -i libqt4-core_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8_amd64.deb
Selecting previously unselected package libqt4-core.
(Reading database ... 221375 files and directories currently installed.)
Preparing to unpack libqt4-core_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8_amd64.deb ...
Unpacking libqt4-core (4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8) ...
dpkg: dependency problems prevent configuration of libqt4-core:
libqt4-core depends on libqt4-dbus (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqt4-dbus:amd64 on system is 4:4.8.7+dfsg-5ubuntu2.
libqt4-core depends on libqt4-network (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqt4-network:amd64 on system is 4:4.8.7+dfsg-5ubuntu2.
libqt4-core depends on libqt4-script (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqt4-script:amd64 on system is 4:4.8.7+dfsg-5ubuntu2.
libqt4-core depends on libqt4-test (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqt4-test:amd64 on system is 4:4.8.7+dfsg-5ubuntu2.
libqt4-core depends on libqt4-xml (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqt4-xml:amd64 on system is 4:4.8.7+dfsg-5ubuntu2.
libqt4-core depends on libqtcore4 (= 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu8); however:
Version of libqtcore4:amd64 on system is 4:4.8.7+dfsg-6+b1.
dpkg: error processing package libqt4-core (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libqt4-core
Esto también falla al intentar utilizar gdebi y el Centro de software.
Tenga en cuenta que todos los intentos de instalar las dependencias manualmente también fallan.
Respuesta1
Éste es el problema. Parece que los desarrolladores están en lo cierto. https://support.open365.io/index.php/en/forum/englishsuport/25-problem-with-client-install-on-ubuntu-16-04-lts?limitstart=0
Respuesta2
Después de investigar un poco, llegamos a la conclusión de que se trata de un problema conocido que debería solucionarse en la próxima versión de las actualizaciones de Ubuntu 16.04: