dev-perl/ORLite: Fix tests

Closes: https://bugs.gentoo.org/650514
Package-Manager: Portage-3.0.17, Repoman-3.0.2
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
This commit is contained in:
Andreas K. Hüttel
2021-04-26 00:37:52 +02:00
parent 01ff119d72
commit 349dd3b33c
2 changed files with 50 additions and 2 deletions

View File

@@ -1,4 +1,4 @@
# Copyright 1999-2019 Gentoo Authors
# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -31,5 +31,9 @@ DEPEND="
RDEPEND="
${COMMON_DEPEND}
"
PATCHES=( "${FILESDIR}/${PN}-1.98-dot-in-inc.patch" )
PATCHES=(
"${FILESDIR}/${PN}-1.98-dot-in-inc.patch"
"${FILESDIR}/${PN}-1.98-vacuum.patch"
)
DIST_TEST="do" # Parallel tests broken

View File

@@ -0,0 +1,44 @@
Description: Fix cleanup in tests.
Since SQLite 3.15, VACUUM either needs no arguments, or the name of an
attached database.
.
From https://sqlite.org/lang_vacuum.html :
Compatibility Warning: The ability to vacuum attached databases was added
in version 3.15.0 (2016-10-14). Prior to that, a schema-name added to the
VACUUM statement would be silently ignored and the "main" schema would be
vacuumed.
.
That means that 'VACUUM ANALYZE' never did what it was probably supposed to
do.
.
Maybe 'VACUUM; ANALYZE' works as well. -- And besides this change in the
testsuite, the documentation for cleanup() in the POD would need to be
updated as well.
.
Origin: vendor
Bug-Debian: https://bugs.debian.org/841545
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2016-10-21
--- a/t/10_cleanup.t
+++ b/t/10_cleanup.t
@@ -29,7 +29,7 @@
use strict;
use ORLite {
file => '$file',
- cleanup => 'VACUUM ANALYZE',
+ cleanup => 'VACUUM',
};
1;
--- a/t/11_cleanup.t
+++ b/t/11_cleanup.t
@@ -29,7 +29,7 @@
use strict;
use ORLite {
file => '$file',
- cleanup => 'VACUUM ANALYZE',
+ cleanup => 'VACUUM',
};
1;