Did ADOdb is missing in last release?

[smaugain]

I’ve upgraded my egroupware server with release 17.1.20190222
The last release 17.1.20190222 don’t work on my Debian server 9,8.
I use the repository:
deb http://download.opensuse.org/repositories/server:/eGroupWare/Debian_8.0/ ./

The log talks about a « ADOdb » missing file:

[Wed Feb 27 08:43:13.428847 2019] [:error] [pid 28995] [client 192.168.1.68:52677] PHP Fatal error: require_once(): Failed opening required ‘/usr/share/egroupware/api/src/Db/ADOdb/adodb.inc.php’ (include_path=’/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Compress:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Crypt:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Crypt_Blowfish:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Date:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Exception:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Http:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Idna:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Imap_Client:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_ListHeaders:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Mail:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_ManageSieve:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Mapi:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Mime:/usr/share/egroupware/vendor/pear-pear.horde.org/Horde_Nls:/usr/share/egroupware/vendor/pear- in /usr/share/egroupware/api/src/loader.php on line 77
[Wed Feb 27 08:43:24.100882 2019] [:error] [pid 28997] [client 192.168.1.68:52682] PHP Warning: require_once(/usr/share/egroupware/api/src/Db/ADOdb/adodb.inc.php): failed to open stream: No such file or directory in /usr/share/egroupware/api/src/loader.php on line 77

The directory « /usr/share/egroupware/api/src/Db/ADOdb/ » has disappear.
I have to use the 17.1.20190111 release to repair the installation.
Did I miss something? Did you forget to include those files in the packages ?

Thanks,
Silvère Maugain

[RalfBecker]

ADOdb is loaded now via composer into vendor/egroupware/adodb-php/ directory.

You were probably logged in while updating. If you logout and in again, everything should be fine.

Ralf

[smaugain]

Thanks Ralf, it solve the problem.
An another question, do I need to logout the admin user at every upgrade ? Other users need to be log off ?
Silvère maugain

[RalfBecker]

That’s hard to answer in general.

For most updates that is not necessary:

• server-side php files just execute the new code and are no problem in most cases
• client-side javascript get loaded with next full reload or login

Of cause it does no harm, if everyone is logged out, when an update runs

Ralf