all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: 52652@debbugs.gnu.org
Subject: bug#52652: FreeCAD requires write access to store for parsetab.py
Date: Sun, 19 Dec 2021 03:07:27 +0000	[thread overview]
Message-ID: <2cd187f7-cfc1-02c4-51a8-b8f0c791a605@rixotstudio.cz> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]

The FreeCAD on guix with patch 52608 to satisfy the dependency for 
python-ply requires write access to the store to work with OpenSCAD files:

Steps to reproduce:
0. Get FreeCAD and open a new project
2. Navigate to OpenSCAD workbench
3. In top-menu: OpenSCAD -> Add OpenSCAD Element...
4. Try to create `cube()` as **NON**-mesh and expect the following:

ImportCSG Version 0.6a
Start Lex
End Lex
Load Parser
WARNING: Token 'DOT' defined, but not used
WARNING: Token 'WORD' defined, but not used
WARNING: There are 2 unused tokens
WARNING: Couldn't create 'parsetab'. [Errno 30] Read-only file system: 
'/gnu/store/wga178lb0hiwyplv00mpvv6q3i74nqbr-freecad-0.19.2/Mod/OpenSCAD/parsetab.py'
Parser Loaded
Start Parser
size vector
('size', ['1', '1', '1'])
('center', 'false')
cube :  {'size': ['1', '1', '1'], 'center': 'false'}
End Cube
End Parser
[<Part::PartFeature>]
End processing CSG file

-- 
-- Jacob Hrbek


[-- Attachment #1.2: publickey - kreyren@rixotstudio.cz - 1677db82.asc --]
[-- Type: application/pgp-keys, Size: 713 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

             reply	other threads:[~2021-12-19  3:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19  3:07 Jacob Hrbek [this message]
2021-12-31 10:44 ` bug#52652: FreeCAD requires write access to store for parsetab.py Guillaume Le Vaillant
2021-12-31 13:26   ` Jacob Hrbek
2021-12-31 13:29     ` Guillaume Le Vaillant

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=2cd187f7-cfc1-02c4-51a8-b8f0c791a605@rixotstudio.cz \
    --to=kreyren@rixotstudio.cz \
    --cc=52652@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.