[Bug 1683229] Re: package mariadb-server-10.1 failed to install since mysql-server-5.7 isn't purged

Note that purging MySQL 5.7 server prior Installing MariaDB 10.1 won't work neither due to apparmor profile. At least, MariaDB server won't start. See https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1806263 Env: Ubuntu Bionic Beaver ;) -- You received this bug notification because

[Bug 1806263] [NEW] MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed

Public bug reported: If you purge MySQL 5.7 server, then install MariaDB 10.1, that last won't start due to wrong AppArmor profile. CURRENT RESULT ON mariadb-server-10.1 package installation ... Job for mariadb.service failed because a timeout was exceeded. See "systemctl status

[Bug 1702677] Re: Add an option to override version prefix (~ubuntu)

We need that too ;) That's really a valuable addition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702677 Title: Add an option to override version prefix (~ubuntu) To manage notifications about

[Bug 1633754] Re: dirmngr is used as daemon

@Julian So, if I understand well, you want remove the APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE environment variable but keep the warning when APT-KEY detect that its output is captured? That would be tedious for us.. We do not want such a warn in our case. We capture STDOUT for the purpose of

[Bug 1633754] Re: dirmngr is used as daemon

@Julian Thank for your advise. So basically, putting keys into the trusted.gpg.d directory should be sufficient to make APT happy? I never tried that way, even worse (shame on me), I was not aware of that possibility... Regarding the environment variable, I really don't understand why we are

[Bug 1633754] Re: dirmngr is used as daemon

We get identical problem in our software installer. It seem that dirmngr processes never goes away. We workaround the issue by terminating the process manually: {code} =item addRepositories( @repositories ) See iMSCP::DistPackageManager::Interface::addRepositories() Param list @repositories

