IRC channel logs

2017-08-31.log

back to list of logs

<cbaines>sneek, later tell civodul regarding the ISO installer, I've only got as far as creating a bug, and sending the changes that I had lying around https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28288
<sneek>Will do.
<lfam>I'm looking at this backtrace while working on the go-build-system: http://paste.lisp.org/+7LQC
<sneek>Welcome back lfam, you have 1 message.
<sneek>lfam, efraim says: you have two copyright lines in gnu/packages/image.scm
<lfam>The issue is that the values in the backtrace are truncated
<lfam>Can I make it show me the full filenames?
<lfam>I guess it doesn't matter too much in this case since there is only one gzip archive
<garlox[m]>Hi guix. I saw an old thread on the devel list about including a package for syncthing. Seems it went nowhere. Does anyone what the current state of this is?
<ng0>Okay, after today I'm positive I'm getting somewhere with the icecat plugin project :)
<ng0>might take a while though
<lfam>garlox[m]: You can use it from my repo for now: https://github.com/lfam/pkgs/blob/master/leo/packages/syncthing.scm
<lfam>garlox[m]: I'm currently working on a go-build-system so that we can include Syncthing and other Go software in Guix
<dustyweb>uhoh D:
<dustyweb>oh ok :)
<dustyweb>ignore my uhoh :)
<quiliro>hello guix
<quiliro>i had an error with guix system reconfigure
<quiliro>guix system errer: failed to install bootloader
<quiliro>/gnu/store/...-bootloader-installer
<buenouanq>what does the bootloader line in your config look like?
<quiliro>buenouanq: (bootloader (grub-configuration (grub grub-efi)
<quiliro> (device "/dev/sda1")))
<quiliro>
<quiliro>Instalando para plataforma x86_64-efi.
<quiliro>/gnu/store/yxvmba7ig8gj1rxgirg90psacg93agrn-grub-efi-2.02/sbin/grub-install: error: no se pudo obtener la ruta canónica de «none».
<quiliro>
<quiliro>and /dev/sda1 is mounted as vfat on /boot/efi
<quiliro>the file-system line is:
<quiliro>(file-system
<quiliro> ;; Specify partition here since FAT
<quiliro> ;; labels are currently unsupported.
<quiliro> (device "/dev/sda1")
<quiliro> (mount-point "/boot/efi")
<quiliro> (type "vfat"))
<buenouanq>get rid of the 1 from device
<buenouanq>should just be /dev/sda
<buenouanq>wait
<buenouanq>I'm confused
<buenouanq>ok, I see
<quiliro>it is weird...it worked the last time i used it
<buenouanq>in the bootloader line what I said is true
<buenouanq>(bootloader (grub-configuration (grub grub-efi) (device "/dev/sda")))
<quiliro>i will try....thank you
<quiliro>did not work
<quiliro>buenouanq: the error with grub is that the canonical route <<none>> could not be obtained
<quiliro>with sda1 and also with sda
<buenouanq>hmmm
<quiliro>;;; WARNING: loading compiled file /gnu/store/nmjzgf4d6h27p1hmikin00mylcydk74c-module-import-compiled/gnu/build/activation.go failed:
<quiliro>;;; ERROR: In procedure load-thunk-from-memory: not an ELF file
<quiliro>;;; WARNING: loading compiled file /gnu/store/nmjzgf4d6h27p1hmikin00mylcydk74c-module-import-compiled/gnu/build/activation.go failed:
<quiliro>;;; ERROR: In procedure load-thunk-from-memory: not an ELF file
<quiliro>making '/gnu/store/4135grlwhxdk4hbvxl6rrzg4zkmgil3j-system' the current system
<quiliro>sorry for the flood
<quiliro>do i need to guix pull or something?
<quiliro>or guix package -u ?
<buenouanq>unless you have a reason not to, running guix pull before anything I think is good practice
<quiliro>ar
<quiliro>doing it now
<buenouanq>otherwise you'll have to wait for someone more knowledgeable in general and about efi than I am
<quiliro>be
<quiliro>buenouanq: thank you
<buenouanq>sorry i couldn't help
<buenouanq>my experience with guix and guixsd is that everything just works and i never have any problems anymore
<buenouanq>and that's unfortunately not a great place to be for learning about how it works or to help navigate other peoples"s issues (;-___-)
<quiliro>buireally? you never have any errors?
<quiliro>buenouanq: really? you never have any errors?
<buenouanq>network/server problems sometimes that force me to just use --fallback, but nothing major
<buenouanq>I don't do anything fancy with it though.
<pmikkelsen>hello guix, I have a working package definition for the godot engine, but I made it using the unreleased version 3. would anyone be interrested in a version for the current stable? Otherwise I will keep the package local untill version 3 is released, which might take some time :)
<roelj>I'm getting a bunch of these errors: http://paste.lisp.org/+7LQX
<roelj>The paths to the store given in the backtrace do not exist..
<roelj>Any idea why it uses non-existent paths?
<civodul>Hello Guix!
<sneek>Welcome back civodul, you have 1 message.
<sneek>civodul, cbaines says: regarding the ISO installer, I've only got as far as creating a bug, and sending the changes that I had lying around https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28288
<civodul>cbaines: oh great, i haven't caught up with email yet
<qwe123>hi, i stopped "guix system init" with ctrl-c when i found i wanted to change some configuration(rm some pkg then add other pkg) . is it just safe "gunix system init" again?
<Apteryx>qwe123: sure
<buenouanq>yay functional management~
<civodul>ctrl-c safety for all!
<Apteryx>:)
<qwe123>Apteryx: thanks all. i don't like doing it again from the beginning and the answer is really pleasing. :) can you give me some hints about guix logic or source file i can look around myself?
<Apteryx>I'm starting to grok debbugs. I like how it uses Gnus to display the mail thread.
<Apteryx>qwe123: Hmm, you could just browse anything under guix/guix
<qwe123>Apteryx: i see. i'm doing that and wanted kind of fastpath. good luck :
<qwe123>:)
<Apteryx>I'm not sure if emacs support tags for Scheme for navigation, but I bet i does. I've been using Geiser for navigating (jumping from one def to another) and it works usually well; you might have to 'load' the module being looked at though, with C-c C-a for example.
<mekeor>hellou guix :)
<efraim>sneek: later tell lfam I dont know the freedom status, but the nvidia Jetson tx1 is on sale https://www.cnx-software.com/2017/08/23/nvidia-jetson-tx1-developer-kit-se-offered-for-199-promo/
<sneek>Okay.
<efraim>sneek: botsnack
<sneek>:)
<wigust>mekeor: o/
<civodul>efraim: it would be a surprise if NVIDIA had become concerned with user freedom...
<efraim>I think everything except for the GPU is free
<civodul>okay
<civodul>well it's hardware so it cannot be "free", only the design can be free, as rms would say ;-)
<efraim>True
<efraim>On another note, I started last night to see about adding debian as a content-addressed-mirror, but it looks like I'll need to either parse the 'file' and have complex rules to match Debian's tarball names
<quiliro>Hello Guix!
<quiliro>How is everyone?
<quiliro>I have a bootloader-installer error on 'guix system reconfigure lightweight-desktop.scm'. Will it not boot or spit some kind of other error if I ignore it?
<quiliro>I have pasted the exact error before on this chat.
<quiliro>Shall I report a bug or mail to the help list or wait for a reply here?
<mekeor>quiliro: if you don't know that it's a bug, you should not probably report a bug. rather ask on the help-list if required
<quiliro>mekeor: Thank you. I will do it now.
<mekeor>quiliro: i can't help you because i don't have the link to your error message
<quiliro>be back
<Apteryx>civodul: I just sent a small patch that should allow us to close #27157 (Building Guile 2.2 "times out").
<civodul>Apteryx: woohoo!
<Apteryx>It took the bug to bite me again to fix it this time around ;)
<civodul>heheh, thanks
***fkz is now known as Guest43034
<ng0>has someone successfully used the --branch option of guix pull?
<ng0>I get this with cgit:
<ng0>user@shadownet ~$ guix pull --url=https://gitweb.krosos.org/ng0_guix/guix --branch=thisisatestbranch
<ng0>Updating from Git repository at 'https://gitweb.krosos.org/ng0_guix/guix'...
<ng0>guix pull: error: Git error: invalid Content-Type: text/plain; charset=UTF-8
<ng0>while git clone works
<ng0>and afaik guix pull without the --branch works
<ng0>correction: doesn't. since I can clone via https which is not provided by the git-daemon running on the same server, it isn't caused by cgit?
<civodul>ng0: are you sure this is the repo URL and not the web UI URL?
<ng0>for this repo, /etc/cgitrc has:
<ng0>repo.url=ng0_guix/guix
<ng0>repo.owner=ng0
<ng0>repo.path=/srv/git/ng0/ng0_guix/guix.git
<ng0>or maybe the build server is on an commit too old.. that's a possibility. locally (here, keyboard) I was able to git clone via https://… which didn't work on that build machine
<ng0>I'm pulling and reconfiguring now to exclude that option
<ng0>might take a couple of hours.. or days
<efraim>ng0: with 'git fetch --all' I get: fatal: repository 'https://gitweb.krosos.org/ng0_guix/guix.git/' not found
<ng0>because it is not ending on .git
<ng0>for git:// it is
<ng0>though it uses different urls then
<efraim>url = https://gitweb.krosos.org/ng0_guix/guix.git
<ng0>the bottom here: https://gitweb.krosos.org/ng0_guix/guix/
<ng0>oh
<ng0>where's that url from?
<efraim>no clue, but I think it worked at least once, i have a 'ng0/system/mate' branch locally
<ng0>hm
<ng0>I changed the urls for cgit when I had to figure out groups
<efraim>when i took off the '.git' it works again
<ng0>yes:
<ng0>@sharknado9000:/tmp# git clone https://gitweb.krosos.org/ng0_guix/guix --branch system/mate
<ng0>Klone nach 'guix'...
<ng0>Prüfe Konnektivität... Fertig.
<ng0>so it's weird that guix pull doesn't
<quigonjinn>Is there a way to generate a bootable iso image with guix? If so, where can I find the instructions?
<efraim>quigonjinn: I would check the makefile
<ng0>I want to revisit this discussion: http://guix-devel.gnu.narkive.com/dpNUIsm9/use-zsh-as-login-shell while zsh might work a bit better, I need some way to include the fpath to detect the zsh extensions provided through guix.
<ng0>without testing it would look like what Nix does (there's more to it, but basically:)
<ng0> for p in ''${(z)NIX_PROFILES}; do
<ng0> fpath+=($p/share/zsh/site-functions $p/share/zsh/$ZSH_VERSION/functions $p/share/zsh/vendor-completions)
<ng0> done
<ng0>taken from https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/programs/zsh/zsh.nix
<ng0>and I'm reading some more files
<Apteryx>Where does the two spaces "rule" comes from? I was surprised to encounter it for the first time in texinfo/scheme docstring. It doesn't hold any ground in the typography world (does TeX does it, for example? No.), so it got me curious!
<ng0>all I found was some countries use it
<rekado_>“two spaces” is an old typewriter convention
<rekado_>and it made its way into Emacs where it is used to jump from sentence to sentence.
<Apteryx>Ah, I see. So the tools now rely on this?
<rekado_>what tools?
<Apteryx>Well, say, that Emacs can jump from one sentence to another; there's some parsing involved which expects this format?
<rekado_>“M-x forward-sentence” looks at “. ” by default.
<rekado_>This can be changed, of course. (This is Emacs, after all.)
<rekado_>“parsing” in this case is just a regular expression.
<Apteryx>OK. No big deal. Is it "christened" in the GNU coding standards?
<Apteryx>I found the reference in (standards)5.2 Commenting Your Work: "Please put two spaces after the end of a sentence in your comments,
<Apteryx>so that the Emacs sentence commands will work.
<quiliro>hello
<quiliro>i had an error on grub but it booted anyway
<quiliro>why?
<rekado_>that depends on the error
<quiliro>mekeor[m]: my error is in the chat log approx at 0h17 utc'5
<quiliro>my error is in the chat log approx at 0h17 utc-5
<quiliro>/gnu/store/3c8fpdlbf3k22znhidn9gawjrw2wm1v0-bootloader-installer
<quiliro>activating system...
<quiliro>;;; WARNING: loading compiled file /gnu/store/nmjzgf4d6h27p1hmikin00mylcydk74c-module-import-compiled/gnu/build/activation.go failed:
<quiliro>;;; ERROR: In procedure load-thunk-from-memory: not an ELF file
<quiliro>;;; WARNING: loading compiled file /gnu/store/nmjzgf4d6h27p1hmikin00mylcydk74c-module-import-compiled/gnu/build/activation.go failed:
<quiliro>;;; ERROR: In procedure load-thunk-from-memory: not an ELF file
<quiliro>making '/gnu/store/4135grlwhxdk4hbvxl6rrzg4zkmgil3j-system' the current system...
<quiliro>Instalando para plataforma x86_64-efi.
<quiliro>/gnu/store/yxvmba7ig8gj1rxgirg90psacg93agrn-grub-efi-2.02/sbin/grub-install: error: no se pudo obtener la ruta canónica de «none».
<quiliro>guix system: error: failed to install bootloader /gnu/store/3c8fpdlbf3k22znhidn9gawjrw2wm1v0-bootloader-installer
<quiliro>
<quiliro>I flooded again...sorry
<quiliro>have to learn to avoid the enter key to add vertical spacing
<quiliro>anyway...those are the error lines in the output...there is a bunch of output before the x86_64-efi line and after the previous line
<quigonjinn>how can one change the root password inside a guixsd usb image, so that the machine is accessible for installation via ssh? passwd does not exist.
<quiliro>quigonjinn: yes...i need that too
<quiliro>that would be very handy
<quiliro>quigonjinn: perhaps making a new usb bootable image
<quiliro>the manual instructs how to do it... perhaps that would be a good contribution
<quiliro>without much knowledge
<quiliro>needed
<quigonjinn>well, some vps provider booted the 0.13.0 image for me, so it's not an option to make a new USB image.
<quigonjinn>it must be an omission of the 0.13.0 image anyway, the instructions exist in the manual.
<ng0>it was mentioned in the release notes or soon afterwards that passwd was missing nad has since then be readded
<ng0>sneek: later tell civodul: A check for shell support before I continue working on it: would you accept new introduced files especially for tcsh/csh and fish to get their environment variables from? Those are so far the 2 major shells which differ from the way zsh/*ksh*/bash sets them. In (guix search-path) I just need to add 2 variations which will then be used in (guix build profiles) to generate the
<sneek>Got it.
<ng0>etc/csh.profile and one other thing for fish i haven't looked into yet
<ng0>I think that message broke
<ng0>sneek: later tell civodul: etc/csh.profile and one other thing for fish i haven't looked into yet
<sneek>Will do.
<reed_>Hi all, I have a basic question. If I am updating my os config with "guix system reconfigure . . ." Should I run the command as root?
<cbaines>reed_, I believe so, I think you'll get a permissions error if you don't
<reed_>thanks! Same thing with guix pull?
<Apteryx>reed_: you don't need root for guix pull
<Apteryx>guix pull will update the guix copy for whatever user runs that command
<cbaines>Apteryx, reed_ saying that, I think if you're going to run guix system reconfigure ... as root, you'll also want to run guix pull as root for it to have any effect.
<reed_>That makes sense. I'll try that once my un-privileged pull command has finished
<quigonjinn>any workouround to 'guix pull'/build guix from source for machines with not enough RAM?
<cbaines>quigonjinn, how many cores has the machine got?
<mekeor>quigonjinn: you could try `guix pull -M 1` maybe
<mekeor>"-M" = "--max-jobs=N" = "allow at most N build jobs"
<cbaines>I don't think the --max-jobs/-M option will help, as I expect that guix pull uses one job, -c/--cores=1 might help though, as it might get guix pull to use only one core
<mekeor>or this option: "-c" = "--cores=N" = "allow the use of up to N CPU cores for the build"
<mekeor>:)
<quigonjinn>I alreadu used '-c1 -M1'. It has one core, but the problem is that RAM is only 500MB
<cbaines>quigonjinn, one crude workaround is giving the machine some more swap space?
<rmoe>that's what I have to do to run guixsd on my 512MB digital ocean VM, it takes about 1.5GB of swap for guix pull to complete
<cbaines>I think this issue has a coresponding bug report here https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27284
<Apteryx>this must take ages to build on swao though?
<Apteryx>*swap
<rmoe>takes around 3 hours
<Apteryx>surprinsingly OK
<rmoe>I just have a cron job that does it once a week at night
<quigonjinn>cbaines: thanks, didn't thought of that! I think it will work
<efraim>swapfile
<efraim>only 3 hours? It takes more like 7 on my aarch64 boards last I checked
<quiliro>quigonjinn: efraim's idea is good too
<quiliro>is it possible to have a precompiled version in order to avoid such long installation times?
<quiliro>is it necessary to always have to compile some things locally?
<quiliro>wouldn't reproducibility allow this reproduction of previously compiled packages unnecessary unless it was done for testing and verification purposes?
<quigonjinn>quiliro: i think it can't be avoided to compile guix right now, maybe i missed something though
<cbaines>I think there is room for improvement with guix pull, e.g. downloading rather than compiling, but I think the situation is a little complicated, at least I don't have a full understanding
<efraim>i believe the hope still is that it can be fixed in guile
<garlox[m]>Hi. Given that there is no Tor Browser package in guix yet and I am unable to make the Tor-Browser binary download work, what is the recommended way of browsing anonymously on GuixSD?
<buenouanq>gnunet :3
<cbaines>garlox[m], I'm not sure a recommendation has been made
<cbaines>there is a tor-service though, so you could possibly route traffic through that
<cbaines>you lose some advantages over the Tor Browser though
<garlox[m]>yeah, that's what I considered as well. Probably have to make sure to disable JS in order to prevent fingerprinting in Icecat
<ng0>I want an environment for development where I can build a release reliable. But when I use: guix environment --ad-hoc --container gnutls libidn bash gettext texinfo zlib autoconf automake libtool groff perl pkg-config python@2 sed coreutils make this environment gives me:
<ng0>./buildconf
<ng0>buildconf: autoconf version 2.69 (ok)
<ng0>buildconf: autom4te not found. Weird autoconf installation!
<ng0>am I doing it wrong?
<cbaines>isn't autom4te in autoconf, which would suggest it should be on the $PATH?
<ng0>I could just write another guix package definition to run what I want, but that's not the purpose here, I want to look more into the manual way with guix
<ng0>it should be
<ng0>one moment, entering again
<ng0>which autom4te
<ng0>/gnu/store/fhk1swzld81z40sypzq7ngg2gc568qcq-profile/bin/autom4te
<ng0>I added which
<ng0>my use of g environment was basic so far
<ng0>just used it for aliases
<ng0>like software I don't need so much
<efraim>ng0: autoconf-wrapper maybe?
<ng0>that's not a public package, right? guix environment: error: autoconf-wrapper: unknown package
<efraim>huh, I thought it was
<ng0>with just an --ad-hoc it works
<civodul>ng0: re shells and etc/profile, i'd rather stick to Bash and/or POSIX shells, but we can discuss :-)
<ng0>okay, I don't think irc is good for people like myself. I like to talk in long length to go into detail. What I don't propose is to change the default shell. Only better support for those that aren't supported that well atm, which I've written in some recent emails
<civodul>right, when i say "discuss", i say on the list
<civodul>er, i mean on the list
<ng0>oops^^
<ng0>ok :)
<civodul>:-)