Your message dated Tue, 2 Nov 2021 10:34:29 +0100
with message-id <20211102093429.GA105785@devrim>
and subject line rddmarc sql Specified key was too long; max key length is 767
bytes for mariadb
has caused the Debian Bug report #880218,
regarding rddmarc sql Specified key was too long; max key length is 767 bytes
for mariadb
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
880218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880218
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: rddmarc
version: 1.3.2-2: stable
from file mkdmarc at /usr/share/doc/rddmarc
CREATE TABLE report (
serial int(10) unsigned NOT NULL AUTO_INCREMENT,
mindate timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP,
maxdate timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
domain *varchar(255)* NOT NULL,
org varchar(255) NOT NULL,
reportid varchar(255) NOT NULL,
PRIMARY KEY (serial),
UNIQUE KEY domain (domain,reportid)
);
error in mariadb not mysql
Logs error as:
ERROR 1071 (42000) at line 31: Specified key was too long; max key
length is 767 bytes
other errors in sql file might exist
for example non packaging of mysql_ip6.c - required or not
First time install of package and your sql syntax is widely used by
many other dmarc report tools
Aim to import emailed dmarc reports into sql from email
Can the sql reflect that non oracle software features is packaged in
debian if possible
Using debian Jessie [stable]
--- End Message ---
--- Begin Message ---
Closing as no longer reproducible.
--- End Message ---
