Bug 22174 - Add igraph to Core Backports
Summary: Add igraph to Core Backports
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Backport
Depends on:
Blocks:
 
Reported: 2017-12-12 01:54 CET by Kristoffer Grundström
Modified: 2019-12-10 10:02 CET (History)
3 users (show)

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


Attachments

Description Kristoffer Grundström 2017-12-12 01:54:46 CET
Description of problem: python-igraph is missing in the official Mageia 6 medias. I was looking in the Fedora spec file for the Tribler client and it's listed as a require.

Version-Release number of selected component (if applicable): 0.7.1
Kristoffer Grundström 2017-12-12 01:55:43 CET

CC: (none) => hamnisdude
Priority: Normal => High

Comment 1 Marja Van Waes 2017-12-13 07:02:12 CET
We do have igraph in cauldron, which seems to be the C version... I don't understand why there are also python and R versions of igraph.

I suppose the C version should do everything the python version does, since igraph was imported into cauldron because of your request for python-igraph in bug 21312

Changing this report into a backport request for stable and assigning to the igraph maintainer.

Priority: High => Normal
Assignee: bugsquad => shlomif
Summary: Add python-igraph to Core Updates => Add igraph to Core Backports
CC: (none) => marja11
Keywords: (none) => Backport
Source RPM: python-igraph => igraph
Version: 6 => Cauldron
Severity: normal => enhancement
Component: New RPM package request => RPM Packages

Comment 2 Shlomi Fish 2018-07-04 15:51:49 CEST
igraph backport submitted to mga6 - pls test.
Comment 3 Lewis Smith 2019-12-02 19:58:30 CET
@ Kristoffer : you did not reply to the previous comment - which answered your request.
We are now in Mageia 7, which has igraph. Do you want to comment on this, or shall we close the bug?

CC: (none) => lewyssmith
Assignee: shlomif => bugsquad

Comment 4 Kristoffer Grundström 2019-12-02 20:22:29 CET
Uhm.
I'm not really sure if igraph and python's igraph package use the same source.
Comment 5 Lewis Smith 2019-12-08 12:12:14 CET
(In reply to Kristoffer Grundström from comment #4)
> I'm not really sure if igraph and python's igraph package use the same
> source.
Does this matter? If Mageia's 'igraph' package does the job, what would be the advantage of adding 'python-igraph' - if indeed that is different?

The bug title says "Add igraph": resolved, fixed (comment 2, 2018).
The description talks about 'Tribler client' - which we do not seem to have; so the related "python-igraph ... listed as a require" is not the issue.

Do you agree?
Comment 6 Kristoffer Grundström 2019-12-09 02:31:41 CET
(In reply to Lewis Smith from comment #5)
> (In reply to Kristoffer Grundström from comment #4)
> > I'm not really sure if igraph and python's igraph package use the same
> > source.
> Does this matter? If Mageia's 'igraph' package does the job, what would be
> the advantage of adding 'python-igraph' - if indeed that is different?
> 
> The bug title says "Add igraph": resolved, fixed (comment 2, 2018).
> The description talks about 'Tribler client' - which we do not seem to have;
> so the related "python-igraph ... listed as a require" is not the issue.
> 
> Do you agree?

The differences between igraph and python-igraph according to people in the #python channel on IRC is:

The genode.

igraph is a C library whilst python-igraph is a python interface to it, but I get your point if it actually does the same.
Comment 7 Lewis Smith 2019-12-10 10:02:29 CET
Good.

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


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