Bug 26203 - Update request: strace-5.5-1.mga7
Summary: Update request: strace-5.5-1.mga7
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: 26202
Blocks:
  Show dependency tree / graph
 
Reported: 2020-02-16 20:09 CET by Thomas Backlund
Modified: 2020-02-22 00:07 CET (History)
4 users (show)

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

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

Description Thomas Backlund 2020-02-16 20:09:05 CET 
update strace to 5.5 to match the new kernel

SRPM:
strace-5.5-1.mga7.src.rpm

i586:
strace-5.5-1.mga7.i586.rpm

x86_64:
strace-5.5-1.mga7.x86_64.rpm
Thomas Backlund 2020-02-16 20:10:09 CET

Depends on: (none) => 26202

Comment 1 Herman Viaene 2020-02-19 16:05:20 CET 
MGA7-64 Plasma on Lenovo B50
No installation issues.
Following lead in bug 25831, used strace on dolphin and kpat, got loads of info in trace files and the prgrams behaved OK.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => herman.viaene

Comment 2 PC LX 2020-02-19 16:42:30 CET 
Installed and tested without issues.


System: Mageia 7, x86_64, Plasma DE, LXQt DE, Intel CPU, nVidia Geforce 210 using nvidia340 proprietary driver.


$ uname -a
Linux marte 5.5.4-desktop-1.mga7 #1 SMP Sat Feb 15 08:41:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q strace
strace-5.5-1.mga7

CC: (none) => mageia

Comment 3 Thomas Andrews 2020-02-20 17:48:20 CET 
Validating.

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

Thomas Backlund 2020-02-21 22:19:26 CET

Keywords: (none) => advisory

Comment 4 Mageia Robot 2020-02-22 00:07:23 CET 
An update for this issue has been pushed to the Mageia Updates repository.

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

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