Bug 20275

Summary:	mariadb-bench should require perl-DBD-mysql
Product:	Mageia	Reporter:	Dave Hodgins <davidwhodgins>
Component:	RPM Packages	Assignee:	AL13N <alien>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jackal.j, lists.jjorge, marja11, pkg-bugs
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mariadb-10.0.29-1.2.mga5.src.rpm	CVE:
Status comment:
Bug Depends on:	20487
Bug Blocks:

Description Dave Hodgins 2017-02-12 19:47:50 CET

After installing mariadb-bench, running it fails with Can't locate DBD/mysql.pm

After installing perl-DBD-mysql, it runs using
perl run-all-tests --server=mysql --user=root --password=munged --small-test

It'a also being affected by bug 20143, which is causing the daemon to restart
every 5 minutes. Any of the tests run during the restart fail.

The first time I ran it, 9 of the 10 tests failed. The second time, 3 failed.

Comment 1 Marja Van Waes 2017-02-13 11:39:03 CET

Assigning to the registered maintainer, but CC'ing all packagers collectively, in case AL13N is unavailable

CC: (none) => marja11, pkg-bugs

Comment 2 Marja Van Waes 2017-02-13 11:39:34 CET

(really assigning)

Assignee: bugsquad => alien

David Walser 2017-03-15 01:59:13 CET

Depends on: (none) => 20487

Comment 3 Jack M 2017-12-10 09:50:30 CET

Is this a simple case of adding requires: perl-DBD-mysql?

CC: (none) => jackal.j

Comment 4 José Jorge 2017-12-10 10:24:53 CET

(In reply to Jack M from comment #3)
> Is this a simple case of adding requires: perl-DBD-mysql?

Seems like. But this is against MGA5, which is EOL in less than one month. I'd say that if it was fixed in MGA6 and cauldron, close the bug : it is no worth pushing a fix for MGA5...

CC: (none) => lists.jjorge

Comment 5 Jack M 2017-12-10 10:44:23 CET

It seems to be fixed in cauldron.

It seems to be fixed in mga5 as well.

It seems to be fixed in mga6 as well.

Not sure why this bug is still open. At least the spec files seem to be fixed. Seems like the fixes went through without testing? According to logs fixes were done by March itself! Even this bug is referenced!

Comment 6 José Jorge 2017-12-10 11:01:39 CET

I'd say human error, just close it.

Status: NEW => RESOLVED
Resolution: (none) => FIXED