On 2022-01-13 23:15, Ludovic Courtès wrote:
> Andrew Tropin skribis:
>
>> A day ago I found out that I can't pull/time-machine from my local guix
>> repo with patches. After running guix time-machine -C ./channels ...,
>> guix reported the following:
>>
>> Updating channel 'guix' from Git
Am Freitag, dem 14.01.2022 um 00:17 -0500 schrieb Faerryn:
> It looks like module tkinter doesn't load for some reason. Here is
> the tail of the build log:
Note that a patch to exclude tkinter and winreg from the sanity check
is already in the mailing list [1], but hasn't been applied yet.
Looks like upgrading zeroconf (33898cd5b7fa5cd3c5e5af17d72ee84a95b6a5ba)
broke calibre:
...
starting phase `install'
...
Installing calibre environment module: /gnu/store/q227rjddwqxvkd165ydj648gmak7x4xi-calibre-5.21.0/lib/python3.9/site-packages/init_calibre.py
Traceback (most recent call last):
bash-5.0$ flameshot
(process:6205): Gtk-WARNING **: 06:51:44.636: Locale not supported by C
library.
Using the fallback 'C' locale.
QSettings::value: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
QSettings::value: Empty key passed
Hi Leo,
Leo Famulari writes:
> On Guix Git commit c7d74a9bccfc1b1274fc8754a6e78bb6887c7fea, at least
> some manpages are not being built correctly for packages such as elogind
> and gnome-keyring-daemon. Are we seeing raw groff input? I'm not sure of
> the technology used here.
Thank you for
S_ I_ 写道：
| 'patch-xserver' phasebuilder
I've fixed the build on master and am hopefully closing this bug.
Please reopen it if the package still has problems.
Kind regards,
T G-R
signature.asc
Description: PGP signature
It looks like module tkinter doesn't load for some reason. Here is the
tail of the build log:
starting phase `sanity-check'
validating 'future'
/gnu/store/9qknps8svnw5njfr823bm1il1gw5nxlm-python2-future-0.18.2/lib/python2.7/site-packages
...checking requirements: OK
...trying to load module
Tobias Geerinckx-Rice 写道：
This sounds like your guix is out of date.
Never mind, the problem was here.
I can reproduce the failure (the error message is pleasantly clear
for once :-).
Kind regards,
T G-R
signature.asc
Description: PGP signature
Hullo,
S_ I_ 写道：
building
/gnu/store/yr3qw7zy5r60w8ijfs6zsfmcd04p83hm-tigervnc-server-1.11.0.drv...
| 'patch-xserver' phasebuilder for
`/gnu/store/yr3qw7zy5r60w8ijfs6zsfmcd04p83hm-tigervnc-server-1.11.0.drv'
failed with exit code 1
This sounds like your guix is out of date.
Could you run
guix install tigervnc-server
The following package will be installed:
tigervnc-server 1.11.0
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
The following derivations will be built:
Hello Simon,
Simon Streit writes:
> While experimenting with Samba, I noticed that some tools, especially
> samba-tools will not run, and crash:
>
> root@motor ~# samba-tool
> Traceback (most recent call last):
> File "/run/current-system/profile/bin/samba-tool", line 33, in
> from
>What do you mean by “freezing”? Does ‘herd status’ and similar commands
block forever?
Yes
>Requests in the Shepherd are currently handled sequentially. So if you
issue several ‘herd restart’ commands, they’ll be processed one at a
time. This is usually okay because ‘start’ commands are
Andrew Tropin skribis:
> A day ago I found out that I can't pull/time-machine from my local guix
> repo with patches. After running guix time-machine -C ./channels ...,
> guix reported the following:
>
> Updating channel 'guix' from Git repository at
>
Hi Leo!
Leo Famulari writes:
> On Thu, Jan 13, 2022 at 12:42:18PM -0500, Maxim Cournoyer wrote:
>> Hello Guix,
>>
>> I'm lacking investigation detail, but this seems worthy of reporting.
>>
>> I had tested installing gnome-terminal from guix on top of a Debian
>> stable distribution, and was
Hello,
[ Sending again to 48903 (and excluding everyone else from the recipients)
because this bug was archived and thus the original message bounced. ]
I’m sending this email to two bugs because they are both about the same
problem. Bug 48903 (which is currently closed) has fairly intense
Hello,
I’m sending this email to two bugs because they are both about the same
problem. Bug 48903 (which is currently closed) has fairly intense attempts
at debugging what is going on, but unfortunately without arriving at an
answer.
This problem is also affecting Cuirass builds. This
Hello,
I discovered that on a Debian 9 (stretch) box equipped with
gnome-terminal 3.22.2, Guix would use terminal ANSI codes to represent
hyperlinks in its output, which were not supported by GNOME terminal
3.22.2 which uses VTE 0.46.1 (it picked up support in 3.26 IIRC).
Thanks,
Maxim
On Thu, Jan 13, 2022 at 12:42:18PM -0500, Maxim Cournoyer wrote:
> Hello Guix,
>
> I'm lacking investigation detail, but this seems worthy of reporting.
>
> I had tested installing gnome-terminal from guix on top of a Debian
> stable distribution, and was surprised that login would not longer
Hello Guix,
I'm lacking investigation detail, but this seems worthy of reporting.
I had tested installing gnome-terminal from guix on top of a Debian
stable distribution, and was surprised that login would not longer work
(!) until I 'guix remove gnome-terminal' from a TTY.
We should
Hi Ludo!
Ludovic Courtès writes:
> Hello,
>
> Maxim Cournoyer skribis:
>
>> + herd -s t-socket-1651 status root
>> Started:
>> + root
>> + herd -s t-socket-1651 stop root
>> ++ cat t-pid-1651
>> + kill 1896
>> + exit 1
>> + rm -f t-socket-1651
>> + test -f t-pid-1651
>> ++ cat t-pid-1651
>> +
Hello,
Ludovic Courtès writes:
> Hi,
>
> Mathieu Othacehe skribis:
>
>>> This sounds a lot like this:
>>>
>>> https://issues.guix.gnu.org/32182#1
>>
>> I was just kicked out of my own server due to this PAM/SSH issue. It
>> happens quite frequently here. Time for a fix :).
Not a meaningful
Seems issue appeared after 9f371f23eb.
This one fails:
guix time-machine --commit=9f371f23ebfa20f70b3bfd55dc459b683f21ba91 --
time-machine --commit=d87d6d6812 --disable-authentication -- describe
This one works:
guix time-machine --commit=1a0696e0a6dcde342094712957037c586f572efb --
Hello,
Maxim Cournoyer skribis:
> + herd -s t-socket-1651 status root
> Started:
> + root
> + herd -s t-socket-1651 stop root
> ++ cat t-pid-1651
> + kill 1896
> + exit 1
> + rm -f t-socket-1651
> + test -f t-pid-1651
> ++ cat t-pid-1651
> + kill 1896
> + rm -f t-pid-1651
> FAIL
Hi,
zimoun skribis:
> Using Guix 3dcc74d, 'sed' and 'cat' are missing from 'texinfo'.
Are these two programs just used by texi2dvi?
We could patch texi2dvi to refer to them by absolute file name, from
‘coreutils-minimal’.
> Moreover, 'texlive' seems also missing.
We won’t propagate that
Hi,
Mathieu Othacehe skribis:
>> This sounds a lot like this:
>>
>> https://issues.guix.gnu.org/32182#1
>
> I was just kicked out of my own server due to this PAM/SSH issue. It
> happens quite frequently here. Time for a fix :).
Note that ‘guix deploy’ now opens a single SSH session,
Hi,
On Thu, 25 Nov 2021 at 00:39, zimoun wrote:
> On Tue, 23 Jan 2018 at 13:00, Ricardo Wurmus wrote:
>
>>> When a python module needs to load a dynamic shared object, it looks in the
>>> path provided by *LD_LIBRARY_PATH*(1), but guix doesn't modify this
>>> environment
>>> variable to export
Hi,
Nathan Dehnel skribis:
> When dns is specified, wireguard runs wg-quick, which runs resolvconf,
> which runs /run/current-system/profile/bin/herd restart, which causes
> shepherd to freeze because I guess it doesn't like being given
> multiple start commands at once. I'm not sure how to fix
Hello,
Mathieu Othacehe skribis:
>> Hmm. Can we keep “image” persistent by default, and make ‘vm’ volatile
>> by default? That way, ‘--volatile’ would only make sense for ‘image’,
>> and ‘--persistent’ would only make sense for ‘vm’. (So we’d be adding
>> just one option: ‘--persistent’.)
>>
A day ago I found out that I can't pull/time-machine from my local guix
repo with patches. After running guix time-machine -C ./channels ...,
guix reported the following:
--8<---cut here---start->8---
Updating channel 'guix' from Git repository at
> Yeah nautilus doesn't build at the moment for a similar reason as eog, I
> just posted a patch on https://issues.guix.gnu.org/53195 to fix it. I
> can push it shortly.
Closing, thanks for fixing it Pierre.
Mathieu
> Regarding the two potential solutions that you proposed in 2018, are
> they still actual? If yes, I could maybe try to implement the second
> suggestion: introducing service chain-loading.
Oh sorry, I stopped reading the thread at
https://issues.guix.gnu.org/32182#1. Looks like the service
Hey,
> This sounds a lot like this:
>
> https://issues.guix.gnu.org/32182#1
I was just kicked out of my own server due to this PAM/SSH issue. It
happens quite frequently here. Time for a fix :).
Regarding the two potential solutions that you proposed in 2018, are
they still actual? If yes,
> > Yeah nautilus doesn't build at the moment for a similar reason as eog, I
> > just posted a patch on https://issues.guix.gnu.org/53195 to fix it. I
> > can push it shortly.
>
> Closing, thanks for fixing it Pierre.
Confirming that gnome-desktop now builds completely, thanks Pierre and
Hey,
> Hmm. Can we keep “image” persistent by default, and make ‘vm’ volatile
> by default? That way, ‘--volatile’ would only make sense for ‘image’,
> and ‘--persistent’ would only make sense for ‘vm’. (So we’d be adding
> just one option: ‘--persistent’.)
>
> WDYT?
I'm not fan of adding
34 matches
Mail list logo
