Ludovic Courtès writes:
>>> The last manifest it reads is
>>> /gnu/var/guix/profiles/per-user/wneuber/guix-profile-1-link/manifest
>>> with the following contents
>>>
>>> (manifest
>>> (version 1)
>>> (packages
>>> (("gcc"
>>> "4.9.2"
>>> "out"
>>> "/gnu/store/ym7sybrd
Hi Ludo’,
On 2023-07-12 21:52, Ludovic Courtès wrote:
> Hi,
>
> Bruno Victal skribis:
>
>> Although 'register-services' is exported its counterpart
>> 'deregister-service' is not.
>>
>> Some notes:
>> * 'register-services' is in its plural form while its counterpart
>> is not, maybe one of them
Csepp writes:
> Ludovic Courtès writes:
>
>> Hi,
>> n
>> Csepp skribis:
>>
>>> Ludovic Courtès writes:
>>>
Hi,
Csepp skribis:
> I **finally** managed to finish a guix pull on my netbook by offloading
> it to my desktop machine, and I tried to build the latest yt-d
When the server name can't be resolved (typically because of DNS
problems, though NSS could be used for other resolvers), we get a
backtrace+error message (see end-of-email).
Some kind of error message seems desirable, but:
* the first warning
‘guix weather: waarschuwing: ci.guix.gnu.org:
Hi,
Bruno Victal skribis:
> Although 'register-services' is exported its counterpart
> 'deregister-service' is not.
>
> Some notes:
> * 'register-services' is in its plural form while its counterpart
> is not, maybe one of them should be renamed for consistency sake?
>
> * From the docstring and
Hi Mekeor,
Am Mittwoch, dem 12.07.2023 um 18:19 + schrieb Mekeor Melire:
> If I understand correctly, it is only the following Emacs-packages
> that ship with eln-files when installed with Guix, because they
> specify `#:emacs ,emacs` in the package declaration, so that native-
> compilation i
Emacs can interpret/load at least four kinds of source files.
Listed with increasing performance:
- Emacs-Lisp source code: *.el
- Byte-compiled Emacs-Lisp: *.elc
- Native-compiled Emacs-Lisp: *.eln
- Shared-object files: *.so
Guix installs el- and elc-files into ~/.guix-profile/share/emacs/sit
Hi!
Ludovic Courtès skribis:
> Turns out that this happens when calling the ‘daemonize’ action on
> ‘root’. I have a reproducer now and am investigating…
Good news: this is fixed in Shepherd commit
f4272d2f0f393d2aa3e9d76b36ab6aa5f2fc72c2!
The root cause is inconsistent semantics when mixing
In the first case below, there’s no ‘guix’ command in the environment,
whereas in the second case there is one, as expected:
--8<---cut here---start->8---
$ guix shell -CPW -D -f guix.scm -- guix
guix shell: error: guix: command not found
hint: Did you mean 'gui
Fixed in commit b43841c124d15eaecc41b3928f08a26dbd5c653a
--
Ricardo
Hi Lars,
Lars-Dominik Braun writes:
> I think the problem is bigger than usercustomize. Any custom PYTHONPATH
> also slips through and causes this issue, as well as any custom
> GUIX_PYTHONPATH, because the executable wrapper appends it (think nested
> `guix shell` invokations with different ver
11 matches
Mail list logo
