Error when zentyal-core unpacking

[emilien.macchi@…]

I use Ubuntu 12.04 Precise, and i want to setup Zentyal 2.3.

I do "sudo apt-get install zentyal*", and i have an error when zentyal-core is unpacked :

Unpacking zentyal-core (from .../zentyal-core_2.3.1_all.deb) ... dpkg: error processing /var/cache/apt/archives/zentyal-core_2.3.1_all.deb (--unpack):

trying to overwrite '/usr/share/perl5/EBox/SOAPClient.pm', which is also in package libebox 2.0.8-0ubuntu1

No apport report written because MaxReports? is reached already

dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Errors were encountered while processing:

/var/cache/apt/archives/zentyal-core_2.3.1_all.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

I try "sudo apt-get -f upgrade", with same error for result.

I'm looking forward to test the new version !

[jamor@…]

Hello Emilien Macchi,

the upgrade from 2.0 to 3.0 is not supported. In fact the upgrade from 2.0 to 2.2 is not automatic and needs to use the update-tool so from 2.0 to 3.0 it would be even more problematic.

If you want to install 2.3, it would be better to purge all the previous 2.0 Zentyal installation and install 2.3 then.

Regards,

Javier

[emilien.macchi@…]

Hi Javier, thank you for the response.

But i was on a fresh Ubuntu 12.04 (from HP Cloud), without any Zentyal software.

Anyway, i have tested today a fresh install, and i don't have the issue anymore, but a new one : i cannot login to the dashboard, my login (which is in the admin group) does not work !

If you have any idea, you can contact me by e-mail directly.

Regards,

Emilien

[zentyal@…]

Hi Emilien,

in Ubuntu 12.04 you will need to add your user to sudo

group, since there is no admin group in 12.04

adduser MYUSER sudo

[jamor@…]

Hello,

as for the original error was due to a error in the postinst script. The workaround is to kill all process owned by 'ebox' before the upgrade.

A ubuntu package with the fix will be released soon.

[ira@…]

Still getting this issue on 2.3-2 amd64 on a fresh install running in VirtualBox?. Found that rebooting before installing any modules fixes this issue aswell. killing all ebox processes doesn't work for me.