bug#32360: gst-plugins-base has test failures (when built as a dependency)

On Sat, Aug 18, 2018 at 01:34:09PM +0200, Tobias Geerinckx-Rice wrote: > Pjotr, Leo, Guix, > > Pjotr Prins wrote: > > Someone still needs to push the patch. > > I went ahead and did so in 399c5fafcdb2d0c13ab51e4ab57d451d2c7cb1bd > since it's not really acceptable to have this broken in master.

bug#32293: wrap-program with non-colon separtor produces incorrect bash substitutions

Hello Jelle! Jelle Licht skribis: > While working to package some lua-related stuff, I need to deal with the > LUA_PATH environment variable. This variable uses `;' as a separator, and > as such, I wanted to wrap one of my programs > > ... > (wrap-program (string-append out "/bin/fennel") >

bug#32473: Broken menu entry in manual, section 4.1

I noticed a broken menu entry in the Info version of the Guix manual: the node `Defining Packages` (4.1) has an extra space between the last word and the closing colons: * package Reference :: The package data type The standalone Info reader tolerates it, but not the Info.vim reader, w

bug#32347: gzip cannot be patched

Hello, Efraim Flashner skribis: > On Thu, Aug 02, 2018 at 01:32:02PM +0200, Marius Bakke wrote: >> Hello! >> >> I'm trying to add a patch to 'gzip', but it causes an infinite loop and >> eventually the system runs out of memory. >> >> It can be reproduced by adding this hunk: >> > >> modified

bug#31974: If a phase returns #f, a warning is issued, but the build continues

Mark H Weaver skribis: > Mark H Weaver writes: > >> I just noticed that I made a mistake in commit >> d8a3b1b9e847d4a44d2695f95af77170d4d2788f, which changed 'gnu-build' in >> (guix build gnu-build-system) to issue a warning if a phase returns a >> value other than #t. >> >> The result is that i

bug#32234: [PATCH 2/2] database: Serialize all database accesses in a thread.

Hi Clément! Clément Lassieur skribis: > Fixes . > > * bin/cuirass.in (main): Keep only one WITH-DATABASE call around all fibers. > Remove all DB arguments. > * src/cuirass/base.scm (evaluate, update-build-statuses!, spawn-builds, > handle-build-event, build-packages):

bug#32377: guix gc -> build failed: executing SQLite statement: FOREIGN KEY constraint failed

Hello, Benjamin Slade skribis: > I'm running the latest GuixSD, and when I run: > > `guix gc` > > I get the error: > build failed: executing SQLite statement: FOREIGN KEY constraint failed That happens with ‘guix gc’ without any options? Do all runs of ‘guix gc’ fail like this? Does ‘guix gc

bug#32385: no code for module (guix build utils) - info-dir.drv - e921234d02 (master)

Hi Chris, Chris Marusich skribis: > On commit e921234d02 (current master branch head), I've noticed that > attempting to run "guix system reconfigure" using pre-inst-env on one of > my x86_64-linux systems fails with a message like: > > ERROR In procedure scm-error: > no code for module (guix bu

bug#32397: GCC 4.8 Failed to build.

fis trivial skribis: > guix Version: > guix (GNU Guix) cc48997de56864191a4a4ed4bed8763139c3add6 > > Platform: > Fedora 27 > > Original command: > guix environment --ad-hoc gcc@4.8 Fixed in 0b93d04ac537d6413999349ebe7cdcb1e961700e, thanks! Ludo’.

bug#32382: libchop has build failures

Hello, Björn Höfling skribis: > Build log at failure: > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../include/chop -I../include > -I../i > nclude -I../lib -I../lib -DGCRYPT_NO_MPI_MACROS -DGCRYPT_NO_DEPRECATED > -I/gnu/st > ore/dysmb6hz7rr5rvcb05p23dazc5hz26qm-libgcrypt-1.8.2/include > -I

bug#32385: no code for module (guix build utils) - info-dir.drv - e921234d02 (master)

l...@gnu.org (Ludovic Courtès) writes: > What version of Guile did you use to compile Guix? > > (If you used ‘guix pull’, then Guile 2.2.4 was used.) Yes, I believe it was Guile 2.2.4. I reported the bug on August 6th. The last time I ran "guix pull" before reporting the bug was on July 29th. T