Bug 13941 - Trojita missing dependency qt4-database-plugin-sqlite
Summary: Trojita missing dependency qt4-database-plugin-sqlite
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard: has_procedure MGA4-32-OK MGA4-64-OK a...
Keywords: validated_update
: 13762 (view as bug list)
Depends on:
Blocks: 13762
  Show dependency treegraph
 
Reported: 2014-08-19 17:51 CEST by Dimitrios Glentadakis
Modified: 2014-08-25 10:44 CEST (History)
4 users (show)

See Also:
Source RPM: trojita-0.3.93-2.1.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Dimitrios Glentadakis 2014-08-19 17:51:37 CEST
Suggested advisory:
========================

Update trojita to fix missing dependency:

Error message when running trojita due the missing dependency qt4-database-plugin-sqlite

Reported bug:
https://bugs.mageia.org/show_bug.cgi?id=13762
========================

Updated packages in core/updates_testing:
========================
trojita-0.3.93-2.1.mga4

Source RPMs: 
trojita-0.3.93-2.1.mga4.src

Reproducible: Yes

Steps to Reproduce: Install trojita, assuming the package qt4-database-plugin-sqlite is not installed, there is the following error:
http://up.picr.de/18947527rh.png
After installing the missing dependency qt4-database-plugin-sqlite, the problem is solved

Reproducible: 

Steps to Reproduce:
Dimitrios Glentadakis 2014-08-19 17:52:10 CEST

Blocks: (none) => 13762

Comment 1 Rémi Verschelde 2014-08-19 19:27:26 CEST
Testing complete on Mageia 4 64bit.

I could reproduce the issue with the package from core/release, and the update candidate fixes it. Briefly played around with trojita to make sure there were no really obvious regressions.

CC: (none) => remi
Whiteboard: (none) => has_procedure MGA4-64-OK

Comment 2 Rémi Verschelde 2014-08-23 13:38:47 CEST
*** Bug 13762 has been marked as a duplicate of this bug. ***

CC: (none) => c934w-xavm493b

Comment 3 Christian PERRY 2014-08-24 20:47:18 CEST
Testing complete on Mageia 4 32bit.

I have reproduced the problem with core / release. The update corrects it. I briefly used trojita to make sure that there is no obvious problem.

CC: (none) => ducp54

Comment 4 Christian PERRY 2014-08-24 20:49:00 CEST
(In reply to Christian PERRY from comment #3)
> Testing complete on Mageia 4 32bit.
> 
> I have reproduced the problem with the package from core / release. The update candidate corrects it. I briefly used trojita to make sure that there is no obvious problem.
Comment 5 Christian PERRY 2014-08-24 20:50:54 CEST
(In reply to Christian PERRY from comment #4)
> (In reply to Christian PERRY from comment #3)
> > Testing complete on Mageia 4 32bit.
> > 
> > I have reproduced the problem with the package from core / release. The update candidate corrects it. I briefly used trojita to make sure that there is no obvious problem.

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 6 Rémi Verschelde 2014-08-24 20:54:19 CEST
Thanks for your test Christian.

When you consider that the test was successful, you can add the MGA4-32-OK tag in the "Whiteboard" field (or MGA4-64-OK on 64bit, etc.).
I will do it for you this time.

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1
Whiteboard: has_procedure MGA4-64-OK => has_procedure MGA4-32-OK MGA4-64-OK

Comment 7 Rémi Verschelde 2014-08-24 20:57:18 CEST
Validating the update. Advisory uploaded.

Could a sysadmin push trojita to Mageia 4 core/updates? Thanks!

Keywords: (none) => validated_update
Whiteboard: has_procedure MGA4-32-OK MGA4-64-OK => has_procedure MGA4-32-OK MGA4-64-OK advisory
CC: (none) => sysadmin-bugs

Comment 8 Christian PERRY 2014-08-24 21:15:44 CEST
Thanks for your help Rémi.

Sorry for the mistake comments 4 and 5.
Comment 9 Mageia Robot 2014-08-25 10:44:38 CEST
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2014-0163.html

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


Note You need to log in before you can comment on or make changes to this bug.