bug#56288: Pitivi can't be started

Am Dienstag, dem 28.06.2022 um 17:52 + schrieb Christian Miller: > Running the command pitivi results to the following output: > > [...] >     EMBLEMS[status] = GdkPixbuf.Pixbuf.new_from_file_at_size( > gi.repository.GLib.GError: gdk-pixbuf-error-quark: Couldn’t recognize > the image file

bug#56209: Shepherd 0.9 not cleanly unmounting root

I tried your patch on one of my computers and it works. Thank you.

bug#56209: Shepherd 0.9 not cleanly unmounting root

Hi, I believe the attached patch fixes the problem. I’ll do more testing on my side but I’d be grateful if someone would give it a try too. Ludo’. diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm index 17b7b38a15..dea58354d9 100644 --- a/gnu/packages/admin.scm +++

bug#56290: Guix is at version 0, according to "guix --version"

Maxime Devos schreef op di 28-06-2022 om 22:56 [+0200]: > Reproducible on #guix by foreign distroers, but not by Guix Systemers. Correction: also by Guix Systemers. signature.asc Description: This is a digitally signed message part

bug#56290: Guix is at version 0, according to "guix --version"

Maxime Devos schreef op di 28-06-2022 om 22:49 [+0200]: > $ guix --version > guix (GNU Guix) 0 > Copyright © 2022 de auteurs van Guix > Licentie GPLv3+: GNU GPL versie 3 of nieuwer > > Dit is vrije software: je bent vrij om het aan te passen en het verder > te

bug#56288: Pitivi can't be started

Running the command pitivi results to the following output: ** (gst-plugin-scanner:21018): CRITICAL **: 19:44:14.963: pygobject initialization failedTraceback (most recent call last): File "/gnu/store/qzlwacdsvswq2ahayd3p6iail5n3rpwk-pitivi-0.999.0-2021.05.0/bin/.pitivi-real", line 172, in

bug#56287: Downloading latest development snapshots not working

It currently is not possible to download latest development snapshots of Guix through https://guix.gnu.org/en/download/latest/ since it returns a json with the message "Could not find the request build product.".

bug#56290: Guix is at version 0, according to "guix --version"

$ guix --version guix (GNU Guix) 0 Copyright © 2022 de auteurs van Guix Licentie GPLv3+: GNU GPL versie 3 of nieuwer Dit is vrije software: je bent vrij om het aan te passen en het verder te verspreiden. Er is GEEN ENKELE GARANTIE, voor zover wettelijk

bug#56289: "guix shell -f guix2.scm" fails always

Put the folllowing in "oops-guix.scm": (use-modules (gnu packages)) (specifications->packages '("hello")) then do: "guix shell -f oops-guix.scm" to make an environment with "hello". I get: > guix shell: warning: no packages specified; creating an empty environment $ which hello >

bug#52663: taisei build failure

Am Dienstag, dem 28.06.2022 um 07:16 -0500 schrieb bdju: > On Sun Jun 26, 2022 at 5:30 AM CDT, Liliana Marie Prikler wrote: > > Am Sonntag, dem 19.12.2021 um 21:58 +0100 schrieb Liliana Marie > > Prikler: > > > Am Sonntag, dem 19.12.2021 um 14:01 -0600 schrieb bdju: > > > > guix system > > > >

bug#56285: azpainter does not cross-compile

Hi, Following discussions [1,2], this report tracks issue when cross-compiling the package ’azpainter’, if it would make sense to cross-compile such package. ;-) For the record, upstream [3] does not have a clear bug tracker where to report the issue. 1:

bug#53355: bug#51466: bug#53355: guix shell --check: confusing error message

( schreef op di 28-06-2022 om 17:57 [+0100]: > On Tue Jun 28, 2022 at 11:38 AM BST, Maxime Devos wrote: > > Then it could be fixed in that distro? And if the distro intentionally > > keeps it broken for years, then that seems more a problem in the distro > > than Guix to me. > > I believe Ludo'

bug#53355: bug#51466: bug#53355: guix shell --check: confusing error message

On Tue Jun 28, 2022 at 11:38 AM BST, Maxime Devos wrote: > Then it could be fixed in that distro? And if the distro intentionally > keeps it broken for years, then that seems more a problem in the distro > than Guix to me. I believe Ludo' is referring to LTS distros and other situations where

bug#52663: taisei build failure

On Sun Jun 26, 2022 at 5:30 AM CDT, Liliana Marie Prikler wrote: > Am Sonntag, dem 19.12.2021 um 21:58 +0100 schrieb Liliana Marie > Prikler: > > Am Sonntag, dem 19.12.2021 um 14:01 -0600 schrieb bdju: > > > guix system > > > guix (GNU Guix) b3a0db7a0e5fa7186c090647cfd5666e2b9287ff > > > build log

bug#56076: guix shell -P behavior is surprising with persistent home

Ludovic Courtès schreef op di 28-06-2022 om 09:43 [+0200]: > Hi, > > Maxime Devos skribis: > > > > > Having to add openssl looks like a bug, > > > > > > It is, but it’s a reasonable solution for the problem at hand. > > > > I don't think it is. > > On another distro, you might have to set

bug#56076: guix shell -P behavior is surprising with persistent home

> On another distro, you might have to set SSL_CERT_DIR manually. It’s > not that big of a deal, or at least not really worse. On other distros, that's sufficient because they only have global installation, in /etc/ssl/certs. So I don't think it's a good comparison, given that Guix is all about

bug#51466: bug#53355: guix shell --check: confusing error message

Ludovic Courtès schreef op di 28-06-2022 om 09:45 [+0200]: > Maxime Devos skribis: > > > Ludovic Courtès schreef op ma 27-06-2022 om 12:17 [+0200]: > > > I agree that Dash should be fixed, but in the meantime, we still want > > > our stuff to work with the broken Dash (it’s the default on > > >

bug#55657: libgccjit is unusable

Hi, --- Original Message --- On Tuesday, June 28th, 2022 at 12:17 AM, Liliana Marie Prikler wrote: > Keyword here is "has worked for emacs". I've tried porting the logic > from flatwhatson's channel over, but regardless of what I do, it > already fails in the configure step of Emacs (in

bug#51466: bug#53355: guix shell --check: confusing error message

Maxime Devos skribis: > Ludovic Courtès schreef op ma 27-06-2022 om 12:17 [+0200]: >> I agree that Dash should be fixed, but in the meantime, we still want >> our stuff to work with the broken Dash (it’s the default on >> Debian/Ubuntu, isn’t it?). > > If Dash is fixed, then it's non-broken

bug#56076: guix shell -P behavior is surprising with persistent home

Hi, Maxime Devos skribis: >> > Having to add openssl looks like a bug, >> >> It is, but it’s a reasonable solution for the problem at hand. > > I don't think it is. On another distro, you might have to set SSL_CERT_DIR manually. It’s not that big of a deal, or at least not really worse.