unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Thorsten Wilms <t_w_@freenet.de>
To: 33608@debbugs.gnu.org
Subject: bug#33608: bug#33882: Blender is not loading menu scripts
Date: Sun, 6 Jan 2019 12:03:03 +0100	[thread overview]
Message-ID: <cc76c9a9-df7c-eb04-99bf-953e15e5f08b@freenet.de> (raw)
In-Reply-To: <20190106002725.GA31242@jasmine.lan>

On 06/01/2019 01.27, Leo Famulari wrote:
> But since our Blender package is currently broken, I guess it's the
> right thing to do.
> 
> I will test one more possible fix to our current Blender package, and if
> that fails,I will push the patch to update to "2.80-beta".

Sounds reasonable. However, Blender is a case where it might be 
worthwhile to keep a 2.79 around even after the final release of 2.8, 
because the graphics card requirements have been increased to  OpenGL 
core 3.3 *

* https://www.blender.org/2-8/


-- 
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/

  reply	other threads:[~2019-01-06 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  4:12 bug#33882: Blender is not loading menu scripts znavko
     [not found] ` <handler.33882.B.154588436217739.ack@debbugs.gnu.org>
2018-12-28 16:20   ` bug#33882: Acknowledgement (Blender is not loading menu scripts) znavko
2019-01-05 18:06     ` bug#33608: bug#33882: Blender is not loading menu scripts Ludovic Courtès
2019-01-06  0:27       ` Leo Famulari
2019-01-06 11:03         ` Thorsten Wilms [this message]
2019-01-06 18:19           ` bug#33608: " Leo Famulari
2019-01-07  8:18             ` Thorsten Wilms
2019-01-09 19:36               ` Leo Famulari
2019-02-19 20:54           ` Leo Famulari
2019-03-20 22:36             ` Mark H Weaver
     [not found]             ` <87ftrhdvn2.fsf@netris.org>
2019-03-21 17:41               ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc76c9a9-df7c-eb04-99bf-953e15e5f08b@freenet.de \
    --to=t_w_@freenet.de \
    --cc=33608@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).