Re: Reproducible rust builds
On Mon, Oct 15, 2018 at 1:21 PM Joe Hillenbrand wrote: > > I've pulled your repo and started a build with 4 rounds just to check. > It will probably take a couple of days. > FYI, the build completed without issue.
Re: GHC 8.4.3
I'm not a guix expert yet, so I looked at updating GHC and I got way out of my depth real fast. I just wanted to say thanks. > Some of you may recall that I started work on updating all of our > Haskell packages to their LTS 12 versions, and making sure they all > build with GHC 8.4.3. Is this lts-12.10? ghc-8.6.1 was release a couple weeks ago, but I assume it will be added after lts-13.0 comes out. > There are 21 failing packages. corrode[1] should probably be removed. It hasn't been touched in over a year and a half and has been surpassed by c2rust[2]. I'm also pretty sure nobody except the author ever really used it as it had a lot of bugs and couldn't convert much C code. [1] https://github.com/jameysharp/corrode [2] https://github.com/immunant/c2rust
Re: SeaGL 2018 Accepts Guix-Themed Talk: "Everyday Use of GNU Guix"
Awesome! I've never had a reason to go to SeaGL before, but you just gave me one for this year. See you there!
Re: Manage ssh public keys?
On Thu, Apr 9, 2015 at 5:00 AM, Ludovic Courtès l...@gnu.org wrote: No (not yet?). I guess you mean the authorized keys, right? Yes It would be nice to have something like that, especially for automated deployment scenarios. That is specifically the scenario I am building for. I am also trying to build testing VMs that need to be able to ssh after the images boot up. How do you suggests this functionality should be added? NixOS has the openssh.authorizedKeys.keys setting, but I don't think that translates to Guix. https://nixos.org/nixos/manual/sec-user-management.html
Manage ssh public keys?
Is there a way to manage users' ssh public keys via the operating-system configuration?
