IRC channel logs


back to list of logs

<jxself>er; that was supposed to be "wonderful"
<civodul>jxself: ah, davexunit's talk?
<civodul>err, probably
<civodul>jxself: the kernel config seems to work fine, thanks!
<civodul>it puts more pressure on having a working udev
<jxself>Enjoy, sir.
<jxself> predicts 3.16 for mid-August so I'll send over an updated one around that time.
<jxself>Or maybe everything will be ready by then and I can just go make the changes myself... :)
<davexunit>hey, back from talk
<davexunit>it went well, I think
<davexunit>got some good questions
<davexunit>signing off!
<civodul>jxself: just pushed that
<civodul>so yes, you may be able to make the changes yourself ;-)
<davexunit>hello #guix
<davexunit>good night, #guix
<civodul>Hello Guix!
<atheia>Hi Civodul!
<atheia>Exciting news, the technology preview — turns out I don't have a 64 bit laptop for testing at the moment :-(
<civodul>howdy atheia
<civodul>ah, good!
<civodul>ah no, not good ;-)
***llida is now known as gry
***DusXMT_ is now known as DusXMT
<phant0mas>hello civodul
<phant0mas>youpi said that for now we could use glibc without nscd
<phant0mas>so should I continue with nscd disabled?
<civodul>sneek: later say phant0mas yes, ok to use libc without nscd support
<civodul>sneek: later tell phant0mas yes, ok to use libc without nscd support
<sneek>Will do.
<DusXMT>Is sneek a bot, or a person?
<svetlana>bobotpp version 2.3.0 yadda
<alezost>is a full name (like "guile-2.0.11") a proper way to identify a package?
<davexunit>alezost: in what context?
<alezost>I mean if I need to get a particular package, (find-packages-by-name "guile" "2.0.11") is the best choice. Am I right?
<davexunit>oh, this is from the guile API, I see.
<alezost>yes, I'm working on Emacs UI for Guix and I just want to be sure that there is no better way to identify a package. As I can see some packages are duplicated in their own <package>.scm and in base.scm files
<davexunit>alezost: oh you're working on that? I am *really* looking forward to that.
<davexunit>but yeah, a package "foo" can be a variable defined in many modules.
<davexunit>and we package a few different versions of guile
<civodul>alezost: package + version should be OK, but there can be several packages with the same name and version
<civodul>there are a few occurrences of that
<civodul>and it's theoretically possible
<civodul>glad you're already working on this, BTW :-)
<alezost>I think I'll publish some usable version next week so that people could see how it looks like.
<civodul>hurrah! :-)
<bavier>civodul: I was looking at the glib failure on i686
<bavier>it's a strange failure; looks like perhaps a floating-point rounding error
<davexunit>oh, speaking of i686, I was unable to build the installation image for i686. I don't have the backtrace handy right now, but I'll try to send it to the list later.
<bavier>it would be easy enough to get a patch that lets glib build, but it'd be nice to understand the actual problem.
<civodul>bavier: if you have enough details, perhaps you could report it upstream, and skip it locally for now?
<civodul>or you could post the details on the list before sending upstream, just to see
<bavier>I'll post some details to the list soon.
<civodul>cool, thanks
<civodul>davexunit: would be cool if you could send the details, indeed
<sneek>Welcome back phant0mas, you have 1 message.
<sneek>phant0mas, civodul says: yes, ok to use libc without nscd support
<davexunit>a thought just popped into my head: what does the existence of guix mean for the guile guildhall?
<davexunit>I imagine we'll have all the guile libs available via guix, but I guess guildhall will still be useful to those that aren't guix users.
<civodul>davexunit: yeah, for non-Guix users, it's still convenient to have the guildhall, i think
<civodul>same for pip, package.el, etc.
***grasshop` is now known as grasshopprWhoppr