bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform.

Ricardo Wurmus skrev: (23 januari 2019 23:27:26 CET) > >Julien Lepiller writes: > >> Le 23 janvier 2019 22:12:58 GMT+01:00, swedebugia > a écrit : >>>"Installing for i386-pc platform. >>>Installation finished. No error reported." >>> >>>After reboot: >>> $ uname -a >>>Linux komputilo 4.20.3-gnu

bug#34182: gnucash-docs update failed

Hello, writes: > downloading from > https://ci.guix.info/nar/0891alvyi59rn7136127456ahlndjnn5-gnucash-3.4.tar.bz2 > ... >  gnucash-3.4.tar.bz2  12.9MiB 1.3MiB/s 00:10 [##] > 100.0% > Updates

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

Vagrant Cascadian writes: > On 2019-01-23, Mark H Weaver wrote: >> Here's a proposed (untested) patch. Would you like to test it and see >> if it eliminates the need for this workaround? > > It did, thanks! Okay, I pushed it to master, commit ff0b73028c0bbbcbf352989ed3863947357c3bce. I'm

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

On 2019-01-23, Mark H Weaver wrote: > Vagrant Cascadian writes: > >> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an >> aarch64 system failed to boot (using 4.19.10 worked fine): > > [...] > >> Workaround or fix was to add to config.scm: >> >> (initrd (append (list

bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform.

Julien Lepiller writes: > Le 23 janvier 2019 22:12:58 GMT+01:00, swedebugia a > écrit : >>"Installing for i386-pc platform. >>Installation finished. No error reported." >> >>After reboot: >> $ uname -a >>Linux komputilo 4.20.3-gnu #1 SMP 1 x86_64 GNU/Linux >> >>The i386 is technically

bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform.

Le 23 janvier 2019 22:12:58 GMT+01:00, swedebugia a écrit : >"Installing for i386-pc platform. >Installation finished. No error reported." > >After reboot: > $ uname -a >Linux komputilo 4.20.3-gnu #1 SMP 1 x86_64 GNU/Linux > >The i386 is technically incorrect according to

bug#34184: Nitpick on reconfigure message: Installing for i386-pc platform.

"Installing for i386-pc platform. Installation finished. No error reported." After reboot: $ uname -a Linux komputilo 4.20.3-gnu #1 SMP 1 x86_64 GNU/Linux The i386 is technically incorrect according to https://en.wikipedia.org/wiki/Intel_80386 and https://en.wikipedia.org/wiki/X86-64 I

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

Hi, Vagrant Cascadian writes: > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > aarch64 system failed to boot (using 4.19.10 worked fine): [...] > Workaround or fix was to add to config.scm: > > (initrd (append (list "crc32c_generic" ... ) %base-initrd-modules))

bug#34182: gnucash-docs update failed

Hello, ezt írta (időpont: 2019. jan. 23., Sze, 20:12): > > downloading from > https://ci.guix.info/nar/0891alvyi59rn7136127456ahlndjnn5-gnucash-3.4.tar.bz2... > gnucash-3.4.tar.bz2 12.9MiB 1.3MiB/s 00:10 [##] > 100.0% > Updates result this > > $ guix pull && guix

bug#34182: gnucash-docs update failed

downloading from https://ci.guix.info/nar/0891alvyi59rn7136127456ahlndjnn5-gnucash-3.4.tar.bz2 ...  gnucash-3.4.tar.bz2  12.9MiB 1.3MiB/s 00:10 [##] 100.0% Updates result this $ guix pull &&

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

On Wed, Jan 23, 2019 at 07:54:24PM +0200, Efraim Flashner wrote: > On Wed, Jan 23, 2019 at 11:54:31AM +0100, Ludovic Courtès wrote: > > Hi Vagrant, > > > > Vagrant Cascadian skribis: > > > > > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > > > aarch64 system failed to

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

On Wed, Jan 23, 2019 at 11:54:31AM +0100, Ludovic Courtès wrote: > Hi Vagrant, > > Vagrant Cascadian skribis: > > > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > > aarch64 system failed to boot (using 4.19.10 worked fine): > > > > [3.692351] device-mapper: ioctl:

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

On 2019-01-23, Ludovic Courtès wrote: > Vagrant Cascadian skribis: >> After upgrading to linux-libre 4.20, and again tested with 4.20.3, an >> aarch64 system failed to boot (using 4.19.10 worked fine): >> >> [3.692351] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: >>

bug#32458: Acknowledgement (SDL SEGFAULTs on foreign distro)

Hi, So the machine that has this error has the following properties: Distro: Debian Stretch ``` sources.list deb http://ftp.de.debian.org/debian/ stretch main deb-src http://ftp.de.debian.org/debian/ stretch main deb http://security.debian.org/debian-security stretch/updates main deb-src

bug#34181: guile-hall: no code for module (config)

Hi Jack, Thanks for your bug report — this is super helpful to debug the guile-build-system in guix! Jack Hill writes: > The guile-hall package appears to be broken. All hall commands that I > run result in a "no code for module (config)" error. The Guile build system propagates installs of

bug#34181: guile-hall: no code for module (config)

The guile-hall package appears to be broken. All hall commands that I run result in a "no code for module (config)" error. Using a current version of guix: $ guix --version guix (GNU Guix) f0caf7607d42b7d3daa3da2bd8e662fdf6e54b18 I first build guile-hall. In the build, there are serveral

bug#33999: CP437: Invalid Argument on init

I am indeed using flash storage, specifically a Samsung Evo 850 (it's a few years old and has had many distress installed and reinstalled on it; now that I'm thinking about it, it wouldn't surprise me at all if this was the underlying issue). I'm trying your recommendation of reinstalling and

bug#34158: dnscrypt hash failed

Hi Björn, Björn Höfling writes: > Someone needs to update the package. I'm not sure, is this the same: > > https://dnscrypt.info/ > https://github.com/jedisct1/dnscrypt-proxy Dnscrypt-proxy 2 (dnscrypt.info) is very different from dnscrypt-proxy 1 (dnscrypt.org). Their config files are

bug#34162: linux-libre 4.20+ fails to mount ext4 on aarch64

Hi Vagrant, Vagrant Cascadian skribis: > After upgrading to linux-libre 4.20, and again tested with 4.20.3, an > aarch64 system failed to boot (using 4.19.10 worked fine): > > [3.692351] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: > dm-de...@redhat.com >

bug#33859: ghc-conduit-extra build fails

Builds without problem since 5de93cdba77db3777f8f026c029acadd7b8bdde3 signature.asc Description: PGP signature

bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9)

Hello Mike, Mike Gerwitz ezt írta (időpont: 2019. jan. 23., Sze, 7:10): > > Well, I'm not getting those hours of my life back. > Sorry to hear that. > On Wed, Jan 23, 2019 at 00:58:57 -0500, Mike Gerwitz wrote: > > usb usb3: root hub lost power or was reset > > [...] > > > uhci_hcd

bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9)

On Wed, Jan 23, 2019 at 01:08:39AM -0500, Mike Gerwitz wrote: > Well, I'm not getting those hours of my life back. > > On Wed, Jan 23, 2019 at 00:58:57 -0500, Mike Gerwitz wrote: > > usb usb3: root hub lost power or was reset > > [...] > > > uhci_hcd :00:1d.0: host controller process error,

bug#33647: First `guix pull' behaves unexpectedly

Hi Diego, Diego Nicola Barbato skribis: >> Thanks for the heads-up. Commit >> 3bbd6919bd84b76686d1aa626ba861faf3fc8ceb changes ‘guix pull’ to display >> a hint in this case. >> >> Ludo’. > > I just tried to check if this worked. I installed GuixSD in a VM (with > the 0.16.0 installer),