Depending on the exact use case, there are some other possibilities that don't
run "natively" on Guix, but are still free software and could be installed from
Flatpak or Nix. E.g. the Signal client for desktop and Matrix Element.
Though, actually, I think the Nheko client for Matrix (available
Le lundi 01 août 2022 à 15:26 +, Gottfried a écrit :
>
> Jitsi Meet isn't in guix. But Jami is there.
Jitsi is for voice / video calls / screen sharing, it requires running
a server on one machine but particpants just need a web browser (major
web browser work).
I use a cheap VPS to run a
On Tue, 02 Aug 2022, Csepp wrote:
> Olivier Dion via writes:
>
>> Hi,
>>
>> Say I have a .guix.scm in my project with something like
>> (specifications->manifest (list "guile" "guile-fibers" "guile-gcrypt"))
>>
>> If I want to develop with Geiser, it needs to find these modules in its
>> load
On Mon, 01 Aug 2022, "(" wrote:
> On Mon Aug 1, 2022 at 7:45 PM BST, Olivier Dion via wrote:
>> I would like to use guix as a native-inputs for a package. Is there any
>> issue with that?
> Nope :)
There seems to be an issue after all. When building with Guix, my
script failed to access
If you're trying to access the build daemon from inside the package build
container, that must mean you have a derivation you're trying to build. Instead
of trying to circumvent the container (which is there for a reason), you could:
- write a bit of Scheme code that returns that derivation
-
On Tue Aug 2, 2022 at 2:41 PM BST, Olivier Dion wrote:
> There seems to be an issue after all. When building with Guix, my
> script failed to access /var/guix/daemon-socket/socket with `guix
> shell'. I guess there's probably some way to make it available for the
> build?
You're in a container
On Tue, 02 Aug 2022, "(" wrote:
> On Tue Aug 2, 2022 at 2:41 PM BST, Olivier Dion wrote:
>> There seems to be an issue after all. When building with Guix, my
>> script failed to access /var/guix/daemon-socket/socket with `guix
>> shell'. I guess there's probably some way to make it available
Hello,
I've recently setup two Debian11 machines, intalled Guix then Emacs using `guix
install emacs`.
For some reason, it's impossible de input the `ê` character after `emacs -Q` ;
but it is possible to enter the `ê` character after `emacs -Q -nw`.
How to have `guix install emacs` install
Benjamin Slade writes:
> Depending on the exact use case, there are some other possibilities
> that don't run "natively" on Guix, but are still free software and
> could be installed from Flatpak or Nix. E.g. the Signal client for
> desktop and Matrix Element.
>
> Though, actually, I think the
Hi Luis,
Luis Felipe writes:
> Hi Gottfried,
>
> On Monday, August 1st, 2022 at 15:47, Gottfried wrote:
>
>> Has somebody got experience with Jami or Mumble?
>
> I've used Jami until recently. As other people already mentioned, installing
> the "jami" package should be enough.
>
> I only used
Hi Ricardo,
>> Or do you recommend a different way to run NSCD and SSSD at the same time on
>> RHEL/CentOS systems?
>
> You only need to start it. We don't use it as a cache. We are only interested
> in its network interface for use with glibc.
OK! We started NSCD:
% service nscd status
I suppose once you get information about these channels, you could create an
inferior with these channels, and evaluate your package in it.
Le 2 août 2022 19:10:31 GMT+02:00, Olivier Dion a
écrit :
>On Tue, 02 Aug 2022, Julien Lepiller wrote:
>> If you're trying to access the build daemon
On Tue, 02 Aug 2022, Julien Lepiller wrote:
> If you're trying to access the build daemon from inside the package
> build container, that must mean you have a derivation you're trying to
> build. Instead of trying to circumvent the container (which is there
> for a reason), you could:
>
> - write
Hi Chris,
>>> Or do you recommend a different way to run NSCD and SSSD at the same time
>>> on RHEL/CentOS systems?
>>
>> You only need to start it. We don't use it as a cache. We are only
>> interested in its network interface for use with glibc.
[…]
> We turned off all NSCD caching:
>
>
Akib Azmain Turja writes:
> [[PGP Signed Part:Undecided]]
> Benjamin Slade writes:
>
>> Depending on the exact use case, there are some other possibilities
>> that don't run "natively" on Guix, but are still free software and
>> could be installed from Flatpak or Nix. E.g. the Signal client
Or do you recommend a different way to run NSCD and SSSD at the same time
on RHEL/CentOS systems?
>>>
>>> You only need to start it. We don't use it as a cache. We are only
>>> interested in its network interface for use with glibc.
> […]
>> We turned off all NSCD caching:
>>
>> %
Hi,
"cont...@phfrohring.com" writes:
> Hello,
>
> I've recently setup two Debian11 machines, intalled Guix then Emacs using
> `guix install emacs`.
> For some reason, it's impossible de input the `ê` character after `emacs -Q` ;
> but it is possible to enter the `ê` character after `emacs -Q
Christopher Batten writes:
> So my sysadmin and I are worried about turning on caching in NSCD and
> SSSD at the same time? Are you running both and have you seen any
> issues?
We have been running SSSD and NSCD together since a number of years on
all cluster nodes and all RHEL servers.
Hi Guix,
I have some commits on my local guix repo like this:
(master) HEAD -> A -> B -> C
When I do `git format-patch -3 --base=auto` I get prerequisite patch
ids in some of the patches. But I want to each patch to depend only on
HEAD. In other words I want to export patches like so:
HEAD ->
19 matches
Mail list logo
