Bug#665487: dovecot-managesieved: Error upgrading dovecot with managesieved
Package: dovecot-managesieved
Version: 1:2.0.18-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When upgrading dovecot from 2.0.15-1 to 1:2.0.18-1 the configuration failed
withe errors related to managesieved.
Here is the relevant output from the 'aptitude safe-upgrade':
-- BEGIN --
Unpacking replacement dovecot-managesieved ...
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_settings.so
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 9:
Unknown setting: managesieve_notify_capability
Starting IMAP/POP3 mail server: dovecotdoveconf: Error: Module is for different
version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_settings.so
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 9:
Unknown setting: managesieve_notify_capability
failed!
invoke-rc.d: initscript dovecot, action start failed.
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_settings.so
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 9:
Unknown setting: managesieve_notify_capability
Starting IMAP/POP3 mail server: dovecotdoveconf: Error: Module is for different
version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so
doveconf: Error: Module is for different version 2.0.18:
/usr/lib/dovecot/modules/settings/libmanagesieve_settings.so
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 9:
Unknown setting: managesieve_notify_capability
failed!
invoke-rc.d: initscript dovecot, action start failed.
dpkg: error processing
/var/cache/apt/archives/dovecot-managesieved_1%3a2.0.18-1_i386.deb (--unpack):
subprocess new post-removal script returned error exit status 1
configured to not write apport reports
[..]
Errors were encountered while processing:
/var/cache/apt/archives/dovecot-managesieved_1%3a2.0.18-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
[..]
Errors were encountered while processing:
dovecot-core
dovecot-sieve
dovecot-imapd
dovecot-common
dovecot-ldap
-- END --
At this point dovecot seems to refuse to start.
After commenting the line 9 in dovecot.conf starting with
'managesieve_notify_capability' and rerunning safe-upgrade the following errors
were encountered:
-- BEGIN --
Preparing to replace dovecot-managesieved 1:2.0.15-1 (using
.../dovecot-managesieved_1%3a2.0.18-1_i386.deb) ...
doveconf: Error: Module is for different version 2.0.15:
/usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so
doveconf: Error: Module is for different version 2.0.15:
/usr/lib/dovecot/modules/settings/libmanagesieve_settings.so
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 10:
Unknown setting: managesieve_sieve_capability
-- END --
After commenting out line 10 in the configuration file and restarting dovecot
the mail server worked again.
Relevant lines in dovecot.conf:
9: managesieve_notify_capability = mailto
10 managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date imapflags
Expected outcome: upgrading would have worked without causing dovecot to fail
to start.
Actual outcome: manual intervention was required to revive dovecot
Classification: grave, because upgrade left dovecot unable to start
Sincerly,
Laurens
-- Package-specific info:
dovecot configuration
-
# 2.0.18: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-1-686-pae i686 Debian wheezy/sid ext3
auth_mechanisms = plain login
disable_plaintext_auth = no
log_timestamp = %Y-%m-%d %H:%M:%S
login_greeting = Courier-IMAP ready.
mail_location = maildir:/var/mail/%d/%n/Maildir
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave imapflags
namespace {
inbox = yes
location =
prefix = INBOX.
type = private
}
passdb {
args = /etc/dovecot/dovecot-ldap-uid.conf
driver = ldap
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
plugin {
sieve_extensions
Bug#639733: wordpress: Wordpress breaks TinyMCE install
Package: wordpress Version: 3.2.1+dfsg-1 Severity: critical Justification: breaks unrelated software Upgrading from 3.0.5+dfsg-1 to 3.2.1+dfsg-1 causes plugin files to be written to /usr/share/tinymce which is partily symlinked from /usr/share/wordpress/wp-includes/js/tinymce/ this in turns causes TinyMCE to BREAK on Firefox 6 and Chrome 13. Which in turn breaks applications such as Roundcube hence the critical severity. Wordpress should NEVER write files in another packages directory! The only way to fix this is to force the removal of tinymce manually delete the directory and then reinstall tinymce. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wordpress depends on: ii apache2-mpm-prefork 2.2.19-1Apache HTTP Server - traditional n ii libapache2-mod-php5 5.3.6-13server-side, HTML-embedded scripti ii libjs-cropper1.2.1-2 JavaScript image cropper UI ii libjs-jquery 1.6.2-1 JavaScript library for dynamic web ii libjs-jquery-form4-1 jQuery Form Plugin ii libjs-jquery-ui 1.8.ooops.14+dfsg-1 JavaScript UI library for dynamic ii libjs-prototype 1.7.0-2 JavaScript Framework for dynamic w ii libjs-scriptaculous 1.9.0-2 JavaScript library for dynamic web ii libphp-phpmailer 5.1-1 full featured email transfer class ii libphp-simplepie 1.2-3 RSS and Atom feed parsing in PHP ii libphp-snoopy1.2.4-2 Snoopy is a PHP class that simulat ii mysql-client-5.1 [my 5.1.58-1MySQL database client binaries ii php5 5.3.6-13server-side, HTML-embedded scripti ii php5-gd 5.3.6-13GD module for php5 ii php5-mysql 5.3.6-13MySQL module for php5 ii tinymce 3.4.3.2+dfsg0-1 platform independent web based Jav Versions of packages wordpress recommends: ii wordpress-l10n 3.2.1+dfsg-1 weblog manager - language files Versions of packages wordpress suggests: ii mysql-server-5.1 [mysql-serve 5.1.58-1 MySQL database server binaries and -- Configuration Files: /etc/wordpress/wp-config.php changed [not included] -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625484: libdb4.8: 'Build signature doesn't match environment' in 4.8.30-6
Package: libdb4.8 Version: 4.8.30-4 Severity: critical Justification: breaks the whole system When upgrading libdb4.8 from version 4.8.30-4 to 4.8.30-6 slapd fails to start. Executing e.g. slapcat returns the following error: --- BEGIN --- # slapcat bdb(dc=blankersfamily,dc=com): Build signature doesn't match environment bdb_db_open: database dc=blankersfamily,dc=com cannot be opened, err -30971. Restore from backup! backend_startup_one (type=bdb, suffix=dc=blankersfamily,dc=com): bi_db_open failed! (-30971) slap_startup failed --- END --- Because my systems relies on LDAP for user authentication this makes the entire system unusable (hence the critical). Downgrading to 4.8.30-4 makes slapd and slapcat work again. A quick fix would be greatly appreciated, Laurens -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libdb4.8 depends on: ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib libdb4.8 recommends no packages. libdb4.8 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613586: roundcube: Missing tables and columns after upgrade
On 16-2-2011 8:38, Vincent Bernat wrote: In the 0.5-1 upgrade file, there is some ALTER TABLE ... FOREIGN KEY .. ON DELETE CASCADE ON UPDATE CASCADE. I think the whole file was played in a transaction which rolled back. Could you execute them as well and see if this fixed your issue? Executing the ALTER TABLE ... DROP FEREIGN KEY and ALTER TABLE ... ADD CONTRAINT ... FOREIGN KEY do the trick. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576568: scala: Unable to establish connection to compilation daemon
Package: scala Version: 2.7.7.dfsg-4 Severity: grave Justification: renders package unusable Using scala to run a scala script results in the following error (after a number of seconds): Unable to establish connection to compilation daemon Afterwards 24 java processes have spanned. Every time I try to run the script again another 24 processes spawn and the error message is the same. Executing fsc with verbose flag gives the following output: -- BEGIN -- $ fsc -verbose hello.scala [Server arguments: -d /home/laurensb/scala/. -verbose /home/laurensb/scala/hello.scala] [VM arguments: ] [Temp directory: /home/laurensb/tmp] [Port number: 40020] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 40020 failed; re-trying...] [Port number: 40020] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 40020 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 43867] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 43867 failed; re-trying...] [Port number: 43867] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 43867 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 48830] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 48830 failed; re-trying...] [Port number: 48830] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 48830 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 46824] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 46824 failed; re-trying...] [Port number: 46824] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 46824 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 54642] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 54642 failed; re-trying...] [Port number: 54642] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 54642 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 35835] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 35835 failed; re-trying...] [Port number: 35835] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 35835 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 52572] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 52572 failed; re-trying...] [Port number: 52572] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 52572 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 44152] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 44152 failed; re-trying...] [Port number: 44152] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 44152 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 49130] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 49130 failed; re-trying...] [Port number: 49130] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 49130 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 46759] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 46759 failed; re-trying...] [Port number: 46759] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 46759 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 39028] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 39028 failed; re-trying...] [Port number: 39028] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 39028 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 48718] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 48718 failed; re-trying...] [Port number: 48718] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 48718 failed; re-trying...] [Executed command: scala scala.tools.nsc.CompileServer] [Port number: 52586] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 52586 failed; re-trying...] [Port number: 52586] java.net.SocketException: Network is unreachable [Connecting to compilation daemon at port 52586 failed; re-trying...] [Executed command: scala
Bug#576568: [Pkg-scala-maint] Bug#576568: scala: Unable to establish connection to compilation daemon
On 5-4-2010 19:58, Mehdi Dogguy wrote: Can you please tell what does /etc/sysctl.d/bindv6only.conf contain? If the value is 1, can you try to: 1) sudo sed -i 's/net.ipv6.bindv6only\ =\ 1/net.ipv6.bindv6only\ =\ 0/' \ /etc/sysctl.d/bindv6only.conf sudo invoke-rc.d procps restart 2) Then, run scala/fsc as usual and see if the bug is still there. Cheers, Hi Mehdi, Changing the option from 1 (default) to 0 does solve the problem! So it this a scala issue, (Sun) java issue, Debian configuration issue or a kernel issue? Laurens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576568: [Pkg-scala-maint] Bug#576568: scala: Unable to establish connection to compilation daemon
Good! Thanks for the quick test! Welcome :-) I think it's rather a JVM issue which was also experienced with OpenJDK (See #560056 and #575163 for reference). I see that your currently used JVM is Sun's one. Can you please perform some other tests? 1) test with OpenJDK (≥ 6b18~pre3-1) and net.ipv6.bindv6only=1 2) test with OpenJDK (≥ 6b18~pre3-1) and net.ipv6.bindv6only=0 (this solution should work anyway) and see if the problems goes away. Scala does work with OpenJDK version 6b18~pre4-1 both with bindv6only enabled and disabled. So it seems that a bug fix in OpenJDK solves the problem. Laurens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572265: horde3: Upgrade to php 5.3 results in fatal error
Package: horde3 Version: 3.3.6+debian0-2 Severity: grave Justification: renders package unusable After upgrading to PHP 5.3.1-5 (testing) Horde stops working and displays the following errors when navigating to the main page: -- BEGIN -- Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/php/Log.php on line 168 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Notification.php on line 64 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Perms.php on line 455 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Perms.php on line 462 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Perms/datatree.php on line 82 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/horde3/lib/Horde/Prefs.php on line 847 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/php/Log.php:168) in /usr/share/horde3/index.php on line 92 -- END -- It looks like PHP 5.3 deprecates some functionality and is very vocal about it causing a redirects not to work. Not that the problem is not limited to Horde but also effects any application using Pear Log. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages horde3 depends on: ii apache2-mpm-prefork [httpd] 2.2.14-5 Apache HTTP Server - traditional n ii libapache2-mod-php5 5.3.1-5server-side, HTML-embedded scripti ii libjs-scriptaculous 1.8.3-1JavaScript library for dynamic web ii php-log 1.10.0-1 Log module for PEAR ii php-mail 1.1.14-2 PHP PEAR module for sending email ii php-mail-mime 1.5.3-0.1 PHP PEAR module for creating MIME ii php5-gd 5.3.1-5GD module for php5 ii php5-mcrypt 5.3.1-5MCrypt module for php5 Versions of packages horde3 recommends: ii fckeditor 1:2.6.6-1 rich text format javascript web ed ii locales 2.10.2-6 Embedded GNU C Library: National L ii logrotate 3.7.8-4Log rotation utility ii php-date 1.4.7-1PHP PEAR module for date and time ii php-db1.7.13-2 PHP PEAR Database Abstraction Laye ii php-file 1.3.0-1PHP Pear modules for common file a ii php-mdb2 2.5.0b2-1 PHP PEAR module to provide a commo ii php-mdb2-driver-mysql 1.5.0b2-1 PHP PEAR module to provide a MySQL ii php-mdb2-driver-sqlite1.5.0b2-1 PHP PEAR module to provide a SQLit ii php-services-weather 1.4.2-2acts as an interface to various on ii php5-cli 5.3.1-5command-line interpreter for the p ii php5-ldap 5.3.1-5LDAP module for php5 ii php5-mysql5.3.1-5MySQL module for php5 ii php5-pgsql5.3.1-5PostgreSQL module for php5 ii tinymce 3.2.7-1platform independent web based Jav ii tinymce2 2.1.3-1platform independent web based Jav Versions of packages horde3 suggests: pn chora2 none (no description available) pn enscript none (no description available) pn gettext none (no description available) pn gollem none (no description available) ii imp4 4.3.6+debian0-2 webmail component for horde framew pn kronolith2 none (no description available) ii libgeoip11.4.6.dfsg-19 A non-DNS IP-to-country resolver l pn libwpd-tools none (no description available) pn mnemo2 none (no description available) pn php-net-imap none (no description available) pn php5-auth-pamnone (no description available) ii php5-common [php5-mhash] 5.3.1-5 Common files for packages built fr pn ppthtml none (no description available) pn rpm none (no description available) pn source-highlight none (no description available) ii turba2 2.3.3+debian0-3 contact management component for h pn unrtfnone (no description available) pn webcpp none (no description available) pn wv none (no description available)
Bug#537242: (no subject)
This bug has been blocking the migration of php 5.2.10 to testing for a month now. Please fix the dependency. Laurens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
