<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hello,<br>
Memory is still 512 MB?<br>
Thing that pops to my eye in 10.11 is<br>
mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio
read' returned OS error 0. Cannot continue operation <br>
As on 10.5 is used fsync not O_DIRECT which is default from 10.6 you
can try (not promising anything) get it 10.11 working (more slowly
though) with:<br>
<code>innodb_flush_method=fsync</code><br>
<code>More on change here:<br>
</code><br>
<code><a class="moz-txt-link-freetext" href="https://mariadb.com/kb/en/innodb-system-variables/#innodb_use_native_aio">https://mariadb.com/kb/en/innodb-system-variables/#innodb_use_native_aio</a><br>
</code><br>
Sincerely,<br>
Tuukka<br>
<p><br>
</p>
<div class="moz-cite-prefix">Scott Barker kirjoitti 21.12.2023 klo
0.20:<br>
</div>
<blockquote type="cite" cite="mid:ZYNoltdHpFfx1qDn@mostlylinux.ca">On
my secondard ARM NAS, I downgraded from bookworm to bullseye, and
installed mariadb 10.5 from scratch (no pre-existing
/var/lib/mysql or /etc/mysql). Everything worked without issues.
From syslog:
<br>
<br>
mysqld_safe: Starting mariadbd daemon with databases from
/var/lib/mysql
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] Starting MariaDB
10.5.21-MariaDB-0+deb11u1 source revision
bed70468ea08c2820647f5e3ac006a9ff88144ac as process 2250
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Uses event mutexes
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Compressed tables use
zlib 1.2.11
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Number of pools: 1
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using generic crc32
instructions
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Using Linux native
AIO
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Initializing buffer
pool, total size = 134217728, chunk size = 134217728
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Completed
initialization of buffer pool
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 128 rollback segments
are active.
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Creating shared
tablespace for temporary tables
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Setting file
'./ibtmp1' size to 12 MB. Physically writing the file full; Please
wait ...
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: File './ibtmp1' size
is now 12 MB.
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: 10.5.21 started; log
sequence number 45079; transaction id 20
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] Plugin 'FEEDBACK' is
disabled.
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Loading buffer
pool(s) from /var/lib/mysql/ib_buffer_pool
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] InnoDB: Buffer pool(s) load
completed at 231220 7:58:07
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] Server socket created on IP:
'127.0.0.1'.
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] Reading of all Master_info
entries succeeded
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] Added new Master_info '' to
hash table
<br>
mysqld: 2023-12-20 7:58:07 0 [Note] /usr/sbin/mariadbd: ready for
connections.
<br>
mysqld: Version: '10.5.21-MariaDB-0+deb11u1' socket:
'/run/mysqld/mysqld.sock' port: 3306 Debian 11
<br>
<br>
I then proceeded to upgrade from bookworm all packages containing
libraries to which /usr/sbin/mariadbd and /usr/lib/mysql/plugin/*
were linked, one at a time, restarting mariadb after each package
was installed, and there were no issues.
<br>
<br>
I then upgraded the rest of the system to bookworm, a few packages
at a time, excluding the mariadb packages. I restarted mariadb
after each batch of packages, and there were no issues, including
after reboot into the new kernel.
<br>
<br>
I then renamed /var/lib/mysql to /var/lib/mysql.bak and ran:
<br>
<br>
dpkg-reconfigure -plow mariadb-server-10.5
mariadb-server-core-10.5
<br>
<br>
Again, no issues - /var/lib/mysql was re-created and mariadbd
started just fine, with the same syslog entries as above.
<br>
<br>
I then copied /var/lib/mysql to /var/lib/mysql-10.5 and upgraded
mariadb with:
<br>
<br>
apt upgrade mariadb-server-10.5
<br>
<br>
Here is the entire output, you can see the errors at the end:
<br>
<br>
Reading package lists... Done
<br>
Building dependency tree... Done
<br>
Reading state information... Done
<br>
Calculating upgrade... Done
<br>
The following packages will be REMOVED:
<br>
mariadb-client-10.5 mariadb-client-core-10.5
mariadb-server-core-10.5
<br>
The following NEW packages will be installed:
<br>
libnuma1 liburing2 mariadb-client mariadb-client-core
mariadb-server mariadb-server-core
<br>
The following packages will be upgraded:
<br>
mariadb-server-10.5
<br>
1 upgraded, 6 newly installed, 3 to remove and 0 not upgraded.
<br>
Need to get 12.7 MB of archives.
<br>
After this operation, 28.0 MB of additional disk space will be
used.
<br>
Do you want to continue? [Y/n]
<br>
Get:1 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel
mariadb-server-10.5 armel 1:10.11.4-1~deb12u1 [22.7 kB]
<br>
Get:2 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel
mariadb-client-core armel 1:10.11.4-1~deb12u1 [754 kB]
<br>
Get:3 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel
mariadb-client armel 1:10.11.4-1~deb12u1 [2,510 kB]
<br>
Get:4 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel libnuma1
armel 2.0.16-1 [18.3 kB]
<br>
Get:5 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel liburing2
armel 2.3-3 [13.2 kB]
<br>
Get:6 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel
mariadb-server-core armel 1:10.11.4-1~deb12u1 [6,328 kB]
<br>
Get:7 <a class="moz-txt-link-freetext" href="https://deb.debian.org/debian">https://deb.debian.org/debian</a> bookworm/main armel
mariadb-server armel 1:10.11.4-1~deb12u1 [3,027 kB]
<br>
Fetched 12.7 MB in 5s (2,486 kB/s)
<br>
Preconfiguring packages ...
<br>
(Reading database ... 24167 files and directories currently
installed.)
<br>
Preparing to unpack
.../mariadb-server-10.5_1%3a10.11.4-1~deb12u1_armel.deb ...
<br>
Stopping MariaDB database server: mariadbd.
<br>
Unpacking mariadb-server-10.5 (1:10.11.4-1~deb12u1) over
(1:10.5.21-0+deb11u1) ...
<br>
(Reading database ... 24042 files and directories currently
installed.)
<br>
Removing mariadb-client-10.5 (1:10.5.21-0+deb11u1) ...
<br>
Removing mariadb-client-core-10.5 (1:10.5.21-0+deb11u1) ...
<br>
Removing mariadb-server-core-10.5 (1:10.5.21-0+deb11u1) ...
<br>
Selecting previously unselected package mariadb-client-core.
<br>
(Reading database ... 23850 files and directories currently
installed.)
<br>
Preparing to unpack
.../0-mariadb-client-core_1%3a10.11.4-1~deb12u1_armel.deb ...
<br>
Unpacking mariadb-client-core (1:10.11.4-1~deb12u1) ...
<br>
Selecting previously unselected package mariadb-client.
<br>
Preparing to unpack
.../1-mariadb-client_1%3a10.11.4-1~deb12u1_armel.deb ...
<br>
Unpacking mariadb-client (1:10.11.4-1~deb12u1) ...
<br>
Selecting previously unselected package libnuma1:armel.
<br>
Preparing to unpack .../2-libnuma1_2.0.16-1_armel.deb ...
<br>
Unpacking libnuma1:armel (2.0.16-1) ...
<br>
Selecting previously unselected package liburing2:armel.
<br>
Preparing to unpack .../3-liburing2_2.3-3_armel.deb ...
<br>
Unpacking liburing2:armel (2.3-3) ...
<br>
Selecting previously unselected package mariadb-server-core.
<br>
Preparing to unpack
.../4-mariadb-server-core_1%3a10.11.4-1~deb12u1_armel.deb ...
<br>
Unpacking mariadb-server-core (1:10.11.4-1~deb12u1) ...
<br>
Selecting previously unselected package mariadb-server.
<br>
Preparing to unpack
.../5-mariadb-server_1%3a10.11.4-1~deb12u1_armel.deb ...
<br>
/var/lib/mysql: found previous version 10.5
<br>
Unpacking mariadb-server (1:10.11.4-1~deb12u1) ...
<br>
Setting up mariadb-client-core (1:10.11.4-1~deb12u1) ...
<br>
Setting up libnuma1:armel (2.0.16-1) ...
<br>
Setting up liburing2:armel (2.3-3) ...
<br>
Setting up mariadb-client (1:10.11.4-1~deb12u1) ...
<br>
Setting up mariadb-server-core (1:10.11.4-1~deb12u1) ...
<br>
Setting up mariadb-server (1:10.11.4-1~deb12u1) ...
<br>
Installing new version of config file /etc/init.d/mariadb ...
<br>
Installing new version of config file /etc/logrotate.d/mariadb ...
<br>
Installing new version of config file /etc/mysql/debian-start ...
<br>
Installing new version of config file
/etc/mysql/mariadb.conf.d/50-server.cnf ...
<br>
Stopping MariaDB database server: mariadbd.
<br>
Starting MariaDB database server: mariadbd . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . failed!
<br>
invoke-rc.d: initscript mariadb, action "start" failed.
<br>
dpkg: error processing package mariadb-server (--configure):
<br>
installed mariadb-server package post-installation script
subprocess returned error exit status 1
<br>
dpkg: dependency problems prevent configuration of
mariadb-server-10.5:
<br>
mariadb-server-10.5 depends on mariadb-server (>= 1:10.11);
however:
<br>
Package mariadb-server is not configured yet.
<br>
<br>
dpkg: error processing package mariadb-server-10.5 (--configure):
<br>
dependency problems - leaving unconfigured
<br>
Processing triggers for libc-bin (2.36-9+deb12u3) ...
<br>
Errors were encountered while processing:
<br>
mariadb-server
<br>
mariadb-server-10.5
<br>
E: Sub-process /usr/bin/dpkg returned an error code (1)
<br>
<br>
Here is what was logged to syslog:
<br>
<br>
mariadb-server.postinst[3596]: mysql.user table already exists!
<br>
mariadb-server.postinst[3596]: Run mysql_upgrade, not
mysql_install_db
<br>
mysqld_safe: Starting mariadbd daemon with databases from
/var/lib/mysql
<br>
mysqld: 2023-12-20 10:23:51 0 [Note] Starting MariaDB
10.11.4-MariaDB-1~deb12u1 source revision as process 3765
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Compressed tables use
zlib 1.2.13
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Number of transaction
pools: 1
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using generic crc32
instructions
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Using liburing
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Initializing buffer
pool, total size = 128.000MiB, chunk size = 2.000MiB
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Completed
initialization of buffer pool
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers
for log disabled (block size=4096 bytes)
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Upgrading redo log:
96.000MiB; LSN=45767
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File system buffers
for log disabled (block size=4096 bytes)
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: 128 rollback segments
are active.
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: Setting file
'./ibtmp1' size to 12.000MiB. Physically writing the file full;
Please wait ...
<br>
mysqld: 2023-12-20 10:23:52 0 [Note] InnoDB: File './ibtmp1' size
is now 12.000MiB.
<br>
mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: log sequence number
45767; transaction id 20
<br>
mysqld: 2023-12-20 10:23:53 0 [Note] InnoDB: Loading buffer
pool(s) from /var/lib/mysql/ib_buffer_pool
<br>
mysqld: 2023-12-20 10:23:53 0 [Note] Plugin 'FEEDBACK' is
disabled.
<br>
mysqld: 2023-12-20 10:23:53 0 [ERROR] InnoDB: File ./ibdata1: 'aio
read' returned OS error 0. Cannot continue operation
<br>
mysqld: 231220 10:23:53 [ERROR] mysqld got signal 6 ;
<br>
mysqld: This could be because you hit a bug. It is also possible
that this binary
<br>
mysqld: or one of the libraries it was linked against is corrupt,
improperly built,
<br>
mysqld: or misconfigured. This error can also be caused by
malfunctioning hardware.
<br>
mysqld: mysqld: To report this bug, see
<a class="moz-txt-link-freetext" href="https://mariadb.com/kb/en/reporting-bugs">https://mariadb.com/kb/en/reporting-bugs</a>
<br>
mysqld: mysqld: We will try our best to scrape up some info that
will hopefully help
<br>
mysqld: diagnose the problem, but since we have already crashed,
mysqld: something is definitely wrong and this may fail.
<br>
mysqld: mysqld: Server version: 10.11.4-MariaDB-1~deb12u1 source
revision: mysqld: key_buffer_size=134217728
<br>
mysqld: read_buffer_size=131072
<br>
mysqld: max_used_connections=0
<br>
mysqld: max_threads=153
<br>
mysqld: thread_count=1
<br>
mysqld: It is possible that mysqld could use up to mysqld:
key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads = 466625 K bytes of memory
<br>
mysqld: Hope that's ok; if not, decrease some variables in the
equation.
<br>
mysqld: mysqld: Thread pointer: 0x0
<br>
mysqld: Attempting backtrace. You can use the following
information to find out
<br>
mysqld: where mysqld died. If you see no messages after this,
something went
<br>
mysqld: terribly wrong...
<br>
mysqld: stack_bottom = 0x0 thread_stack 0x49000
<br>
mysqld: The manual page at
<a class="moz-txt-link-freetext" href="https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/">https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/</a>
contains
<br>
mysqld: information that should help you find out what is causing
the crash.
<br>
mysqld: Writing a core file...
<br>
mysqld: Working directory at /var/lib/mysql
<br>
mysqld: Resource Limits:
<br>
mysqld: Limit Soft Limit Hard
Limit Units mysqld: Max cpu time
unlimited unlimited seconds mysqld: Max
file size unlimited unlimited
bytes mysqld: Max data size unlimited
unlimited bytes mysqld: Max stack size
8388608 unlimited bytes mysqld: Max
core file size 0 unlimited
bytes mysqld: Max resident set unlimited
unlimited bytes mysqld: Max processes
1904 1904 processes mysqld: Max
open files 32183 32183
files mysqld: Max locked memory 8388608
8388608 bytes mysqld: Max address space
unlimited unlimited bytes mysqld: Max
file locks unlimited unlimited
locks mysqld: Max pending signals 1904
1904 signals mysqld: Max msgqueue size
819200 819200 bytes mysqld: Max
nice priority 0 0
mysqld: Max realtime priority 0
0 mysqld: Max realtime timeout
unlimited unlimited us mysqld: Core
pattern: core
<br>
mysqld: mysqld: Kernel version: Linux version 6.1.0-16-marvell
(<a class="moz-txt-link-abbreviated" href="mailto:debian-kernel@lists.debian.org">debian-kernel@lists.debian.org</a>) (gcc-12 (Debian 12.2.0-14)
12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 Debian 6.1.67-1
(2023-12-12)
<br>
mysqld: mysqld_safe: mysqld from pid file /run/mysqld/mysqld.pid
ended
<br>
/etc/init.d/mariadb[4054]: 0 processes alive and
'/usr/bin/mariadb-admin --defaults-file=/etc/mysql/debian.cnf
ping' resulted in
<br>
/etc/init.d/mariadb[4054]: #007/usr/bin/mariadb-admin: connect to
server at 'localhost' failed
<br>
/etc/init.d/mariadb[4054]: error: 'Can't connect to local server
through socket '/run/mysqld/mysqld.sock' (2)'
<br>
/etc/init.d/mariadb[4054]: Check that mariadbd is running and that
the socket: '/run/mysqld/mysqld.sock' exists!
<br>
<br>
After the upgrade, a "diff" on the two mysql folders shows:
<br>
<br>
Only in mysql/: ddl_recovery.log
<br>
Only in mysql/: debian-10.11.flag
<br>
Only in mysql-10.5/: debian-10.5.flag
<br>
Binary files mysql-10.5/ib_logfile0 and mysql/ib_logfile0 differ
<br>
Only in mysql/: ibtmp1
<br>
<br>
No other files changed.
<br>
<br>
I then added these two lines in the [server] section of
/etc/mysql/mariadb.conf.d/50-server.cnf:
<br>
<br>
innodb = OFF
<br>
default-storage-engine = MyISAM
<br>
<br>
Then I ran:
<br>
<br>
apt install -f
<br>
<br>
After this, mariadbd started successfully, but without the InnoDB
engine, as can be seen in syslog:
<br>
<br>
mysqld_safe: Starting mariadbd daemon with databases from
/var/lib/mysql
<br>
mysqld: 2023-12-20 11:01:31 0 [Note] Starting MariaDB
10.11.4-MariaDB-1~deb12u1 source revision as process 5560
<br>
mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'InnoDB' is disabled.
<br>
mysqld: 2023-12-20 11:01:32 0 [Note] Plugin 'FEEDBACK' is
disabled.
<br>
mysqld: 2023-12-20 11:01:32 0 [Warning] You need to use --log-bin
to make --expire-logs-days or --binlog-expire-logs-seconds work.
<br>
mysqld: 2023-12-20 11:01:32 0 [Note] Server socket created on IP:
'127.0.0.1'.
<br>
mysqld: 2023-12-20 11:01:32 0 [Note] /usr/sbin/mariadbd: ready for
connections.
<br>
mysqld: Version: '10.11.4-MariaDB-1~deb12u1' socket:
'/run/mysqld/mysqld.sock' port: 3306 Debian 12
<br>
/etc/mysql/debian-start[5589]: Upgrading MySQL tables if
necessary.
<br>
/etc/mysql/debian-start[5599]: Checking for insecure root
accounts.
<br>
/etc/mysql/debian-start[5603]: Triggering myisam-recover for all
MyISAM tables and aria-recover for all Aria tables
<br>
<br>
On Tue, Dec 19, 2023 at 08:07:16AM -0700, Scott Barker wrote:
<br>
<blockquote type="cite">For myself, I am not using XEN/KVM/Docker.
I am installing this on a NAS device with an ARM chip and only
512M of RAM. I tried adding a 2G swap file, but it did not make
a difference. I was able to start mariadb by disabling INNODB
and using MyISAM instead with the options:
<br>
<br>
--innodb=OFF --default-storage-engine=MyISAM
<br>
<br>
On Mon, Dec 18, 2023 at 09:23:55AM +0200, Tuukka Pasanen wrote:
<br>
<blockquote type="cite">Hello,
<br>
<br>
Have you monitored that is memory exhausted at the
installation? This could lead error like that.
<br>
<br>
I assume your XEN/KVM/Docker base machine is some older system
with not so fancy CPU or is there any particular reason to use
armel build?
<br>
<br>
Sincerly,
<br>
<br>
Tuukka
<br>
<br>
Scott Barker kirjoitti 17.12.2023 klo 19.15:
<br>
<blockquote type="cite">Same result with the latest kernel:
<br>
<br>
Linux nas-1 6.1.0-16-marvell #1 Debian 6.1.67-1 (2023-12-12)
armv5tel GNU/Linux
<br>
<br>
On Sun, Dec 17, 2023 at 09:59:23AM -0700, Scott Barker
wrote:
<br>
<blockquote type="cite">Prior to the installation,
/var/lib/mysql did not exist. After installation:
<br>
<br>
61559 4 drwxr-xr-x 2 mysql mysql 4096 Dec 17
09:56 /var/lib/mysql
<br>
61975 4 -rw-rw---- 1 mysql mysql 52 Dec 17
09:56 /var/lib/mysql/aria_log_control
<br>
61983 12304 -rw-rw---- 1 mysql mysql 12582912 Dec 17
09:56 /var/lib/mysql/ibdata1
<br>
61963 0 -rw-r--r-- 1 root root 0 Dec 17
09:56 /var/lib/mysql/debian-10.11.flag
<br>
61990 98404 -rw-rw---- 1 mysql mysql 100663296 Dec 17
09:56 /var/lib/mysql/ib_logfile101
<br>
61982 16 -rw-rw---- 1 mysql mysql 16384 Dec 17
09:56 /var/lib/mysql/aria_log.00000001
<br>
<br>
uname -a reports:
<br>
<br>
Linux nas-1 5.10.0-26-marvell #1 Debian 5.10.197-1
(2023-09-29) armv5tel GNU/Linux
<br>
<br>
On Sun, Dec 17, 2023 at 11:48:16PM +0800, Otto Kekäläinen
wrote:
<br>
<blockquote type="cite">Hi Scott and Kr!
<br>
<br>
Did you note this line?
<br>
<br>
2023-12-14 14:51:33 0 [Note] InnoDB: Header page
consists of zero bytes in
<br>
datafile: ./ibdata1, Space ID:0, Flags: 0
<br>
<br>
Can you include the output of `find /var/lib/mysql -ls`
so we can see what
<br>
files your system has?
<br>
<br>
What is the hardware you have? The report shows 'Linux
5.10.0-26-marvell '.
<br>
What does `uname -a` yield?
<br>
<br>
The test suite passes on armhf at
e.g. <a class="moz-txt-link-freetext" href="https://launchpad.net/~mysql-ubuntu/">https://launchpad.net/~mysql-ubuntu/</a>
<br>
+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all.
At https://
<br>
ci.debian.net/packages/m/mariadb/unstable/armel/ it
fails due to regression in
<br>
subselect which is unrelated to what you reported.
<br>
<br>
</blockquote>
<br>
-- <br>
Scott Barker
<br>
<br>
-- <br>
To unsubscribe, send mail to
<a class="moz-txt-link-abbreviated" href="mailto:1058706-unsubscribe@bugs.debian.org">1058706-unsubscribe@bugs.debian.org</a>.
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
-- <br>
Scott Barker
<br>
<br>
-- <br>
To unsubscribe, send mail to
<a class="moz-txt-link-abbreviated" href="mailto:1058706-unsubscribe@bugs.debian.org">1058706-unsubscribe@bugs.debian.org</a>.
<br>
</blockquote>
<br>
</blockquote>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>