IRC channel logs


back to list of logs

<Sleep_Walker>`inherit' is defined by guix or it is available in Guile in general?
<davexunit>Sleep_Walker: it's a part of the define-record-type* syntax that Guix defines.
<Sleep_Walker>it thought so
<Sleep_Walker>the most scary file in Guix
<zacts>is there a guide for how to do full disk encryption with guix 0.8.1?
<taylanub>while H.264 is proprietary/patented, x264 is free software; what would our guidelines say about packaging x264?
<_`_>isn't that the same scenario as mp3 and lame
<_`_>oh nvm mp3's actually open…
<taylanub>oh, mp3's patent still applies too doesn't it. I guess x264 should be fine too then.
<taylanub>Wikipedia says "active patents in the US"
<_`_>it's open standard with patents then?
<_`_>guess h264 is the same, I thought they were both closed standards.
<df_>aiui the issue is that theoretically mpeg la can shake down anyone distributing an implementation
<taylanub>has our build system changed wrt. network connections? the ngircd test suite fails to connect to
<taylanub>wait, never mind, it just fails to connect to a port
<civodul>Hello Guix!
<civodul>this san4 is annoying
<taylanub>I'm getting "warning: failed to install locale: Invalid argument" from applications again. I have glibc-{,utf8-}locales installed and LOCPATH set to ~/.guix-profile/share/locale.
<civodul>it's lib/locale nowadays
<taylanub>aha, that fixed it :-)
<civodul>good :-)
<civodul>the bad thing is that you only get a warning for LOCPATH if libc itself is in the profile
<civodul>+b san4
<civodul>let's see if that works
<effa>I think I've found the problem with GHC on i686 systems: it try to use 64 bit binaries instead of 32bit ones.
<effa>I was trying to select the binaries with (%current-system), but I guess we need to handle cross-compiling.
<effa>I've tryied with "(if (string-match "x86_64" (or (%current-target-system)
<effa> (%current-system)))"
<effa>but it still loads 64 bit binaries.
<effa>what is the correct way to do this?
<noob9000>I'm really confused with the .xz file extension. How do I change it to .iso so it can be installed on usb?
<noob9000>what is this... I don't even
<df_>decompress it with the program of the same name
<davexunit>noob9000: it's not an ISO
<davexunit>it's a raw disk image
<davexunit>you can use a tool like 'dd' to write it to the USB drive
<noob9000>Ohh Cool. will virtualbox recognize it? My laptop wifi is incompatible with freedom. I already reported to h-node. :D
<noob9000>well gonna test it on virtualbox.
<davexunit>noob9000: I think there's extra effort needed on virtualbox.
<davexunit>but I don't know the steps
<davexunit>because I don't use virtualbox since it's nonfree now.
<noob9000>Virtualbox won't recognized it. I uncompressed it, and try again, won't recognized it. I change uncompress file format to .iso, it still won't recognized it. I guess I'm SOL.
<davexunit>someone here has gotten it to work
<davexunit>but there's a conversion step
<davexunit>we'd like to have ISOs eventually, but no one has stepped up to work on it yet.
<civodul>effa: that looks like the correct way
<civodul>ah no
<civodul>i see
<civodul>effa: the value of ghc-bootstrap-7.8.4 is evaluated once and for all
<civodul>so you get whatever (%current-system) value was defined when haskell.scm was loaded
<civodul>the solution is to make ghc-bootstrap-7.8.4 a procedure that takes a 'system' parameter
<civodul>and then to call it from ghc's 'native-inputs'
<civodul>('native-inputs' is a "thunked" field, so it gets to see the "right" %current-system)
<effa>civodul: yes, I've found. I've split the binaries in 2 defines, one for x86_64 and one for i686. Then do the test when I use it in the source GHC.
<effa>It's building...
<civodul>ok, sorry for the delay then
<effa>Have to go. Will look later if the build was successfull.
<zacts>hello guix
<zacts>I guess no-one had an answer for my previous question
<zacts>I would like to install guix 0.8.1 on my main laptop, but I need documentation on how to do a fully encrypted root install
***noob9000 is now known as Lysander_Akili
<_`_>there probably isn't a detailed guide on that yet.
<civodul>zacts: in 0.8.1 encrypted root doesn't work
<civodul>in master there has been some progress but i suspect we're not there yet
<civodul>zacts: if you're will to try to install from master, it may allow us to go further with this bug
<zacts>oh I see, cool
<zacts>you may want to check this out, I'm looking at the bug report
<zacts>I'm guessing a step was missing in guix to do this
<zacts>although, you guys don't use mkinitcpio if I recall correctly
<_`_>that's arch specific…
<_`_>mkinitcpio that is.
<zacts>ah ok
<_`_>civodul: is guix's initramfs creator able to include cryptsetup to unlock luks containers?
<civodul>_`_: yes it does that automatically
<_`_>oh okay cool
<civodul>i have an encrypted /home on my machine
<civodul>that works well
<civodul>zacts: the thing is we don't use LVM yet
<civodul>but we could provide encrypted root without LVM
<zacts>oh I see
<Sleep_Walker>can I somehow distinguish between architectures during the build?
<taylanub>Sleep_Walker: grep for 'current-system' in gnu/packages/*.scm to see how it's typically done