Your message dated Sat, 07 Mar 2026 21:17:07 +0000
with message-id <[email protected]>
and subject line Bug#1127431: fixed in mariadb 1:11.8.6-0+deb13u1
has caused the Debian Bug report #1127431,
regarding libdbd-mysql-perl: FTBFS: Failed 1/77 test programs. 0/412 subtests
failed.
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.)
--
1127431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127431
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libdbd-mysql-perl
Version: 4.054-1
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/202602/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:libdbd-mysql-perl, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
LC_ALL=C.UTF-8 dh_auto_configure
/usr/bin/perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE="-g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2"
LD="x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wl,-z,relro -Wl,-z,now"
PLEASE NOTE:
[... snipped ...]
# RETREF 4
ok 42 - $ret_ref should contain four rows in result set
ok 43 - Testing prepare of dropping table
ok 44 - Executing drop table
ok 45 - Prepare - Testing bug \#20153
ok 46 - Execute - Testing bug \#20153
ok 47 - Fetch - Testing bug \#20153
ok 48 - Not Fetch - Testing bug \#20153
ok 49 - Testing disconnect
ok
t/40bindparam.t .........................
1..41
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23 - id set to -1
ok 24 - name eq abc
ok 25 - id set to 1
ok 26 - $name set to Alligator Descartes
ok 27 - id set to 2
ok 28 - $name set to Tim Bunce
ok 29 - id set to 3
ok 30 - $name set to Jochen Wiedmann
ok 31 - id set to 4
ok 32 - $name set to Andreas Koenig
ok 33 - id set to 5
ok 34 - name not defined
ok 35 - id set to 6
ok 36 - $name set to '?'
ok 37 - $id set to 7
ok 38 - $name set to '?'
ok 39
ok 40
ok 41
ok
t/40bindparam2.t ........................
1..13
ok 1
ok 2
ok 3 - create table dbd_mysql_t40bindparam2
ok 4 - insert into dbd_mysql_t40bindparam2 (null, 1)
ok 5
ok 6 - $rows->[0][1] == 1
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok
t/40bit.t ...............................
1..15
ok 1 - Drop table if exists dbd_mysql_b1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9 - result returned defined
ok 10 - should be 11111111
ok 11 - should be 1010
ok 12 - should be 101
ok 13
ok 14 - Drop table dbd_mysql_b1
ok 15
ok
t/40blobs.t .............................
1..14
ok 1 - Drop table if exists dbd_mysql_t40blobs
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8 - row returned defined
ok 9 - records from dbd_mysql_t40blobs returned 2
ok 10 - id set to 1
ok 11 - blob set equal to blob returned
# 00000000 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
# 00000020 202122232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f
# 00000040 404142434445464748494a4b4c4d4e4f505152535455565758595a5b5c5d5e5f
# 00000060 606162636465666768696a6b6c6d6e6f707172737475767778797a7b7c7d7e7f
# 00000080 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f
# 000000a0 a0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbebf
# 000000c0 c0c1c2c3c4c5c6c7c8c9cacbcccdcecfd0d1d2d3d4d5d6d7d8d9dadbdcdddedf
# 000000e0 e0e1e2e3e4e5e6e7e8e9eaebecedeeeff0f1f2f3f4f5f6f7f8f9fafbfcfdfeff
# 00000000 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
# 00000020 202122232425262728292a2b2c2d2e2f303132333435363738393a3b3c3d3e3f
# 00000040 404142434445464748494a4b4c4d4e4f505152535455565758595a5b5c5d5e5f
# 00000060 606162636465666768696a6b6c6d6e6f707172737475767778797a7b7c7d7e7f
# 00000080 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f
# 000000a0 a0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbebf
# 000000c0 c0c1c2c3c4c5c6c7c8c9cacbcccdcecfd0d1d2d3d4d5d6d7d8d9dadbdcdddedf
# 000000e0 e0e1e2e3e4e5e6e7e8e9eaebecedeeeff0f1f2f3f4f5f6f7f8f9fafbfcfdfeff
ok 12
ok 13 - Drop table dbd_mysql_t40blobs
ok 14
ok
260218 18:09:37 [ERROR] /usr/sbin/mysqld got signal 11 ;
Sorry, we probably made a mistake, and this is a bug.
Your assistance in bug reporting will enable us to fix this for the next
release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to
report
a bug on https://jira.mariadb.org/.
Please include the information from the server start above, to the end of the
information below.
Server version: 11.8.6-MariaDB-1 from Debian source revision:
9bfea48ce1214cc4470f6f6f8a4e30352cef84e7
The information page at
https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
contains instructions to obtain a better version of the backtrace below.
Following these instructions will help MariaDB developers provide a fix quicker.
Attempting backtrace. Include this in the bug report.
(note: Retrieving this information may fail)
Thread pointer: 0x7f01fc000cd8
stack_bottom = 0x7f0230313000 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x32) [0x5651795004f2]
/usr/sbin/mysqld(handle_fatal_signal+0x1a7) [0x565178f78247]
/usr/lib/x86_64-linux-gnu/libc.so.6(+0x40a70) [0x7f0247a4aa70]
Connection ID (thread ID): 28
Status: NOT_KILLED
Query (0x7f01fc012fd0): SELECT NULL AS PKTABLE_CAT,
A.REFERENCED_TABLE_SCHEMA AS PKTABLE_SCHEM,
A.REFERENCED_TABLE_NAME AS PKTABLE_NAME,
A.REFERENCED_COLUMN_NAME AS PKCOLUMN_NAME,
A.TABLE_CATALOG AS FKTABLE_CAT,
A.TABLE_SCHEMA AS FKTABLE_SCHEM,
A.TABLE_NAME AS FKTABLE_NAME,
A.COLUMN_NAME AS FKCOLUMN_NAME,
A.ORDINAL_POSITION AS KEY_SEQ,
NULL AS UPDATE_RULE,
NULL AS DELETE_RULE,
A.CONSTRAINT_NAME AS FK_NAME,
NULL AS PK_NAME,
NULL AS DEFERABILITY,
NULL AS UNIQUE_OR_PRIMARY
FROM INFORMATION_SCHEMA.KEY_COLUMN_USAGE A,
INFORMATION_SCHEMA.TABLE_CONSTRAINTS B
WHERE A.TABLE_SCHEMA = B.TABLE_SCHEMA AND A.TABLE_NAME = B.TABLE_NAME
AND A.CONSTRAINT_NAME = B.CONSTRAINT_NAME AND B.CONSTRAINT_TYPE IS NOT NULL
AND A.REFERENCED_TABLE_NAME = 'parent' AND A.TABLE_NAME = 'child' ORDER BY
A.TABLE_SCHEMA, A.TABLE_NAME, A.ORDINAL_POSITION
Optimizer switch:
index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=on,sargable_casefold=on
Writing a core file...
Working directory at /<<PKGBUILDDIR>>/t/testdb
Resource Limits (excludes unlimited resources):
Limit Soft Limit Hard Limit Units
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max processes 30885 30885 processes
Max open files 32184 32184 files
Max locked memory 8388608 8388608 bytes
Max pending signals 30885 30885 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Core pattern: core
Kernel version: Linux version 6.12.73+deb13-cloud-amd64
([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19)
14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian
6.12.73-1 (2026-02-17)
DBD::mysql::db foreign_key_info failed: Lost connection to server during query
at t/40catalog.t line 68.
DBD::mysql::db foreign_key_info failed: Lost connection to server during query
at t/40catalog.t line 68.
# Looks like your test exited with 11 just after 4.
t/40catalog.t ...........................
1..78
ok 1 - connecting
ok 2 - cleaning up
ok 3
ok 4
Dubious, test returned 11 (wstat 2816, 0xb00)
Failed 74/78 subtests
t/40keyinfo.t ........................... skipped: no database connection
t/40listfields.t ........................ skipped: no database connection
t/40nulls.t ............................. skipped: no database connection
t/40nulls_prepare.t ..................... skipped: no database connection
t/40numrows.t ........................... skipped: no database connection
t/40server_prepare.t .................... skipped: no database connection
t/40server_prepare_crash.t .............. skipped: no database connection
t/40server_prepare_error.t .............. skipped: no database connection
t/40types.t ............................. skipped: no database connection
t/41bindparam.t ......................... skipped: no database connection
t/41blobs_prepare.t ..................... skipped: no database connection
t/41int_min_max.t ....................... skipped: no database connection
t/42bindparam.t ......................... skipped: no database connection
t/43count_params.t ...................... skipped: no database connection
t/50chopblanks.t ........................ skipped: no database connection
t/50commit.t ............................ skipped: no database connection
t/51bind_type_guessing.t ................ skipped: no database connection
t/52comment.t ........................... skipped: no database connection
t/53comment.t ........................... skipped: no database connection
t/55utf8.t .............................. skipped: no database connection
t/55utf8mb4.t ........................... skipped: no database connection
t/56connattr.t .......................... skipped: no database connection
t/57trackgtid.t ......................... skipped: no database connection
t/60leaks.t ............................. skipped: Skip $ENV{EXTENDED_TESTING}
is not set
t/65segfault.t .......................... skipped: no database connection
t/65types.t ............................. skipped: no database connection
t/70takeimp.t ........................... skipped: no database connection
t/71impdata.t ........................... skipped: no database connection
t/75supported_sql.t ..................... skipped: no database connection
t/76multi_statement.t ................... skipped: no database connection
t/80procs.t ............................. skipped: no database connection
t/81procs.t ............................. skipped: no database connection
t/85init_command.t ...................... skipped: no database connection
t/86_bug_36972.t ........................ skipped: no database connection
t/87async.t ............................. skipped: no database connection
t/88async-multi-stmts.t ................. skipped: no database connection
t/89async-method-check.t ................ skipped: no database connection
t/91errcheck.t .......................... skipped: no database connection
t/92ssl_backronym_vulnerability.t ....... skipped: no database connection: DBI
connect('test','sbuild',...) failed: Can't connect to local server through
socket '/<<PKGBUILDDIR>>/t/testdb' (111) at t/lib.pl line 57.
t/92ssl_optional.t ...................... skipped: no database connection: DBI
connect('test','sbuild',...) failed: Can't connect to local server through
socket '/<<PKGBUILDDIR>>/t/testdb' (111) at t/lib.pl line 57.
t/92ssl_riddle_vulnerability.t .......... skipped: no database connection: DBI
connect('test','sbuild',...) failed: Can't connect to local server through
socket '/<<PKGBUILDDIR>>/t/testdb' (111) at t/lib.pl line 57.
t/99_bug_server_prepare_blob_null.t ..... skipped: no database connection
# DBI connect('test','sbuild',...) failed: Can't connect to local server
through socket '/<<PKGBUILDDIR>>/t/testdb' (111) at t/gh352.t line 12.
t/gh352.t ............................... skipped: no database connection
t/manifest.t ............................ skipped: these tests are for release
testing
t/pod.t ................................. skipped: Test::Pod 1.00 required for
testing POD
t/rt110983-valid-mysqlfd.t .............. skipped: no database connection
t/rt118977-zerofill.t ................... skipped: no database connection
t/rt25389-bin-case.t .................... skipped: no database connection
t/rt50304-column_info_parentheses.t ..... skipped: no database connection
t/rt61849-bind-param-buffer-overflow.t .. skipped: no database connection
t/rt75353-innodb-lock-timeout.t ......... skipped: no database connection
t/rt83494-quotes-comments.t ............. skipped: no database connection
t/rt85919-fetch-lost-connection.t ....... skipped: no database connection
t/rt86153-reconnect-fail-memory.t ....... skipped: $ENV{EXTENDED_TESTING} is
not set
t/rt88006-bit-prepare.t ................. skipped: no database connection
t/rt91715.t ............................. skipped: no database connection
t/version.t .............................
ok 1 - version format
ok 2 - version starts with "4." (update for 5.x)
ok 3 - VERSION strings should be the same in all .pm files in dist
1..3
ok
Test Summary Report
-------------------
t/40catalog.t (Wstat: 2816 (exited 11) Tests: 4 Failed:
0)
Non-zero exit status: 11
Parse errors: Bad plan. You planned 78 tests but ran 4.
Files=77, Tests=412, 4 wallclock secs ( 0.12 usr 0.06 sys + 2.77 cusr 0.93
csys = 3.88 CPU)
Result: FAIL
Failed 1/77 test programs. 0/412 subtests failed.
make[2]: *** [Makefile:1207: test_dynamic] Error 255
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j2 test TEST_VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:20: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: mariadb
Source-Version: 1:11.8.6-0+deb13u1
Done: Otto Kekäläinen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Otto Kekäläinen <[email protected]> (supplier of updated mariadb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 06 Mar 2026 13:13:13 +0000
Source: mariadb
Architecture: source
Version: 1:11.8.6-0+deb13u1
Distribution: trixie
Urgency: medium
Maintainer: Debian MySQL Maintainers <[email protected]>
Changed-By: Otto Kekäläinen <[email protected]>
Closes: 1122811 1127431 1127863
Changes:
mariadb (1:11.8.6-0+deb13u1) trixie; urgency=medium
.
[ Otto Kekäläinen ]
* New upstream maintenance release 11.8.6. For details about fixes please see
https://mariadb.com/docs/release-notes/community-server/11.8/11.8.6
* For details about fixes in 11.8.5 please see
https://mariadb.com/docs/release-notes/community-server/11.8/11.8.5
and the security notices:
- CVE-2025-13699
- CVE-2026-21968
* For details about fixes in 11.8.4 please see
https://mariadb.com/docs/release-notes/community-server/11.8/11.8.4
* The version 11.8.4 was skipped in Debian (and Ubuntu) as it has a severe
regression causing partial data deletion when using the DELETE statement on
MyISAM or Aria tables under specific conditions (MDEV-38068)
* Already existing plugins marked ready for general availability by upstream
in this release: uuid_v4, uuid_v7 and inet4
* Upstream 11.8.5 included fix to MDEV-36556 about upgrades failing from 10.4
when encryption enabled (Closes: #1122811)
* Add debian/source/local-options to suppress WolfSSL line ending errors
* Patch new upstream test main.alter_merge to allow 'from Debian'
* Fix path to mariadb-server.README in mariadb-secure-install
(Closes: #1127863)
* Add preliminary upstream patch to fix MDEV-38811 that affected Akonadi and
any other use case that relies on 'skip-grant-tables' (Closes: #1127431)
* Update patch statuses and Forwarded fields to aid patch maintenance in
future new upstream version updates
* Update server trace to include new 'new-mode' value 'FIX_INDEX_LOOKUP_COST'
* Salsa CI: Apply several fixes already in use on debian/latest branch and
which are needed on this branch as well due to external changes since
August 2026, most notably Salsa CI switching to be sbuild based
.
[ Daniel Black ]
* MDEV-37411: Re-enable AIO in Debian to fix earlier incomplete fix that was
done after new upstream 11.8.3 release introduced innodb_linux_aio
* MDEV-15502: With recent changes in upstream systemd, the tmpfiles are now
required, otherwise starting MariaDB would fail on error:
"cannot create /run/mysqld/wsrep-start-position: Directory nonexistent"
Checksums-Sha1:
f240cc146783ae5e35ff2b956c6874fb9206b380 5677 mariadb_11.8.6-0+deb13u1.dsc
67708c3a39324d1013e58c965c8ebad10b7e5663 120887651 mariadb_11.8.6.orig.tar.gz
59b9e0d37144688480428b31f2b97c24a64d2d2d 833 mariadb_11.8.6.orig.tar.gz.asc
ab9c4ba05dd3e4776e1cc61a79b09880201d6ac4 290320
mariadb_11.8.6-0+deb13u1.debian.tar.xz
8a472684b6101f17c5a58ab29f341b9d188a89eb 13811
mariadb_11.8.6-0+deb13u1_source.buildinfo
Checksums-Sha256:
c38d7ec65b2f6cf3d7b5edc21f0732d749b75507837219832a0e8dca89cf9556 5677
mariadb_11.8.6-0+deb13u1.dsc
b126581a8ca89376d2a3ce63fee97c114c3e15315345e769b9d00c51e1b7d619 120887651
mariadb_11.8.6.orig.tar.gz
83fdc365789ef5f4b2974468061896971c10c605b0e41e1888a90f4e5342008a 833
mariadb_11.8.6.orig.tar.gz.asc
84da78759f1de6452e19cbc24eaa3855ed352fc9306eb12fa9c8f30832d1613b 290320
mariadb_11.8.6-0+deb13u1.debian.tar.xz
8856d0e16e3cbe5ff56487f3b29e4a2586b6ab30cf6087df77bad2f9ff8ebe3b 13811
mariadb_11.8.6-0+deb13u1_source.buildinfo
Files:
fdb8be3555f0819bd4118535695c091d 5677 database optional
mariadb_11.8.6-0+deb13u1.dsc
85044cd1ec59cbdbcc4d27a9646d6261 120887651 database optional
mariadb_11.8.6.orig.tar.gz
d81bfdd2a81823c23482cc25afc30c7a 833 database optional
mariadb_11.8.6.orig.tar.gz.asc
8f8f7952843b7108e86a1bb98fb728ac 290320 database optional
mariadb_11.8.6-0+deb13u1.debian.tar.xz
103dadb023a570ea0e4f17cf689be46c 13811 database optional
mariadb_11.8.6-0+deb13u1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmmsQlAACgkQvthEn87o
2ogvWA/7BzPLEQeflcGbkcynOTxoTqiQJGrNPXg4M1aPEITvETVdawSQWwEOTV74
FwSvsO0mZfU60ozU3vXtafIvw8DJvid1OzxH2RB50He5WXGUfRcUphZEm+GKmwHE
n/XXBO7TdaOlJYwQGOnhb1cI4Xqp7YI6kpnThEZLmmvj6J7atB6DgC+crHEskSTd
dTVhpSDBVOkHjfUS/+cbEToFQZiKq052mUYuKLrPTlwSHPiORBHQI50NbG8SsNf9
9p1nRidE0LdKTqtMi1LSD6fH62xZUkMkXRsomADgVqler/uJfHJ2yk1V3NInGWFU
SPNzfFzvKV1esw4oJMox+ZL3ytw/JnlnJjvJ6ER+7MLsjctT9gq+/bZ1HSDJ1E2a
IX+Lsjhy3pUiXnLUH7x5Us4iyphmBcet10C0tG6B4KHSr4Rvc9ldCjR54+SEfX9j
dv1qew+9X0qy7sOFrwcEN2GXZ3FUnt819tu1YdY/7UdhX8pQ5W8+RHMWFURh/ERn
HE2JNLIZ+kRRWyFipjYe0T5FVxxsrhiGYzO05kaECLfU22JYqR0ZrWZUPGjJ/nQS
b6KR2PghzsdeCfBo0L3FClwoR+3TKP3Ybscsis/Pz6xyOF6yXCWgcKxU7D+0WB0v
nynWvvJguS8dMYdYD2Uom1JHMIOpfUGNl8ZMY8iAlCLG+sf4pcc=
=L0U8
-----END PGP SIGNATURE-----
pgptphUUnEKNf.pgp
Description: PGP signature
--- End Message ---
