Bug 17493 - Q4wine bugfix update with Qt5 support
Summary: Q4wine bugfix update with Qt5 support
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Rémi Verschelde
URL:
Whiteboard: MGA5-64-OK advisory
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-01-14 13:07 CET by Otto Leipälä
Modified: 2016-01-20 18:54 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Otto Leipälä 2016-01-14 13:07:38 CET
Q4wine have full qt5 support so it should be build against qt5 instead of old qt4 in Cauldron,maybe backport it to Mageia 5.

https://github.com/brezerk/q4wine/commit/2d6569ce3a5650ee9c90303cd82d9bebe82c84c1

Original developer brezerk have restarted project,it was time ago quite dead project but not anymore.

https://github.com/brezerk/q4wine
http://q4wine.brezblock.org.ua/

Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2016-01-14 13:11:32 CET
Thanks for the notice, I had also noticed the new release a few days ago and was intended to take over the maintainership for this package. I'll push it to cauldron asap.

Assignee: bugsquad => rverschelde

Comment 2 Otto Leipälä 2016-01-14 13:55:58 CET
Thx Rémi.
Comment 3 Rémi Verschelde 2016-01-14 23:08:09 CET
Updated in Cauldron with Qt5 build.

I'll have a look for a potential Mageia 5 update, as it's mostly a bugfix release.

Version: Cauldron => 5

Comment 4 Otto Leipälä 2016-01-15 15:49:56 CET
Thanks it seems to me too bugfix only release no any major features.
Comment 5 Rémi Verschelde 2016-01-15 16:28:27 CET
I've now pushed q4wine-1.2.r2-1.mga5 to core/updates_testing. It's a bugfix update from upstream and it provides the possibility to use Qt5 instead of Qt4, so I've tried that.


Advisory:
=========

Updated q4wine package provides maintenance release

  q4wine 1.2-r2 brings bug fixes and translation updates over the 1.1-r2
  version provided in Mageia 5.
  It is now also built with the Qt5 toolkit instead of Qt4 previously.

  Please refer to the referenced release notes for more information.

References:
 - http://q4wine.brezblock.org.ua/news/43
 - http://q4wine.brezblock.org.ua/news/44


RPM in core/updates_testing:
============================
q4wine-1.2.r2-1.mga5

SRPM:
=====
 - q4wine-1.2.r2-1.mga5

Assignee: rverschelde => qa-bugs
Summary: Q4wine build against qt5 => Q4wine bugfix update with Qt5 support
QA Contact: (none) => rverschelde

Comment 6 Rémi Verschelde 2016-01-15 16:31:18 CET
Actually I rebuilt it to change s/Qt4/Qt5/ in the package summary, so here it is:

RPM in core/updates_testing:
============================
q4wine-1.2.r2-1.1.mga5

SRPM:
=====
 - q4wine-1.2.r2-1.1.mga5
Comment 7 Otto Leipälä 2016-01-18 15:19:53 CET
I have tested it but i am not anymore in qa team so somebody could validate this. I also have some problems with my laptop,it's not this point good idea to rejoin to qa team righ now.

Everything works ok with Mageia own wine and winehq-staging.
Comment 8 Rémi Verschelde 2016-01-18 15:24:46 CET
Well by doing testing, you are still somewhat in the QA team, so you can put MGA5-64-OK (actually anyone can put an OK, whether "officially" in the team or not).
Comment 9 Otto Leipälä 2016-01-18 17:32:17 CET
Thanks for notify me i have totally forgot everyting qa team things,i used arch linux long time until something inside me told come back to home.

Whiteboard: (none) => MGA5-64-OK

Rémi Verschelde 2016-01-18 18:42:08 CET

Whiteboard: MGA5-64-OK => MGA5-64-OK advisory

Comment 10 Dave Hodgins 2016-01-20 00:21:50 CET
Advisory updated and validating the update

Keywords: (none) => validated_update
CC: (none) => davidwhodgins, sysadmin-bugs

Comment 11 Mageia Robot 2016-01-20 18:54:19 CET
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0013.html

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


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