IRC channel logs

2015-12-05.log

back to list of logs

<fps>oh well, sleepy time. nn
<lfam>sneek: botsnack
<sneek>lfam, you have 4 messages.
<sneek>lfam, mark_weaver says: cross-compilation doesn't work for all of our packages. in many packages, the problems might be easily fixable. for others, it might be significantly more difficult.
<sneek>lfam, mark_weaver says: we have generic code to handle cross-compilation, but hydra.gnu.org tests cross-compilation for only a small number of core packages and targets. my impression is that most of our packages have not been tested for cross-compilation.
<sneek>lfam, mark_weaver says: bug reports, or better yet, patches, to improve the situation would be welcome :)
<sneek>lfam, davexunit says: I updated wip-lets-encrypt in the official guix repo. could you test it out and make sure it still works for you and then I will merge it?
<sneek>:)
<lfam>mark_weaver: That grub cross-compilation error seems unrelated to architectural issues. It fails while trying to unpack grub.scm's unifont package. Speaking of which, there is a proper font-gnu-unifont package now. I'll try to use that one instead.
<lfam>sneek later tell davexunit: Thanks for doing that! I'm looking through it now. I appreciate your peeved comment about python2-pythondialog / dialog ;)
<sneek>Will do.
<lfam>sneek later tell davexunit: The comment on python2-zope-testrunner was really just for myself while working on the python2 package variants. It was a note to remind myself that even if some of the other variants could get away with a plain 'package-with-python2', this one could not. Feel free to remove or edit the comment. Or I can make edits and then push them to my repo.
<sneek>Will do.
<lfam>sneek later ask davexunit: What do you think about the name 'lets-encrypt'? Is it Guix policy to hyphenate? I think it will be confusing for users, because the Let's Encrypt binary is named 'letsencrypt'.
<sneek>Will do.
***operhiem1 is now known as Thynix
<CustosL1men>hi
<CustosL1men>does guix work for solaris ?
<rekado>I haven't tried.
<davexunit>morning guix
<sneek>davexunit, you have 3 messages.
<sneek>davexunit, lfam says: Thanks for doing that! I'm looking through it now. I appreciate your peeved comment about python2-pythondialog / dialog ;)
<sneek>davexunit, lfam says: The comment on python2-zope-testrunner was really just for myself while working on the python2 package variants. It was a note to remind myself that even if some of the other variants could get away with a plain 'package-with-python2', this one could not. Feel free to remove or edit the comment. Or I can make edits and then push them to my repo.
<sneek>davexunit, lfam says: What do you think about the name 'lets-encrypt'? Is it Guix policy to hyphenate? I think it will be confusing for users, because the Let's Encrypt binary is named 'letsencrypt'.
<davexunit>sneek: later tell lfam yes, we should change the package name to "letsencrypt", as that is what the upstream package name is. I assume this means that the program is still working for you. I will do final clean up and push later today.
<sneek>Got it.
<guimingyuan>iyzsong: 祖国人民需要你的帮助
<iyzsong>guimingyuan: hi, you can talk in Chinese to me at other channels..
<guimingyuan>iyzsong: #guix-zh come in plz
<civodul>Hello Guix!
<civodul>long time no see ;-)
<davexunit>hey civodul
<iyzsong>hi :o
<civodul>ACTION spams people about the goodness of the reproducible summit
<civodul>we need to draft something like https://www.fsf.org/news/fsf-launches-fundraising-program-for-replicant-the-fully-free-android-based-mobile-os for Guix
<civodul>difficult exercise :-)
<lfam>sneek later tell davexunit: From your branch I entered an --ad-hoc guix environment. It worked! Using the 'certonly' method, which just dumps the files in /etc/letsencrypt and needs to bind to port 80.
<sneek>lfam, you have 1 message.
<sneek>lfam, davexunit says: yes, we should change the package name to "letsencrypt", as that is what the upstream package name is. I assume this means that the program is still working for you. I will do final clean up and push later today.
<sneek>Will do.
<lfam>davexunit: FYI the hash of my store object is pi2gwzk5n2jzj624y0brzpfdpp879cjf-lets-encrypt-0.1.0 when built from git commit fdd7a8498. Hopefully it matches yours.
<davexunit>I'm building from the 0.1.0 release tarball
<sneek>davexunit, you have 1 message.
<sneek>davexunit, lfam says: From your branch I entered an --ad-hoc guix environment. It worked! Using the 'certonly' method, which just dumps the files in /etc/letsencrypt and needs to bind to port 80.
<davexunit>civodul: I'm going to push the let's encrypt patch set to master if you don't mind.
<davexunit>lfam and I have been reviewing each other's work for the past few days
<fps>yo
<davexunit>doing some final linter checks.
<davexunit>ooh, here's a question about naming conventions: an upstream package is named "pythondialog". should the guix package be "python-pythondialog" or just "python-dialog"?
<davexunit>I've gotta run so I'm going to merge letsencrypt
<fps>btw: that bug with getting window maker if you enter the password wrong works across users, too
<fps>enter any username and the wrong pw
<davexunit>it's not a bug
<fps>the next user that logs in gets windows maker
<fps>it's a feature?
<davexunit>it's just an annoying slim quirk
<davexunit>it's expected
<davexunit>I wish it didn't do that
<fps>wat?
<davexunit>but it's not a bug
<fps>that sounds slightly stupid
<davexunit>it is
<davexunit>it's just bad user interface design
<fps>um, upstream rejected it as a bug?
<fps>how can this not be a bug?
<fps>ACTION 's mind assplodes
<davexunit>I don't think anyone has talked to upstream
<davexunit>it seems like a bad feature to me
<fps>is it documented behaviour?
<davexunit>not sure
<davexunit>gotta run
<fps>hf :)
<davexunit>letsencrypt now in master!
<fps>n1
<fps>even if letsencrypt is horrible
<fps>still: nice one :)
<fps>yay, lxterminal actually offers installed fonts..
<fps>xfce4-terminal somehow never sees new fonts..
<civodul>sneek: later tell davexunit pushing let's encrypt sounds good to me!
<sneek>Got it.
<civodul>sneek: later tell davexunit i'm very grateful lfam & you have done all this work
<sneek>Got it.
<a_e>sneek: later tell davexunit python-dialog. I think it is documented in the manual.
<sneek>Will do.
<rgrau>hi. I installed tcl via guix, and I have tclsh but no executable called 'tcl'
<rgrau>are they supposed to be the same file? (like, called interactively vs batch)
<rgrau>(pretty general and vague qustion)
<rgrau>ah sry, my bad ( /me was confused )
<civodul>rgrau: i must say i'm really unfamiliar with tcl, dunno
<fps>hmm, i wonder how i can deploy the guix-daemon version i patched on my guixsd system
<fps>so i can test my changes
<rgrau>I can't find java (jre nor jsdk) in guix packages. Am I failing to search correctly? or they're just not there? (I guess they'd be big enablers for future packages, no?)
<civodul>fps: you could modify the guix-devel recipe in (gnu packages package-management) to include your patch
<rekado>rgrau: the JDK/JRE is "icedtea7".
<rekado>unfortunately, having the JDK doesn't help much. We need maven to build most Java stuff, and maven needs packages that need maven to be built.
<civodul>heheh
<fps>civodul: oh ok. hmmm. and then basically reconfigure my system from within ./pre-inst-env?
<rgrau>rekado: aha, thanks. I was failing failing to search it correctly :)
<rekado>I admit it's unusually named.
<rekado>but you can find it with both "guix package -s openjdk" and "-s java".
<rgrau>my smartypantysm backfired... I was 'guix package -s java G name G jre' and 'guix package -s java G name G java'
<rgrau>G being an alias for '| grep '
<rgrau>¯\\_(ツ)_/¯
<rgrau>anyway, I think https://github.com/mozart/mozart2 is over my packaging skills.... it seems I'm always picking non-standard packages to try :/
<civodul>fps: yes, for example