From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 52652@debbugs.gnu.org
Subject: bug#52652: FreeCAD requires write access to store for parsetab.py
Date: Fri, 31 Dec 2021 13:26:01 +0000 [thread overview]
Message-ID: <83c1dbb1-69e2-150b-ace3-ae0daa5986e2@rixotstudio.cz> (raw)
In-Reply-To: <87h7apavpe.fsf@kitej>
[-- Attachment #1.1: Type: text/plain, Size: 809 bytes --]
I started building it after the patch was merged, it finished now and
the presented issue is no longer present.
On 12/31/21 11:44, Guillaume Le Vaillant wrote:
> Hi,
>
> With Guix at b7078d5d49d72cb5e5356d698b99540612b4d6c4, I tried to
> reproduce the issue, but I didn't get any error.
>
> I started FreeCAD with:
>
> --8<---------------cut here---------------start------------->8---
> guix shell freecad openscad -- FreeCAD
> --8<---------------cut here---------------end--------------->8---
>
> Then I selected "OpenSCAD" in the box, then the "OpenSCAD -> Add
> OpenSCAD Element" menu item, then I typed "cube();", clicked "Add", and
> it created a cube without any error message (I tried with the "mesh" box
> ticked and unticked).
>
> Can you still reproduce the issue on your side?
--
-- 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 --]
next prev parent reply other threads:[~2021-12-31 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 3:07 bug#52652: FreeCAD requires write access to store for parsetab.py Jacob Hrbek
2021-12-31 10:44 ` Guillaume Le Vaillant
2021-12-31 13:26 ` Jacob Hrbek [this message]
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
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=83c1dbb1-69e2-150b-ace3-ae0daa5986e2@rixotstudio.cz \
--to=kreyren@rixotstudio.cz \
--cc=52652@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).