From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: igraph: update to 0.10.2.
Date: Mon, 31 Oct 2022 00:17:50 +0100 [thread overview]
Message-ID: <20221030231750.PWy6AQ9muvJFb8aqj2C_1ISkCpc7SFL1p034LyO_TTk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40224@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/40224#issuecomment-1296375680
Comment:
> does `rankwidth` need to be revbumped for this?
No, because it's statically linked. But maybe it should (so we make sure it still builds ok).
Maybe I should put together update SuiteSparse (#39846) + update igraph + revbump rankwidth. I'm not in a hurry with this, the priority is to get sagemath updated (#39876) and hopefully working with python 3.11.
BTW, the issue with SuiteSparse is that there are file conflicts between `SuiteSparse-devel` and `mongoose-devel`, but those already conflict in current versions (try `xlocate libmongoose`). I don't know if there's anything we can do about this. Hopefully the sonames remain different.
next prev parent reply other threads:[~2022-10-30 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 17:30 [PR PATCH] " tornaria
2022-10-30 19:06 ` classabbyamp
2022-10-30 23:17 ` tornaria [this message]
2022-10-31 15:08 ` szhorvat
2022-10-31 15:11 ` szhorvat
2022-11-03 2:16 ` tornaria
2022-11-12 19:19 ` [PR PATCH] [Updated] " tornaria
2022-11-13 2:52 ` tornaria
2022-11-15 19:14 ` [PR PATCH] [Updated] " tornaria
2022-11-16 2:47 ` tornaria
2022-12-03 22:36 ` [PR PATCH] [Merged]: " Piraty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221030231750.PWy6AQ9muvJFb8aqj2C_1ISkCpc7SFL1p034LyO_TTk@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).