<vtomole>Hmm i see, so this hanging thing... Never happened to you?
<adfeno>Hm... Sorry for not informing you earlier, but I'm not using GuixSD. Instead, I use Guix on top of Trisquel.
<vtomole>ahh yes, i want to do that now too, i know guixsd is in beta, I want to move to nixos cause everything has been working perfectly for me, but i just love lisp so much :( so i don't want to give up
<vtomole>I've heard it's very easy to install on baremetal, but i don't want to do a full one, can i dual boot it?
<adfeno>In my case, I'm still not ready to make my work-computer use GuixSD. So I decided to help the Guix project while testing some packages that I like from Guix (and occasionally testing other packages just to contribute fixing possible bugs with them, even though I'll probably uninstall them once finished).
<adfeno>vtomole: That's my concern too. For both of us, I think it's better to make sure that you have a way to, while installing GuixSD, be online here at #guix (with other computer or cellphone) , just in case you need some support.
<vtomole>hmm theres no other choice than to install guix on nixos then
<adfeno>vtomole: And of course: be sure to back-up important things of your current work-computer before installing.
<adfeno>(↑ my last message was still referrring to the installation of GuixSD)
<adfeno>Now, if we instead take each component/hardware model/name from your computer, and search for these instead (the links differ, but you would either go to "Hardware" or "Search" and select the category that fits said hardware).
<emyles>I made a module for a haskell package and its dependencies by doing 'guix import hackage [PACKAGE]' repeatedly. There is also a nix package. Next time would it be better to import the nix package somehow?
<jmd>civodul: Once a merge-evaluation process has started, nobody is permitted to commit to the branch. So we need a staging-pending branch where people can commit to. When staging is merged, then staging-pending can be renamed to staging.
<quiliro>cbaines: i would like 2 things: to be able to install offline and to have an end user ready desktop installation that does not take too long to install in an old machine...i reffer to the system distribution
<quiliro>civodul already answered my question on the bugs mailing list. I am figuring out how to give feedback to that question
<jmd>quiliro: Installing offline would be possible if somebody was to produce dvds mirroring hydra.
<jmd>Answering your second question would require a definition of "too long" and "old".
<snape>how long should I wait before sending an updated patch, on the Prosody service? Not sure there is enough feedback
<lfam>snape: I'd wait for a deeper review. So far I don't think anyone has read the patch very closely.
<lfam>snape: Preliminary feedback: Please separate the changes to gnu/packages/messaging.scm into their own patch. We prefer one patch per change, and fixing a broken package is worth doing even without adding a service.
<snape>lfam: well, the package changes don't make sense without the service
<snape>because they are related to prosodyctl, whose only point is to talk to the service
<lfam>snape: Do they make it impossible to use the package without the service? Or could people still use our Prosody package with another service manager?
<snape>there are two binaries in the Prosody package. One is prosody and the other is prosodyctl