Bug 24162 - Update paraview to 5.6.0
Summary: Update paraview to 5.6.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2019-01-10 16:29 CET by kunda 1
Modified: 2019-01-13 20:58 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
SPEC patch (3.44 KB, patch)
2019-01-13 02:51 CET, Adrien Guichard
Details | Diff
source patch (512 bytes, patch)
2019-01-13 02:52 CET, Adrien Guichard
Details | Diff
source patch 2 (416 bytes, patch)
2019-01-13 02:56 CET, Adrien Guichard
Details | Diff

Comment 1 Adrien Guichard 2019-01-12 01:19:41 CET
I am rebuilding paraview for Python 3.7, I will try to update for 5.6 version.

CC: (none) => guichard.adrien

Comment 2 kunda 1 2019-01-12 14:15:15 CET
Thank you!
Comment 3 Adrien Guichard 2019-01-13 02:51:56 CET
Created attachment 10658 [details]
SPEC patch
Comment 4 Adrien Guichard 2019-01-13 02:52:55 CET
Created attachment 10659 [details]
source patch
Comment 5 Adrien Guichard 2019-01-13 02:56:25 CET
Created attachment 10660 [details]
source patch 2
Comment 6 Adrien Guichard 2019-01-13 02:56:56 CET
Here is the patch for the spec file and 2 patches to add to the SOURCES directory.

I have had problems recompiling this version because gcc crashes during the build on my machine. The solution was to reduce the # of concurrent instance of gcc by defining macro _smp_ncpus_max into the spec file.
Comment 7 Marja Van Waes 2019-01-13 08:25:46 CET
Assigning to the registered maintainer.

Assignee: bugsquad => joequant
CC: (none) => marja11
Keywords: (none) => PATCH

Comment 8 José Jorge 2019-01-13 20:58:16 CET
I'll apply this patches, as I mentor aguichard.

Status: NEW => RESOLVED
Assignee: joequant => lists.jjorge
Resolution: (none) => FIXED
CC: (none) => lists.jjorge


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