Mono and .NET Core

Hi all, Two questions here. 1) Has anybody already started taking to try and upgrade Mono to latest? If not, I will give it a go. 2) Have we started any packaging on .NET Core, would like to know to prevent redundancy in work. Best, -- Brett M. Gilio Free Software Foundation, Member https://

Re: Come back and graphical installer

Hey Danny, > welcome back! Thank you :) > I agree. I've been meaning to write parted bindings for guile, but > I got side-tracked with https://github.com/daym/guile-gcc-unit which > can extract prototypes out of gcc source files (in order to automate > wrapper generation). Now I'm motivated

Re: Package for LXQt. Help wanted.

Hello, Mr. Song. Thank you for your reply. > Some notes to you: > - Wrap lines under 80 characters if possible. My emacs automatically wrap lines at exactly 80 characters. Should I set it to less than 80? #+BEGIN_SRC emacs-lisp (setq-default fill-column 80) ;; Change this to 70? #+END_SRC "

Re: Come back and graphical installer

Hi Ludo! > Woow, that’s an impressive comeback! :-) Thank you :) > BTW, if your bicycle trip stops by Paris, do not miss > : you’d have > nice stories to tell us about. :-) Haha, it would have been with pleasure, but I'll still be

Re: Come back and graphical installer

On Mon, 22 Oct 2018 22:47:29 -0400 bill-auger wrote: > if non-technical people are ever going > to try guixsd, then a fully graphical liveISO X desktop environment > with a mouse-centric installer will be essential i should qualify that statement as well to note that a graphical package manager wo

Re: Come back and graphical installer

FWIW, i will add that the bulk of effort required to have a pretty user-friendly mouse-centric installer for guixsd is not with the installer itself, but in making a liveISO that boots a graphical environment - i would not consider ncurses to be "graphical" and most casual users would not either -

Re: Package for LXQt. Help wanted.

Hello, I checked kwindowsystem's package in debian. It seems the plugins directory in kwindowsystem should be installed to /run/current-system/profile/lib/qt5/plugins rather than /run/current-system/profile/lib/plugins. Maybe this is a bug in the kwindowsystem package. File list of package libkf5

Re: Tensorflow package

Gábor Boskovits writes: > Hello Ricardo, > > Ricardo Wurmus ezt írta (időpont: 2018. > okt. 22., H, 22:17): >> I think that the patch I previously posted is not quite as useful as I >> had originally hoped. The new package uses the (now removed) CMake >> build system and unfortunately must be

Re: Tensorflow package

Hello Ricardo, Ricardo Wurmus ezt írta (időpont: 2018. okt. 22., H, 22:17): > I think that the patch I previously posted is not quite as useful as I > had originally hoped. The new package uses the (now removed) CMake > build system and unfortunately must be built with all the bundled > librarie

Re: Blog: Guix packaging tutorial

Pierre Neidhardt writes: > Divan writes: >> Off topic, but how did you convert this? Guessing pandoc, but it seems >> converted better then the standard, =pandoc index.org -t gfm -o >> /tmp/index.md= would do. > > This is a very good question. Indeed, Org support in Pandoc is sub-par, so I > di

Re: Tensorflow package

Hi Adam, > l...@gnu.org (Ludovic Courtès) writes: > >> Ricardo eventually submitted a preliminary TensorFlow package: >> >> https://issues.guix.info/issue/31386 >> >> It’s not directly usable at this stage but I’m sure Ricardo would >> welcome testing and help. As a first step, I suppose you

Re: Tensorflow package

l...@gnu.org (Ludovic Courtès) writes: > Ricardo eventually submitted a preliminary TensorFlow package: > > https://issues.guix.info/issue/31386 > > It’s not directly usable at this stage but I’m sure Ricardo would > welcome testing and help. As a first step, I suppose you could apply > the pat

GuixSD on AArch64

On 2018-10-22, Ludovic Courtès wrote: > On IRC earlier today Vagrant mentioned that the Pinebook AArch64 laptop > (see ) should be able to run > GuixSD when Linux-libre 4.19 and U-Boot 2018.11 are out, with 100% free > software. That may give another incentive

Re: In reference to outreachy Intership

Hello Swati, Could you give us a status update? Best regards, g_bor

Re: Outreachy applicant

Hello Cecilia, Could you give us a status update? Best regards, g_bor

