Ren'py 8.2.0 Crash on startup

  • Open
  • quality assurance status badge
Details
2 participants
  • Liliana Marie Prikler
  • msglm
Owner
unassigned
Submitted by
msglm
Severity
normal
M
M
msglm wrote on 7 Feb 21:38 +0100
(address . bug-guix@gnu.org)
CYZ4RBC62OPU.3L52B5DJ5G7F3@joybuke-desktop
When starting the ren'py launcher on version Ren'Py 8.2.0.24012702,
currently my guix channel is on commit
5d2302a1959d09e6d5a5f02ac199458095847a82, the program crashes with the
following error:

Full traceback:
File "/gnu/store/2m851i42kc8i929rfhrn6w545w6a94lz-python-renpy-8.2.0/lib/python3.10/site-packages/renpy/bootstrap.py", line 354, in bootstrap
renpy.config.logdir = renpy.__main__.path_to_logdir(basedir)
AttributeError: module '__main__' has no attribute 'path_to_logdir'
L
L
Liliana Marie Prikler wrote on 8 Feb 09:09 +0100
73bf25e6ece8ffe35afc41cb31eed552a0099d4b.camel@student.tugraz.at
Am Mittwoch, dem 07.02.2024 um 14:38 -0600 schrieb msglm:
Toggle quote (11 lines)
> When starting the ren'py launcher on version Ren'Py 8.2.0.24012702,
> currently my guix channel is on commit
> 5d2302a1959d09e6d5a5f02ac199458095847a82, the program crashes with
> the following error:
>
> Full traceback:
>   File "/gnu/store/2m851i42kc8i929rfhrn6w545w6a94lz-python-renpy-
> 8.2.0/lib/python3.10/site-packages/renpy/bootstrap.py", line 354, in
> bootstrap
>     renpy.config.logdir = renpy.__main__.path_to_logdir(basedir)
> AttributeError: module '__main__' has no attribute 'path_to_logdir'
If you have a local guix checkout, try adding the following lines to
gnu/packages/aux-file/renpy.in:

def path_to_logdir(basedir):
return basedir

However, it seems upstream also has a predefined_searchpath added in
8.2, and changed the semantics of path_to_saves. I think we might want
to revert to 8.1 to deal with all those changes properly.

Cheers
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 68982@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 68982
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch