Hi,
On Sat, 05 Dec 2020 at 20:42, "Bonface M. K." wrote:
> Just curious, how do you get debbugs to show
> forgotten patches. I'm only beginning to use it
> now ...
Forgotten patches are just old patches. ;-)
What I do with Emacs is: “M-x debbugs-gnu“ to have all the bugs and
patches; with
On Sun, Dec 06, 2020 at 03:20:50PM -0500, Leo Famulari wrote:
> `guix refresh --list-dependents` doesn't dependencies that go through
> build systems, unfortunately. You could do `git grep ruby-build-system
> gnu/packages`, choose some test packages, and let the build farm sort
> out the rest.
Hi All,
I believe the recommended suggestion is Debian specific is it not?
My kernel supports user namespaces and doesn't expose that file at that
location.
The only way I can work around the issue is to downgrade guix to the commit
on the master branch right before
Hi Zimoun,
I tried as you suggested but it didn't work...
root@guix ~# echo "kernel.unprivileged_userns_clone = 1" >
/etc/sysctl.d/local.conf
-bash: /etc/sysctl.d/local.conf: No such file or directory
root@guix ~# sysctl --system
root@guix ~# logout
~$ guix environment -C
On Sun, Dec 06, 2020 at 07:11:49PM +, Ryan Prior wrote:
> It would be great if we can update the default Ruby to 2.7.2. Is there a
> process for updating Ruby I can follow to help out?
I don't know about Ruby in particular. The general process for updating
a "compiler" package is to update
On December 6, 2020, Ricardo Wurmus wrote:
> What do you think about adding an output format that is no format at
> all
> but a file enumeration printed to stdout? That way I could use “guix
> pack” to produce a list of files to transfer and use that to transfer
> only the unchanged files.
On December 6, 2020, Leo Famulari wrote:
> Are there any other changes we should make on [staging]?
It would be great if we can update the default Ruby to 2.7.2. Is there a
process for updating Ruby I can follow to help out?
Hello Arun,
Yes it is a typo, it should have been the 20th.
I will update it
https://libreplanet.org/wiki/FOSDEM2021-devroom-declarative-and-minimalistic-computing
Thank you,
Manolis
On Sun, 6 Dec 2020 at 20:03, Arun Isaac wrote:
>
>
> > = Important dates: =
> >
> > - Dec 15th 2020:
On Sat, Dec 05, 2020 at 10:41:50PM +0100, Tobias Geerinckx-Rice wrote:
> I think you misunderstood my (and Ludo's) point, which was to prevent
> possible abuse of a name still in common use. For whatever reason, outside
> of our little echo chamber people say GuixSD, not Guix System. Squatting
>
> = Important dates: =
>
> - Dec 15th 2020: submission deadline for talk proposals
> - Dec 15th 2020: submission deadline for recordings
Is there a typo here? Are the submission deadlines for the talk
proposals and the recordings both on Dec 15?
> - Dec 31th 2020: announcement of the
Hello,
I just pushed a fix for #40832 (alsa-lib cannot find its plugins) to a
new 'staging' branch on Savannah.
The plan is to start building it next Friday, December 11.
Marius is planning to update Qt and Mesa in this round.
Are there any other changes we should make on this branch?
Leo
Hi,
On Sat, 05 Dec 2020 at 22:41, Tobias Geerinckx-Rice wrote:
> I think you misunderstood my (and Ludo's) point, which was to
> prevent possible abuse of a name still in common use. For
> whatever reason, outside of our little echo chamber people say
> GuixSD, not Guix System. Squatting
Hi,
Please try the recommendation. Have you tried it?
please set /proc/sys/kernel/unprivileged_userns_clone to "1"
As root, you just do:
echo 1 > /proc/sys/kernel/unprivileged_userns_clone
then “guix environment -C” should work as expected. To do the trick
automatically with Sheperd, I
yasu 写道：
Now, I don't use Debian at all (I use Guix System) and do you
think
this is a Bug in Guix (in that this Debian specific word should
never
even be mentioned in Guix?)
It's not Debian-specific. It is a bug in Guix.
It should try to create a namespace and properly report an error
On Sun, Dec 06, 2020 at 03:57:00PM +0100, Ricardo Wurmus wrote:
> A common complaint about Guix is that it requires root permissions to
> install, which is “scary” and may seem unnecessary on single-user
> systems. By wrapping guix-daemon so that it uses file system
> virtualization (via user
Ricardo Wurmus writes:
> Bonface M. K. writes:
>
>> Just curious, how do you get debbugs to show
>> forgotten patches. I'm only beginning to use it
>> now ...
>
> Debbugs doesn’t have a built-in mechanism to query forgotten issues.
> Mumi implements “forgotten-bug-numbers”, which has the
Hi Guix,
recently I’ve been playing with “guix pack -RR” and I’m very happy to
see how well it works. Now I wonder if we could use the very same
mechanism to wrap guix-daemon and let it manage a store directory that
is not located at /gnu/store.
Surely somebody has already tried this?
A common
Hi,
I really don't know much about Linux but it looks like the problem I
reported has something to do with Debian?
https://unix.stackexchange.com/questions/303213/how-to-enable-user-namespaces-in-the-kernel-for-unprivileged-unshare
Now, I don't use Debian at all (I use Guix System) and do you
Hey,
I've been chasing some performance issues in the Guix Build Coordinator
and thought that the size of the WAL file was a contributing factor.
I believe SQLite checkpoints the WAL file after transactions commit, if
the WAL is over 1000 pages in size. At least for the Guix Build
Coordinator
Hi Guix,
“guix pack” is great for deployment of applications to servers that
don’t have Guix. For a project I have a “deploy” target in my Makefile
that essentially does this:
cat $(shell guix pack -RR -e '(load "guix.scm")' -S /bin=bin) | ssh
remote-server "tar xvzf - -C /where/i/want/it"
20 matches
Mail list logo
