From: CaioFrancisco <CaioFrancisco@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: blender: update to 4.3.2
Date: Fri, 10 Jan 2025 10:52:37 +0100 [thread overview]
Message-ID: <20250110095238.096DC20241@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53676@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
New comment by CaioFrancisco on void-packages repository
https://github.com/void-linux/void-packages/pull/53676#issuecomment-2582236306
Comment:
My PR doesn't implement a really clean fix, you might want to look at alternatives (like downloading the Blender binaries and extracting the assets from there, as proposed by sgn in my PR) or just waiting for the Blender developers to properly add the assets submodule to the source code, which is the most sensible solution at the moment.
Slightly unrelated, but I have compiled my own version of Blender to forgo the problem at the moment. You can probably also just copy the assets to where it is expected to be in and it'll work like normal. I recommend doing the same if you want to do use Blender while there's no fix.
next prev parent reply other threads:[~2025-01-10 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 5:05 [PR PATCH] " knightcole
2024-12-26 5:59 ` classabbyamp
2024-12-26 5:59 ` classabbyamp
2024-12-26 5:59 ` classabbyamp
2024-12-26 18:10 ` [PR PATCH] [Updated] " knightcole
2024-12-26 18:10 ` knightcole
2024-12-26 19:31 ` [PR PATCH] [Updated] " knightcole
2024-12-26 19:58 ` classabbyamp
2024-12-30 0:42 ` [PR PATCH] [Updated] " knightcole
2024-12-30 0:52 ` knightcole
2025-01-02 18:50 ` ahesford
2025-01-05 13:35 ` hiltjo
2025-01-08 3:24 ` [PR PATCH] [Updated] " knightcole
2025-01-08 3:34 ` knightcole
2025-01-08 3:38 ` knightcole
2025-01-08 3:43 ` knightcole
2025-01-08 4:43 ` knightcole
2025-01-10 9:52 ` CaioFrancisco [this message]
2025-01-11 23:59 ` knightcole
2025-02-09 21:35 ` [PR PATCH] [Closed]: " knightcole
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=20250110095238.096DC20241@inbox.vuxu.org \
--to=caiofrancisco@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).