bug#48142: [PATCH] gnu: gupnp: Add missing input.

Mathieu, Thanks for your gupnp fix in 2710df38b0c317bdc69c61c7775d8141eb214dd1. Would you mind explaining how you determined gsettings-desktop-schemas needed to be a propagated input? I was confused [0][1] about which type of input it should be. Do you think the fix for appstream-glib [2]

bug#48114: Disarchive occasionally fails tests

Timothy Sample writes: > I’m still looking into this, but I wanted to quickly post this > reproducer for the Guile bug: > > (use-modules (ice-9 regex)) > (define str > "\U101514\U103ab0\U0f6e6e\U02e278\U01d9eb\U10b996\U1089b5\uea15\U0fa074\U101e41\U02e330\u0177\u2492") >

bug#47928: go-gopkg-in-yaml-v2-2.2.2 build fails

go-gopkg-in-yaml-v2 is a dependency for Docker and I am not able to build it on x86_64 or i686. On a x86-64 computer when I run `sudo guix system --no-substitutes reconfigure configuration.scm` I get this error. ``` building

bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build

To do what you want (create a new generations ignoring failures) is not easy to implement. We would have to "change our mind" and build a different derivation for that new profile. I hope to do so, For better guix usability future.

bug#48114: Disarchive occasionally fails tests

Hi, Ludovic Courtès writes: [...] > ERROR: In procedure substring: > Value out of range 6 to 7: 8 > > Note that this is in C locale, which may mean that ‘regexp-exec’, which > passes strings to libc, gets offsets wrong somehow (see > ‘fixup_multibyte_match’ in libguile), though I couldn’t

bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build

I don't think --keep-going works as you expect it to. When you do guix upgrade, guix creates a derivation for your new profile and proceeds to build it. If it has dependents that need to be built (packages that were updated), it builds them as they are needed to build the new profile. If one

bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build

> I think you can use `guix package --upgrade . --keep-going`: Thank you for the hint, sorry i didnt know this command exist. Currently i cant test this because i dont have a package which has an error in the building (previous icedove bug should be fixed) to see how this is going to go. -

bug#47724: acknowledged by developer (control message for bug #47724)

Its more of an enhancement not a bug. Did the popup message put in any better way than the current state? GNU bug Tracking System: This is an automatic notification regarding your bug report #47724: error: connect: /run/user/1000/shepherd/socket: No such file or directory, which was filed

bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2

On 2021-05-02, Vagrant Cascadian wrote: > On 2021-05-02, Ludovic Courtès wrote: >> Vagrant Cascadian skribis: >>> On 2021-04-30, Vagrant Cascadian wrote: I've been unable to build version 1.3.0rc1 for i386 on Debian: [ 70%] GUILEC gnu/packages/direct-connect.go [ 70%]

bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2

On 2021-05-02, Ludovic Courtès wrote: > Vagrant Cascadian skribis: > >> On 2021-04-30, Vagrant Cascadian wrote: >>> I've been unable to build version 1.3.0rc1 for i386 on Debian: >>> >>> [ 70%] GUILEC gnu/packages/direct-connect.go >>> [ 70%] GUILEC gnu/packages/disk.go >>> GC Warning:

bug#48178: Out of memory error when generating a docker-image.

Dear Guix, While generating a docker-image that contains only a sshd service, an nginx service, and an iptables service, it seems the VM that is spawned to generate a docker image was allocated too little memory. I attached the log file. Looking at 'guix/scripts/system.scm', it seems that we

bug#48110: I found a bug

Hi, Michael Mausler skribis: > 1. : > message: "some substitutes for the outputs of derivation > `/gnu/store/c8bnwlki4wa6s8rz4ynbcr95imhx3s13-graphviz-2.42.3.drv' failed > (usually happens due to networking issues); try `--fallback' to build > derivation from source " > status: 1

bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2

Hi! Vagrant Cascadian skribis: > On 2021-04-30, Vagrant Cascadian wrote: >> I've been unable to build version 1.3.0rc1 for i386 on Debian: >> >> [ 70%] GUILEC gnu/packages/direct-connect.go >> [ 70%] GUILEC gnu/packages/disk.go >> GC Warning: Failed to expand heap by 8388608 bytes >>

bug#48174: meld TypeError on startup

nathan@guixlaptop ~ $ meld Traceback (most recent call last): File "/gnu/store/ry77lgy02rs7605gyn6cai8ff9v64h4l-meld-3.20.3/bin/..meld-real-real", line 385, in setup_settings() File "/gnu/store/ry77lgy02rs7605gyn6cai8ff9v64h4l-meld-3.20.3/bin/..meld-real-real", line 270, in setup_settings

bug#48152: no code for module (json) on guix upgrade

It works now for me, thanks. On Sun, May 2, 2021, 1:51 PM Timothy Sample wrote: > Hi Leo, > > Thanks for pinging me. > > Leo Prikler writes: > > > Am Sonntag, den 02.05.2021, 19:03 +0200 schrieb Mathieu Othacehe: > >> Hello, > >> > >> > I found this stops being an issue after reverting > >> >

bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build

On Sun, May 02, 2021 at 08:29:31PM +, bo0od wrote: > Current (manual) solution is: > > guix package --upgrade . --do-not-upgrade x I think you can use `guix package --upgrade . --keep-going`: https://guix.gnu.org/manual/devel/en/html_node/Common-Build-Options.html --keep-going -k Keep

bug#48169: icecat extensions icons disappeared

Hi There, Icecat browser comes with default extensions, But currently (seems after latest upgrade) extensions images disappeared. (Please check the uploaded image) ThX!

bug#48166: Dont stop the upgrade process - Better guix handling when Package failed to build

Hi There, Guix distro is a rolling distro, Packages almost hourly/daily get upgraded. This is nice but it wont go through without errors due to many factors. Current situation when there is an error and package failed to build guix will stop upgrading all the upgrade process e.g: If you

bug#48114: Disarchive occasionally fails tests

Hello! Timothy Sample skribis: > I can’t seem to reproduce this. I’ve run the test suite many, many > times, but I also tried: I can reproduce it quickly with: while make check TESTS=tests/kinds/octal.scm -j5 ; do : ; done … in C locale (LC_ALL & co. all unset). > However, isn’t it

bug#48152: no code for module (json) on guix upgrade

Hi Leo, Thanks for pinging me. Leo Prikler writes: > Am Sonntag, den 02.05.2021, 19:03 +0200 schrieb Mathieu Othacehe: >> Hello, >> >> > I found this stops being an issue after reverting >> > 66b14dccdd0d83c875ce3a8d50ceab8b6f0a3ce2. >> > @Timothy do you know how we can get guile-json in

bug#48152: no code for module (json) on guix upgrade

Am Sonntag, den 02.05.2021, 19:03 +0200 schrieb Mathieu Othacehe: > Hello, > > > I found this stops being an issue after reverting > > 66b14dccdd0d83c875ce3a8d50ceab8b6f0a3ce2. > > @Timothy do you know how we can get guile-json in there for SWH? > > I think this is fixed with

bug#48152: no code for module (json) on guix upgrade

Hello, > I found this stops being an issue after reverting > 66b14dccdd0d83c875ce3a8d50ceab8b6f0a3ce2. > @Timothy do you know how we can get guile-json in there for SWH? I think this is fixed with d2b5bb5f9de8dc1a51260e17cd91c3039070a7f2 to fd5527407ff336c4af1c5511e19c0956720cd7aa. Could you

bug#48152: no code for module (json) on guix upgrade

Am Samstag, den 01.05.2021, 21:17 -0500 schrieb Nathan Dehnel: > bzip2 -dkc /var/log/guix/drvs/00/1p94i7q8kks3pngjah0b2v4fzl3npr- > module-import-compiled.drv.bz2 > [ 1/26] Loading './guix/base16.scm'... > [ 2/26] Loading './guix/base64.scm'... > [ 3/26] Loading './guix/build/download-nar.scm'...

bug#48151: mariadb-10.5.8 build failing

Tobias Geerinckx-Rice writes: > Your bug is available at and > through the usual 48151 at debbugs.gnu.org. However, it wasn't > sent to subscribers' inboxes because it was a whopping >9 MiB. > > Like most mailing lists, bug-guix@ has a (generous) message size >

bug#48160: Mumi renders huge messages

...when it should probably give up sooner, clearly indicate truncation, and point users to the raw view. is a >9 MiB mail. The rendered HTML is >11 MiB. Apart from being A Bit Much to send to clients, I get 504s most of the time. It succeeded once.

bug#48151: mariadb-10.5.8 build failing

Hi! Your bug is available at and through the usual 48151 at debbugs.gnu.org. However, it wasn't sent to subscribers' inboxes because it was a whopping >9 MiB. Like most mailing lists, bug-guix@ has a (generous) message size limit. SMTP is not a broadcast

bug#46038: guix 1.3.0rc1 test failure: channels-news, one entry

On 2021-01-22, Vagrant Cascadian wrote: > I've uploaded guix 1.2.0 built against guile-2.2 to Debian, and while it > builds fine on the official buildd.debian.org infrastructure, on amd64 > and arm64 the "channel-news, one entry" test from tests/channels.scm > fails on

bug#47195: xboard: alsa-utils dependency

Hello Christopher, Thank you reporting this! This patch should fix this: https://issues.guix.gnu.org/48158 I'm not sure if we should also patch paths to other programs like engines (gnuchess, fruit, crafty) and polyglot though. (Only gnuchess is packaged currently). -- You can no more win a

bug#48156: basic system test broken: qemu-system-x86_64: error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory

This is on commit 1b792e8b5275dc010c53d91062082340431204f2. → make check-system TESTS=basic Compiling Scheme modules... Selected 1 system tests... The following derivation will be built: /gnu/store/7dyw16iakczr7qg89rb3rgbh443cvwpc-basic.drv building