From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: blender: update to 2.90.1.
Date: Wed, 14 Oct 2020 21:17:03 +0200 [thread overview]
Message-ID: <20201014191703.FAEM9h8gqoKaNzo7_PWJcao0obIazhkMMwAr6JnPkiA@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: 1019 bytes --]
There's a closed pull request on the void-packages repository
blender: update to 2.90.1.
https://github.com/void-linux/void-packages/pull/25547
Description:
Python 3.9 may have broken blender 2.83.6. The patch I pulled to compile against Python 3.9 left me with an installation that can launch, but a user [reported on reddit](https://www.reddit.com/r/voidlinux/comments/j9sj8x/blender_crashing_importing_obj/) that there are some runtime problems. Hopefully an update to 2.90.1 will resolve the issue.
Note that this release relies on 64-bit atomics that don't seem to be available for `i686`, and upstream only provides prebuilt versions for 64-bit Linux systems, so I've dropped `i686*` from the `archs`. We can add it back if there is a straightforward fix.
@martnnw @jkoderu-git, you both weighed in on the last update (#24644) so please comment if there is an argument against moving off of LTS (part of that argument is that the LTS release works against Python 3.9).
cc: @Gottox (package maintainer)
prev parent reply other threads:[~2020-10-14 19:17 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
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 ` ahesford [this message]
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=20201014191703.FAEM9h8gqoKaNzo7_PWJcao0obIazhkMMwAr6JnPkiA@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).