IRC channel logs


back to list of logs

<yenda>then in check.scm the code is wrong? (it's cons-before configure)
<yenda>mark_weaver: this is what I get
<yenda>I'm trying to build util-cursor, which is one of i3 dependencies, which I'm trying to package
<mark_weaver>yenda: yes, in the 'cunit' package it's wrong. I'll fix that
<mark_weaver>yenda: can you show me the package definition that generated that output
<mark_weaver>yenda: is there a tarball release you could use instead?
<mark_weaver>my guess is that util-cursor is old and doesn't work with the latest autotools
<mark_weaver>and anyway, we generally prefer tarball releases over git checkouts
<yenda>mark_weaver: this is the release I picked (from march)
<mark_weaver>understood, but don't they distribute a tarball for that release somewhere? tarball releases usually already have built configure files ready to go, so no need to run autoreconf.
<mark_weaver>yenda: see
<mark_weaver>that announcement includes URLs for the tarball releases
<yenda>yes but they are borken
<mark_weaver>broken how?
<mark_weaver>also, I guess the name of the package should be 'xcb-util-cursor' and it should go in xorg.scm near the other xcb packages.
<yenda>broken like dead link, isn't it for you too ?
<mark_weaver>no, I just downloaded the .bz2 file and looked at the contents
<yenda>ok wget worked
<yenda>it just doesn't work with icecat
<mark_weaver>hmm, that's surprising.
<mark_weaver>I would try it myself, but I'm waiting until IceCat 38.x before I run it again.
<yenda>what do you use in the meantime ?
<mark_weaver>oh, nothing good, I'm unhappy in the meantime
<mark_weaver>I'm in the process of trying to update webkitgtk to the latest, so that I can run epiphany safely.
<mark_weaver>for now I'm using eww in emacs, although emacs-w3m is quite a bit more usable in practice.
<mark_weaver>I worry a lot about the security of modern web browsers. they are incredibly complex, their attack surface is enormous, and they are exposed to input from a huge variety of untrusted sources.
<mark_weaver>hence I've put a lot of effort into promptly patching icecat when fixes are released.
<mark_weaver>but mozilla is no longer providing fixes for version 31, so now we're stuck
<mark_weaver>but i raised the alarm on the gnuzilla ML, and was encouraged by the response from ruben.
<mark_weaver>he had been planning to add more features and polish before releasing it, but I think I've convinced him to expedite it and deal with the niceties later.
<mark_weaver>in the meantime, I'm working on updating webkitgtk to the latest release, which is the engine for epiphany.
<mark_weaver>unfortunately, it takes forever to build, and there was a problem deep into the build (multiple hours in)
<mark_weaver>and my first attempt to fix it failed (I'm clueless with cmake)
<mark_weaver>so now I'm trying to build the second attempt..
<mark_weaver>when it succeeds, then I'll be able to use epiphany
<yenda>wouldn't it be easier to keep a stripped down firefox uptodate rather than doing a fork like icecat ?
<mark_weaver>that's not as trivial as it sounds
<mark_weaver>we need to modify it because it has some problems, e.g. directing users to install non-free plugins, that makes it not comply with the GNU FSDG.
<mark_weaver>and we're not allowed to modify it at all without changing the entire branding, because of the firefox trademark rules.
<mark_weaver>and I think there are some other problems with upstream firefox as well.
<mark_weaver>so, for us there's no getting around the fact that we need a non-trivial fork.
<dmarinoj>What about iceweasel?
<mark_weaver>yeah, doing something based on iceweasel would be another option, but it also needs modifications because I think it also directs people to non-free plugins
<mark_weaver>but the other thing is that we want to prefer GNU projects in general, and IceCat has been fine for the most part.
<mark_weaver>this is an unusual situation, and hopefully it won't happen again.
<mark_weaver>I think ruben didn't realize that mozilla had stopped issuing security updates for version 31.
<yenda>well that plus the fact that the javascript engine doesn't get updated either
<yenda>how would you name this package ?
<yenda>perl-pod-simplr ?
<guixnewbie>Hi! I managed to install GuixSD, but borked(?) it soon after by doing a reconfigure -- it seems it tried to update the kernel but failed. I'm trying again from scratch.
<guixnewbie>Is there a guix tutorial of some kind online? Aside from the official docs?
<guixnewbie>Something a bit more lightweight. :)
<yenda>why would you retry from scratch ?
<yenda>can't you just rollback to previous working conf
<guixnewbie>Also: my /gnu/store ended up having >4000 entries after reconfiguring with stuff like xfce enabled. Is this normal?
<guixnewbie>yenda: I tried picking an earlier configuration from the boot menu, but the boot failed. I wasn't sure if the system was in a coherent state -- I might have messed something up.
<guixnewbie>yenda: You'll forgive me if I steal your config. :)
<mark_weaver>guixnewbie: simply reconfiguring shouldn't have messed up the earlier configurations
<mark_weaver>when you picked an earlier configuration from the grub menu, how did it fail?
<mark_weaver>this is one of our primary features: that you can fearlessly try updating/modifying things without fear, because you can always boot from an earlier working configuration, and so far that has never failed me.
<mark_weaver>but of course, if you do something like delete/modify items in /gnu/store, all bets are off.
<guixnewbie>mark_weaver: I don't remember the messages -- I just assumed I borked something by behaving inappropriately. After booting, they initial messages flew by and I was never given a login prompt.
<mark_weaver>guixnewbie: did you try hitting return? in practice there are many messages that come *after* the login prompt, thus obscuring it.
<guixnewbie>mark_weaver: Ah, I see. I'll try not to purge everything the next time I mess something up -- I didn't poke around /gnu/store. :)
<mark_weaver>(I actually avoid using tty1 at all, since that's where all the output from various daemons go)
<guixnewbie>mark_weaver: Yes, I assumed the login prompt was actually there (just not immediately visible). However that doesn't appear to be the case.
<mark_weaver>probably we should move all that output to another tty like tty6 or something
<guixnewbie>I didn't even try jumping to another tty -- probably that would have worked.
<yenda>guixnewbie: remove some stuff like the java package then or linux-nonfree depending on which one you take
<guixnewbie>yenda: Will do!
<guixnewbie>I have multiple systems I need accessible via the grub bootloader, but guixsd seems to overwrite all that. I have to specify them all manually in my config's grub-configuration section?
<mark_weaver>bah, new users starting with non-free software from the get-go, what a shame.
<guixnewbie>mark_weaver: Not sure if this idiom is translatable, but in English it would go something like "That train has long passed." :))
<mark_weaver>it translates fine
<mark_weaver>guixnewbie: however, I'm not quite sure what you mean by it in this context.
<mark_weaver>do you mean to suggest that we shouldn't try to run fully free systems? that we should accept that our computers are under the control of others?
<mark_weaver>the way we usually interpret such a phrase in english is "it's too late"
<guixnewbie>mark_weaver: Only that I've long had non-free software on my computer, so in a manner of speaking it's too late for me to be someone who's "starting" with all-free software.
<guixnewbie>mark_weaver: Only hopefully *ending* with free software. :)
<yenda>I'm looking for Xlib ?
<mark_weaver>yenda: libx11
<mark_weaver>guixnewbie: ah, okay, well I'm glad to hear that you strive toward that end :)
<yenda>mark_weaver: ty
<yenda>I'm done with the dependencies of i3
<yenda>but I get this
<yenda>"pkg-config was not found". Stop."
<yenda>but it is in my native-inputs
<mark_weaver>yenda: if 'pkg-config' is in native-inputs, then it will be in PATH. maybe the i3 build system is not looking in PATH, but rather expecting it to be a fixed place like /usr/bin. you'll have to investigate
<mark_weaver>oh, there's no configure phase at all, just a Makefile, eh?
<mark_weaver>in this case, you'll probably need to override some of those variables by adding #:make-flags to arguments..
<guixnewbie>If I have multiple systems I want available via the Grub bootloader (say, an additional Arch Linux), can I specify them via the config.scm file? Or would I have to manually invoke grub-install after each guix system reconfigure?
<guixnewbie>I don't see how to do that in the docs: So I'm thinking I have to run grub manually.
<mark_weaver>guixnewbie: you can add menu items to the grub configuration in the OS config
<guixnewbie>extra menu-entries? are there examples I can reference online? not sure what to put in.
<mark_weaver>see the 'menu-entries' field, and the 'menu-entry' objects described in section 6.2.12 of the guix manual.
<guixnewbie>my google-fu fails me.
<mark_weaver>sorry, I don't know of examples.
<guixnewbie>thanks anyway, I know what to look for now
<joshuasgrant>Besides logind, is/are there any known issuses for GNOME? I keep seeing more and more Gnome software being added to the repo, which is great, but I'm wondering what roadblocks are still there to besides it?
<joshuasgrant>ACTION backstepped from GuixSD back to Fedora for the time being, namely due to lack of GNOME, but wants to help work towards getting GNOME proper to work.
<mark_weaver>we're working on it as we have time and energy
<joshuasgrant>mark_weaver: Well yeah, I'm just asking if there is any known roadblocks besides logind regarding GNOME via GuixSD?
<mark_weaver>no roadblocks, just complications
<mark_weaver>I don't have time to explain now, sorry
<joshuasgrant>mark_weaver: Np.
<mark_weaver>but basically there's a lot of infrastructure behind the scenes that GNOME depends on, and we have to get all of that working right
<joshuasgrant>I mean ultimately it's something I somefactor of "know" will get done, I guess it's more-so a matter of when as you eluded to.
<yenda>^ mark_weaver
<yenda>ignore the previous message
<yenda>^ mark_weaver this is where my error is coming from
<yenda>(shell which pkg-config ... doesn't work apparently
<mark_weaver>yenda: 'which' is not included by default. if it's needed, then you need to add it to native-inputs.
<yenda>nice, it was the problem, now it uses an alias, cc instead of gcc
<mark_weaver>yenda: usually there's a Makefile variable CC that can be set to override that. if so, then #:make-flags '("CC=gcc") should work
<yenda>damn I replace 'configure and did ((setenv "CC" (which "gcc")))
<yenda>which one is cleaner ?
<mark_weaver>yenda: it's cleaner to set make-flags
<yenda>yes it looked like it
<mark_weaver>IMO anyway
<yenda>no I agree
<yenda>it makes more sense it is a make-flag
<mark_weaver>okay, good :)
<yenda>omg so vicious dependcies everywhere
<yenda>hopefully i3 is small I can't imaging having to wait 20 min before each failure
<yenda>is there a difference between libev and libevdev ?
<yenda>(I mean a difference that would cause a failure)
<mark_weaver>I don't know
<mark_weaver>I would do the same things you can do: try it and see, do web searches, etc
<mark_weaver><pkgname> is a good trick
<yenda>mark_weaver: it is really confusing
<yenda>we have a libevdev package in version 1.3 in xorg.scm
<mark_weaver>why is that confusin?
<yenda>because there is also libevent and libev
<mark_weaver>looking at gives me the impression that libev is something different, something we don't yet have.
<mark_weaver>a "
<yenda>and libevdev should depend on libev according to debian which explains why I miss ev.h
<mark_weaver>a "high-performance event loop library modelled after libevent"
<yenda>but there is a libevdev which depends on libev
<mark_weaver>yenda: no, you are confusing it with libev-dev
<yenda>right ! the "-"
<yenda>what a mess
<mark_weaver>in the debian world, libraries are typically broken up into a package with things needed at run-time (libev), and a development package with extra bits needed to compile new code against that library (e.g. header files, etc)
<mark_weaver>and those development packages have names that end with "-dev"
<yenda>yeah and libevdev dev stands for devices not development
<yenda>I'm getting closer
<yenda>mark_weaver: install: cannot create directory ‘/usr’: Permission denied
<mark_weaver>yenda: you need to find the Makefile variable that is set to /usr and override it.
<mark_weaver>e.g. if the variable is called PREFIX, then do this: #:make-flags (list "CC=gcc" (string-append "PREFIX=" %output))
<mark_weaver>(for packages with a 'configure' script, this is handled automatically because gnu-build-system passes --prefix=... to configure)
<yenda>ok I'm going to check that, I was going for bruteforce and grep the files containing /usr/bin to replace it by output
<yenda>oh boy it succeeded :)
<yenda>now if I put it in my config file and reconfigure instead of xfce I should have i3
<mark_weaver>the easy thing is to create an executable shell script ~/.xsession that has a shebang at the top and does "exec i3" or whatever, possibly with some other commands before it.
<mark_weaver>there's a way to add it more properly so that it will automatically be an option from the display manager (slim), but I don't know off hand how that works.
<mark_weaver>iyzsong would know
<yenda>sneek: later tell iyzsong how do you add new package manager to slim ?
<sneek>Will do.
<yenda>package manager :D time to go to bed
<yenda>sneel: later tell iyzsong I meant window manager ofc
<iyzsong>yenda: doesn't the i3 package contains its desktop file as $out/share/applications/i3.desktop? then add it to the 'packages' field is enough ;-)
<sneek>iyzsong, you have 1 message.
<sneek>iyzsong, yenda says: how do you add new package manager to slim ?
<iyzsong>yenda: oh, sorry, it should be $out/share/xsessions/i3.desktop
<yenda>nice !
<yenda>I'll see tomorrow then, reconfigure decided to recompile the kernel for some reason
<iyzsong>yeah, have a good night!
<yenda>you too
<yenda>what license is it suppose to be when it says "This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.", there is no license in the repo
<iyzsong>maybe '(license (package-license perl))'?
<iyzsong>yenda: look perl.scm, so it's the way.
<mark_weaver>iyzsong: thank you for epiphany! you are my hero :)
<mark_weaver>I just pushed an update to webkitgtk to the latest version. with this, we now have an up-to-date modern browser :)
<yenda>so much wierd licenses
<yenda> this one is a mix of bsd and gpl
<yenda>i'll just put bsd-style
<mark_weaver>yenda: bsd-style is deprecated, because it's a confusing term, and in the FSF list of "words to avoid".
<mark_weaver>please use 'non-copyleft' instead
<iyzsong>mark_weaver: well, epiphany doesn't work with HTTPS now, I passed certs path (/etc/ssl/...) to glib-networking, but then testing failed :-(
<mark_weaver>iyzsong: oh, interesting. hmm.
<mark_weaver>well, we can fix that later. it's still a great step to have this :)
<mark_weaver>iyzsong: maybe tests failed because /etc/ssl isn't in the build environment?
<yenda>and what is this ^ MIT + non advertising clause
<yenda>License I fascinating, I bet most of the time they are picked up quite randomly by the author and yet the implications can be totaly different depending on the license he choose
<mark_weaver>MIT license is also ambiguous, since there are many licenses used by MIT, and two very popular ones: expat and x11
<yenda>but those don't have this clause
<yenda>"Except as contained in this notice, the names of the authors or their
<yenda>institutions shall not be used in advertising or otherwise to promote the
<yenda>sale, use or other dealings in this Software without prior written
<yenda>authorization from the authors."
<mark_weaver>yeah, so you'll have to use 'non-copyleft'.
<mark_weaver>search for it in gnu/packages/*.scm for examples
<mark_weaver>it's a procedure that returns a license object; you need to add arguments.
<mark_weaver>oooh, wesnoth too! I love that game :)
<yenda>ok thanks for the help, I'll post all the packages soon, but my mail client is still broken, I'm not use to gnus yet
<mark_weaver>yenda: okay, sleep well!
<mark_weaver>iyzsong: since epiphany uses nss, I would expect it to use its own internal CA trust store
<mark_weaver>although I guess I don't know how that works.
<iyzsong>mark_weaver: you're right about the testing, I'm going to disable the failed ones.
<mark_weaver>since icecat might have known security flaws right now, it would be great to have another browser to recommend in the meantime.
<mark_weaver>so it's great timing for epiphany to be added :)
<iyzsong>agree :-)
<mark_weaver>iyzsong: the glib-networking update broke the libsoup test suite, which led to 40 newly failed jobs.
<mark_weaver>iyzsong: can you look into it?
<mark_weaver>(if I don't hear back soon I'll revert that change for now)
<iyzsong>mark_weaver: oops, it seem that I have to disable tests for libsoup :-(
<mark_weaver>other things might fail as well
<iyzsong>libsoup's tests log say the same thing as glib-networking, missing ca-certificates.crt.
<mark_weaver>it's possible that several other packages might fail for the same reason
<mark_weaver>it might be best to revert the glib-networking change on master and instead try things on another branch. wdyt?
<mark_weaver>also, I wonder if it's possible to set the CA store location via an environment variable instead of hard-coding it.
<mark_weaver>that would be preferable anyway, and better yet: it would allow us to set that variable during builds to something in /gnu/store
<iyzsong>sure, but as far as I know, it only used at runtime. (only tests may fail).
<iyzsong>yes, use env will be better.
<mark_weaver>then we could add nss-certs (or maybe something else) as an input to such builds, and then set the environment variable accordingly.
<mark_weaver>iyzsong: so, how would you feel about reverting this change on master and then trying things out on another branch?
<mark_weaver>I could create a jobset on hydra for it
<iyzsong>mark_weaver: agree. thanks!
<DusXMT>I remember writing a program which used libsoup; to use an env. var, I had to load the certificate bundle with g_tls_file_database_new and then pass that as the "tls-database" property of the soup session
<DusXMT>I didn't find an automatic way
<DusXMT>for the certificates, that is, to use an env. variable
<mark_weaver>iyzsong: okay, can you revert it now please?
<mark_weaver>or should I?
<DusXMT>Perhaps we could patch soup_{a}sync_session_new () to automatically do that?
<iyzsong>ok, reverted.
<mark_weaver>iyzsong: thank you! and what should we call the wip branch?
<mark_weaver>DusXMT: since glib-networking is the thing that wants to know where the certificate store is, I would think that's the thing to patch to look for an environment variable instead (if we decide to do that), no?
<iyzsong>mark_weaver: how about 'wip-glib-networking-tls-ca-file'? or a short one..
<mark_weaver>how about just 'wip-glib-networking-tls' ?
<DusXMT>mark_weaver: indeed, that would probably be a better option in the long run
<iyzsong>yeah, found a patch for it:
<rekado->I wonder if now would be a good time for an update to fontconfig from 2.11.92 to 2.11.94, fixing ghostscript conversion from ps to pdf.
<mark_weaver>iyzsong: looks good, but I think we should call the environment variable SSL_CERT_FILE, since that's what we already have set and it's what openssl looks for as well.
<mark_weaver>rekado-: hmm, that will be a massive rebuild
<iyzsong>mark_weaver: sure. the next step is build the crt file into nss-certs? since we only build it into profile now.
<mark_weaver>iyzsong: actually, it would be better to not add nss as a dependency for all of these packages
<mark_weaver>I wonder if instead we could have a little dummy package for this purpose that just has a few test certs in it.
<mark_weaver>I wonder how many, and which ones, are needed to make the tests pass?
<rekado->mark_weaver: in core-updates maybe, targeting the next release?
<iyzsong>I hope to update fontconfig too :-)
<mark_weaver>rekado-: sounds good to me! I have a bunch of other updates queued up for core-updates as well, we should probably start that soon.
<mark_weaver>rekado-, iyzsong: I could get the core-updates changes I want committed this weekend, and then we could start hydra building it early next week. what do you think?
<mark_weaver>anyway, I need to sleep now...
<mark_weaver>happy hacking!
<iyzsong>mark_weaver: that's cool. good night!
<mark_weaver>ACTION --> zzz
<alezost>WESNOTH!!! Ave iyzsong!
<iyzsong>ACTION like wesnoth all the time, expect when his soldiers dies (which happend frequently :-()
<yenda>what about wesnoth ? someone added it to the packages ,
<taylanub>yenda: yup, iyzsong added a wesnoth package
<remi`bd>I need to generate, for some given store items, their corresponding nar archives
<remi`bd>I understand (guix serialize) is made for the job, but my question is: where should I place these archives?
<remi`bd>in the store? in `/root/.cache/guix/'?
<yenda>I'm so close to have i3 fully working on guix, I can't wait, xfce is driving me nuts, too much mouse
<taylanub>random musing: the other day I did a "graphical install" of Debian 8.1 for my mother's new laptop, choosing GNOME as the DE. I was amazed by how well everything works out of the box and has a *really* modern look. I figure we're not that far in Guix yet, but it's definitely something to look forward to.
<yenda>taylanub: try again with linux-libre kernel
<yenda>and without the non-free repo
<amz3>taylanub: have you tried it's nice little note taking application
<amz3>it blends nicely with GNOME
<amz3>well it's gnome app ^^
<yenda>I'm a bigger fan of this for the simple user
<rekado_>yenda: I used GNOME with Fedora and linux-libre and I still don't find anything wrong with what taylanub noted.
<rekado_>if your hardware requires non-free software that's unfortunate, but hardware can be changed.
<rekado_>many of the packages in games.scm seem to fit better into game-development.scm.
<rekado_>examples: retroarch, glkterm, irrlicht
<iyzsong>rekado_: retroarch is for playing games really, and glkterm is used only by glulxe internal.
<rekado_>oh, okay.
<taylanub>yenda: it was on a T420, and I think the only package from the non-free repo was firmware-iwlwifi. would linux-libre make any other differences on a T420?
<taylanub>the ElementaryOS GUI looks the same as what I saw in Debian, except the "app icons" are at the bottom instead of the left edge (which is probably configurable), and the "theme" I suppose. both GNOME 3 I guess.
<amz3>Elementary is hype that is all ;)
<yenda>amz3: there is nothing wrong with being hype if it makes the user happy
<yenda>having a fully free system with that hype would be good for fully free system
<amz3>yenda: it's possible to package elementary ?
<yenda>amz3: I don't know, for now I focus on packaging i3 and a working java
<amz3>you are right, I will stop asking silly question
<amz3>there is not enough hours in a day :(
<yenda>it's not silly I think it would be cool, but I also think elementary OS is mostly like configuration changes over ubuntu to increase user friendlyness
<yenda>so it's not something you just package
<taylanub>I thought Ubuntu uses Unity not GNOME 3?
<amz3>yenda: silly question in the sens: I enquire for something I won't do
<yenda>is there a particular reason to explain why we have to systematicaly to ("package" ,package) in inputs for a package ? wouldn't it be possible to have a macro to just write (inputs package1 package2 package3) ?
<DusXMT>yenda: I guess so you can potentially have different versions of the same package, and can distinguish between them in the building phases?
<taylanub>yenda: it might be a good idea to have such a macro for the simplest cases, but there are a couple cases where one needs to pass a different structure, e.g. ("package" ,package "lib") to pass package's "lib" output
<taylanub>yenda: and ISTR Ludovic mentioning the whole thing will become unnecessary once we fully utilize Gexps, but I don't know details
<yenda>any idea how to get fix this : "undefined reference to symbol 'trunc@@GLIBC_2.2.5'"
<yenda>here is the full build report ^
<mark_weaver>yenda: the reference is from libiw, so the problem is there
<mark_weaver>looks like it's asking for a specific version of 'trunc' which is different from the one that's in our libc. blah.
<mark_weaver>what is libiw/
<mark_weaver>actually, trunc is in libm
<yenda>hello mark_weaver , libiw is a set of tools allowing to manipulate the wireless extensions
<mark_weaver>somewhere, -lm is missing from the link command
<mark_weaver>and I would guess that it's missing from the libiw package
<yenda>which is a generic api alloing a driver to expose to the user space configuration and statistics specific to common wireless lans
<mark_weaver>also, is it actually using libiw.a as opposed to
<mark_weaver>can you look at the contents of your built libiw package? does it has or only libiw.a?
<yenda>so since I'm making the package for i3status I think I can safely assume it is what displays the state of the wifi connection
<mark_weaver>it may be that you need to ask it to build shared libraries.
<mark_weaver>look in /gnu/store/shi6xf1psgkjyfps4x2572m6qwxf4lf3-libiw-30.pre9/lib
<mark_weaver>what libiw.* files are in there?
<yenda>only libiw.a
<yenda>I read some stack overflow questions talking about the -lm flag for that kind of errors indeed
<mark_weaver>yenda: okay, so you need to look at libiw again. there may be a configuration option like --enable-shared to create shared libraries.
<yenda>there is BUILD_STATIC = y in the makefile
<yenda>"comment that option to save space and to build build by third parties"
<mark_weaver>is there a BUILD_SHARED also?
<mark_weaver>yenda: okay
<mark_weaver>hmm, commenting it can certainly be done, but I wonder if this can be done with #:make-flags instead
<mark_weaver>how is it checked for elsewhere?
<mark_weaver>can you give me the URL for the libiw source code?
<yenda>or if you want the tar.gz
<yenda>to me it looks like the make file defines BUILD_STATIC=y and it is the variable that defines if the .so should be build or not am I right ?
<mark_weaver>actually, including BUILD_STATIC= in #:make-flags (with nothing after the '=') might work
<yenda>ok i try that
<yenda>if it doesnt should I do a subsitute "BUILD_STATIC=y" "#BUILD_STATIC=y" on the Makefile ?
<mark_weaver>I looked up 'ifdef' in the GNU make manual, and ifdef considers a variable with an empty value to be undefined.
<mark_weaver>yenda: yeah, that would be the other option
<mark_weaver>an empty value _should_ make ifdef consider it undefined. however, it's also possible that an empty value on the command line will fail to override the variable setting in the makefile, so I don't know if it will work.
<yenda>the validate_runpath phase is faliing now
<mark_weaver>we already have wireless-tools
<mark_weaver>it's defined in gnu/packages/linux.scm
<mark_weaver>however, our package seems to also build the static library. I guess we wanted it for the programs, not the library, and didn't notice.
<mark_weaver>so, instead of making another copy of this package, we should just fix the one we have and use it
<yenda>yes I didn't see it I was looking for libiw :/
<mark_weaver>I'll fix it..
<yenda>of course, we can update it with make-fakg and modify-phases
<mark_weaver>give me a few minutes
<yenda>you can take my definition as a base
<mark_weaver>can you show me your definition?
<yenda>I think the argument section is better
<yenda>more up to date with the new way to do things
<mark_weaver>yeah, our existing package was not done as nicely as it could be
<mark_weaver>hmm, interesting that our existing package doesn't set CC=gcc and it still works, but you added it anyway. did it fail without that?
<mark_weaver>also, our existing package says the license is gpl2+ and you say gpl2
<mark_weaver>hmm, which is right?
<mark_weaver>ACTION looks
<yenda>^license mark_weaver
<mark_weaver>the license is determined by the copyright notices in the source files
<mark_weaver>the existence of a COPYING file in the tarball is just something that the copyright notices (or README) can reference; it does not itself imply that the code is under that license.
<yenda>" * This file is released under the GPL license.
<yenda> * Copyright (c) 1997-2007 Jean Tourrilhes <>"
<mark_weaver>bah, they are using proper copyright notices
<mark_weaver>they are _not_, I mean.
<mark_weaver>they don't even say which version(s)
<yenda>that's why I backup to the COPYING file
<mark_weaver>yeah, I tend to think you got it right here
<mark_weaver>but I'm curious what Debian thought
<mark_weaver>wow, that's totally different than what I saw
<mark_weaver>I wonder if it changed at some point
<mark_weaver>wireless.22.h is under lgpl2.1+
<mark_weaver>okay, I'm going with (list gpl2 lgpl2.1+)
<mark_weaver>the wireless.N.h headers, where N is less than 21, are not marked as free software at all :-(
<mark_weaver>well, this kind of thing is not unusual, in fact it's often much worse than this :-(
<mark_weaver>the C
<mark_weaver>CHANGELOG.h even says "Put licensing info everywhere (almost). Yes, it's GPL !"
<mark_weaver>note the "almost"
<mark_weaver>I think we'll have to delete the older wireless.N.h headers
<mark_weaver>and my guess is, that won't actually break anything, because almost nothing else uses this package anyway.
<yenda>ACTION used to randomly chose a license and consider the LICENSE file to be engouh
<mark_weaver>I'm glad it is "used to" :)
<mark_weaver>there is only one other package in guix that uses wireless-tools, and that's wicd, and it uses it for the programs, not the library
<mark_weaver>okay, almost done here
<yenda>i just deleted 'validate-runpath phase and it works
<yenda>but I dont know if it's a good idea
<yenda>and i3status still doesn't build
<mark_weaver>yenda: heh, then those programs are broken
<mark_weaver>the wireless-tools programs, that is
<mark_weaver>the right fix is to add (string-append "LDFLAGS=-Wl,-rpath=" %output "/lib") to #:make-flags
<yenda>well I have i3 on arch and the wifi display works well
<mark_weaver>but anyway, I'll push this package soon
<mark_weaver>I see that you are impatient, and I can understand that.
<yenda>can you send me a paste of the package def so I can build locally ?
<yenda>yeah I want to run i3 so I can be confortable when I dev on guix
<yenda>I hate xfce
<mark_weaver>yenda: okay, I just pushed the fixed 'wireless-tools'.
<mark_weaver>yenda: are you running guix out of a git checkout?
<mark_weaver>if so, you can just 'git pull'
<mark_weaver>I have to go afk for a while. good luck!
<yenda>ok, i3status build succeedeed
<mark_weaver>that's good. I will try to look here every once in a while for updates, in case you run into another problem.
<guixnewbie>I've installed the default desktop system (xfce) and can successfully use it as root. However, when logging as a non-root account I get a weird GUI I've not seen before (and don't know to use).
<guixnewbie>What's going on?
<guixnewbie>It has two square things in the upper right, and one in the upper left of the screen.
<guixnewbie>The rest is blank.
<guixnewbie>And nothing seems to be clickable.
<bavier>guixnewbie: did you log in with the xfce session?
<davexunit>guixnewbie: that's windowmaker
<davexunit>at the login screen you can change the session type with f1
<davexunit>it's not the best UI, that's for sure.
<guixnewbie>bavier, davexunit: I suppose I assumed xfce was the default (as it was for root) and so that's why I ended up there. Thanks!
<davexunit>guixnewbie: I would like to use a better display manager that it makes it more clear what session is being used
<davexunit>I noticed a weird thing where if I mistyped my password it would change the session to windowmaker
<davexunit>so if I wasn't paying attention and re-entered my password successfully I wouldn't get the DE I was expecting
<guixnewbie>davexunit: Ah, so that's what happened to me too probably. I fuddled my password the first time around because the keyboard layout got reset to default qwerty while I was logging in.
<mark_weaver>it's probably unwise to run a complex desktop environment like xfce as root
<guixnewbie>mark_weaver: I agree, I'm trying to jump to a separate user account as soon as possible.
<guixnewbie>Actually, I'll go right now. See you soon.
<bavier>davexunit: I updated the fish package. I hope that's alright with you.
<davexunit>bavier: totally fine
<davexunit>I don't use fish anymore
<bavier>I've grown a bit fond of it :)
<davexunit>it has nice built-in autocomplete, but it lacks all of the more advanced bash stuff that I use a lot
<davexunit>so I just use bash
<guixnewbie>It worked!
***davi_ is now known as Guest27519
<yenda>i3 is now working on guixSD :)
<yenda>some little things to fix : default screen resolution, font
<mark_weaver>yenda: that's good news!
<yenda>I saw the discussion in the mailing list regarding screen resolution setting
<yenda>is it how you do it ? with a %store-mode ?
<guixnewbie>I'm missing /usr/bin/env, so a lot of my scripts won't run. How do you fix this? Just manually link a /gnu/store/.../env to the appropriate location?
<davexunit>guixnewbie: that would do the trick
<davexunit>if you don't want to change any shebangs
<guixnewbie>davexunit: Thanks!
<davexunit>I believe NixOS just does this, but I'm unsure if we should do the same.
<guixnewbie>What would the alternative be? Manually modify every shebang?
<guixnewbie>It seems more practical just to link the thing.
<guixnewbie>Similar to how there's still /bin/sh.
<davexunit>all of my projects uses autoconf to preprocess scripts
<davexunit>so the shebangs use absolute paths to the interpreters
<davexunit>you can also change your shebangs to use $HOME/.guix-profile/bin
<guixnewbie>I linked to /usr/bin/env, it was the laziest thing to do at the moment. :)
<guixnewbie>I'm in another mess now, though: I have no idea how to find what would on other systems be my /usr/share/terminfo directory.
<guixnewbie>Ah, okay, found it.
<guixnewbie>Anyone here use rxvt-unicode? What do you set your $TERM to in order to avoid various unpleasantness like "not fully functional" errors?
<davexunit>hmm not sure
<guixnewbie>Okay, TERM=rxvt seems to do the trick for now.
<davexunit>TERM=xterm is what mine is set to
<guixnewbie>davexunit: Thanks, I'll try that one too.
<dmarinoj>guixnewbie: You using ratpoison?
<guixnewbie>dmarinoj: No, just regular xfce. My current plan is to get ghc running and drop down to just xmonad.
<dmarinoj>guixnewbie: sounds good
<davexunit>fun :)
<guixnewbie>huh, there's a guile-wm config file in what I assumed to be a my fresh home directory. sneaky devs!
<guixnewbie>I didn't know about guile-wm though. Is anyone using it and is it good?
<dmarinoj>I have been wondering the same thing
<guixnewbie>looks like it hasn't been updated in a year
<guixnewbie>dmarinoj: yenda baked i3 recently I think, so you might have try that if you're shopping for tiling wms
<yenda>you can check on my github for early try
<dmarinoj>I want to package stumpwm for guix
<dmarinoj>It is my window manager of choice next to ratpoison
<yenda>anyone tried to add the ubuntu font to guix ?
<alezost>ACTION uses stumpwm on GuixSD (compiling it from source)
<alezost>yenda: I think no one tried
<davexunit>if I had infinite time, I'd hack on guile-wm to build a functional window manager like xmonad
<davexunit>applying FRP to window management would be cool.
<yenda>ACTION throws infinite time at davexunit... it failed
<yenda>I'm just gonna stay with i3 which is just perfect to stay out of my emacs way and just make the windows key usefull to switch to browser
<yenda>once wayland will be out I might bother with a new one
<DusXMT>Wayland is already "out" from what I know...
<yenda>does it work with guix ?
<davexunit>we need a package :)
<davexunit>I'd love a guile-wm for wayland
<davexunit>good news: got working shards
<davexunit>wrong chat
<davexunit>rekado-: :)
<yenda>is trivial-build system still the recommended way of building fonts packages ?
<boegel>rekado_: are you planning to attend FOSDEM next year (Jan'16)?
<davexunit>yenda: yeah
<yenda>I guess so since it's just a copy/pasta
<boegel>(or anyone else here)
<yenda>maybe we could have a font-build-system
<davexunit>there's nothing to build
<yenda>^ is this license ok ?
<taylanub>ACTION notes we don't have the Rust compiler packaged yet
<yenda>we don't have valid certificates for java either, I tried to add them but I don't have enough knowledge yet
<yenda>It's wierd under xfce the font in emacs was fine, now that I have i3 is ugly and I don't know how to change it, I installed font-ubuntu package (in config.scm packages) but it doesn't change anything
<paroneayea>rekado_: oh nice, you're also using Haunt then? :)
<yenda>can we define the system wide font in the config.scm file ?
<yenda>it's too annoying to configure emacs font
<dmarinoj>that sounds like a great idea