bug#43296: bug#43269: Gnome Builder doesn't install.

Hi Marinus, I've noticed your report and quickly found a rather crude way of fixing it. I'm not sure, why meson tries to link gnome-builder statically against selinux in the first place, but it should do the job. Regards, Leo Leo Prikler (1): gnu: Fix gnome-builder build. gn

bug#43296: [PATCH 1/1] gnu: Fix gnome-builder build.

As reported in #43296, gnome-builder tries to be linked against the static version of libselinux (propagated through glib/gio), failing to do so, as it also wants to be a PIE. To keep the PIE, link it against the dynamic library. * gnu/packages/gnome.scm (gnome-builder)[#:phases]: Add 'fix-ninja.

bug#43296: [PATCH] gnu: Fix gnome-builder build.

As reported in #43296, gnome-builder tries to be linked against the static version of libselinux (propagated through glib/gio), failing to do so, as it also wants to be a PIE. To keep the PIE, link it against the dynamic library. * gnu/packages/gnome.scm (gnome-builder)[#:phases]: Add 'fix-ninja.

bug#42688: Running a script with `guix repl` doesn't "see" additional channels using (%package-module-path)

Hi Guix, I've finally figured out, what causes this issue. Guix repl uses the following code to call scripts: ``` (unless (null? script) ;; Run script (save-module-excursion (lambda () (set-program-arguments script) (set-user-module) (load-in-vici

bug#42688: Running a script with `guix repl` doesn't "see" additional channels using (%package-module-path)

Hi Ludo, Am Donnerstag, den 17.09.2020, 17:31 +0200 schrieb Ludovic Courtès: > Hi Leo, > > [...] > > ‘scm_program_arguments_fluid’ is marked as SCM_INTERNAL, so it’s > really > inaccessible. Thought so. > However, perhaps we could save the initial value of (program- > arguments) > in (guix ui) a

bug#42688: Running a script with `guix repl` doesn't "see" additional channels using (%package-module-path)

Hi, Am Donnerstag, den 17.09.2020, 21:10 +0200 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > Am Donnerstag, den 17.09.2020, 17:31 +0200 schrieb Ludovic Courtès: > > > Hi Leo, > > > > > > [...] > > > > > > ‘

bug#41058: GNOME Maps fails to start in GNOME

Bumping this, as it has been months since I've posted my fix. For the record, it might also be worth looking into #39324, which uses a different workaround, and seeing whether the dbus service can be patched in a similar manner. Regards, Leo

bug#44090: Packaging a python library that is implemented with rust

Hello Hamzeh, I think part of the issue here, is that the build system for etebase-py tries to also build etebase-rs, which you have already packaged. There are two ways you could continue here: 1. Patch the build system of etebase-py, so that it works with your already built etebase-rs. 2. Pu

bug#44272: guix edit doesn't work when $EDITOR is set to "kate"

Easy solution, set $EDITOR to "gedit" ;) The reason why kate "doesn't work" when opening files as specified by `guix edit`, is that kate apparently can't handle the "$EDITOR +$N $FILE" syntax, where $N is the number of lines to skip. It instead opens two files, one of which will likely always be

bug#36376: Application menu of desktop environment not automatically updated

Hi Ludo, Am Dienstag, den 03.11.2020, 23:46 +0100 schrieb Ludovic Courtès: > Ludovic Courtès skribis: > > > This is not news to us, but as > > notes, > > the > > application menu of desktop environments is not automatically > > updated >

bug#44452: Clash between guile-3.0 and guile-3.0-latest

