Bug 24345

Summary: Switch itest on qt5
Product: Mageia Reporter: Alex Loginov <loginov_alex>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: geiger.david68210, kde, mageia, marja11, yvesbrungard
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: itest CVE:
Status comment:

Description Alex Loginov 2019-02-11 02:00:30 CET
Description of problem: the latest git snapshot https://github.com/michal-tomlein/itest has qt5 support with patch:

--- shared/question.h
+++ shared/question.h
@@ -22,8 +22,9 @@
 #include "defs.h"
 #include <QStringList>
+#include <QObject>
 class PassMark;
 class QApplication;
Comment 1 Marja Van Waes 2019-02-12 08:51:25 CET

I didn't know iTest, but it looks very useful for schools and universities.

CC'ing papoteur, because I think it would be good to ask our French translators to translate iTest into French, but I'd like his opinion (his wife being a French teacher ;-) )

Assigning to all packagers collectively and CC'ing KDE team, because there is no registered maintainer for this package

Assignee: bugsquad => pkg-bugs
CC: (none) => kde, marja11, yves.brungard_mageia

Comment 2 David GEIGER 2019-02-12 09:28:12 CET
And one more dead and unmaintained upstream project...

Latest commit about 3 years old now... So how mageia can maintain a package while upstream does not?

CC: (none) => geiger.david68210

Comment 3 Alex Loginov 2019-02-12 12:50:10 CET
David, half of education software are dead, but it's not problem absolutely.
It is workable, no bugs in our bugzilla. To build as qt5 and it will work many years while qt6. You can add French translation, any patches.
Comment 4 Nicolas Lécureuil 2019-02-12 13:20:09 CET
would be nice to submit this patch on the upstream project

CC: (none) => mageia

Comment 5 David GEIGER 2021-01-23 07:24:18 CET
Current master branch (https://github.com/michal-tomlein/itest) doesn't build with current Qt 5.15.2.

So closing this bug as wontfix!

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