IRC channel logs


back to list of logs

<Apteryx>Now I got grub to fail: FAIL: grub_cmd_set_date
<Apteryx>I'll try updating grub to 2.02 (not rc1) to see if there's any improvement.
<happy_gnu>lfam: hello :) I am installing Guix and have a question :P
<lfam>Okay :)
<mekeor`>go ahead :)
<happy_gnu>So is guix not GuixSD
<happy_gnu>I just did all the steps
<happy_gnu>and it has a link to application setup
<happy_gnu>I am currently running this command
<happy_gnu> guix package -i glibc-locales
<happy_gnu>but every package that is getting downloaded it shows a warning
<happy_gnu>warning: failed to install locale: Invalid argument
<lfam>happy_gnu: What distro are you using?
<lfam>Okay, are you using the guix-daemon.service file to run the guix-daemon with systemd?
<happy_gnu>Yes :)
<happy_gnu>I just insstalled hello
<happy_gnu>guix package -i hello
<happy_gnu>it works
<happy_gnu>but it also showed the warning
<lfam>Okay. You'll need to install glibc-locales as root, and then add this line to guix-daemon.service: Environment=GUIX_LOCPATH=/var/guix/profiles/per-user/root/guix-profile/lib/locale
<lfam>Then, reload and restart the guix-daemon
<lfam>That warning comes from guix-daemon
<happy_gnu>ok wait
<happy_gnu>Isn't that going to take a bunch of spacke to install glibc-locales twice :/
<happy_gnu>it was almost 500mb
<lfam>If your user and root try to install the same build of glibc-locales, there will only be one copy on your disk
<happy_gnu>so just do
<happy_gnu>sudo guix package -i glibc-locales
<lfam>sudo -i guix package -i glibc-locales
<happy_gnu>error: directory `/var/guix/profiles/per-user/root' is not owned by you
<happy_gnu>Please change the owner of `/var/guix/profiles/per-user/root' to user "root".
<lfam>That's weird, it should be owned by root
<happy_gnu>i did chown
<happy_gnu>and it run
<happy_gnu>The following environment variable definitions may be needed:
<happy_gnu> export PATH="/root/.guix-profile/bin:/root/.guix-profile/sbin${PATH:+:}$PATH"
<happy_gnu>what do I do with that enviroment variable?
<happy_gnu>copy and paste to terminal?
<happy_gnu>or do I need to add it to .bashrc or something??
<mekeor`>you should NOT put that in the bashrc of you user for sure!
<happy_gnu>mekeor`: jajajaja :P
<happy_gnu>Ok I won't :)
<happy_gnu>so I just copy and paste it in the same terminal
<happy_gnu>but should I do something else with it?
<happy_gnu>Save it or something?
<mekeor`>i wouldn't execute it either
<happy_gnu>waaaaaaatttttttt :/ did I just broke my system :(
<mekeor`>no, the command is nothing persistent
<mekeor`>you can just close the shell/terminal and the effect of that command will be gone
<happy_gnu>so what now ?
<happy_gnu>reload guix daemon? lfam?
<mekeor`>ACTION doesn't know
<lfam>happy_gnu: If you need to change PATH, do it in ~/.bash_profile
<lfam>And to reload the daemon, `systemctl daemon-reload && systemctl restart guix-daemon`
<happy_gnu>lfam: what is what should I do with that?
<happy_gnu>That pat is supposed to be on my bash profile?
<lfam>happy_gnu: It's probably easier if you add this to ~/.bash_profile: `. ~/.guix-profile/etc/profile`
<mekeor`> lfam, happy_gnu: i don't think it makes sense to add /root/.guix-profile to the PATH of a (normal) user
<lfam>Right, it's for the root user
<lfam>The ~/.guix-profile/etc/profile will have the special PATH settings, and other things will be added to it as you install more Guix packages
<happy_gnu>lfam: I am lost :/
<happy_gnu>I have to export path
<happy_gnu>one for my normal user and one for root
<happy_gnu>what do I do with those path settings? save them ?
<lfam>Any user who you want to use Guix with
<lfam>Put this command in ~/.bash_profile for each user: `. ~/.guix-profile/etc/profile`
<happy_gnu>then if I have 2 packages lets say emacs
<happy_gnu>when I open Emacs is gonna open the guix one right?
<happy_gnu>and how do I open the not-guix Emacs?
<happy_gnu>should it be with quotes `. ~/.guix-profile/etc/profile` or without . ~/.guix-profile/etc/profile
<happy_gnu>great lfam :)
<lfam>To use the not-guix emacs, I'd run it with the full pathname. Probably /usr/bin/emacs, but I don't know
<happy_gnu>i have it like this
<happy_gnu>[[ -f ~/.bashrc ]] && . ~/.bashrc
<happy_gnu>. ~/.guix-profile/etc/profile
<happy_gnu>is that ok? or should the guix one go before bashrc?
<mekeor`>looks good to me
<happy_gnu>mekeor`: ok :)
<happy_gnu>I need IceCat
<happy_gnu>today I did "pacman -Syu" and I lost IceCat :/
<lfam>They removed icecat
<happy_gnu>noo but and upgrade made it unusable for some dependencies
<happy_gnu>lfam: when you clean new gogles tell me to beat you :) ;)
<happy_gnu>I don't have hedgewars though :/
<happy_gnu>Recently I learned a little about lisp-scheme
<happy_gnu>and yesterday I read more about GuixSD
<happy_gnu>I fall in love :)
<happy_gnu>I will install it on a new SSD I am gonna buy
<happy_gnu>everything is so logical and simple
<happy_gnu>unlike parabola :/
<happy_gnu>with a lot of files
<happy_gnu>and GuixSD everything in one file
<happy_gnu>I am happy because now I understand
<happy_gnu>half year ago it was like reading russian to me :/
<lfam>happy_gnu: Please feel free to ask more questions and give feedback :)
<happy_gnu>lfam: well I do have a question
<happy_gnu>are guix packages inside containers?
<happy_gnu>lfam this is the output of icecat :/
<happy_gnu>guix package: error: build failed: some substitutes for the outputs of derivation `/gnu/store/wxzg3vcvjnyvk5xw07jwbdrdm30vyrfq-icecat-45.5.1-gnu1.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source
<lfam>happy_gnu: Try --fallback :)
<happy_gnu>guix package -i icecat --fallback
<happy_gnu>like that lfam?
<lfam>Guix packages are not in containers but you can run them in containers with `guix environment --container` and `guix container`
<happy_gnu>so after installing I do
<happy_gnu>guix container icecat
<lfam>happy_gnu: Here are some notes about how to do that:
<happy_gnu>great lfam :)
<lfam>I only know how to use `guix environment --container`. I haven't used `guix container`. But our manual should help you get started:
<lfam>I mean,
<happy_gnu>it has instructions on how to do it with IceCat :)
<happy_gnu>thanks lfam :)
<lfam>Yes, a common and urgent request :)
<happy_gnu>lfam: it is still downloading
<happy_gnu>I will tell you when it is finished :)
<happy_gnu>lfam: it downloaded a lot of stuff
<happy_gnu>and now is checking everything
<happy_gnu>is this normal?
<happy_gnu>it even downloaded python :/
<lfam>icecat depends on python
<happy_gnu>ohh ok :)
<DoublePlusGood23>Is there a reason to use IceCat over IceWeasel + plugins?
<happy_gnu>DoublePlusGood23: IceWeasel I completely forgot about that :/
<happy_gnu>I installed Icecat on Parabola
<DoublePlusGood23>happy_gnu: IceWeasel is pretty much firefox w/o branding and a few different compile options.
<DoublePlusGood23>I think IceCat is more or less the same, just more outdated.
<happy_gnu>DoublePlusGood23: thanks :)
<happy_gnu>lfam: my pc is starting to make a lot of noise :/ I am gonna cancelate the fallback
<DoublePlusGood23>happy_gnu: your cpu will just throttle if it gets "too hot" not anything to worry about.
<happy_gnu>well I cancelated :P
<happy_gnu>I am trying normal installation again
<happy_gnu>hey it worked :D
<happy_gnu>I have Icecat now :)
<happy_gnu>probably because of the fallback :P
<happy_gnu>:) I am glad
<DoublePlusGood23>Hoping I can install here without using fallback
<happy_gnu>how can I see the generations
<happy_gnu>lfam: yes :D
<happy_gnu>It works
<happy_gnu>I rebooted
<happy_gnu>I can launch Icecat not only from terminal
<happy_gnu>I am so happy
<happy_gnu>Now I need to add the store to emacs
<marusich>Man, the iteration time for hacking around with Guix's system tests is so slow.
<marusich>I added one 'pk' line to a source file, and now I'm apparently recompiling the entire system. It's been over an hour :(
<marusich>I can barely remember what I was trying to debug.
<DoublePlusGood23>need to pick up one of those Libreboot workstation boards for compiling.
<happy_gnu>lfam I am still getting the warning though
<lfam>happy_gnu: You need to do install glibc-locales and set GUIX_LOCPATH for your user, too
<happy_gnu>ohh I only did that for my user
<happy_gnu>not for root
<happy_gnu>and i am trying to install from my user
<lfam>Any user that uses the guix-daemon needs GUIX_LOCPATH set in order to avoid the warning. Or you could just ignore, since it's only a warning
<happy_gnu>now I've got this 2
<happy_gnu>export PATH="/home/albertoefg/.guix-profile/bin${PATH:+:}$PATH"
<happy_gnu>export INFOPATH="/home/albertoefg/.guix-profile/share/info${INFOPATH:+:}$INFOPATH"
<happy_gnu>lfam: thank you so much my friend :)
<lfam>happy_gnu: Is it working okay for you?
<Apteryx>Building linux-libre now. Hopefully passed that my system will be up-to-date with master again! I hit many small road bumps this week (flaky tests, corrupted nars, errors caused by failing substitute servers) :)
<DoublePlusGood23>Apteryx: Yeah getting corrupted archives. seems odd.
<Apteryx>I think they were zero length files that got cached somehow. I'm hoping the latest nginx config tweaks done by Ludovic will help prevent that.
<DoublePlusGood23>Apteryx: Stuck using fallback for the time being. Not sure how long it'll take this time
<Apteryx>DoublePlusGood23: I think it actually resumed working normally for me today or so.
<Apteryx>Except for the flaky tests :)
<bombastus>I installed guile 2.2.2 with the command 'guix package -i guile@2.2.2'. I get an error when trying to run it without sudo.. is this the correct/best way to install a different version of a global package?
<lfam>bombastus: Are you using GuixSD or Guix on another distro?
<lfam>On GuixSD, you can make a package available for all users by listing it in the (packages) field of your system configuration file
<mbuf>Is it possible to create a meta-meta-package from a list of meta-packages?
<mbuf>For example, if i want the user to install just one package, say, it describes a profile for setting up LAMP (just an example)
<happy_gnu>lfam: it is working :)
<happy_gnu>thanks lfam
<mbuf>but, these packages are already available in other meta packages?
<mbuf>if I have a lamp.scm, can it pull from these other .scms?
<bombastus>lfam: is that the best way to upgrade guile? How do I specify the version of guile to be installed when I do a system reconfigure?
<lfam>bombastus: I'm not sure. If nobody else pipes up, I'd ask on <>
<bombastus>ok, thanks
<rekado>janneke: the code I use to prevent Emacs from printing long lines is kinda ugly.
<rekado>janneke: it also doesn’t work well in the terminal where lines are erased and rewritten (e.g. for progress bars or counters)
<janneke>rekado: okay...
<janneke>this is one of the `it would be nice if someone fixed this' thingies
<janneke>fwiw, i'm trying out exwm
<rekado>janneke: what I use is a variant of this:
<janneke>rekado: right, thanks -- with a good explanation of why it's not `fixed' yet
<roptat>hi, I'm trying to make bind:utils globally visible on my guisd, but I don't know what I should use for that
<roptat>(specification->package "bind:utils") says: guix system: error: bind:utils: unknown package
<davexunit>roptat: import (gnu packages dns) and add (list bind "utils") to the packages field of your OS config
<davexunit>I don't recommend using specification->package
<roptat>thanks :)
<rekado>you can use specification->package+output (?)
<davexunit>those procedures are inherently limited and they make it unclear to know exactly which package you are using just by looking at the code.
<roptat>how could I have known that I could use (list package "output")?
<davexunit>roptat: gnu/system.scm has a comment about it
<davexunit>line 161
<davexunit>in the definition of the <operating-system> record type
<roptat>shouldn't it be in the manual too?
<davexunit>doesn't seem to be in the manual though
<roptat>I'll send a patch
<davexunit>but if you want to use guix you really shouldn't be afraid to look at the source
<davexunit>if all you do is look at the manual you won't get far
<davexunit>that said, a patch to the manual would be great.
<roptat>I don't think that's how you get more people involved :p
<davexunit>well this is a system for programmers
<davexunit>the source is very readable and well commented.
<roptat>I can read the code, no worries, I just don't usually read the code to find more info
<roptat>and I think it would be sad to have a system only for programmers
<davexunit>this particular detail should obviously be in the manual, but I wish people wouldn't stop at the manual.
<az`>hi there
<brendyn>Is there some reason why (assoc-ref outputs "out") needs to be used instead of %outputs ?
<snape`>instead of %output, you mean :)
<brendyn>Yeah that
<brendyn>%outputs exists too though
<snape>I think (assoc-ref outputs "out") is more functionnal, because it depends on "outputs", which is given as an argument of the function, whereas %output, which means (getenv "out"), depends on the less reliable global state. Not sure though.
<efraim>%output assumes that "out" is the only output, whereas it could potentially change in the future
<snape>ah, thanks efraim :)
<catonano>in the definition o the scmutils package there's a "make-img" procedure. Wat is that ?
<az`>guix nub question: Here: , linux-firmware defined in configuration, it's ok? Or I can (need to) save it in separate package file?
<az`>and `guix package -i linux-firmware` or what?
<roptat>az`, it's ok to define packages in the os configuration, but I think it won't be visible to 'guix' commands, so you have to put these packages in the packages field of the operating-system declaration
<roptat>actually in your example it's used in the kernel field
<az`>so, now I change my configuration like that, what next? How to reconfigure and install nonfree wifi modules?
<az`>"sudo guix system reconfigure /etc/config.scm" - all I need?
<roptat>I think that's all you need
<Petter>How do you tell the difference between Artistic License and Clarified Artistic License? I'm investigating which is here,
<bavier>OriansJ: I appreciate your stage0 forth interpreter.
<bavier>OriansJ: I'm almost done with a forth implementation of a C-subset language.
<bavier>correction almost done with the parser
<janneke>in what package do we have dig, host?
<mekeor>what's "dig, host"?
<janneke>the replacements for nslookup
<janneke>it seems they are in `bind' but get removed
<janneke>ACTION has a simple vm with internet access, but no dns
<janneke>i'm always out of my water with such problems
<mbakke>janneke: it's in the "utils" output of "bind"
***Steap_ is now known as Steap
<mbakke>efraim: can you check whether rocksdb builds on aarch64 when you have time? :)
<efraim>mbakke: just started the build
<slyfox>how can i check which code is generated in aplce of 'modify-phases' call?
<slyfox>keep struggling with
<slyfox>can I add some magic (display) statement to peek at what happens at expansion time?
<davexunit>slyfox: use ,expand at the REPL to see that
<slyfox>davexunit: i'm a weakling schemer. what should i pass to expand? the package name or the whole '(define-public bash-minimal ...' definition as it is?
<davexunit>the expression to expand
<davexunit>so the latter
<slyfox>aha, got it.
<davexunit>you could leave off the define-public stuff and just pass the package expression
<efraim>Sneek later tell mbakke Unknown value 'native' for -march, I'll take another look at it when I'm not sshing from my phone
<sneek>Will do.
<efraim>sneek: botsnack
<slyfox>is ',expand' a valid scheme? could I plug it into .scm file?
<davexunit>it's a REPL metacommand
<rekado>davexunit: I don’t agree that “specification->package+output” and the like are limited. Package names are almost always unique, and for many people it’s easier to use the same names in the manifest that they would use on the command line.
<rekado>using the variable names helps when you have name conflicts with package definitions on GUIX_PACKAGE_PATH
<davexunit>I guess so.
<davexunit>it's just not very Schemey
<rekado>heh, true :)
<davexunit>I don't like it because you can't inspect the source and discover where the package came from.
<davexunit>it's unhygienic in that way.
<lfam>rekado: I noticed that building for i686-linux from hurd started to fail in the latest evaluation:
<DoublePlusGood23>what the status of guix on hurd?
<lfam>It exists, but I don't know how many substitutes we build for it
<DoublePlusGood23>do most of the packages build?
<lfam>I don't know
<lfam>I recommend asking on <>
<DoublePlusGood23>Just curious. Might try it out on a vm
<lfam>DoublePlusGood23: phant0mas_ might have advice for you. They are the person behind much of Guix / Hurd work
<rekado>lfam: argh, that’s bad
<rekado>I made the change in glibc/linux
<rekado>didn’t expect that this would hurt the hurd :(
<lfam>rekado: I don't know if those builds succeeded before or not. That Hydra comparison page is comparing the current evaluation with an earlier evaluation, skipping the one with ~5000 failures
<Petter>Hurting the hurd is unheard of. Hurd can't be hurt.
<lfam>Even though I wasn't sure, I thought I'd point it out
<grillon_>hi there
<Petter>Hi grillon_
<Petter>How's your Guix adventure going?
<CharlieBrown>Can I dd the GuixSD image to a microSD card and boot from that?
<grillon_>Petter: I have too much problems I gave up. I prefere finish my back erase all and be free to restructure my disk
<lfam>CharlieBrown: Probably. It's intended to be dd-ed to a USB flash drive, but I think it should work on an SD card too
<lfam>ACTION tests a netpbm update
<Petter>grillon_: Are you giving it another go?
<rekado>lfam: no, the error looks like it’s caused by my patch
<lfam>rekado: Bummer :(
<lfam>rekado: Do you think we should cancel the current evaluation?
<grillon_>Petter: not yet. I have not finished my backup.
<bavier>Petter: I appreciate you hanging in there on the crt review, thanks for all the cleanup you did
<grillon_>hi mbakke
<Petter>grillon_: Now is a good time to read through the installation manual ;)
<Petter>bavier: Sure thing, I want to get this right!
<grillon_>Petter: sure :)
<rekado>lfam: not sure.
<grillon_>mbakke: thank you for your help yesturday
<rekado>lfam: we could, because we have to redo it anyway, but on the other hand i686 has been in a broken state for a very long time
<grillon_>thank you to every one :p
<lfam>rekado: Mostly, I'm wondering if I should continue testing the new GRUB on our current i686-linux tree, or if I should wait for a further update
<rekado>with the patch at least i686-linux should be okay, so existing i686 installations can upgrade
<Petter>bavier: I'm currently preoccupied with my next package, parcimonie, which is taking for-ever, but I'll disable unlicensed fonts shortly.
<bavier>Petter: sounds good
<rekado>(previously, upgrades would just result in random crashes)
<bavier>Petter: I look at parcimonie at one point, but didn't make much progress; good luck!
<rekado>maybe we can even make the change just in glibc/hurd
<rekado>so we won’t need to rebuild glibc/linux for i686
<bavier>Petter: I have just a few more pedantic comments about your patch that I'll send later.
<Petter>bavier: I have it working, just cleaning up and adding extra stuff where I shortcutted. Seems to be A Lot of optional dependencies as well as required.
<CharlieBrown>lfam: I will write it to an SD card and see if it boots. :-)
<Petter>bavier: Great! I like pedantics :)
<bavier>Petter: ;)
<slyfox>[ i was pointed at the other day as an interesting case of pedant{ry,icism} ]
<lfam>ACTION begins garbage collecting ~200 system generations
<Petter>Isn't pedantics a word? (I was just guessing.)
<phant0mas_>DoublePlusGood23: yes most packages build on Hurd
<CharlieBrown>dd'ing SD card to file, because IDK how it's formatted by my Android device and I just want to dd it back when I'm done.
<phant0mas_>me and methalo_ are working on it
<phant0mas_>if you want to try it pm me
<phant0mas_>so I can guide you
<phant0mas_>in case you need it
<Petter>slyfox: Now I am confused. How to say: I like pedan*?
<CharlieBrown>Is someone using GNU+Hund?
<phant0mas>it depends on what you mean
<phant0mas>I am using it to experiment and learn
<phant0mas>CharlieBrown: ^
<slyfox>Petter: i have no idea. any word works for me. i was mostly amazed by the type of discussions people are having over internet :)
<Petter>Guess you're looking at the tip of the iceberg then :P
<slyfox>who uses /gnu/store/...-guile-builder files? guix-daemon or guix client that talks to daemon?
<bavier>slyfox: client creates them, builder executes them
<slyfox>aha, that means it's really a representation of RPC
<slyfox>and all the functions used there must never be out of sync between client and server
<slyfox>i'm running guix-daemon from 0.12.0 release, but trying to run guix client from core-updates
<slyfox>and i suspect it does not work because modify-phases changed semantics
<slyfox>(it did)
<slyfox>is it expected behaviour or a bug in core-updates?
<slyfox>how that king of changes is usually managed?
<bavier>slyfox: that shouldn't cause a problem; the guix modules that define modify-phases are only loaded by the guile-builder, not by the daemon
<bavier>slyfox: there were other changes which might be incompatible with the 0.12 daemon
<slyfox>i have only modify-phases problem:
<slyfox>for some reason reverting guile-2.2 to guile-2.0 in core-updates fixes it
<slyfox>the expression required nested call of modify-phases. i suspect guile-2.2 fixed the glotch
<slyfox>the guile-builder rule looks like:
<slyfox>#:phases (modify
<slyfox>-phases (modify-phases %standard-phases (add-after
<bavier>slyfox: I suspect it might be the psyntax-equals bug that was fixed in guile.2.2.1
<slyfox>slightly nicer form: #:phases (modify-phases (modify-phases %standard-phases (add-after
<bavier>but I'm not sure
<slyfox>aha, core-updates has 2.2.0 while master is at 2.2.2. let's see it hewer version will fix it
<lfam>There's a good chance that core-updates is currently unusable. It's very new and I don't know if it's been tested yet
<lfam>I think it's still in the phase where we just dump updates on the branch
<CharlieBrown>The Nix users cringe at Guix just because of the ((())), but their language isn't much cleaner, either.
<slyfox>adding some types would help :)
<buenouanq>I've never understood the hate of lisp"s typical surface form.
<buenouanq>I think parens are far more beautiful and clean and clear than C likes etc.
<bavier>like most languages, I'd argue, after enough time one starts to read through the syntax
<rekado>hmm, how can I reproduce this build: ?
<rekado>it’s glibc-cross-i586-pc-gnu
<rekado>so I tried ./pre-inst-env guix build --fallback --system=i586-pc-gnu glibc
<rekado>but I’m told: “guix build: error: could not find bootstrap binary 'tar' for system 'i586-pc-gnu'”
<slyfox>shouldn't you use --target= instead of --system=?
<slyfox>AFAIU SYSTEM is nix/guix system name, like i686-linux, not a gnu-style triplet
<rekado>slyfox: thanks, I’ll try that. I’ve never done cross-compilation with guix (other than using --system)
<slyfox>i didn't know --system= can also do cross-compilation. if it does you'll need to find hurd's name for guix
<slyfox>bootstrap.scm suggests there is 2 system names like that: i586-gnu and i686-gnu
<slyfox>'guix build --target=i586-pc-gnu glibc' starts building cross-stuff for me ('guix build --system=i686-gnu glibc' does not)
<CharlieBrown>SD card backed up: if=/dev/sdb1 of=PhoneBackup
<CharlieBrown>Writing installer. if=iso of=/dev/sdb
<CharlieBrown>Do I have to manually point Libreboot's GRUB to the initrd and linux in the GuixSD installer image?
<Petter>Later you can flash Libreboot with an GuixSD entry.
<CharlieBrown>Which files in the installer image do I point to?
<Petter>Oh, installer image.
<Petter>I'd expect it have a /boot/grub/grub.cfg.
<CharlieBrown>So Libreboot might be able to just find that cfg and use it?
<Petter>Have you tried the different Libreboot menu entries? I thought it would handle this automatically when you select the right menu entry.
<CharlieBrown>Petter: I haven't tried. If I made a mistake and didn't know which files (maybe there are multiple initrd and linux files) then I'll have to type my long password and boot commands manually. Doing that multiple times in a row is a pain.
<Petter>Try an entry with usb or similar in it and see.
<CharlieBrown>Petter: I'll try it. Now that you've said there's a grub.cfg, I'm sure it'll work.
<Petter>I'd assume there is that on the installation image as well. Not sure though.
<Petter>Don't remember having any issues getting the installation image running.
<mbakke>grillon_: did you get it working?
<sneek>mbakke, you have 1 message.
<sneek>mbakke, efraim says: Unknown value 'native' for -march, I'll take another look at it when I'm not sshing from my phone
<grillon_>good night
<grillon_>mbakke: no I give it up
<grillon_>mbakke: I'm using lvm
<mbakke>did copying the grub.cfg not work?
<mbakke>efraim: weird, it should not be using -march=native, will investigate
<grillon_>mbakke: my bios is buggy, I use lvm, and my backup was not complete
<mbakke>grillon_: O_o
<mbakke>okay, hopefully it will go smoother next time :(
<grillon_>mbakke: yes too much small embarrasing thing
<grillon_>mbakke: hope so, because five hours of compilation is too much
<mbakke>yeah the lack of substitutes was annoying
<grillon_>mbakke: I'll try when substitutes are fine
<mbakke>they should be afte reach release
<mbakke>it's good to start with a minimal image, and add e.g. desktop environments once you have a working system
<mbakke>minimal config*
<mbakke>good night anyway, see you later :)
<grillon_>mbakke: I think so, next time minimal but with subsitute is better :p