Hi!
I've noticed that when starting SuperCollider IDE (with the scide
command) the Help Browser (which is the panel on top on the right side
with vanilla/no configuration) doesn't show any text. IIRC
SuperCollider's documentation is HTML documents (you can also browse it
online [1]) displayed thr
I've come to notice that Fritzing currently does not work in Guix. The
program starts but greets the user with a bunch of warnings/error
pop-ups. One being about "142 parts" missing or not being found and
indeed: the parts pane remains empty and Fritzing therefor unusable.
634fa7e8ed3b5c5dff4 Mon Sep 17 00:00:00 2001
From: Gabriel Wicki
Date: Thu, 10 Nov 2022 01:53:41 +0100
Subject: [PATCH] * gnu/packages/engineering.scm (fritzing): Update to 0.9.6.
[source]: Update hash.
[arguments]: Update libgit2 hacks.
---
gnu/packages/engineering.scm | 34 ++-
ve adjusted it to a less ugly "true".
I'm sorry i don't have the capacity to provide a more satisfying
solution ATM but at least Fritzing is back to a usable state.
Best wishes,
g
> From 242f0f7858435600303333a811635c0c4a72d81b Mon Sep 17 00:00:00 2001
From: Gabriel Wi
i tried running `guix install mes` which fails on my x86_64 debian
machine. CI fails as well
(https://ci.guix.gnu.org/build/286577/details).
log output shows a couple of segmentation faults and an undefined
variable in phase 'check':
test/test10/hello.sh
+ '[' amd64 = amd64 ']'
+ ./test/results/t
(This is a reply to the original bug report [0]; cross-posting to
bug-...@gnu.org for reasons described below. I hope this is ok)
On Sun, Jun 13, 2021 at 02:52:41PM +0200, Ludovic Courtès wrote:
> Hi,
Hello!
I guess i need to clarify: it's not mes building that fails; it's
mescc-tools (version 0.
Hi
Trying to upgrade a somewhat outdated system (from March 23) I noticed
igt-gpu-tools failed to build. Investigating a bit the build fails due
to some "proc/readproc.h" include missing. I think i managed to fix the
failure in procps's Makefile, but testing the patched build results in a
rather
A little more hacking leads me to the conclusion that (probably with
version 4 but it's not exactly clear from the changelog) procps has made
some significant changes to it's API. So, unless igt-gpu-tools (and
probably others) are fixed upstream they remain broken. Fixes through
simple regex-magi
Trying to set up my Pinebook Pro with my favorite distribution i found
out that the usual way (invoking `guix system image
gnu/system/images/pinebook-pro.scm` to build an image which is then dd'd
to a micro SD card) does not yield a working result.
Doing the same with guix time-machine on commit
c
commit b0d47d9e18e52ff7935aebe6ab37e702f58101be (Update u-boot to
2023.07.02) breaks creation of a bootable image.
Building in a time-machine at commit
d6a53849935f8584e1df57faa79c18c23fbb2aa1 works as expected.
This issue seems to have been fixed by Tobias with commit
22642d460488896ec1ddb25d7eb262938db810eb
using a patch to work around the issue. I created a patch that'd
upgrade to the next version where igt-gpu-tools is actually fixed (so
the patch is not needed anymore): https://issues.guix.gnu.org/67
linux-libre-documentation fails to build (see
https://ci.guix.gnu.org/build/3512631/details)
The python-django package makes the admin utility create a manage.py
file with a hard-coded python interpreter.
$ guix shell python python-django -- django-admin startproject foobar
$ head -n 1 foobar/manage.py
#!/gnu/store/my2j5bzapayk59971z2ryzlajdz569f9-python-toolchain-3.10.7/bin/python
Running
guix shell python-django -- django-admin
throws a "ModuleNotFoundError: No module named 'django'".
8f1 Mon Sep 17 00:00:00 2001
Message-ID:
<5601bbf93baf65e1f6902bf678acb9dddb9e98f1.1728384174.git.gabr...@erlikon.ch>
From: Gabriel Wicki
Date: Tue, 8 Oct 2024 12:41:14 +0200
Subject: [PATCH] gnu: python-django: Fix broken django-admin executable.
* gnu/packages/django.scm (python-django) [ph
Hi Richard!
I just stumbled over the same issue and while i am not really sure what
to think about the screen/tmux/SIGHUP proposal (does this apply to all
deploy commands or just a more fancy/sophisticated usage scenario?) i'd
go with the special --reboot flag to the deploy command that
1. cause
Hi!
Thanks for your input!
On Tue, Dec 10, 2024 at 04:59:27PM +0100, Simon Tournier wrote:
> Now, if the purpose of ’django-admin startproject foobar’ is to only
> create generic configuration that does not depends on any Django or
> Python version, then maybe it could be considered as wrong. :-)
Hi there!
Invoking a home container does not create ~/.guix-profile (which in my case
is symlinked to ~/.guix-home/profile). This leads to a problem when
testing my Emacs configuration, since I there add
~/.guix-profile/share/emacs/site-lisp to its load path.
I guess referring to ~/.guix-profile
* guix/scripts/home.scm: Create the symlink.
Change-Id: Ib299c53f7cd0ca6ad204325b5c150d579224afd7
---
guix/scripts/home.scm | 4
1 file changed, 4 insertions(+)
diff --git a/guix/scripts/home.scm b/guix/scripts/home.scm
index b4c82d275f..50aaf2abf6 100644
--- a/guix/scripts/home.scm
+++ b/g
Hi!
IIRC the territory in the installer is in respect to the
language/locale, i.e. if you want to use American English or English
English or Australian English, etc. Other regional settings are to be
configured in a later step.
Have fun with Guix!
Closing this ancient report - SuperCollider worked in the meantime
(including the help browser)
Maybe you need to log out and log back in for environment variables to
take effect in your home profile?
22 matches
Mail list logo