Re: [Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

are using mailman on shared hosting where there are huge of lists. This bug is important to my eyes. -- Laurent Declercq iHMS/i-MSCP CEO & Lead Developer This message and any attachment are intended solely for the addressee

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

@msapiro I can confirm that the fixes solve the problems. Thank you for your involvement here. That is much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696066 Title: Postfix

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

** Description changed: Dear project leader At least in version 2.1.23, there is a bug regarding permissions set for Mailman data/aliases table and Mailman data/virtual-mailman map when these files are created from scratch. Here I describe the current behavior for the Mailman

[Bug 1696066] Re: Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

** Description changed: Dear project leader At least in version 2.1.23, there is a bug regarding permissions set for Mailman data/aliases table and Mailman data/virtual-mailman map when these files are created from scratch. Here I describe the current behavior for the Mailman

[Bug 1696066] [NEW] Postfix module - Mailman wrapper - Couldn't write data/aliases.db and data/virtual-mailman.db files

Public bug reported: Dear project leader At least in version 2.1.23, there is a bug regarding permissions set for Mailman data/aliases table and Mailman data/virtual-mailman map when these files are created from scratch. Here I describe the current behavior for the Mailman data/aliases table

[Bug 1695610] Re: Test missing in lists_lists leading to wrong listing when using -V option

** Also affects: mailman (Ubuntu) Importance: Undecided Status: New ** Also affects: mailman (Debian) Importance: Undecided Status: New ** Description changed: Dear project leader, When we list the lists for specific virtualhost, a wrong result can be printed-out in

[Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

@Mark Sapiro Thank for your answer and the fix ;) That is much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694384 Title: Missing mailman-owner@VIRTUAL_DOMAIN entry in

[Bug 1694384] Re: Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman

** Summary changed: - Missing list owner email alias in data/virtual-mailman + Missing mailman-owner@VIRTUAL_DOMAIN entry in data/virtual-mailman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694384

[Bug 1694384] [NEW] Missing list owner email alias in data/virtual-mailman

Public bug reported: Dear project leader, In the Mailman version 2.1.21, you released a fix regarding Mailman- Postfix:  - Mailman-Postfix integration will now add mailman@domain entries in   data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS   which is a

[Bug 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

Both mysql-server-5.5 and mysql-server-5.6 packages (e.g. under Trusty Thar) provide a sysvinit script and an upstart job for mysql. The problem here is that the maintainer has a very strange approach: 1. The sysvinit script links are symply removed in the postinstall script using update-rc.d

[Bug 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

Both mysql-server-5.5 and mysql-server-5.6 packages (e.g. under Trusty Thar) provide a sysvinit script and an upstart job for mysql. The problem here is that the maintainer has a very strange approach: 1. The sysvinit script links are symply removed in the postinstall script using update-rc.d

[Bug 1326428] Re: clash of upstart and sysvinit scripts

*** This bug is a duplicate of bug 1273462 *** https://bugs.launchpad.net/bugs/1273462 To be more clear: Both mysql-server-5.5 and mysql-server-5.6 packages (e.g. under Trusty Thar) provide a sysvinit script and an upstart job for mysql. The problem here is that the maintainer has a very

[Bug 1326428] Re: clash of upstart and sysvinit scripts

*** This bug is a duplicate of bug 1273462 *** https://bugs.launchpad.net/bugs/1273462 To be more clear: Both mysql-server-5.5 and mysql-server-5.6 packages (e.g. under Trusty Thar) provide a sysvinit script and an upstart job for mysql. The problem here is that the maintainer has a very

[Bug 1542174] Re: Could not install / Could not start service

Seem fixed by: courier-authlib (0.66.4-3) unstable; urgency=medium * Check and create courier user in authdaemon package in case courier-base is not installed first (LP#1542174) -- Ondřej Surý Fri, 05 Feb 2016 09:58:26 +0100 But a question still remains there: Why

[Bug 1542174] Re: Could not install / Could not start service

More details: # root@xenial:/usr/local/src/imscp# LANG=C aptitude install courier-authdaemon The following NEW packages will be installed: courier-authdaemon 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need

[Bug 1542174] [NEW] Could not install / Could not start service

Public bug reported: Latest version of the courier-authdaemon package as provided in Ubuntu Xenial repository cannot be installed due to the following bug: The 'courier' user/group in the /usr/lib/tmpfiles.d/courier- authdaemon.conf file doesn't exists. It should be replaced by the 'daemon'

[Bug 1542174] Re: Could not install / Could not start service

@ Ondřej Surý Loving when you push changes without any test... You should be killed. courier-authlib (0.66.4-2) unstable; urgency=medium * Convert the d/copyright into machine-readable file and add license for authldaplib.c * Use invoke-rc.d to restart authdaemon on mysql and postgresql

[Bug 1002510] Re: package courier-authlib-mysql 0.63.0-3.1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

Same here. Upgrade failed on xenial. Well, to fix the problem, I've created the expected file manually and run apt-get install -f. Once done, I've purged the package and reinstalled it. Then installation failed because the service authdaemon could not start. This is due to the new systemd

[Bug 1538284] Re: Unescaped left brace in regex is deprecated

Wrong package reported. The right package is libpam-runtime root@xenial:/usr/local/src/imscp# LANG=C aptitude show libpam-runtime Package: libpam-runtime State: installed Automatically installed: no Multi-Arch: foreign Version: 1.1.8-3.1ubuntu3 Priority: required Section: admin

[Bug 1538284] [NEW] Unescaped left brace in regex is deprecated

Public bug reported: When installing postgresql on Ubuntu 16.04 (xenial), the following warning are raised: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(?https://bugs.launchpad.net/bugs/1538284 Title: Unescaped left brace in regex is

[Bug 1242376] Re: reload php5-fpm crashes

I agreed totally with Renan... PHP5-FPM reload is broken meaning that restart is mandatory ATM (which is not a way to go for shared hosting environment where configuration should be reloaded without having to do a full restart)... -- You received this bug notification because you are a member of

[Bug 1242376] Re: reload php5-fpm crashes

I agreed totally with Renan... PHP5-FPM reload is broken meaning that restart is mandatory ATM (which is not a way to go for shared hosting environment where configuration should be reloaded without having to do a full restart)... -- You received this bug notification because you are a member of

[Bug 759974] Re: PHP Fatal error: Class 'PEAR' not found in /usr/share/roundcube/program/include/iniset.php on line 132

Hello community ; I've encountered an identical problem on Ubuntu 12.4. To solve it, I've only un-commented the include_path parameter (include_path = .:/usr/share/php) into the /etc/php5/apache2/php.ini and restarted the apache2 service. cheers -- You received this bug notification because