<happy_gnu[m]>As marusich explained yesterday, when you run guix pull, the guix source (Guile scheme modules in files named "foo.scm" and the like) gets compiled (to compiled Guile modules with names like "foo.go"). In other words, all of the Guile scheme source code that Guix uses gets compiled, including all of the package definitions. It isn't compiling all the packages that are defined; it's compiling the Guile modules that contain
<cbaines>sadiq[m], how are you using Guix and the gnome-control-center, e.g. I am using GuixSD, and seem to have it installed in my system profile (I'm running it from /run/current-system/profile/...).
<sadiq[m]>I'm on guixSD, I did open it a few minutes ago. But now not.
<sadiq[m]>I reinstalled gnome-shell, and now it's working fine
<sadiq[m]>in a package define-public I see a checksum of the package archive. It is written as (sha256 \\n(base32 "....". But this checksum doesn't seems to match the sha256 checksum of the archive file. What am I missing?
<efraim>sadiq[m]: run 'guix has foo' where foo is the source
<rekado_>I don’t remember seeing this recently, but it did happen more than once in the past, for different users.
<sadiq[m]>The packaging guidelines doesn't say how to use the package built. I'm trying to build a newer version of already installed package (gtk+), How can run a program (say, gnome-calendar) with the newly built gtk+?
<mekeor>sadiq[m]: i don't know the best way but one way would be to *install* the newly built package.
<sadiq[m]>hm.. guix package: error: profile contains conflicting entries for gtk+:out
<civodul>rekado_: yes, i vaguely remember people reporting it, but it seems we never got a bug report or fix in this area
<civodul>sadiq[m]: it should tell you what's conflicting, right?
<sadiq[m]>3.90 is going to be the next branch with a different so name
<sadiq[m]>Let me make it simple. What is the process of updating a guix package in developers way (ie, build, install, and run prcodure for an updated version of the package that is already installed?)
<wingo>switching from the intel driver to the modesetting driver is thus a switch from a separate 2d and 3d accel path to a unified path
<wingo>additionally, the 2d accel path in the intel driver was not very well maintained.
<wingo>there has been no release for a couple years, just noodling in git
<wingo>and the "SNA" thing they came up with was fast but had some problems that couldn't be resolved related to buffer synchronization, which normally worked fine but for some reason emacs under a composited WM exhibited corruption
<wingo>so in guix we switched back to UXA, an earlier 2d accel architecture, but that was quite slow
<wingo>switching to the modesetting driver and the unified acceleration pipeline fixes both issues
<wingo>the intel driver will still be used for older gpus tho
<thomasd>wingo: I think a dbus module could be useful for GuixSD. Maybe the work you did can be revived, still better than starting from scratch, no? I couldn't find anything yesterday, so any pointers are welcome.
<Apteryx>elc79: I think I fixed that 3600 s silence kill switch, but until you are using a recent guix that might be a chicken and egg problem. You can work around it doing 'guix build whatever-timed-out'
<thomasd>wingo: thanks, I'll have a look. Don't know if I'll write something myself, but it never hurts to look at an existing implementation and steal some ideas.
<nextos>A bit off-topic but what email client do you use in Guix? Gnus, mu4e, mutt?
<wingo>i have a gnus / dovecot / offlineimap thing
<nextos>ok, i used to have that setup, but Gnus supports notmuch now and it seems simpler
<nextos>I also got rid of offlineimap and replaced it by mbsync, although there are some caveats
<rekado_>I tried to switch to mbsync but had big problems with duplicate message ids, so I fell back to offlineimap.
<nextos>rekado_: ok, i note you use mu4e. Do you prefer it to gnus?
<rekado_>I found mu4e much easier to set up, but I’m actually considering to switch to gnus eventually.
<rekado_>mu4e lacks a few things I’d really like to have, such as collapsing threads
<nextos>rekado_: i'm switching back and forth between both Gnus and mu4e. I like both. mu4e has great defaults and 2 basic things I've never been able to achieve on Gnus: address completion based on index, and sync'ing drafts with remote IMAP folder.
<thomassgn>hmm, suddenly almost all the infopages are gone...
<thomassgn>but for some reason only in emacs info, not when I run info from terminal
<Gamayun>I was noticing that the other day as well...
<Apteryx>thomassgn: that's usually because there are no dir files (dir files is a computed file acting as an index for the info files IIRC).
<thomassgn>Apteryx: Ah, ok. Do you know how I can get them?