[Pkg-mailman-hackers] Bug#891691: Bug#891691: mailman3-core: Cannot install mailman3-suite with mysql database
Colin Turner
ct at piglets.com
Thu Mar 1 11:00:02 UTC 2018
Good morning Pierre-Elliott,
Thanks for your speedy response.
[..]
>> File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 250, in execute
>> self.errorhandler(self, exc, value)
>> File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
>> raise errorvalue
>> django.db.utils.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes')
>> dpkg: error processing package mailman3-suite (--configure):
>> installed mailman3-suite package post-installation script subprocess returned error exit status 1
>> Errors were encountered while processing:
>> mailman3-suite
>
> This error is a bummer. It comes from innoDB implementations of SQL servers.
> The main idea is that there is a limited length for the index deployment on
> varchar fields, and one field in django-allauth/mailman is 255 chars, which
> is more than 767 bytes (191 chars).
>
> What SQL server do you use?
Here are the mysql/maria packages on that box:
oldgondolin:/home/colin# dpkg --list | grep -E "mysql|maria"
ii akonadi-backend-mysql 4:16.04.3-6 all MySQL storage backend for Akonadi
ii default-mysql-client 1.0.3 all MySQL database client binaries (metapackage)
ii default-mysql-server 1.0.3 all MySQL database server binaries and system database setup (metapackage)
ii dovecot-mysql 1:2.2.33.2-1 i386 secure POP3/IMAP server - MySQL support
ii libaprutil1-dbd-mysql:i386 1.6.1-1 i386 Apache Portable Runtime Utility Library - MySQL Driver
ii libdbd-mysql-perl 4.041-2+b1 i386 Perl5 database interface to the MariaDB/MySQL database
ii libmariadbclient18:i386 1:10.1.29-6 i386 MariaDB database client library
ii libmysqlclient16 5.1.66-0+squeeze1 i386 MySQL database client library
ii libmysqlclient18:i386 5.6.30-1 i386 MySQL database client library
ii libqt4-sql-mysql:i386 4:4.8.7+dfsg-11 i386 Qt 4 MySQL database driver
ii libqt5sql5-mysql:i386 5.9.2+dfsg-6 i386 Qt 5 MySQL database driver
ii mariadb-client-10.1 1:10.1.29-6 i386 MariaDB database client binaries
ii mariadb-client-core-10.1 1:10.1.29-6 i386 MariaDB database core client binaries
ii mariadb-common 1:10.1.29-6 all MariaDB common metapackage
ii mariadb-server-10.1 1:10.1.29-6 i386 MariaDB database server binaries
ii mariadb-server-core-10.1 1:10.1.29-6 i386 MariaDB database core server files
ii mysql-common 5.8+1.0.3 all MySQL database common files, e.g. /etc/mysql/my.cnf
rc mysql-server-5.1 5.1.61-3 i386 MySQL database server binaries and system database setup
rc mysql-server-5.5 5.5.43-0+deb8u1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.6 5.6.30-1 i386 MySQL database server binaries and system database setup
rc mysql-server-5.7 5.7.17-1 i386 MySQL database server binaries and system database setup
ii php-mdb2-driver-mysql 1.5.0b4-2 all mysql MDB2 driver
ii php-mysql 1:7.0+57 all MySQL module for PHP [default]
ii php5-mysql 5.6.30+dfsg-0+deb8u1 i386 MySQL module for php5
ii php7.0-mysql 7.0.27-1 i386 MySQL module for PHP
ii python-mysqldb 1.3.10-1 i386 Python interface to MySQL
ii python3-pymysql 0.7.11-1 all Pure-Python MySQL Driver - Python 3.x
ii roundcube-mysql 1.3.3+dfsg.1-2 all metapackage providing MySQL dependencies for RoundCube
Interesting to hear what the problem is, I didn’t know of this Django potential problem. I have my own Django web app that was deployed on some other Debian boxes, in this case mariadb-server-10.1=10.1.26-0+deb9u1, so I’ll keep an eye out for that one.
You can see from above this box has history, with lots of mysql server transitions. Is there anything useful I can test for you in this regard? The box in question is now decommissioned but still online, so I can do plenty of tests (before hopefully installing mailman3 on my new box).
> Regarding the missing dependency, we'll add it as soon as possible. :)
Awesome, thank you so much.
One other thing, did you note the issue I had with the init script. Is there something I can help you with there? If you think it’s a real problem and not some side effect I can file a separate bug report.
Kind regards,
CT.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/attachments/20180301/e9bba089/attachment.html>
More information about the Pkg-mailman-hackers
mailing list