Re: Trying to crosscompile for POWER9

On Sun, Oct 21, 2018 at 08:30:03AM +0200, Tobias Platen wrote: > On 10/20/2018 09:09 PM, Tobias Platen wrote: > Here are the build logs from guix. I have tried building the toolchain > twice, but in both cases glibc failed to build. [...] > running configure fragment for sysdeps/powerpc/powerpc64

Re: Come back and graphical installer

Hi Mathieu, welcome back! > I picked up the "Graphical installer" task. After studying the branch > wip-installer-2, I choose to rewrite it for multiple reasons: > > * I found the guile-ncurses approach too low level and think that many > bugs in the current installer could be avoided with a h

Re: Package for LXQt. Help wanted.

Meiyo Peng writes: > Hello everyone, > > I made a series of packages for LXQt. The code is at: > https://github.com/meiyopeng/guix/tree/lxqt Hello, it looks great! > > I did this beacuse I want to run i3 window manager within lxqt > session. Currently most things work great except lxqt-panel. I

Re: Come back and graphical installer

Hi, On Sat, 20 Oct 2018 21:48:34 +0600 Mathieu Othacehe wrote: > * Using Anaconda[1] as suggested by Harmut would mean interfacing a huge > codebase in Python, written for FHS based distributions. I just want to throw this over the fence... *runs away*: ;;; GNU Guix --- Functional package ma

Re: Come back and graphical installer

Hello! Mathieu Othacehe skribis: > To give you my opinion, I think that having a X/Wayland installer would > be really nice and totally agree. However, I also think it is important > to capitalize on the work already done. Plus, writting this kind of > installer is quite complicated because: > >

Re: Come back and graphical installer

Hello Mathieu! Mathieu Othacehe skribis: > First mail since a while ! I'm currently finishing a long bicycle trip, > and was able to start hacking again. Welcome back, I hope you had a good time! > I picked up the "Graphical installer" task. After studying the branch > wip-installer-2, I choos

Re: GuixSD on the SoftIron OverDrive 1000 (AArch64)

Hello! Efraim Flashner skribis: > On Sat, Oct 20, 2018 at 03:20:44PM +0200, Ludovic Courtès wrote: >> Hello Guix! >> >> The device comes with openSuSE preinstalled and I had first installed >> Guix from the binary tarball. It’s a “normal” UEFI machine so we can >> use ‘grub-efi’ directly. I c

Re: GuixSD on the SoftIron OverDrive 1000 (AArch64)

Hi, Jan Nieuwenhuizen skribis: > Ludovic Courtès writes: [...] >> On the first boot, the GuixSD activation snippets fail while trying to >> install /etc, /etc/pam.d, and /etc/skel, and /etc/ssl because these >> directories already exist (from openSuSE) whereas GuixSD assumes that >> they don’t

Re: New Guix reference card

Hello! Leo Famulari skribis: > On Sat, Oct 20, 2018 at 01:05:18PM -0700, Chris Marusich wrote: >> I see that the second page is mostly blank. Is that intended? > > I think it's meant to be the back of a printed card. Exactly! If you don’t have a double-sided printer, you can obviously skip th

Re: Tensorflow package

Hello Adam, Adam Massmann skribis: > I was wondering if anyone is currently working on packaging > Tensorflow, and if so what the progress is looking like. It > looked like back in April Ricardo was least looking at > it[1]. > > I just found out I need to use it for a collaboration, and > if I c

Re: Channel dependencies

Hello! Ricardo Wurmus skribis: >> I’d recommend ‘match’ for the outer sexp, and then something like the >> ‘alist-let*’ macro from (gnu services herd) in places where you’d like >> to leave field ordering unspecified. > > I keep forgetting about alist-let* (from srfi-2, not herd), even though >

Re: Channel dependencies

Hello! Chris Marusich skribis: > Ricardo Wurmus writes: > >> [...] >> >>> Chris raises interesting issues. I think it’s OK to first come up with >>> an implementation that has some limitations but works with the simple >>> use cases we have in mind. >> >> I’ve fixed this according to what we’v

Re: New Guix reference card

Hello Leo, Leo Famulari ezt írta (időpont: 2018. okt. 22., H, 4:56): > > I think it's meant to be the back of a printed card. It would be great > to have a stack of these for FOSDEM :) How big stack are you thinking about? Maybe I can help there :) g_bor