Maybe I should start a new topic, but I thought I'd put this here since I'm working out of beta25.
Fortunately, I've gotten good enough with manipulating upper_changes that I can break the system and revert with little effort. My remaster has been running well, and I've added a couple of numbered upper_changes directories after making tweaks. The nice thing about upper_changes as opposed to a save file, is you can document the incremental growth of the system a little more easily, and roll back to specific spots.
So my question or comment has to do with doing a system wide update yesterday.
I installed the Void updates which also updated lilypond and that seemed to break frescobaldi, the lilypond code editor. However after rolling back and breaking it again, then examining the terminal output of the xbps update, I'm more inclined to think frescobaldi broke due to python3.10.8 apparently updating to python3.11.0_1. And I notice from the output below that it byte compiles code for modules of python based applications like ranger.
Code: Select all
python3-3.11.0_1: configuring ...
Byte-compiling python code in usr/lib/python3.11...
Byte-compiling python3.11 code for module README.txt...
Updating ldconfig(8) cache...
python3-3.11.0_1: updated successfully.
python3-PyQt5-5.15.7_2: configuring ...
Byte-compiling python3.11 code for module PyQt5...
Updating ldconfig(8) cache...
python3-PyQt5-5.15.7_2: updated successfully.
python3-PyQt5-svg-5.15.7_2: configuring ...
Byte-compiling python3.11 code for module PyQt5...
Updating ldconfig(8) cache...
python3-PyQt5-svg-5.15.7_2: updated successfully.
python3-cairo-1.20.1_4: configuring ...
Byte-compiling python3.11 code for module cairo...
Updating ldconfig(8) cache...
python3-cairo-1.20.1_4: updated successfully.
python3-cups-2.0.1_4: configuring ...
python3-cups-2.0.1_4: updated successfully.
python3-gobject-3.42.2_2: configuring ...
Byte-compiling python3.11 code for module gi...
Byte-compiling python3.11 code for module pygtkcompat...
Updating ldconfig(8) cache...
python3-gobject-3.42.2_2: updated successfully.
python3-sip-PyQt5-12.11.0_2: configuring ...
Byte-compiling python3.11 code for module PyQt5...
Updating ldconfig(8) cache...
python3-sip-PyQt5-12.11.0_2: updated successfully.
ranger-1.9.3_4: configuring ...
Updating MIME database...
Byte-compiling python3.11 code for module ranger...
Updating ldconfig(8) cache...
ranger-1.9.3_4: updated successfully.
Running frescobaldi from the terminal gives me this error message below, which suggests since I installed it using @wiak's compiled package, perhaps it's not somehow being picked up by xbps and updated. Or maybe it's just incompatible with python3.11:
Code: Select all
root# frescobaldi
Traceback (most recent call last):
File "/sbin/frescobaldi", line 31, in <module>
from frescobaldi_app import toplevel
ModuleNotFoundError: No module named 'frescobaldi_app'
I checked the file /sbin/frescobaldi and line 31 says that it's looking for frescobali_app. I'm wondering how hard it would be to manually get the path correct, or the module built.
Or I might have to choose to ditch frescobaldi on KLV, or freeze my system updates at python3.10.8
OR, maybe I should just uninstall frescobaldi and reload the package? That sounds like it should work.
And maybe even a better idea is to roll back before updaing , and uninstall frescobaldi first, then update, then reload the package... am I getting warmer?