bug#35085: emacs reproducability problem also affects emacs-next 27.0.91

2020-05-01 Thread Jack Hill
Hi, I filed a duplicate bug earlier today while working on emacs-next. The problem now also seems to include the new .pdmp files. Best, Jack

bug#41012: emacs-next does not build deterministically

2020-05-01 Thread Jack Hill
On Fri, 1 May 2020, Jack Hill wrote: For me, emacs-next does not build deterministically. I should add, this is master at commit 26e11cffb983604c813064343e41708b99072e4f I also just tested emacs 26.3, and that also build non-deterministically. If this is a known problem, I apologize, but I

bug#22883: Authenticating a Git checkout

2020-05-01 Thread Ludovic Courtès
Ludovic Courtès skribis: > • Generalize that to channels. As I see it, the generalization would be made by adding the authentication parameters to the ‘.guix-channel’ file, along these lines: (channel (version 0) (keyring-reference "my-keyring-branch") (historical-authorizations

bug#22883: Authenticating a Git checkout

2020-05-01 Thread Ludovic Courtès
Hey! Ludovic Courtès skribis: > • Load the keyring from files in the repo, possibly in a dedicated > branch. > > • Load the list of authorized keys from the parent of the commit being > authenticated. Done! 8916c2fa32 git-authenticate: Load the keyring from the repository. 6960

bug#22883: Authenticating a Git checkout

2020-05-01 Thread Ludovic Courtès
Hi Justus, Justus Winter skribis: > Ludovic Courtès writes: [...] >> Signature verification in (guix openpgp) does just that: signature >> verification. It does not validate signature and key metadata, in >> particular expiration date. I guess it should at least error out when a >> signatur

bug#22883: Authenticating a Git checkout

2020-05-01 Thread Justus Winter
Ludovic Courtès writes: > At this stage, ‘make authenticate’ uses the pure-Scheme implementation > (based on Göran Weinholt’s code, heavily modified). It can authenticate > 14K+ commits in ~20s instead of 4m20s on my laptop, which is really > nice. Neat :) > Signature verification in (guix ope

bug#40977: --load-path does not honor ~

2020-05-01 Thread zimoun
Dear, Sorry to be slow. On Thu, 30 Apr 2020 at 21:20, Tobias Geerinckx-Rice wrote: > Hartmut Goebel 写道: > This is the wrong thing to do and makes the GNU system an > inconsistent mess. …OK, *more* of an inconsistent, loveable, mess > ;-) I still think that the behaviour of Guix could be con

bug#40999: GRUB prevents booting a degraded RAID1 array atop LUKS

2020-05-01 Thread maxim . cournoyer
On a system where: 1) Each disks comprising the array is fully LUKS encrypted 2) Each mapped disk is made part of a Btrfs RAID1 array When attempting to boot the system after pulling out (in BIOS or using the cable) the drive to simulate a complete disk failure, GRUB hangs, prompting for the LUKS

bug#40998: Guix System's initrd doesn't honor rootflags

2020-05-01 Thread maxim . cournoyer
Which means users cannot pass a 'rootflags=degraded' command line option to the kernel line in GRUB to attempt booting a system whose RAID array is degraded. rootflags is standard across distributions, and is what users expect. Such support was added in earlier version of the patches proposed her

bug#40997: [raid] The bootloader can only be installed to a single drive

2020-05-01 Thread maxim . cournoyer
Using Guix System, the bootloader declaration doesn't currently seem to support being installed to multiple drives: --8<---cut here---start->8--- (bootloader (bootloader-configuration (bootloader grub-bootloader) (target "/dev/s

bug#38667: Network-Manager (sometimes) fails reconnecting to network automatically

2020-05-01 Thread maxim . cournoyer
I haven't seen this problem in a long time, so I'm closing the issue. I suspect it is more a problem with Network Manager than with Guix. Maxim

bug#40790: OOM error in graphical installer tests.

2020-05-01 Thread Bengt Richter
Hi Ludo, et al, On +2020-04-30 23:10:05 +0200, Ludovic Courtès wrote: [...] rc1: best-practice: commit logs: message syntax --8<---cut here---start->8--- > Nitpick: please include the canonical bug URL in commit logs rather > than a link to the mailing list, li

bug#35574: bcm5974 touchpad is not recognized as touchpad

2020-05-01 Thread pelzflorian (Florian Pelz)
Pushed as e06664da02a829c7fa8fd084aac47c837451d57a. Closing.

bug#35574: bcm5974 touchpad is not recognized as touchpad

2020-05-01 Thread pelzflorian (Florian Pelz)
On Wed, Apr 29, 2020 at 06:46:51PM +, Brice Waegeneire wrote: > LGTM! I wonder if, as Ubuntu, we should also blacklist “usbkbd” the > counterpart of “usbmouse” or just to wait a bug report about it - if > it ever happen. I will add usbkbd to the blacklist because

bug#35574: bcm5974 touchpad is not recognized as touchpad

2020-05-01 Thread pelzflorian (Florian Pelz)
On Wed, Apr 29, 2020 at 06:41:20PM +0200, pelzflorian (Florian Pelz) wrote: > Actually in my tests I no longer need the modprobe.blacklist=radeon on > my AMD PC. I suggest the attached revert instead and will push it if > there are no objections. Reverted as 73ddcab6075f60ef9b3cd72a35fbf7f5d622b6