Re: problem trying to install python module in python virtual environment on top of Guix
Hi Andy, Andy Tai writes: > Hi, on a Guix system I tried to install python dependencies in a > python virtual environment. I installed Guix packages > python-toolchain and python-virtualenv, and use the basic python > commands virtualenv and pip3 to go ahead and install dependencies in a > typical python manner. > > I got one error in a dependencies that tried to build C modules which > involves using cmake in this python environment: (not the system cmake > but something python stuff installed as part of its process): > > Building wheels for collected packages: llama-cpp-python > Building wheel for llama-cpp-python (pyproject.toml) ... error > error: subprocess-exited-with-error > > × Building wheel for llama-cpp-python (pyproject.toml) did not run > successfully. > │ exit code: 1 > ╰─> [9 lines of output] > Traceback (most recent call last): > File > "/tmp/pip-build-env-44zbk4iu/overlay/lib/python3.10/site-packages/skbuild/setuptools_wrap.py", > line 645, in setup > cmkr = cmaker.CMaker(cmake_executable) > File > "/tmp/pip-build-env-44zbk4iu/overlay/lib/python3.10/site-packages/skbuild/cmaker.py", > line 148, in __init__ > self.cmake_version = get_cmake_version(self.cmake_executable) > File > "/tmp/pip-build-env-44zbk4iu/overlay/lib/python3.10/site-packages/skbuild/cmaker.py", > line 105, in get_cmake_version > raise SKBuildError(msg) from err > > Problem with the CMake installation, aborting build. CMake > executable is > /tmp/pip-build-env-44zbk4iu/overlay/lib/python3.10/site-packages/cmake/data/bin/cmake > [end of output] > > note: This error originates from a subprocess, and is likely not a > problem with pip. > ERROR: Failed building wheel for llama-cpp-python > Failed to build llama-cpp-python > ERROR: Could not build wheels for llama-cpp-python, which is required > to install pyproject.toml-based projects > > [notice] A new release of pip is available: 23.1.2 -> 23.2.1 > [notice] To update, run: pip install --upgrade pip > > > wonders if anyone knows if the above can be attempted on top of Guix; > not sure if the C build environment can be seen properly under Python > virtualenv I've had success in the past using the --emulate-fhs option in a containerized shell, but the better option would be to package what you need in Guix proper. > Also the Python tools packaged in Guix seem rather old, and tat can be > part of the issue here. I'm sure the Python team would welcome new members :-). -- Thanks, Maxim
Re: Putting a file into system image ~user/ but not on reconfigure
On Thu, Aug 10, 2023 at 02:38:24PM +0200, Hartmut Goebel wrote: > Am 10.08.23 um 14:12 schrieb wolf: > > > > I guess you could have a script that would use the existence of the key > > itself > > as a marker. In that case you would likely want to recreate it if the > > marker > > (key) got deleted, > > No! The key must not be recreated. The key is expected to be replaced by a > new one when the box will become a machine. Thus, using the key as a marker > is not possible, as the would recreate the insecure key on next reboot. The > key must never ever be put into back into place. I feel compelled to ask if the key must be in ~vagrant/.ssh/authorized_keys or if /etc/ssh/authorized_keys.d/vagrant is acceptable. Also, could you use /etc/services or another file in /etc/static as a marker that the system has been booted at least once before? > > I do not have much experience with Vagrant, but I assumed the general idea > > for > > these kind of systems declarative systems is to just recreate the when > > updates > > are required. Is it expected to actually run guix reconfigure inside the > > VM? > > This depends on how one uses the virtual machines :-) > > And even if it is not expected to run guix reconfigure on it: If one does, > this but open a front door to the system - which is not what one wants. I suppose if you did include an /etc/os-config file you could include a custom one that doesn't include the file placed in ~vagrant and only have it in the initial creation config. They could still extract the actual file from `guix system describe` but I don't suppose there's much you could do there other than leave a warning to remove those lines. > > Anyhow, thanks for sharing thoughts, > > -- > Regards > Hartmut Goebel > > | Hartmut Goebel | h.goe...@crazy-compilers.com | > | www.crazy-compilers.com | compilers which you thought are impossible | > > -- Efraim Flashner רנשלפ םירפא GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Trying to understand why GUIX isn't reading configuration file?
Previously what I thought was a gdm issue, upon further investigation I believe this to be a guix issue or my lack of understanding guix way of doing things. My current issue is after installing guix with a guided installation. I preceded to install bspwm as a user, what is happening is I created a .xsession file and chmod +x ~/.xsession with the following content: sxhkd -c $HOME/.config/sxhkd/sxhkdrc & polybar -c $HOME/.config/polybar/config & exec bspwm -c $HOME/.config/bspwm/bspwmrc At first I've tried: exec bspwm And it still doesn't work. The issue that I'm not understanding is the bspwmrc file isn't being read after logging in so I have to open a terminal and do this. source $HOME/.config/bspwm/bspwmrc Looking at my config.scm file, I've noticed that services-type-desktop only shows XFCE. How can I get bspwm added to this file? Or is there a way to get bspmwmrc file read automatically? At the login screen, although XFCE and BSPWM are both installed there is only a login prompt. To run XFCE I have to remove the ~/.xsession file. XFCE was installed during installation of GUIX, after install as regular user I install BSPWM. -- www.pippenbuyshouses.com
