Bug 13781 - Qt5 lupdate utility is built without QML support
Summary: Qt5 lupdate utility is built without QML support
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2014-07-22 09:03 CEST by Oleg Bosis
Modified: 2020-07-04 23:37 CEST (History)
5 users (show)

See Also:
Source RPM: qttools5
CVE:
Status comment:


Attachments

Description Oleg Bosis 2014-07-22 09:03:58 CEST
Description of problem:

lupdate utility that comes with qttools5 package can not handle qml files.

I've described the problem on dev ml here: https://ml.mageia.org/l/arc/dev/2014-07/msg00428.html

The reason is that lupdate have to be built with libQt5QmlDevTools.a library that should come with some of qtdeclarative5 development subpackage (probably lib{,64}qt5qml-private-devel one) but is not packaged (all static libs are removed explicitly when packaging and there is no dynamic version of this library).

Version-Release number of selected component (if applicable):
Qt5 5.2.0, 5.3.1. Bug is relevant for both Mageia 4 and Cauldron.

How reproducible:
always

Steps to Reproduce:
1. Get a hello.qml example from http://qt-project.org/doc/qt-4.8/qdeclarativei18n.html
2. Try to use lupdate as described at that page
3.


Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2014-07-22 14:37:52 CEST

Assignee: bugsquad => mageia
Source RPM: (none) => qt5

Comment 1 Nicolas Lécureuil 2014-07-24 02:10:27 CEST
Please test next rpm.
Comment 2 Oleg Bosis 2014-07-24 08:17:36 CEST
First I can not test cauldron packages as I do not have cauldron installation. I can only test them if they are backported to Mageia 4. So it would be better if you first fix Qt 5.2.0 for Mageia 4 and then port changes into cauldron (or, even more better, backport Qt 5.3.1 so that I can drop my own backport).

Second I see that you just updated only qttools5 package but the required library is a part of qtdeclarative5 and it is not packaged properly. So I think you should *first* fix qtdeclarative5 package (bring back the removed static lib) and *then* rebuild qttools5 with it.
Comment 3 Nicolas Lécureuil 2014-07-24 10:24:51 CEST
yes right.

I will reproduce and when fixed in cauldron i will backport in 4.
Comment 4 Samuel Verschelde 2015-05-19 20:26:31 CEST
Has it been fixed in cauldron and Mageia 4 Nicolas?
Comment 5 Samuel Verschelde 2015-06-06 15:59:06 CEST
(In reply to Samuel VERSCHELDE from comment #4)
> Has it been fixed in cauldron and Mageia 4 Nicolas?

Ping Nicolas.
Samuel Verschelde 2016-08-25 16:24:04 CEST

Assignee: mageia => kde

Comment 6 Nicolas Lécureuil 2016-09-18 16:57:15 CEST
This bug is fixed on cauldron.

$ lupdate hello.qml -ts hello.ts
Updating 'hello.ts'...
    Found 1 source text(s) (1 new and 0 already existing)

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

Comment 7 papoteur 2020-06-27 09:04:15 CEST
Hello,
I reopen this report, because I'm facing the same problem:
lupdate mw-ui.qml -ts qml.ts
lupdate warning: Some files have been ignored due to missing qml/javascript support
Updating 'qml.ts'...
    Found 0 source text(s) (0 new and 0 already existing)

It seems that the support has to be set
"I found that this error arise when build with is performed with defined flag QT_NO_QML." https://forum.qt.io/topic/32591/solved-lupdate-missing-qml-javascript-support/4

CC: (none) => yves.brungard_mageia
Resolution: FIXED => (none)
Status: RESOLVED => REOPENED
Version: Cauldron => 7

papoteur 2020-06-27 09:04:43 CEST

Source RPM: qt5 => qttools5

Comment 8 Dave Hodgins 2020-06-28 18:52:09 CEST
Before installing the update ...
[root@x3 /usr/share/mageiawelcome]# lupdate mw-ui.qml -ts qml.ts
lupdate warning: Some files have been ignored due to missing qml/javascript support
Updating 'qml.ts'...
    Found 0 source text(s) (0 new and 0 already existing)

After installing the update ...
[root@x3 /usr/share/mageiawelcome]# lupdate mw-ui.qml -ts qml.ts
/usr/share/mageiawelcome/mw-ui.qml:88: Discarding unconsumed meta data
/usr/share/mageiawelcome/mw-ui.qml:341: Discarding unconsumed meta data
Updating 'qml.ts'...
    Found 89 source text(s) (89 new and 0 already existing)

Validating the update.

Still needs to be assigned to qa and an advisory provided before the update
can be finished.

CC: (none) => davidwhodgins, sysadmin-bugs
Keywords: (none) => validated_update
Whiteboard: (none) => MGA7-64-OK

Comment 9 David GEIGER 2020-06-28 19:12:49 CEST
Assigning to QA,

Advisory:
=============================

Our current qttools5 package was built without the QML support.
This update fixes this issue re-enabling it.



Packages in 7/core/updates_testing:
========================
qttools5-5.12.6-1.1.mga7.i586.rpm
qttools5-assistant-5.12.6-1.1.mga7.i586.rpm
qttools5-designer-5.12.6-1.1.mga7.i586.rpm
qttools5-qtdbus-5.12.6-1.1.mga7.i586.rpm
qttools5-doc-5.12.6-1.1.mga7.noarch.rpm
libqt5help5-5.12.6-1.1.mga7.i586.rpm
libqt5help-devel-5.12.6-1.1.mga7.i586.rpm
libqt5designer5-5.12.6-1.1.mga7.i586.rpm
libqt5designer-devel-5.12.6-1.1.mga7.i586.rpm

qttools5-5.12.6-1.1.mga7.x86_64.rpm
qttools5-assistant-5.12.6-1.1.mga7.x86_64.rpm
qttools5-designer-5.12.6-1.1.mga7.x86_64.rpm
qttools5-qtdbus-5.12.6-1.1.mga7.x86_64.rpm
lib64qt5help5-5.12.6-1.1.mga7.x86_64.rpm
lib64qt5help-devel-5.12.6-1.1.mga7.x86_64.rpm
lib64qt5designer5-5.12.6-1.1.mga7.x86_64.rpm
lib64qt5designer-devel-5.12.6-1.1.mga7.x86_64.rpm

Source RPM:
========================
qttools5-5.12.6-1.1.mga7.src.rpm

CC: (none) => geiger.david68210
Assignee: kde => qa-bugs

Comment 10 Dave Hodgins 2020-06-28 19:56:48 CEST
Advisory committed to svn.

Keywords: (none) => advisory

Comment 11 Mageia Robot 2020-07-04 23:37:41 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0151.html

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


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