Hello Pavel,
> Ok, I tried to format them :)
Thanks, I added commit messages following our guidelines, fixed the
indentation and a few other small details.
Pushed on master!
Mathieu
Hello,
The guix 'texlive' package importer is not working with any package, as
far as I can tell. It does *some* legwork, managing to figure out the
correct URI of the package, but then errors out with signal 11.
Having had a look at previous bug reports, it seems this "signal 11"
thing is not ne
This bug was caused by having my Guix filesystem mounted on a
case-insensitive file system. Re-running pull within the Docker
container mounted on a case-sensitive file system works correctly.
This bug can be closed. Sorry for the noise.
-bjc
On 2022-04-26 18:29, Bastien Rivière wrote:
> Hello,
>
> Here is what I got on my end when running guix home:
>
>> Loading /gnu/store/p74aw384nqzlw73ccr0167lyj8vlj3mr-shepherd.conf.
>> herd: exception caught while executing 'load' on service 'root':
>> In procedure fport_write: Broken pipe
>
> I h
Hi!
Maxim Cournoyer skribis:
> Yeah, I ended up with this [0]:
>
> (define (locate-package-via-git name)
> "Return the location object corresponding to package NAME, searched via
> git."
> (let* ((input-pipe (open-pipe* OPEN_READ
>"git" "grep" "-n" "--column"
Hi Jack,
Jack Hill skribis:
> It's working well for me, allowing connections over both v4 and v6. I
> have another host that I can only access with a v6 via wireguard
> address, which I haven't been able to upgrade yet. I don't anticipate
> any problems there though.
Good, thanks for reporting
Hi,
I've now made some free space. So we have:
- 1GiB of RAM and 16GiB of swap:
> # cat /proc/swaps
> FilenameTypeSizeUsed
Priority
> /dev/mmcblk0p1 partition 1677721216384
-2
- Ab
Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 15:40 [+0200]:
> Hi,
>
> I've now made some free space. So we have:
> - 1GiB of RAM and 16GiB of swap:
> > # cat /proc/swaps
> >
> Filename TypeSize
> UsedPriority
> > /dev/mmcb
Hi André,
André Batista skribis:
> Anyway, the proper think to do is to update guile-git, so I'll be
> opening an issue there.
Yes please! You pretty much already have the code, so we could put
together a new Guile-Git release instead of carrying these modifications
in Guix proper.
(For now c
On Mon, 23 May 2022 16:10:04 +0200
Maxime Devos wrote:
> Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 15:40 [+0200]:
> > Hi,
> >
> > I've now made some free space. So we have:
> > - 1GiB of RAM and 16GiB of swap:
> > > # cat /proc/swaps
> > >
> > FilenameTy
retitle 55583 guix-daemon doesn't cleanly error-out on case-sensitive file
systems.
thanks
Brian Cully schreef op ma 23-05-2022 om 09:00 [-0400]:
This bug was caused by having my Guix filesystem mounted on a
case-insensitive file system. Re-running pull within the Docker
container mounted on a
Ludovic Courtès writes:
> Let me know if anything’s amiss!
Looking all good. v4 and v6 connections are working now.
This issue is related to [1] which was resolved. Pulling to a current
checkout solves this issue.
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55335
Hello,
Yes, the issue is gone, thanks for the fix!
Best regards,
Bastien
On Mon, May 23, 2022, at 3:18 PM, Andrew Tropin wrote:
> On 2022-04-26 18:29, Bastien Rivière wrote:
>
>> Hello,
>>
>> Here is what I got on my end when running guix home:
>>
>>> Loading /gnu/store/p74aw384nqzlw73ccr0167lyj
Maxime Devos writes:
Not sure how a case-insensitivity would cause this, but I think
we
can keep this open -- wouldn't it be better if "guix-daemon"
just says
‘nope, case-sensitivity is required (*), not continuing)?
(*) For reproducible builds, and apparently for substitution.
The issue
Brian Cully schreef op ma 23-05-2022 om 12:54 [-0400]:
> I don’t know of a good way to check this in a file-system
> independent manner
Create a file /gnu/store/case-sensitivity-test (if it doesn't already
exist). Open /gnu/store/CASE-SENSITIVITY-TEST. If it succeeds, you
have a case-sensitive
On Mon, 23 May 2022 16:10:04 +0200
Maxime Devos wrote:
> Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 15:40 [+0200]:
> > Hi,
> >
> > I've now made some free space. So we have:
> > - 1GiB of RAM and 16GiB of swap:
> > > # cat /proc/swaps
> > >
> > FilenameTy
Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 19:30 [+0200]:
> And here I probably lack some knowledge but I was under the
> impression
> that swap was handled transparently by the kernel (through page
> tables,
> virtual memory, and so on), so applications should not notice the
> difference a
Hi Guix,
With Guix commit 4ba4cb1d49d70a00f7236f60bd92e5eccef573dd on Linux x86-64,
I have the following problem trying to import a texlive package:
"""
$ guix import texlive qrcode
command "svn" "export" "--non-interactive" "--trust-server-cert" "-r" "59745"
"svn://www.tug.org/texlive/tags/t
Jack Hill 写道：
"""
$ guix import texlive qrcode
command "svn" "export" "--non-interactive" "--trust-server-cert"
"-r"
"59745"
"svn://www.tug.org/texlive/tags/texlive-2021.3/Master/texmf-dist/doc/latex/qrcode/"
"/tmp/guix-directory.6aY7Gk/doc/latex/qrcode/" failed with
signal 11
guix import: er
Maybe an issue is that I've 2 cores on i686 while I've 4 on armv7h.
Or Maybe I didn't see what was there before (I use screen so it's not
convenient to copy-paste the output). Now I have:
> $ guix pull --commit=f0e9048e98f0789aa98de88984f4ee0fc9687f52 -M 1 -c 1
> Updating channel 'guix' from Git r
On Mon, 23 May 2022 21:08:20 +0200
Denis 'GNUtoo' Carikli wrote:
> I'll now try with the current HEAD to see if that's somehow fixed.
I've a similar failure with HEAD:
> \ 'check' phasebuilder for
> `/gnu/store/m1iyn6y1s3ajl6v0lv5658zq2cngdpq3-ruby-stackprof-0.2.17.drv'
> failed with exit code
Hi!
seg 23 mai 2022 às 16:18:52 (165532), l...@gnu.org enviou:
> Yes please! You pretty much already have the code, so we could put
> together a new Guile-Git release instead of carrying these modifications
> in Guix proper.
Done! Issue 26.
https://gitlab.com/guile-git/guile-git/-/issues/26
Hi,
Ludovic Courtès writes:
> Hello!
>
> Currently (40a729a0e6f1d660b942241416c1e2c567616d4d), shepherd and
> dbus-daemon compete to start elogind: shepherd tries to start it
> eagerly, and dbus-daemon starts it on-demand upon bus activation.
>
> Sometimes dbus-daemon wins, and thus shepherd tri
Hi Ludo,
Ludovic Courtès writes:
> So you confirm that a single “echo” is not enough, right?
I didn't test one specifically. It might work with just one, but it did
work with three. If we want to proceed with the "echo" approach, let me
know and I'll test just one echo to see if that is reliab
25 matches
Mail list logo
