bug#31740: guix pull failed with syntax error.

$guix --version guix (GNU Guix) 909301591d21d3879276e4ede3cebdcc867184f2 Copyright (C) 2018 the Guix authors License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

> >>> The result of running ‘guix pull’ is a “profile” available under >>> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to >>> add it to the beginning of your search path so that you use the latest >>> version, and similarly for the Info manual (*note

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Konrad Hinsen skribis: >>> I am looking for a reasonably straightforward way to have everything in >>> my Guix universe (the guix command line tool, emacs-guix, guile, geiser, >>> ...) consistently use my personal version of the package definitions. >> >> Would ‘guix package --manifest’ suffice?

bug#31719: icedtea-3 binaries contain references to icedtea-2

Gábor Boskovits writes: > Do you think we can do something like rebuild icedtea3 with icedtea3, and > then rewrite the references? I guess this way the dependency loop could be > broken, as we could detach the last icedtea3 build from the packages used > for bootstrapping. > We could even make

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hi Ludo, >> Fine, so if I run update-guix-package.scm and then do the install, I get >> what I expect, right? > > Yes (even with current ‘master’), but it’s quite heavyweight since you > end up recompiling all of Guix. Not great, but doable from time to time. >> I am looking for a reasonably

bug#31708: 'gcc-strmov-store-file-names.patch' causes GCC segfaults

Hi Mark, Mark H Weaver skribis: > Mark H Weaver writes: > >> Here's the declaration of QChar::byteOrderMark from qtools/qstring.h, >> included in the doxygen tarball: >> >> class Q_EXPORT Q_PACKED QChar { >> public: >> QChar(); >> QChar( char c ); >> QChar( uchar c ); >> QChar(

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello! Fis Trivial skribis: >> The result of running ‘guix pull’ is a “profile” available under >> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to >> add it to the beginning of your search path so that you use the latest >> version, and similarly for the Info

bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix

Hello Konrad, Konrad Hinsen skribis: >>> Just wondering: does this mean that I could substitute Guix from my local >>> source tree simply by doing >>> >>>./pre-inst-env guix package -p ~/.config/guix/current -i guix >> >> That would just install the snapshot that the ‘guix’ package refers

bug#31711: qutebrowser is broken

2018-06-06 11:48 GMT+02:00 Efraim Flashner : > On Mon, Jun 04, 2018 at 02:14:27PM +0200, Rutger Helling wrote: > > Hi Guix, > > > > qutebrowser fails to start with the recent python-pyqt upgrade, > > possibly due to the removed qtwebkit input. > > > > The following error occurs: > > --- > > > >

bug#31711: qutebrowser is broken

On Mon, Jun 04, 2018 at 02:14:27PM +0200, Rutger Helling wrote: > Hi Guix, > > qutebrowser fails to start with the recent python-pyqt upgrade, > possibly due to the removed qtwebkit input. > > The following error occurs: > --- > > Fatal error: QtWebEngine is required to run qutebrowser but