You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dolibarr 17.0.0 is not usable because it requires php-imap that has been dropped by most of the distributions as php-imap was relying on the unmaintained uw-imap.
Dolibarr requires the migration of the emailcollector class towards using the webklex/php-imap library.
Environment Version
17.0.0
Environment OS
Arch Linux
Environment Web server
nginx
Environment PHP
php-legacy
Environment Database
mariadb
Environment URL(s)
No response
Expected and actual behavior
No response
Steps to reproduce the behavior
No response
Attached files
No response
The text was updated successfully, but these errors were encountered:
HLFH
added
the
Bug
This is a bug (something does not work as expected)
label
May 14, 2023
Note: Currently you have a warning at install, but you can install despite of this.
The option MAIN_IMAP_USE_PHPIMAP will be forced to true when Dolibarr will support php8.4
Well...I've tried to run rpm -Uvh dolibarr-19.0.1-0.4.noarch.rpm on a Fedora 39 system and I can't install the package because:
*It complains "php-imap" is required (but it can't be installed due to reasons explained in above posts)
*It complains "mysql-server" is required (but it can't be installed due to this package doesn´t exist in Fedora, its alternative -which is what I've installed- is MariaDB)
So, please, update the rpm package in order to get rid of these faulty errors. If not, Dolibarr can't be installed on Fedora systems!
Thanks!
PD: When trying to install rpm package with dnf, I get exactly the same error mentioned in #19967
Critical bug
Dolibarr 17.0.0 is not usable because it requires
php-imap
that has been dropped by most of the distributions asphp-imap
was relying on the unmaintaineduw-imap
.Dolibarr requires the migration of the emailcollector class towards using the webklex/php-imap library.
Environment Version
17.0.0
Environment OS
Arch Linux
Environment Web server
nginx
Environment PHP
php-legacy
Environment Database
mariadb
Environment URL(s)
No response
Expected and actual behavior
No response
Steps to reproduce the behavior
No response
Attached files
No response
The text was updated successfully, but these errors were encountered: