From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: blender: update to 2.90.1.
Date: Tue, 13 Oct 2020 21:39:31 +0200 [thread overview]
Message-ID: <20201013193931.EK1DRwu2SJsGhCru1022isgIV8hsInhgNkY9Y-JBhPk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25547@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/25547#issuecomment-707965037
Comment:
Apparently this will time out on CI, but it builds locally for `x86_64*`. This version does *not* address the Python 3.9 crash reported, but I tracked it down to a call to the deprecated function `PyEval_ReleaseLock` that segfaults on Python 3.9.0. This issue also affects gdb and is easily patched. (See [`srcpkgs/gdb/patches/py39.patch`](https://raw.githubusercontent.com/void-linux/void-packages/master/srcpkgs/gdb/patches/py39.patch).)
If nobody complains in the next day or two, I'll merge this and we should have a working Blender. If somebody objects to the update, we can backport this simple patch (along with the existing `py39.patch` for Blender) and at least get a working version 2.83.6 (or 2.83.7).
next prev parent reply other threads:[~2020-10-13 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 18:43 [PR PATCH] " ahesford
2020-10-12 20:12 ` [PR PATCH] [Updated] " ahesford
2020-10-12 21:12 ` martnnw
2020-10-13 19:33 ` [PR PATCH] [Updated] " ahesford
2020-10-13 19:34 ` ahesford
2020-10-13 19:39 ` ahesford [this message]
2020-10-14 1:49 ` ericonr
2020-10-14 14:19 ` [PR PATCH] [Updated] " ahesford
2020-10-14 14:55 ` [PR REVIEW] " mvf
2020-10-14 14:56 ` mvf
2020-10-14 18:55 ` [PR REVIEW] " ahesford
2020-10-14 19:17 ` [PR PATCH] [Closed]: " ahesford
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=20201013193931.EK1DRwu2SJsGhCru1022isgIV8hsInhgNkY9Y-JBhPk@z \
--to=ahesford@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).