André,
André A. Gomes 写道：
How can I close this bug report? Thank you.
When replying, change the nn...@debbugs.gnu.org address to
n-d...@debbugs.gnu.org (or -close, but IME we don't rely on
the subtle distinction?).
I've done so here.
Kind regards,
T G-R
signature.asc
Description:
Hey,
> Is it #:multicast-on or #:allmulticast-on ?
The "ip link set multicast ..." command corresponds to the the
IFF_MULTICAST flag hence to the #:multicast-on parameter.
> Anyhow, I suggest adding a ‘multicast?’ field to , with
> #t as its default value, and honoring this.
I'm not sure is
Leo Famulari writes:
> On Sat, Dec 18, 2021 at 11:32:46PM +, André A. Gomes wrote:
>> I got the following error after issuing guix pull.
>>
>> --8<---cut here---start->8---
>> building package cache...
>> /builder for
>>
Hey,
> It is possible to have more details my editing the
> build-aux/cuirass/evaluate file and replacing all by system-tests. Then,
> running the following command:
Looks like things went back to normal, not sure what fixed it.
Closing,
Mathieu
Hi,
On Wed, Nov 17 2021, Andrew Tropin wrote:
> Test in guix-home.sh looks correct, but it fails:
> https://git.savannah.gnu.org/cgit/guix.git/tree/tests/guix-home.sh?h=5eb5c0789f34e87ee417a53ddfcfa3b6521bb337#n98
>
> Seems something changed in home-bash-service-type, for some reason it
> adds
On Fri, Dec 17, 2021 at 05:09:01PM -0500, Leo Famulari wrote:
> On Wed, Dec 15, 2021 at 08:03:32PM +0200, Efraim Flashner wrote:
> > I got pretty far commenting out binutils-gold and adding back in gcc:lib
> > and the substitute snippets. Then I started failing tests requiring the
> > linker, so
Xinglu Chen schreef op vr 17-12-2021 om 21:57 [+0100]:
> On Fri, Dec 17 2021, Maxime Devos wrote:
>
> > Xinglu Chen schreef op vr 17-12-2021 om 15:03 [+0100]:
> > > (guard (c ((and (http-get-error? c)
> > > (string=? "rate limit exceeded"
> > >
Am Sonntag, dem 19.12.2021 um 14:01 -0600 schrieb bdju:
> guix system
> guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
> build log here: http://ix.io/3IRZ
Hi, I just pushed a patch, that builds cglm with meson, as taisei
appears to be the only package relying on it (according to `guix
Thanks for the details, and I figured out the problem, though not sure of the
fix. A similar issue was reported upstream some time ago:
https://github.com/kozec/syncthing-gtk/issues/428 and
https://gitlab.gnome.org/GNOME/librsvg/-/issues/210
The answer was that multiple librsvg were being
Hello Maxim,
> Now for the "version-1.3.0" branch, which *does* exist.
The specifications are not removed anymore but can be deactivated. The
following error caused by an inconsistency between the
evaluations/specifications table should then be fixed.
Thanks,
Mathieu
Hello,
"bdju" via Bug reports for GNU Guix writes:
> guix system
> guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
>
> build log here: http://ix.io/3ISu
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
On Sun Dec 19, 2021 at 2:09 PM CST, John Kehayias wrote:
> Thanks for checking. I'm on the same Guix commit. Are you sure
> syncthing-gtk is up to date? I'm running on just a WM (XMonad) on Xorg,
> perhaps that is a difference? My path for syncthing-gtk is:
>
>
Hi Leo,
Leo Famulari writes:
> On Fri, Dec 17, 2021 at 11:56:41PM -0500, Maxim Cournoyer wrote:
>> I'm testing this:
>>
>> --8<---cut here---start->8---
>> gnu: gnupg: Update to 2.3.3.
>>
>> * gnu/packages/gnupg.scm (gnupg): Update to 2.3.3.
>>
Hello,
"bdju" via Bug reports for GNU Guix writes:
> guix system
> guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
> build log here: http://ix.io/3IQP
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Hi,
Maxime Devos skribis:
> Alternatively, %outputs (& friends?) could be re-introduced,
> albeit with #$output and #$(this-package-input ...) being strongly
> preferred above %outputs & %build-inputs & friends.
>
> Reintroducing %build-inputs/%build-target-inputs/... could help with
> the ‘how
Hey,
>> What about increasing it to say 180 days?
>
> Sounds good to me. Can you make the change?
That was done with ca6f40272fdf5644597f6ad2e38fa8ab2907d126.
Closing,
Thanks,
Mathieu
On Sun, Dec 19, 2021 at 03:25:42PM -0500, Maxim Cournoyer wrote:
> > I tested with GnuPG 2.2.23 by building all packages that depend directly
> > on GnuPG. There were no new failures on x86_64-linux when using GnuPG
> > 2.2.32.
I see that my message was confusing, with mixed up version numbers.
On Sun, Dec 19, 2021 at 09:06:55PM +, John Kehayias via Bug reports for GNU
Guix wrote:
> Thanks for the details, and I figured out the problem, though not sure of the
> fix. A similar issue was reported upstream some time ago:
> https://github.com/kozec/syncthing-gtk/issues/428 and
>
Hello Clément,
> retitle 32954 Cuirass: logs of failed dependencies are unavailable
Logs of failed dependencies are now available :).
Thanks,
Mathieu
On Sat Dec 18, 2021 at 9:38 PM CST, John Kehayias via Bug reports for GNU Guix
wrote:
> I should have specified it worked on core-updates-frozen before the last
> big changes (input style, etc.) and merge into master.
I've just ran some updates and I'm on
guix (GNU Guix)
I've pushed a patch to master, which fixes the build, but note that
buku remains broken according to the sanity-check phase, meaning that
at least some of its features will be missing. You're of course always
welcome to add missing packages etc.
Cheers
> Thanks to both of you,
And closing!
Mathieu
guix system
guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
build log here: http://ix.io/3IRZ
guix system
guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
build log here: http://ix.io/3IS0
Hi Mathieu,
Mathieu Othacehe writes:
> Hello Maxim,
>
>> Now for the "version-1.3.0" branch, which *does* exist.
>
> The specifications are not removed anymore but can be deactivated. The
> following error caused by an inconsistency between the
> evaluations/specifications table should then be
Dear guix,
On master, I can’t reconfigure my system, because the linux-modules.drv
fails with the following error:
Backtrace:
17 (primitive-load "/gnu/store/bvjcb7jbwlky0czin8p66949mil?")
In ice-9/eval.scm:
619:8 16 (_ #f)
626:19 15 (_ #)
293:34 14 (_ #(# #))
In
Thanks!!! Awesome :)
guix system
guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
build log here: http://ix.io/3IP6
guix system
guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
build log here: http://ix.io/3IQP
On Sun Dec 19, 2021 at 2:10 PM CST, bdju via Bug reports for GNU Guix wrote:
> I'm using Sway, which is as close to just running a WM as you can get on
> Sway.
Meant to say "on Wayland"!
Hey Maxim,
> successfully built
> /gnu/store/vag2a53byhgrkpchviqz78lilall6412-emacs-org-contrib-20210519.drv
> /gnu/store/40hl0dli745i2ggs1aqhn2drh0fkmrbx-emacs-org-contrib-20210519
Thanks for fixing this one,
Closing,
Mathieu
This one is fixed, thanks to all the persons involved!
Mathieu
On Sun, Dec 19, 2021 at 09:48:42AM +, André A. Gomes wrote:
> > Are you using some 3rd-party channels that might need to be adjusted?
>
> Oh, right!
Glad to hear you've solved the problem!
>
> How can I close this bug report? Thank you.
Like I'm doing now, by sending a message to
guix system
guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff
build log here: http://ix.io/3ISu
Hi,
‐‐‐ Original Message ‐‐‐
On Sunday, December 19th, 2021 at 2:57 PM, bdju wrote:
> On Sat Dec 18, 2021 at 9:38 PM CST, John Kehayias via Bug reports for GNU
> Guix wrote:
>
> > I should have specified it worked on core-updates-frozen before the last
> > big changes (input style,
On Sun, Dec 19, 2021 at 03:25:42PM -0500, Maxim Cournoyer wrote:
> I ended up sticking with 2.2.33, since this is the current "LTS"
> release. Unfortunately it fails 3 new tests of python-gnupg, and its
> author think it is a regression in GnuPG itself [0].
>
> [0]
Hi,
Maxime Devos skribis:
> Actually, glib's build system (meson-build-system) did not support
> cross-compilation at all before the merge. Cross-compilation support
> was added on that branch, but glib's package broke later, presumably in
>
Thanks for pushing and closing Leo!
Hi Guix,
With Guix 11334d15d590073c631c574436d2110aa1ea2142, sway is not able to
start Xwayland. I believe that is was working correctly for me at commit
d627fbad8f4e157103251b07d7543dd2f5647cea.
Running sway manually from a VT, I was able to capture the following
messages:
```
Hi,
Ludovic Courtès writes:
> Hi,
>
> Maxime Devos skribis:
>
>> Actually, glib's build system (meson-build-system) did not support
>> cross-compilation at all before the merge. Cross-compilation support
>> was added on that branch, but glib's package broke later, presumably in
>>
On Sun, Dec 19, 2021 at 08:30:18PM -0500, Leo Famulari wrote:
> Based on the attached patches (rebased / adjusted for current master),
> I'll proceed with testing the build of all Go packages on x86_64-linux.
Well, Go builds are very fast.
There are no new failures of packages using
On Sun, Dec 19, 2021 at 10:19:02AM +0200, Efraim Flashner wrote:
> All of go is blocked on aarch64 with binutils-gold not compiling. I have
> a patch locally to add gcc:lib for (target-arm?) to go-1.17 which I'll
> push after testing with binutils-gold. I think going straight to 1.17 is
> fine,
42 matches
Mail list logo
