IRC channel logs


back to list of logs

<kori>I still haven't quite understood how I make a hosts file
<kori>I know(?) it's a G-expr
<kori>but can i just like
<kori>(hosts `(blah blah blah))
<adfeno>Hm… Now my Minetest-for-testing is immediatelly giving me segmentation fault (don't worry, I'ts not the one I have installed).
<nckx>That's how you gexp a string into a file.
<xavierm02>Any idea on how long installing the full texlive should take?
<xavierm02>mbakke: guix import debian might not be worth it. But it's on the way to "guix install debian-<somepackage>" which installs the package in some kind of chroot. Advantages being that you can get stuff that aren't in Guix, while keeping what I consider to be the main advantage: rollbacks.
<adfeno>Hm… Running Minetest-with-debug-symbols like so gdb -iex "set auto-load safe-path /" "../bin/minetest" "core" to inspect the core dumped, tells me "couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error"
<kori>nckx: nice
<kori>i contest this specific type usage for hosts-file
<kori>could be just a string or a list of strings maybe
<nckx>You contest?
<nckx>kori: But… why?
<nckx>It's a file, it should take a file-like object.
<nckx>So I contest your contestation 😛
<ryanprior>xavierm02: my understanding is texlive is a big install and should complete in the order of hours.
<nckx>xavierm02 ryanprior: It is also almost entirely I/O bound, which is why it used to(?) be blacklisted on Hydra: downloading and unpacking the substitute took about as long as downloading and unpacking the actual sources.
<ryanprior>fwiw I support any kind of interop with Debian, it's a big accessibility win for GuixSD users since there's so much documentation for installing software on Debian.
<xavierm02>texlive installed! And LyX is working properly with just texlive and freefont added. (I got tired of adding texlive packages one by one and recompiling LyX every time)
<xavierm02>I couldn't find a way to say "If this package is installed, then add it to the run-time dependencies of that other package". Is there a way to do that?
<kori>nckx: everything is a file and every file is a bunch of strings so if you think about it everything is a string!
<nckx>kori: That's as good an argument against your point than for it.
<kori>yes it is
<nckx>Turning a string into a file-type object is trivial: (plain-file "name" "contents"). So is 'interning' a file you already have: (local-file "name"). You lose that flexibility and (loose) 'typing' if you settle for strings.
***amiloradovsky1 is now known as amiloradovsky
<minall>Hello guix!, I'm having some problems with a recent guix installation
<minall>I'm getting these messages: WARNING: loading compiled file /gnu/store/kz34yyckqy714p5hmrrvfj1lfq80qvl9-guix-1.0.1/lib/guile/2.2/site-ccache/gnu/packages/samba.go failed: ---- and ;;; In procedure load-thunk-from-memory: segment beyond end of byte array
<minall>;;; WARNING: loading compiled file /run/current-system/profile/lib/guile/2.2/site-ccache/gnu/packages/samba.go failed:
<minall>;;; In procedure load-thunk-from-memory: segment beyond end of byte array
<minall>--- I'm at a loss, I don't know what they mean
<[rg]>hello, guix seems interesting, I am wondering if it can be used to maintain a set of packages on an external drive
<quiliro>[rg]: good
<quiliro>[rg]: it may
<quiliro>[rg]: check channels in the manual
<[rg]>"The channel called guix specifies where Guix itself—its command-line tools as well as its package collection—should be downloaded"
<[rg]>by maintain I mean, install and update on an external drive
<[rg]>not handle my own repositories for guix to install from
<efraim>rg check out 'guix archive' for transfering package bits between computers using the external HDD, or 'guix pack' for keeping binaries on an external HDD. Might be what you're looking for
<quiliro>[rg]: if you want your system to be on an external drive, you just specify it on your configuration file on command line installation or on graphical installation you choose that disk
<[rg]>quiliro: I was thinking of using the standalone package manager
<quiliro>on aforeign distro
<quiliro>so you just can mount your external drive on the /gnu/store directory
<quiliro>does that do the trick?
<[rg]>yes tell me more
<quiliro>then all files will be on that drive but referenced by each user from their own home directory profiles
<quiliro>.guix_profile will point to /gnu/store/.... and .guix_profile is on each user's home
<[rg]>ok so I install standalone, the just mount on /gnu/store, but want if I forget to mount, how would i keep the drive in sync?
<quiliro>but if you put /gnu/store on another partition (external) it wont mind
<quiliro>you should mount on boot i guess
<quiliro>did not think about it
<[rg]>ok, thank you
<quiliro>perhaps if you make it mount on /gnu ... it will create store on your external partition
<quiliro>then, it will give an error if it is not mounted
<[rg]>ah wait
<quiliro>so you will then mount it
<[rg]>then with this method I am required to have guix on my host right? if I move the drive
<quiliro>i guess you must test it
<quiliro>i don't understand
<quiliro>of course...i don't understand why you ask
<quiliro>unless you do not want to touch the external hard drive
<quiliro>because that will cause an inconsistency
<[rg]>I know its an odd question, but I am wondering since this fits my usecase, since /gnu/store is not something I can simply put in my $PATH becuase of user profiles
<quiliro>i do not think it would even work if you use it on different installations of guix
<quiliro>what is the objective?
<quiliro>then i might be better able to help
<quiliro>if we know what you want in the end, it is easier to give a good answer
<[rg]>I wanted to have a bunch of software on a drive, that I can just add to my path and move from system to system
<[rg]>so I thought guix might be usefull here
<quiliro>i would better use guix pack for that
<quiliro>but i have not used it before
<quiliro>it is something like an executable with all dependencies....but you must install it on every machine
<quiliro>maybe it is better to post your question on help-guix mailing list...there you can get more people to contribute their ideas
<quiliro>please investigate guix pack in order to check if it suit you
<quiliro>then post
<[rg]>ok, thanks
<quiliro>check guix pack in the manual
<quiliro>ĝis revido!
<raghavgururajan>Hello Guix!
<raghavgururajan>sneek help
<raghavgururajan>Is sneek's primary nick sneek or sneek_ ???
<roptat>hi guix!
<roptat>raghavgururajan, sneek is the primary name, but it's not connected
<roptat>sneek_, botsnack
<roptat>sneek_, tell raghavgururajan hi
<sneek_>raghavgururajan, roptat says: hi
<roptat>sneek_, later tell raghavgururajan hi :)
<quiliro>saluton Guix
<notnotdan>Is there a way in Guix to start a build process of some package, and then drop down to a shell if it goes wrong?
<notnotdan>on a slightly unrelated note, why is cmake always trying to use programs in /usr/bin?
<notnotdan>oh wait, it might be to do with the stupid cmake cache
<quiliro>efraim: was just reading your blog post...
<pkill9>notnotdan: you can run the build with "-K" to keep the build directory if it fails, and then you can go into the build directory and source "environment" from the root of it to get all it's environment variables
<pkill9>it would be great to be able to just drop into a shell though
<notnotdan>I have a .so file in my profile from the `mesa` pacakge. How do I know why is it there, i.e. which package that I've installed depends on it? `guix graph` lists all the dependants
<notnotdan>pkill9: thanks!
<nckx>Something like --on-error=repl would be awesome.
<minall>Hello guix!
<minall>I'm getting an error on a recent guixSD install, compiled file samba.go failed!
<minall>Never got that error before, what should I do?
***Piece_Maker is now known as Acou_Bass
<quiliro>minall: What is your error?
<quiliro>Kio estas vi eraro?
<minall>WARNING: loading compiled file /gnu/store/kz34yyckqy714p5hmrrvfq80qv19-guix-1.0.1/lib/guile/2.2/site-ccache/gnu/packages/samba.go failed:
<quiliro>no context
<quiliro>why don't you guix pull
<minall>In procedure load-thunk-from-memory: segment beyond end of byte array
<minall>That appears every time I try to do any command with guix package, and also on guix pull
<minall>And guix pull-ing right now
<minall>That's the error, it appears two time
<quiliro> is the context...but I do not understand it
<nckx>samba.scm hasn't changed in any way that could cause weird errors like this.
<quiliro>Maybe a warning is not a important, just a notification...not sure
<nckx>Yeah, I think so.
<quiliro>minall: what did you change?
<minall>Welp, I don't have problems though, I'm using my sistem normaly
<nckx>minall: Could you submit a bug report to with the full output (or as much as copyable) attached?
<quiliro>any non standard config.scm or package modifications
<minall>quiliro: Nothing, as I said before, this is a new guix installation... the only thing I can say I did using guix commands, is installing several packages at the same time. but one can do that on guix, right?
<minall>Nope, the config.scm is the same as the installer build
*nckx .oO Isn't every system .scm 'non-standard'? 🙂
<quiliro>nckx: true!
<quiliro>default is the better word
<nckx>minall: If you're installing multiple packages to the same profile at the same time one of them can 'win' (so only one ends up in the profile) but Guix is certainly designed never to crash or fail in such cases.
<minall>Mhh maybe should I garbage collect?
<quiliro>minall: test it on another (clean) user to see if you have the same problem
<nckx>minall: I suspect it won't help but it can't hurt either.
<minall>I'll check with root
<quiliro>minall: garbage collect affects only nonusable files
*nckx was talking about gc'ing above.
<quiliro>those packages that are not referenced by the user
<quiliro>but it is a good idea to contribute by adding a bug on the mailing list
<quiliro>first you must check if there is another bug with same problem
<quiliro>in order to post on that same thread
<quiliro>minall: si ya hay un reporte de error, es mejor continuar con ese reporte que generar otro
<quiliro>.vidita quiliro
<quiliro>sneek_: help
<quiliro>sneek_: help botsnack
<quiliro>apropos guix
<quiliro>sneek_: apropos guix
<nckx>quiliro: /msg sneek_ help works.
<nckx>Maybe it's a feature to avoid spamming the channel with help output, maybe it's one of sneek's many bugs
<nckx>err, 'personality quirks', of course.
<quiliro>nckx: who adds responses to sneek_ ?
<nckx>sneek_: seen quiliro?
<sneek_>quiliro was here Jul 28 at 02:15 pm UTC, saying: nckx: who adds responses to sneek_ ?.
<quiliro>seen is not on sneek_'s help
<nckx>quiliro: dsmith of #guile, but I don't know if it's actively maintained.
<nckx>(quiliro: I know, I cheated by seeing dsmith use it.)
<nckx>quiliro: Where'd you get '.vidita' from?
<minall>Hello guix!
<minall>My pc creashed, I had a lot of process on t
<minall>But I tried doing a guix pull on root, and got the same error
<nckx>minall: My sympathies. Many processes or not, that shouldn't have happened.
<nckx>minall: Well, just copy the full output from your terminal and submit a bug.
<nckx>I think Ludo' just left on holiday but with a bit of luck someone else might be able to help you.
<minall>nckx: Welp, I just was installing a package, while doing a guix pull, guile doing another guix pull on root, but it crashed.
<minall>While seeing a video lol
<minall>I'll submit the bug then
*nckx is kind of sad about the pervasive 'computers crashing because you're running several things at once is normal and not an unacceptable bug' attitude but that's a different battle.
<nckx>minall: Thanks!
<OriansJ>nckx: well guile doesn't handle low memory conditions well and many scheme programmers don't take the time to recognize the memory footprints of the programs they make
<nckx>OriansJ: I'm as guilty of that as anyone, I'm sure. I just wish the culture weren't quite as complacent.
<OriansJ>nckx: pain is usually the only way cultures change and usually lots of it is required for a cultural change
*nckx tries to be the pain they want to see in the world.
<minall>What is the difference between vesa and fbdev?
<Marlin[m]>vesa is a generic graphics driver for xorg
<Marlin[m]>fbdev is for framebuffer usage
<Marlin[m]>like displaying images in a tty
<quiliro>nckx: .vidita is a command of a bot that is on ##esperanto
<nckx>I thought as much 😃
<quiliro>vidita (eo) = seen (en) =visto (es)
<quiliro>nckx: Mi vidas ke vi estas Esperantisto!
<nckx>Marlin[m]: fbdev is also an Xorg driver, and the kernel Linux can use VESA modes to drive a TTY (I think…) It's more that fbdev is a more generic framebuffer driver than just VESA. I'm not familiar with the implementations.
<nckx>quiliro: Meh, eble esperantisto amatora. Mi nun koncentriĝas al praktiki mia 中文.
<quiliro>japani ĉu?o
<quiliro>japanio ĉu?
<nckx>quiliro: Ĉina lingvo.
<nckx>Ah, the fbdev driver can use vesa-driver devices through the vesafb compatibility driver, but not the other way 'round.
<nckx>This is all pretty obsolete stuff though…
<nckx>It's probably used more by the Xvfb in several Guix test suites than in the wild nowadays 🙂
<quiliro>nckx: kiam vi montras 🙂 , mi vidas kvadraton kun numeroj 01F 642 ...kial?
<nckx>quiliro: Tio estas ':-)' Unicode-a.
<quiliro>nckx: mi havas la Unicode-an
<nckx>quiliro: Vi ne havas la font-on bezonata.
<quiliro>nckx: kiu tiparon?
<nckx>quiliro: Ĉu ☹ funkcias?
<quiliro>nckx: jes!
<nckx>quiliro: 🙂 estas 'emoji', ☹ ne estas tio.
<quiliro>ĉu do?
<quiliro>mi devas instali emoji-an tiparon ĉu?
<nckx>quiliro: Mi uzas 'font-google-noto', ni antaŭe parolis pri ĝi.
<nckx>quiliro: Jes.
<quiliro>mi havas tiun tiparon
<quiliro>nckx: mi uzas guix-an sistemon
<quiliro>font-google-noto 20171025
<nckx>quiliro: Ĉu vi uzas emacs-on?
<quiliro>nckx: jes
<quiliro>ĉu vi ne?
<nckx>Ah. Ĝi estas problemo de emacs-o.
<nckx>quiliro: Ne por IRC.
<nckx>Mi uzas Guix-an Sistemon ankaŭ.
<nckx>Sed Hexchat-on.
<nckx>Mi kredas, ni antaŭe parolis pri ĝi.
<nckx> kaj tiel plu 🙂
<quiliro>jes ni parolis pri ĝi...sed ne funkciis tiam kaj ne funkcias nun
<quiliro>nckx: Ĝi ne estas problemo de Emacs-o...Mi havas la problemon en Icecat-o ankaŭ
<quiliro> havas nenion
<nckx>quiliro: Nenio de kio?
<quiliro>ĝi havas otuso nur
<quiliro>mi serĉis la solvon kiu li havas de la problemo
<quiliro>sed mi ne trovas tion
<quiliro>bone...bone...sed bonvolu ne ekkrias
<nckx>quiliro: 'otuso' = ?
<quiliro>ostuso = buho (es) = owl (en)
<quiliro>ostuso (eo) = buho (es) = owl (en)
<nckx>Ah, mi trovis strigon kaj gufon.
<nckx>Ne otuson.
<nckx>quiliro: Ĉu montras ion ajn?
<nckx>Mi ne havas Guix-an IceCat-on nun…
<nckx>(Ubuntu → SSH → Guix System.)
<nckx>Mi ne volas X11-forwarding-on.
<nckx>(…pardonu min, esperanto…)
<quiliro>Ĉu nckx: vi havas xorg-servilon en Ubuntu-o, sed uzas Guix-an Sistemon en alia maŝino?
<quiliro>nckx: Ĉu vi havas xorg-servilon en Ubuntu-o, sed uzas Guix-an Sistemon en alia maŝino?
<nckx>Mi provos IceCaton morgaŭ.
<quiliro>nckx: dankon!
<nckx>Memorigi min se mi forgesos.
<nckx>Vi havas permeson.
<nckx>quiliro: Vi uzas esperanta IceCaton?
*nckx AFK.
<quiliro>nckx: jes
<minall>Maybe I'm using guix download wrongly? I'm trying to download on package to see its source code, and I'm unable to
<minall>using -guix download xf86-video-openchrome-
<adfeno>It turns out that debugging Minetest from Guix with GDB from Guix is somewhat also challenging, as a Minetest built using `guix environment minetest' immediatelly segfaults in the begining, and GDB complains that libthread-db used in debugging differs somehow.
<nckx>minall: guix build --source xf86-video-openchrome
<nckx>minall: guix download is for URLs.
<minall>Ohh! I see
<minall>thanks you
<nckx>quiliro: Kiel?
<minall>So what's the difference between guix download and guix build? guix download doesn't work with guix packages?
<nckx>quiliro: intl.locale.requested?
<nckx>minall: guix download is for downloading files from URLs, any URL.
<nckx>It can be used as a basic replacement for curl/wget in a pinch, it doesn't care about the contents at all (it just downloads & hashes).
<minall>Thanks you nckx
<nckx>guix build builds a derivation, so it knows about packages, and package sources are themselves derivations, so you can 'build' them.
<nckx>minall: So you could look a the package expression for xf86-video-openchrome, substitute things like 'version' IN YOUR MIND, and 'guix download $THAT_URL' just fine. But it's a) more work and b) (and most importantly) 'guix build --source' applies any patches and snippets from the package expression.
<minall>I see!
<nckx>quiliro: I've packaged all the langpacks but can't convince IceCat to respect $LANG.
<quiliro>nckx: LANG=es ; icecat
<nckx>What the.
<nckx>I tried that approximately six zillion times with no success.
*nckx sighs, makes a not to try again.
<nckx>*note, even.
<quiliro>Ĉu vi faras tiun?
<quiliro>Ĉu aŭ: LANG=fr ; icecat
<minall>Is there any difference in xorg, about using Vesa driver or using the fbdev driver? in performance perhaps?
<nckx>quiliro: Mi provis. Eble mi devos ŝanĝi intl.locale.matchOS.
<quiliro>the best is to use the appropriate driver, not fbdev or vesa
<roptat>quiliro, (icecat:5504): Gtk-WARNING **: 19:30:39.125: Locale not supported by C library. Using the fallback 'C' locale.
<nckx>minall: Performance should be equally atrocious on both.
<roptat>my icecat is also in English
<roptat>even though the rest of my computer is in French
<roptat>I don't know how to install a langpack
<nckx>Same. Kind of sad how I have the locale of my 'entire system' set to zh_CN but it doesn't really matter one bit since IceCat & emacs, the two things I actually use all day, don't respect that.
<nckx>Install like any add-on.
<minall>How do I extract a .tar.bz2 archive?
<nckx>Now, I'd like that to not be necessary and kept in sync automatically (like every single other package locale).
<nckx>minall: tar xf $FILE
<nckx>I.e. exactly as you would extract a tar.gz.
<nckx>Tar sniffs the compression type automatically.
<nckx><Now, I'd like> But until I can make (my?) IceCat respect $LANG there's little point in submitting that upstream.
<gnutec>If GNU Guix tould you to use lzip, you should use it.
<nckx>gnutec: ?
<nckx>Whether or not lzip is preferable to xz is debatable, but it's not relevant to the question of how to extract a bzip2 tarbal…
<roptat>ok, I have a java parser (for top-level definitions) and I'm using it to generate plugin.xml files for maven plugins. I'm getting closer to a working and bootstrapped maven-build-system :)
<nckx>roptat: That sounds impressive!
<roptat>took me a week :)
<roptat>now I actually need to test the plugin I built with that
<roptat>it's building, and the plugin.xml looks quite good, so I have some hope that I won't need too many adjustements
<nixo_>Hi, I'm trying to add support for julia packages. Things are going well and I'm writing an importer (in julia for now) to ease importing packages (since many packages have dozen of dependencies). how do I call guix download on a specific git commit?
<nckx>nixo_: I don't know if guix download can do that (it didn't used to). You can git clone a CLEAN checkout at that commit and run 'guix hash -rx' in it as described in the manual's 'Invoking ‘guix hash’' section, though.
<nckx>roptat: When in doubt, rewrite more of the world in Guile…
<nckx>nixo_: git checkout will work too, just make sure there are no untracked files or changes left over anywhere.
<raghavgururajan>sneek_ later ask mbakke Any improvements regarding core-updates-->master merging? Just following up :)
<sneek_>raghavgururajan, you have 1 message.
<sneek_>raghavgururajan, roptat says: hi :)
<sneek_>Got it.
<raghavgururajan>sneek_ botsnack
<raghavgururajan>roptat hi o/
<adfeno>Well, I reproduced a bug already found in Minetest (upstream) itself.
<raghavgururajan>nckx o/
<quiliro>saluton adfeno
<adfeno>Olá quiliro
<atw>roptat: that's awesome! Could you explain a little more about why you're parsing Java? I don't get that part
<roptat>atw, because the info I need is in the java files
<roptat>in the form of annotations
<atw>aha, thanks!
<nixo_>nckx: Yes thanks, I'm cloning the repo, doing a checkout and then guix hash -rx .
<niten>hey all
<niten>is there any way to add a new channel systemwide?
<niten>the channel proposal talks about "guix channel add", but that doesn't exist...the docs just talk about ~/.config/guix/channels.scm
<nckx>niten: There isn't a system-wide guix, so system-wide channels aren't really a defined term.
<sneek_>Welcome back nckx, you have 1 message.
<sneek_>nckx, raghavgururajan says: Test Message
<nixo_>Yess! I've a working implementation of julia-xyz.scm (installing julia packages). There are many things to fix but I got HTTP.jl working ^^ I'll submit a patch in the following days
<nckx>niten: By which I mean, you're welcome to define & refine it to serve as a concrete proposal that can be considered 🙂 As long as users can easily opt out of any & all system-wide channels it might make some sense.
<nckx>[I forgot to say] hullo raghavgururajan.
<raghavgururajan>nckx o/
<nckx>The beautiful sight of reconfiguring two different systems and seeing the exact same hashes printed never gets old.
<trzcdev>Hello, guix!
<sneek_>Welcome back trzcdev, you have 2 messages.
<sneek_>trzcdev, nckx says: 'guix environment hello' makes all inputs (=dependencies) of the hello package available in the environment. It does not make hello itself available: you get an environment for *building* hello.
<sneek_>trzcdev, nckx says: 'guix environment --ad-hoc hello' makes only hello available in the environment, not its inputs. 'guix environment hello --ad-hoc hello' does both.