Bug 19558 - qarte < 3.4.0 is not compatible anymore with the arte.tv website
Summary: qarte < 3.4.0 is not compatible anymore with the arte.tv website
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA5-32-OK MGA5-64-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-10-09 21:29 CEST by José Jorge
Modified: 2016-10-11 14:40 CEST (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description José Jorge 2016-10-09 21:29:28 CEST 
qarte versions before 2.8.0 are no longer compatible with the arte.tv website, therefore most features are now broken in Mageia 5.
José Jorge 2016-10-09 21:29:51 CEST

CC: (none) => lists.jjorge

Comment 1 José Jorge 2016-10-09 21:31:16 CEST 
Package submit to testing. The advisory is just the same as below, just changing version from 2.3 to 3.4

http://advisories.mageia.org/MGAA-2015-0043.html

Rpms : qarte-3.4.0

Status: NEW => ASSIGNED

Comment 2 Herman Viaene 2016-10-11 11:07:42 CEST 
MGA5-32 on Acer D620 Xfce
No installation issues
I could see the available downloads from arte-tv and download one, the file plays OK. Contents of arte-live-web also accessible, but I didn't try a download there.

CC: (none) => herman.viaene
Whiteboard: (none) => MGA5-32-OK

Comment 3 Nicolas Lécureuil 2016-10-11 14:26:38 CEST 
MGA5-64

install OK
start OK
download video OK
watch video OK

CC: (none) => mageia
Whiteboard: MGA5-32-OK => MGA5-32-OK MGA5-64-OK

Nicolas Lécureuil 2016-10-11 14:31:37 CEST

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

Comment 4 Mageia Robot 2016-10-11 14:40:46 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

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

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.