IRC channel logs

2015-04-23.log

back to list of logs

<davexunit>I kill emacs with geiser sometimes
<davexunit>the result of a repl eval is a large bytevector? bye bye
<davexunit>or how about printing a massively large number: (expt (* 1920 1200) 2)
<davexunit>warning: don't do that in geiser
<paroneayea>mu4e's contacts system kills me
<paroneayea>I need to disable it and find something else
<paroneayea>it extracts about 58000 contacts from my email
<paroneayea>and then suddenly, there goes my emacs
<paroneayea>I wonder how it stores them.
<civodul>davexunit: right, in general very long lines kill emacs
<paroneayea>oh right
<civodul>it gets stuck in the regexp matcher, used by fontification
<paroneayea>davexunit: or structures that refer to other nested structures in their printed representation ;)
<paroneayea>remember that sly bug? :)
<civodul>and long lines can easily happen in geiser
<civodul>mark_weaver: i've justed added http://hydra.gnu.org/jobset/gnu/core-updates for the "core" subset, and as one-shot
<civodul>hope that'll be fine
<civodul>good night/day!
<davexunit>I wish emacs had a way to handle long lines gracefully
<davexunit>seems like a bug that shouldn't exist
<davexunit>in this 2015 world we live in
<nextstep>hello, i read somewhere wicd might be used as default net manager in guix?
<mark_weaver>yes
<mark_weaver>at least until we have network manager
<nextstep>i thought connman might be worth having a look into
<nextstep>no python deps
<nextstep>very simple and fast
<mark_weaver>sure, connman would be great
<mark_weaver>someone has been working on it, on and off, for months. still waiting...
<nextstep>oh ok
<mark_weaver>I love how https://www.openhub.net/p/gnuguix estimates that Guix represents 28 years of effort, starting with its first commit in April 2012 :)
<mark_weaver>I guess we work very efficiently, or something :)
<iyzsong>yeah, look at homebrew(30 years) and nixpkgs(107 years), I agree we are not bad at all.
<mark_weaver>107 years! wow :)
<mark_weaver>I guess the COCOMO model needs an update
*mark_weaver awaits the gcc-5.1.0 guix package build before pushing...
<civodul>Hello Guix!
<rekado_>Hi civodul!
<rekado_>May I push this fix: http://lists.gnu.org/archive/html/guix-devel/2015-04/msg00416.html ?
<civodul>rekado_: yes, definitely!
<civodul>sorry for the lag on messages
<rekado_>no problem. I'm amazed at your usual speed and thoroughness in reviewing posts to the ML!
<rekado_>no apologies needed.
<boegel>bavier: around yet?
<rekado_>I have users who want to use samtools version 1.1 and samtools version 0.1.18; both packages produce /bin/samtools, so there's a conflict and one cannot have both installed at the same time.
<rekado_>what is the recommended approach here to easily switch between two versions?
<davexunit>rekado_: make another profile or use 'guix environment' as needed
<rekado_>switching profile generations seems a little too heavy, especially since it may change availability of other packages.
<rekado_>so, instead of installing the second version into the same profile I'd use "-p"?
<davexunit>yeah
<rekado_>ok, let me try this...
<rekado_>This works pretty well, actually. Nice.
<rekado_>It's a bit ugly that the profile directory gets a "-1-link" suffix, though.
<davexunit>yeah I'm not sure what's up with that
<davexunit>I only use a single profile
<davexunit>and 'guix environment' for all dev stuff
<rekado_>oh, I know....
<rekado_>it's placing links to generations in the parent directory.
<rekado_>so for a profile "~/my-workflow" it generates "~/my-workflow" and for each generation a "~/my-workflow-1-link", "-2-link" etc.
<rekado_>guess I just need yet another layer of directories here.
<civodul>rekado_: yes, generations are saved this way
<rekado_>I find it a little sad how verbose I have to be to create a variant of a package that has a different version number.
<rekado_>since the hash must be updated and it is nested in (source (origin (sha256 (base32 ...)))) I also need to override the (uri ...) field, even though it has not changed at all.
<rekado_>I would like something like lenses here.
<bavier>rekado_: you can use 'inherit' for origins too
<rekado_>Oh, I did not know that.
<bavier>(package (inherit foo) (source (origin (inherit (package-source foo)) ...)))
<davexunit>any data type defined with define-record-type* supports 'inherit'
<rekado_>that's great!
<rekado_>thanks, I'll play with this.
<bavier>still a bit verbose, but better
<davexunit>you could also write a procedure that takes a package, version, and base32 hash and returns a new package
<rekado_>yes, that's what I would have done otherwise.
<davexunit>(package-with-version foo "1.2.3" "foo..")
<davexunit>short and sweet
<davexunit>take advantage of the power Scheme gives you!
<rekado_>I'm just thinking ahead for a time when our users will get access to the guix-builder server to manage their own profiles. Want to anticipate common problems they might encounter.
<rekado_>davexunit: have you decided yet where to host guix-web when gitorious disappears?
<davexunit>rekado_: https://git.dthompson.us/
<davexunit>not there yet
<rekado_>nice
<davexunit>but will be
<davexunit>I'm using a self-signed cert, btw
<davexunit>because I'm not wasting my money on a cert
<davexunit>patiently waiting for "let's encrypt" to launch ;)
<rekado_>I do the same (when I use certs).
<davexunit>ah okay
<davexunit>just figured I'd mention it.
<davexunit>some people freak out when their browser gives them the scary warning page
<rekado_>(I think this mess of warnings is counterproductive)
<davexunit>the whole centralized authority thing isn't great when you have to spend a bunch of money to get a trusted certificate
<paroneayea>pay to play
<paroneayea>security edition
<davexunit>haha
<taylanub>uhh, my Qt bug report has been closed because 5.5 fixes it, but that's not released yet. perhaps I can inquire them on what commit fixes it so we can include a patch; otherwise our Qt 5.4 will probably remain broken until Qt 5.5 is released.
<davexunit>taylanub: they should really document with patch fixes the issue in their tickets
<davexunit>that's some sloppy bug tracking
<civodul>how does it sound to put elogind in freedesktop.scm?
<civodul>well, slightly ironic i guess, but otherwise ok?
<bavier>latest comment at https://github.com/rurban/Set-Object/pull/4 looks good
<civodul>bavier: indeed!
<davexunit> http://www.vitavonni.de/blog/201503/2015031201-the-sad-state-of-sysadmin-in-the-age-of-containers.html
<davexunit>this blog post has caused quite the stir the past couple of days
<davexunit>the prevalence of 'curl | sudo bash' installation, downloading a bunch of unsigned binaries that no one knows how to build from source, etc.
<bavier>nice article
<civodul>indeed, all this is so true
<civodul>the dockerhub and all that
<civodul>bah
<davexunit>the world needs guix now more than ever! :)
<civodul>:-)
<civodul>at work there's also a tendency to paper over slow distros by adding rules in the build system to download and build dependencies
<civodul>like python setuptools et al do
<davexunit>stuff like that is the norm these days, it seems
***Gonbe is now known as _`_
<paroneayea>it will be interesting if we have something like "guix bisect" ;)
*paroneayea hitting an issue where *some* dependency upgrade on his debian machine is making wsgi act insane, but knows not what