Hi divoplade, It is marked as a TODO exactly because it causes a world rebuild. guile-3.0 will presumably be updated on the next core-updates merge, where world rebuilds are acceptable, so be a bit patient until then and use guile-3.0-latest, please :) (Note, that you should also get guile-3.0-la

bug#23196: [Hunting bug#23196]: GNOME "Sharing" settings is blank

Hi simon, The Sharing dialog now consists of two buttons, which at least change some settings, along with the text field, that is still blank. That being said, I am far from able to assert, that this functions as intended; apparently, there should be more settings[1], and those that we do have do

bug#42342: PATCH [0/2] Update wine to 5.21

Hi Guix, the following patch updates wine to version 5.21. An attempt is also made to fix #42342 by copying wine32 libraries into wine64. Regards, Leo

bug#23198: GNOME: Execution of "gkbd-keyboard-display" failed: Command not found

Hello Chris, Am Samstag, den 02.04.2016, 14:39 -0700 schrieb Chris Marusich: > Hi, > > I'm using GuixSD v0.10.0 with GNOME. In GNOME, when you have enabled > a > second keyboard input (via "Settings" > "Region and Language" > > "Input > Sources"), if you click on "Show Keyboard Layout" from the

bug#23874: [PATCH 1/2] profiles: Remove duplicates in manifest transactions.

* guix/profiles.scm (manifest-transaction-effects): Delete duplicates in install and remove. Let multiple upgrades and downgrades shadow previous transactions of the same kind. --- guix/profiles.scm | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/guix/profiles.scm

bug#23874: [PATCH 2/2] profiles: Delete duplicate manifest entries in packages->manifest.

* gnu/profiles.scm (packages->manifest): Delete duplicate entries. --- guix/profiles.scm | 34 ++ 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/guix/profiles.scm b/guix/profiles.scm index 99b7dbf299..14b98852bd 100644 --- a/guix/profiles.scm +++ b/

bug#23874: [PATCH 1/2] profiles: Remove duplicates in manifest transactions.

Hi Mark, Am Mittwoch, den 02.12.2020, 15:26 -0500 schrieb Mark H Weaver: > Hi, > > Leo Prikler writes: > > > * guix/profiles.scm (manifest-transaction-effects): Delete > > duplicates in > > install and remove. Let multiple upgrades and downgrades shadow > &

bug#23874: [PATCH v2 1/2] profiles: Remove duplicates in manifest transactions.

* guix/profiles.scm (manifest-transaction-effects): Delete duplicate effects. --- guix/profiles.scm | 18 -- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/guix/profiles.scm b/guix/profiles.scm index 1b15257210..034591eb79 100644 --- a/guix/profiles.scm +++ b/guix/p

bug#23874: [PATCH v2 2/2] profiles: Delete duplicate manifest entries in packages->manifest.

* gnu/profiles.scm (packages->manifest): Delete duplicate entries. --- guix/profiles.scm | 34 ++ 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/guix/profiles.scm b/guix/profiles.scm index 034591eb79..59a313ea08 100644 --- a/guix/profiles.scm +++ b/

bug#23118: Duplicate entries in various environment variables

Hello, Chris Am Freitag, den 25.03.2016, 20:59 -0700 schrieb Chris Marusich: > Hi, > > I've noticed that my environment variables contain duplicate > (sometimes > more) entries. This occurs regardless of whether the user logs in > directly via a tty or via a desktop environment like GNOME. > >

bug#23874: [PATCH 1/2] profiles: Remove duplicates in manifest transactions.

Hi Ludo Am Samstag, den 05.12.2020, 16:38 +0100 schrieb Ludovic Courtès: > Hi Leo, > > Could you explain what each patch fixes, and perhaps add a test case > for > each that illustrates that? > > Thanks, > Ludo’. Tests sent along with v3. These patches remove duplicates from manifests construct

bug#23874: [PATCH v3 1/2] profiles: Remove duplicates in manifest transactions.

* guix/profiles.scm (manifest-transaction-effects): Delete duplicates in install and remove. Let multiple upgrades and downgrades shadow previous transactions of the same kind. * tests/profiles.scm ("manifest-transaction-effects no double install or upgrades") ("manifest-transaction-effects no dou

bug#23874: [PATCH v3 2/2] profiles: Delete duplicate manifest entries in packages->manifest.

* gnu/profiles.scm (packages->manifest): Delete duplicate entries. * tests/profiles.scm ("packages->manifest, no duplicates"): New test. --- guix/profiles.scm | 34 ++ tests/profiles.scm | 10 ++ 2 files changed, 28 insertions(+), 16 deletions(-) diff --gi

bug#45272: GNOME Builder: Global search, autocompletion, documentation don't work

Hello Luis, After long trial and error I have failed to find a way of enabling this feature. Getting the necessary environment variables into GNOME Builder is doable, albeit not without issues. In particular, naively setting GI_TYPELIB_PATH from build – which would normally be the sane thing to

bug#45267: Using gnome-keyring and LXQt as Desktop Environment

Hello Hamzeh, the gnome-keyring service is not the only place, in which gnome-keyring is used. As far as I understand, all it does is unlocking your login keyring; you have to ensure on your own, that the keyring argument passed to it matches the keyring used by your applications. I think you h

bug#45270: [PATCH] gnu: gnome-builder: Fix python and GI paths.

This patch fixes #45270 by patching PYTHON_PATH at application start time and prepending "the correct" GI typelib paths at plugin load time. * gnu/packages/gnome.scm (gnome-builder)[#:phases]: Add python-wrap and patch-gi-repository-path. --- gnu/packages/gnome.scm | 49 ++

bug#45272: [PATCH] gnu: gnome-builder: Disable jedi plugin.

As pointed out in #45272, it is broken. * gnu/packages/gnome.scm (gnome-builder)[#:configure-flags] Add -Dplugin_jedi=false. --- gnu/packages/gnome.scm | 1 + 1 file changed, 1 insertion(+) diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm index 5a166d1b86..9f37c605be 100644 --- a/gnu

bug#45272: [PATCH v2] gnu: gnome-builder: Disable jedi plugin.

As pointed out in #45272, it is broken. * gnu/packages/gnome.scm (gnome-builder)[#:configure-flags] Add -Dplugin_jedi=false. --- gnu/packages/gnome.scm | 1 + 1 file changed, 1 insertion(+) diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm index 5a166d1b86..a533480b42 100644 --- a/gnu

bug#45272: [PATCH] gnu: gnome-builder: Disable jedi plugin.

Am Freitag, den 18.12.2020, 17:49 +0100 schrieb Ludovic Courtès: > Hi! > > Leo Prikler skribis: > > > As pointed out in #45272, it is broken. > > Please add this as a comment above “-Dplugin_jedi=false” (refer to > the > bug by URL so there’s no ambiguity). I fee

bug#45272: [PATCH v3] gnu: gnome-builder: Disable jedi plugin.

As pointed out in #45272, it is broken. * gnu/packages/gnome.scm (gnome-builder)[#:configure-flags] Add -Dplugin_jedi=false. --- gnu/packages/gnome.scm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm index 5a166d1b86..f90c0b92a6 100644 --- a/

bug#45316: [PATCH]: Re-introduce Emacs packages specific installation prefix.

Hello Maxim, As someone, who lobbied for the current status quo, I have some thoughts to share. Am Montag, den 21.12.2020, 22:28 -0500 schrieb Maxim Cournoyer: > The Emacs packages built with the Emacs built system used to be > installed in a sub-directory under the share/emacs/guix.d/ directory,

bug#45316: [PATCH]: Re-introduce Emacs packages specific installation prefix.

Hi Maxim, Am Dienstag, den 22.12.2020, 13:09 -0500 schrieb Maxim Cournoyer: > Hi Leo, > > Leo Prikler writes: > > > Hello Maxim, > > > > As someone, who lobbied for the current status quo, I have some > > thoughts to share. > > I'm hap

bug#26215: gschemas.compiled should not be added to the profile by multiple packages

Hello Florian, I'm writing you, because you've filed issue #26215 against Guix (see [1] for full context). Am Mittwoch, den 22.03.2017, 09:30 +0100 schrieb pelzflorian (Florian Pelz): > Currently multiple packages contain the file > share/glib-2.0/schemas/gschemas.compiled (which is built by > gl

bug#45316: [PATCH]: Re-introduce Emacs packages specific installation prefix.

Hi Maxim, Am Samstag, den 26.12.2020, 00:01 -0500 schrieb Maxim Cournoyer: > > > > > While this change allowed to expose simply and directly the > > > > > packages > > > > > found in EMACSLOADPATH, it does introduce the risk of file > > > > > name > > > > > collisions when multiple Emacs packages

bug#26215: gschemas.compiled should not be added to the profile by multiple packages

Hello Florian, Am Sonntag, den 27.12.2020, 01:02 +0100 schrieb pelzflorian (Florian Pelz): > [...] > I think the bug is done. Purging the gschemas.compiled files from > all > packages would need to be done in an extra phase for many build > systems (glib-or-gtk build system, cmake build system, m

bug#45316: [PATCH]: Re-introduce Emacs packages specific installation prefix.

Hi Maxim, Am Samstag, den 26.12.2020, 23:44 -0500 schrieb Maxim Cournoyer: > Hi Leo, > > Leo Prikler writes: > > [...] > > > > If you want to have a clearer idea of how packages from ELPA and > > > the > > > likes are installed, you can

bug#41058: GNOME Maps fails to start in GNOME

Hello Guix, I've just pushed a variant of the patch I proposed as a2d5f9f60d0f440e5d5ce1a1cc81743b27d6cede. I tested it yesterday in a VM; it should work. Regards, Leo

bug#45404: [PATCH] gnu: kiwix-desktop: Fix program start.

Pushed, thanks! Small hint, if you want to use pure environments, don't forget to expose environment variables such as DISPLAY and XAUTHORITY. Regards, Leo Am Freitag, den 25.12.2020, 17:36 +0100 schrieb Michael Rohleder: > Fixes ;. > > * gnu/packages/web.scm (kiwix

bug#45537: Update fails with this error

Hello, It would appear, that this specific issue was fixed by Mathieu in commit 0c8bb20b7cbd39537999fce29979a6acaf64e601. If such a slip-up happens again in future and you really need to update a week-old generation, note that you can also specify slightly older commits using "guix pull --commit=C

bug#45537: Update fails with this error

each me how use list of commits convenient way? > > December 29, 2020 11:56 PM, "Leo Prikler" < > leo.prik...@student.tugraz.at> wrote: > > > Hello, > > > > It would appear, that this specific issue was fixed by Mathieu in > > commit 0c8bb20b7cbd3953

bug#45537: Update fails with this error

each me how use list of commits convenient way? > > December 29, 2020 11:56 PM, "Leo Prikler" < > leo.prik...@student.tugraz.at> wrote: > > > Hello, > > > > It would appear, that this specific issue was fixed by Mathieu in > > commit 0c8bb20b7cbd3953

bug#45570: [PATCH] system: Assert, that user and group names are unique.

*gnu/system/shadow.scm (assert-unique-account-names) (assert-unique-group-names): New variables. (account-activation): Use them here. --- gnu/system/shadow.scm | 28 1 file changed, 28 insertions(+) diff --git a/gnu/system/shadow.scm b/gnu/system/shadow.scm index a693

bug#45571: Support stable uids and gids for all accounts

Hello Danny, I don't think changing the way UIDs are allocated by default is a good solution as that will break many running installations on real hardware, that default to those. A better solution would be to make user accounts and groups explicit configuration wherever account- service-type is

bug#45571: Support stable uids and gids for all accounts

Hi, Am Freitag, den 01.01.2021, 18:50 +0100 schrieb Danny Milosavljevic: > Hello, > > On Fri, 01 Jan 2021 17:20:58 +0100 > Leo Prikler wrote: > > > I don't think changing the way UIDs are allocated by default is a > > good > > solution as that will br

bug#45571: Fwd: Re: bug#45571: Support stable uids and gids for all accounts

Forgot to CC the ML. --- Begin Message --- Hi Danny, Am Freitag, den 01.01.2021, 21:22 +0100 schrieb Danny Milosavljevic: > Hi Leo, > > On Fri, 01 Jan 2021 19:44:12 +0100 > Leo Prikler wrote: > > > Ah, that puts things into perspective. In other words, the problem >

bug#45571: Fwd: Re: bug#45571: Support stable uids and gids for all accounts

Hi Danny, Am Samstag, den 02.01.2021, 02:40 +0100 schrieb Danny Milosavljevic: > Hi Leo, > > On Sat, 02 Jan 2021 00:16:45 +0100 > Leo Prikler wrote: > > > > And it indeed is possible to add (uid 4711) in the literal and it > > > will work > > > just

bug#45570: [PATCH] system: Assert, that user and group names are unique.

*gnu/system/shadow.scm (find-duplicates): New variable. (assert-unique-account-names, assert-unique-group-names): New variables. (account-activation): Use them here. --- gnu/system/shadow.scm | 35 +++ 1 file changed, 35 insertions(+) diff --git a/gnu/system/shadow

bug#45571: Fwd: Re: bug#45571: Support stable uids and gids for all accounts

Hi Jason, Am Samstag, den 02.01.2021, 09:02 -0500 schrieb Jason Conroy: > On Fri, Jan 1, 2021 at 10:11 PM Leo Prikler < > leo.prik...@student.tugraz.at> wrote: > > Hi Danny, > > Am Samstag, den 02.01.2021, 02:40 +0100 schrieb Danny > > Milosavljevic: > > > H

bug#45571: Fwd: Re: bug#45571: Support stable uids and gids for all accounts

Hi Danny, Am Samstag, den 02.01.2021, 15:50 +0100 schrieb Danny Milosavljevic: > [...] > I agree, if in addition. > > (Or if a registry is undesireable, calculate the uids by user name. > These are the possibilities. If hashing user names is too uncommon > on > UNIX elsewhere, I say that we have

bug#45571: Support stable uids and gids for all accounts

Hi Danny, Am Samstag, den 02.01.2021, 16:04 +0100 schrieb Danny Milosavljevic: > Hi Leo, > > > > Considering the goal of Guix, it's weird that with Guix, one > > > needs to > > > store&restore /etc/passwd at all. It's state, but not very > > > useful > > > one. > > > I mean that's how it is right

bug#45571: Fwd: Re: bug#45571: Support stable uids and gids for all accounts

Hello Jason, Am Samstag, den 02.01.2021, 09:52 -0500 schrieb Jason Conroy: > On Sat, Jan 2, 2021 at 9:29 AM Leo Prikler < > leo.prik...@student.tugraz.at> wrote: > > Hi Jason, > > Am Samstag, den 02.01.2021, 09:02 -0500 schrieb Jason Conroy: > > > On Fri, Ja

bug#45676: Store references inside compressed data

ame references are kept through other files, e.g. uncompressed binaries? I'll attach a patch, that fixes Emacs just in case. Regards, Leo From 57c23bf6ecac79c397cb49ff251176ec3a7b1cf5 Mon Sep 17 00:00:00 2001 From: Leo Prikler Date: Wed, 6 Jan 2021 09:24:07 +0100 Subject: [PATCH] gnu: emacs: Don&#

bug#45570: [PATCH] system: Assert, that user and group names are unique.

Hi, Am Mittwoch, den 06.01.2021, 10:56 +0100 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > *gnu/system/shadow.scm (find-duplicates): New variable. > > (assert-unique-account-names, assert-unique-group-names): New > > variables. > >

bug#45570: [PATCH] system: Assert, that user and group names are unique.

Hi, Am Mittwoch, den 06.01.2021, 14:32 +0100 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > > > +((first . rest) > > > > + (if (member first rest =) ; (srfi srfi-1) member > > > > + (cons first (find-duplicates

bug#45570: [PATCH v2] system: Assert, that user and group names are unique.

*gnu/system/shadow.scm (find-duplicates): New variable. (assert-unique-account-names, assert-unique-group-names): New variables. (account-activation): Use them here. --- gnu/system/shadow.scm | 38 ++ 1 file changed, 38 insertions(+) diff --git a/gnu/system/sha

bug#45706: vscodium

Hello Hamzeh, Am Donnerstag, den 07.01.2021, 00:19 +0330 schrieb Hamzeh Nasajpour: > Hello, > > I want to package the `vscode` in guix. Actually I packaged it, but I > faced with some issues that I think the package definition needs some > modifications. > > I installed it and I get this error:

bug#45570: [PATCH v3] system: Assert, that user and group names are unique.

*gnu/system/shadow.scm (find-duplicates): New variable. (assert-unique-account-names, assert-unique-group-names): New variables. (account-activation): Use them here. --- gnu/system/shadow.scm | 44 +++ 1 file changed, 44 insertions(+) diff --git a/gnu/syste

bug#45570: [PATCH v2] system: Assert, that user and group names are unique.

Am Donnerstag, den 07.01.2021, 09:35 +0100 schrieb Ludovic Courtès: > Leo Prikler skribis: > > > *gnu/system/shadow.scm (find-duplicates): New variable. > > (assert-unique-account-names, assert-unique-group-names): New > > variables. > > (account-activation): Use

bug#45570: [PATCH v3] system: Assert, that user and group names are unique.

Am Montag, den 11.01.2021, 14:09 +0100 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > *gnu/system/shadow.scm (find-duplicates): New variable. > > (assert-unique-account-names, assert-unique-group-names): New > > variables. > > (account-a

bug#45830: Assert, that user and group names are unique -> breaks guix system reconfigure

Hi Jonathan, Am Mittwoch, den 13.01.2021, 00:03 +0100 schrieb Jonathan Brielmaier: > Hi Leo, > > your commit a3002104: > system: Assert, that user and group names are unique. > > breaks `guix system reconfigure` for me and other people (at least > two > in IRC). > > $ guix system reconfigure co

bug#45830: Assert, that user and group names are unique -> breaks guix system reconfigure

Hello again, Am Mittwoch, den 13.01.2021, 00:23 +0100 schrieb Leo Prikler: > Hi Jonathan, > > Am Mittwoch, den 13.01.2021, 00:03 +0100 schrieb Jonathan Brielmaier: > > Hi Leo, > > > > your commit a3002104: > > system: Assert, that user and group names are uni

bug#45836: cups-service-type duplicates lp group

Hello Guix, it has come to my attention due to the recent reporting of #45830 and some conversation in IRC, that cups-service-type adds an lp group, which is already defined in %base-groups. Since both share the same definition, this is not too big an issue, but it prohibits us from using a hard

bug#45836: cups-service-type duplicates lp group

Hi Ludo, Am Mittwoch, den 13.01.2021, 12:28 +0100 schrieb Ludovic Courtès: > Hi Leo, > > Leo Prikler skribis: > > > it has come to my attention due to the recent reporting of #45830 > > and > > some conversation in IRC, that cups-service-type adds an lp group, &

bug#45836: [PATCH] services: Let cups-service-type reuse base lp group.

* gnu/services/cups.scm (%cups-accounts): Try to use the lp group defined in %base-groups. * gnu/system/shadow.scm (account-activation): Delete duplicate (eq?) users and groups before transforming them to specs and asserting, that names are unique. --- gnu/services/cups.scm | 10 -- gnu/sy

bug#45856: Shadowsocks issue

Hello musics, I don't think that's necessarily a bug in Guix or even in shadowsocks. shadowsocks actually has a wiki including an example configuration [1]. To be fair, however, that configuation is not immediately usable, as you are supposed to change both server and password to make it run. Ev

bug#45676: Store references inside compressed data

Hi Ludo, Am Donnerstag, den 14.01.2021, 22:31 +0100 schrieb Ludovic Courtès: > Hi Leo, > > Leo Prikler skribis: > > > From 57c23bf6ecac79c397cb49ff251176ec3a7b1cf5 Mon Sep 17 00:00:00 > > 2001 > > From: Leo Prikler > > Date: Wed, 6 Jan 2021 09:24:07 +

bug#45836: [PATCH] services: Let cups-service-type reuse base lp group.

Hi, Am Samstag, den 16.01.2021, 19:37 +0100 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > * gnu/services/cups.scm (%cups-accounts): Try to use the lp group > > defined in > > %base-groups. > > * gnu/system/shadow.scm (account-activation): Dele

bug#45836: [PATCH] services: Let cups-service-type reuse base lp group.

Am Montag, den 18.01.2021, 15:47 +0100 schrieb Ludovic Courtès: > Hi, > > Leo Prikler skribis: > > > > > diff --git a/gnu/system/shadow.scm b/gnu/system/shadow.scm > > > > index 0538fb1a24..7c57222716 100644 > > > > --- a/gnu/syste

bug#46314: Fwd: Re: materialdecoration failed to build with Qt 5.15.2.

I really need to learn how to type ML addresses correctly. --- Begin Message --- Hello, Am Freitag, den 05.02.2021, 11:32 +0800 schrieb Zhu Zihao: > In c852d897551f514de95c224fa79e748f48808068, try `guix build > materialdecoration` and failed. Thanks for formally reporting this bug. It is sadly a

bug#41177: [PATCH 0/2] OpenJDK: Fix NullPointerException when accessing fonts

Hi Björn Am Freitag, den 12.02.2021, 00:14 +0100 schrieb Björn Höfling: > These two patches fix a NullPointerException in the OpenJDK packages. > > The patches apply only to OpenJDK9 and OpenJDK11, but with > inheritence > all OpenJDKx with x\in[9..14] are covered. > > Here is the bug report: >

bug#46314: Fix build of materialdecoration.

Hi Raghav, Am Montag, den 15.02.2021, 12:41 -0500 schrieb Raghav Gururajan: > Thanks for the review. I have attached revised patches. Thanks for the patches. I've pushed them upstream, so I'll be closing this and 46314. Regards, Leo

bug#46669: Godot fails to start

Hi, Am Sonntag, den 21.02.2021, 10:05 +0100 schrieb Maxime Devos: > Hi, > > On Sat, 2021-02-20 at 19:37 -0500, Leo Famulari wrote: > > [...] > > It will be while before libx11 is updated in Guix, because changing > > it > > causes a huge number of packages to be rebuilt: > > > > $ guix refresh -

bug#47106: Bubblewrap hates Guix containers 😞

Hi Guix, both Epiphany and Eolie (post fixing #47097; will submit patch shortly) fail inside Guix containers with the suggested incantation. After getting the environment to no longer complain about $DISPLAY by adding `--preserve="XAUTHORITY" --expose=$XAUTHORITY', it repeatedly outputs lines lik

bug#47097: [PATCH] gnu: eolie: Add missing inputs.

This fixes errors observed directly at launch of Eolie inside pure environments. (See for more information.) It is still not possible to launch Eolie inside a container, however. (See also .) * gnu/packages/gnome.scm (eolie)[inputs]: Add li

bug#47106: Bubblewrap hates Guix containers 😞

Hi! Am Samstag, den 13.03.2021, 11:48 +0100 schrieb Ludovic Courtès: > Hi! > > Leo Prikler skribis: > > > both Epiphany and Eolie (post fixing #47097; will submit patch > > shortly) > > fail inside Guix containers with the suggested incantation. After > >

bug#47106: Bubblewrap hates Guix containers 😞

Am Samstag, den 13.03.2021, 13:27 +0100 schrieb Bengt Richter: > Hi, > > On +2021-03-13 12:07:51 +0100, Leo Prikler wrote: > > Hi! > > Am Samstag, den 13.03.2021, 11:48 +0100 schrieb Ludovic Courtès: > > > Hi! > > > > > > Leo Prikler skribis: >

bug#47106: Bubblewrap hates Guix containers 😞

Am Samstag, den 13.03.2021, 18:07 +0100 schrieb Bengt Richter: > I am not a Wayland developer, if that's what you mean by "Wayland > folk" :) I meant it as "folk using Wayland in their display manager". > I am curious what the commands below would show inside your > container. > "pidparents" [1] i

bug#47106: Bubblewrap hates Guix containers 😞

Hi again³ Am Sonntag, den 14.03.2021, 18:45 +0100 schrieb Bengt Richter: > Hi again^2, > > Maybe > pstree -at > would show a little more? sh |-dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --sess |-dbus-launch --autolaunch=fa7a4d52637958ddd37547bb5d8bd9d2--binary- synt

bug#47106: Bubblewrap hates Guix containers 😞

Am Sonntag, den 14.03.2021, 21:32 +0100 schrieb Ludovic Courtès: > Hi Leo, > > Leo Prikler skribis: > > > Nah, it's a rather ad-hoc definition grown from what should be an > > Eolie > > container from the cookbook (also refer to #47097). > > >

bug#47106: Bubblewrap hates Guix containers 😞

Am Montag, den 15.03.2021, 10:52 +0100 schrieb Ludovic Courtès: > Hi Leo, > > Leo Prikler skribis: > > > > /sys is already mounted inside ‘guix environment -C’ containers > > > so I > > > don’t see what difference it would make. > > I think I've

bug#47106: Bubblewrap hates Guix containers 😞

Hi, Am Dienstag, den 16.03.2021, 11:54 +0100 schrieb Bengt Richter: > Hi Leo, > One more favor? ;) > > On +2021-03-14 19:05:24 +0100, Leo Prikler wrote: > > Hi again³ > > > > Am Sonntag, den 14.03.2021, 18:45 +0100 schrieb Bengt Richter: > > > Hi again^2,

bug#47097: eolie broken => unworking example from manual

Am Mittwoch, den 24.03.2021, 04:14 +0100 schrieb zimoun: > Hi, > > On Thu, 18 Mar 2021 at 21:44, Ludovic Courtès wrote: > > Leo Prikler skribis: > > > > > This fixes errors observed directly at launch of Eolie inside > > > pure > > > environme

bug#47097: eolie broken => unworking example from manual

Am Mittwoch, den 24.03.2021, 17:17 +0100 schrieb Ludovic Courtès: > Leo Prikler skribis: > > > Am Mittwoch, den 24.03.2021, 04:14 +0100 schrieb zimoun: > > > Hi, > > > > > > On Thu, 18 Mar 2021 at 21:44, Ludovic Courtès > > > wrote: > > &

bug#47458: Terrible UX upgrading Emacs in Guix

Am Sonntag, den 28.03.2021, 22:02 -0400 schrieb Mark H Weaver: > I just updated my Guix system, which included the Emacs update from > 27.1 > to 27.2. After "guix package -m mhw-manifest.scm" finished running > (which takes a long time for me, since I don't use substitutes), and > before I even no

bug#47458: Terrible UX upgrading Emacs in Guix

Am Montag, den 29.03.2021, 10:24 +0200 schrieb Maxime Devos: > On Mon, 2021-03-29 at 10:07 +0200, Leo Prikler wrote: > > [...] > > > > In a similar manner, if I see an Emacs version upgrade at the start > > of > > the transaction, I already know to prepare for

bug#47470: [PATCH] gnu: crypto++: Update to 8.5.0.

* gnu/packages/crypto.scm (crypto++): Update to 8.5.0. [origin]: Use git-fetch and git-reference. --- gnu/packages/crypto.scm | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/gnu/packages/crypto.scm b/gnu/packages/crypto.scm index 94f9cbeebf..57d417de80 100644 --

bug#45316: [WIP PATCH 1/3] profiles: Add hook for Emacs subdirs.

* guix/profiles.scm (emacs-subdirs): New variable. (%default-profile-hooks): Add it here. * guix/status.scm (hook-message): Add a message for emacs-subdirs. --- guix/profiles.scm | 41 + guix/status.scm | 2 ++ 2 files changed, 43 insertions(+) diff --gi

bug#45316: [WIP PATCH 2/3] build-system: emacs: Use subdirectories again.

With this, Emacs libraries are installed in the ELPA_NAME-VERSION subdirectory of site-lisp and potential subdirectories should no longer collide. * guix/build/emacs-build-system.scm (build, patch-el-files, make-autoloads): Use ELPA name and version to construct subdirectories of %install-dir. (in

bug#45316: [WIP PATCH 3/3] gnu: emacs-libgit: Adjust to changes in emacs-build-system.

* gnu/packages/emacs-xyz.scm (emacs-libgit)[set-libgit--module-file]: Adjust libgit--module-file path. --- gnu/packages/emacs-xyz.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm index f45507c647..3712429651 100644 --

bug#47458: [PATCH] gnu: emacs: Wrap EMACSLOADPATH.

With this, the search path specification of EMACSLOADPATH does no longer depend on the version of Emacs, which should make upgrading major versions less painful. See also: - - * gnu/packages/emacs.scm (emacs)[#:phases]: Add ‘wrap-load-path

bug#47537: specification->package does not seem to support outputs

Hello, Am Donnerstag, den 01.04.2021, 03:50 + schrieb fsdfsdfsd3: > Hello, > > An example of this behavior in a guile repl is: > > (use-modules (gnu packages)) > (specification->package "qemu") ; works > (specification->package "qemu:doc") ; errors and closes the repl Given its docstring,

bug#47557: attempting to package MegaZeux

/bootlicker.party That's a nice domain to have reserved ;) Regards, Leo From 4667217092ae9a058a5b370295c6b913671819a4 Mon Sep 17 00:00:00 2001 From: Leo Prikler Date: Sat, 3 Apr 2021 00:45:51 +0200 Subject: [PATCH] gnu: Add megazeux. * gnu/packages/game-development.scm (megazeux): New variable. -

bug#47458: Terrible UX upgrading Emacs in Guix

Hi Maxim! Am Sonntag, den 04.04.2021, 00:35 -0400 schrieb Maxim Cournoyer: > Hi Leo! > > Leo Prikler writes: > > > With this, the search path specification of EMACSLOADPATH does no > > longer > > depend on the version of Emacs, which should make upgrading major

bug#47592: [WIP Emacs] Emacs packages, that fail to build on master

I'm currently in the process of verifying, that all Emacs packages build in the wip-emacs branch. To that end, I'm running a manifest generated from all emacs-xyz exports, which will fail for some package, that I've broken, then rinse and repeat. However, there are some build failures, that exist

bug#47470: bug#47477: [PATCH] gnu: crypto++: Update to 8.5.0.

Am Montag, den 05.04.2021, 11:47 +0200 schrieb Ludovic Courtès: > Hi Leo, > > Leo Prikler skribis: > > > * gnu/packages/crypto.scm (crypto++): Update to 8.5.0. > > [origin]: Use git-fetch and git-reference. > > If dependents still build fine, go for it! > &g

bug#47610: gnome-keyring service doesn't appear

gnome-keyring-service is not a shepherd service. It is a pam service, that ensures your login keyring (if it exists) is unlocked when you log in. That's all it does. `ps x | grep gnome-keyring` should have a non-empty output. Mine includes this: /gnu/store/47nl5kpkc3sgwasrbk06sgaig22w07ha-gnome

bug#47458: Terrible UX upgrading Emacs in Guix

Hi Maxim! Am Dienstag, den 06.04.2021, 08:09 -0400 schrieb Maxim Cournoyer: > Hi Leo! > > Leo Prikler writes: > > [...] > > > > Shouldn't we wrap all the binaries to be on the safe > > > side? Things > > > such > > > as emacsclie

bug#47097: eolie broken => unworking example from manual

Am Samstag, den 10.04.2021, 14:40 -0400 schrieb Leo Famulari: > On Wed, Mar 24, 2021 at 09:07:34AM +0100, Leo Prikler wrote: > > Am Mittwoch, den 24.03.2021, 04:14 +0100 schrieb zimoun: > > > Hi, > > > > > > On Thu, 18 Mar 2021 at 21:44, Ludovic Courtès >

bug#47761: Guile Segfaulting on guix build -f

Hi Nicolò Am Dienstag, den 13.04.2021, 23:36 +0200 schrieb Nicolò Balzarotti: > Hi guix! > > A package definition that used to build fine, recently (don't know > exactly when) started failing, with guile segfaulting. > > After removing a few things, it seems that the MWE is this: > > echo '(use

bug#47106: Bubblewrap hates Guix containers 😞

Am Mittwoch, den 14.04.2021, 16:07 -0400 schrieb Leo Famulari: > This bug is registered as "blocking" the upcoming release. > > Is there any chance it will be closed in the next 3 days? Or should I > "unblock"? There is a slim chance, that someone might fix it "by accident", but I'm personally not

  1   2   3   >