bug#61469: Xfce window snapping broke with latest upgrade

2023-02-12 Thread 宋文武 via Bug reports for GNU Guix
Nathan Dehnel writes: > Latest guix pull and reconfigure caused window snapping to stop > working in XFCE. I have tried toggling it off and on a few times in > the settings. > Current generation: ccf742f120452acf587d16e40adea570d15169c4 > Previous generation: 658c09333da095edf6e1b3c5e351a7bfa3c87

bug#61469: Xfce window snapping broke with latest upgrade

2023-02-12 Thread Nathan Dehnel
Latest guix pull and reconfigure caused window snapping to stop working in XFCE. I have tried toggling it off and on a few times in the settings. Current generation: ccf742f120452acf587d16e40adea570d15169c4 Previous generation: 658c09333da095edf6e1b3c5e351a7bfa3c87354

bug#58719: core-updates: Build failure for file on i686-linux

2023-02-12 Thread Kaelyn via Bug reports for GNU Guix
As a bit of followup, this bug still exists with the latest core-updates commit. This not only affects i686 systems, but also some x86_64 packages like wine/wine64 which require a 32-bit build in addition to a 64-bit one.

bug#61455: i686: go-gopkg-in-yaml-v3 build failed.

2023-02-12 Thread Denis 'GNUtoo' Carikli
Hi, go-gopkg-in-yaml-v3 is a dependency of docker and it fails to build on i686. Here's my guix revision: > $ guix describe > Generation 60 Feb 10 2023 01:09:07(current) > guix 07f19ef > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: master > commit: 07f19e

bug#51505: Request for official docker image on dockerhub

2023-02-12 Thread Denis 'GNUtoo' Carikli
Hi, If the idea is to be able to use a Guix docker image, as I understand dockerhub is not strictly required. For instance Fedora has its own docker registry[1] that works out of the box with docker pull. More generally to download an image one can just run: 'docker pull /'. As I understand that

bug#53296: Intermittent segfaults when parsing (?) custom package from repo.

2023-02-12 Thread elaexuotee--- via Bug reports for GNU Guix
Nothing like ACKing a year later! This was almost certainly a local hardware issue. The machine this happened on ended up showing progressively more mysterious behaviour that could not be reproduced on other machines. Feel free to close! Ludovic Courtès wrote: > Hi, > > Any update on this one?