IRC channel logs


back to list of logs

*davexunit notices that there's no general crypto module.
<davexunit>where should I put a package for a crypto library?
<phant0mas>good morning guix
<civodul>Hello Guix!
***DusXMT_ is now known as DusXMT
<jmd>How do I kill a package?
<taylanub>jmd: kill? do you mean remove?
<jmd>Well I tried gc -d and got a message saying cannot delete because it is still alive.
<davexunit>jmd: I assume you've uninstalled the package. could it be that you have another installed package that depends on the package you want gc'd?
<jmd>Is there a way to do a sure gc ?
<jmd>Or to find out which package might be using it?
<bavier>jmd: there's the --references and --referrers options for gc
<jmd>Yes. The only referrers are /gnu/store/*profile
<jmd>But obviously I can't delete that.
<bavier>you can explicitely kill old profiles
<bavier>guix package -d <profile>
<jmd>I thought I tried that.
<civodul>rather: guix package --delete-generations=X
<civodul>"guix package --delete-generations" deletes all generations except the current one
<civodul>(hi all!)
<jmd>Is there not an easier way to reap a drv?
<civodul>reap a drv?
<civodul>there's "guix gc -d /gnu/store/foo" to explicitly remove foo from the store
<jmd>I want to garbage collect /gnu/store/m76g3dafx88zq05y93irzy4vpr6nsvph-glade-3.8.4
<civodul>(if possible)
<civodul>then yes, "guix gc -d /gnu/store/m76g3dafx88zq05y93irzy4vpr6nsvph-glade-3.8.4"
<jmd>It tells me that it is still alive. How do I kill it?
<civodul>if it's alive, it cannot be killed
<civodul>wonderful world
<bavier>civodul: in jmd's case, the referrer is an old profile
<civodul>ah, ok
<jmd>Can I persauge it then to die of natural causes?
<civodul>then "guix package --delete-generations=theoldgen"
<jmd>I'm not sure which generation it is. I have rather a lot :(
<bavier>what is "guix package" expecting for "theoldgen"
<bavier>a number?
<civodul>a number or a duration spec
<civodul>RTFM :-)
<civodul>--delete-generations=1m removes stuff more than one month old
<civodul>pretty convenient
<jmd>Anyway the reason I am messing about, is that I notice that the glade package includes
<jmd>It should not.
<bavier>speaking of glade, I'm trying to package 3.18.3 right now.
<jmd>ok. But don't remove the old one please!
<jmd>Older glades are required for use with gtk2
<bavier>jmd: no, I wasn't planning on that
<bavier>I noticed the gtk requirement
<bavier>I just have another package that needs gladeui-2.0
<jmd>Anyway, can anyone explain how /gnu/store/m76g3dafx88zq05y93irzy4vpr6nsvph-glade-3.8.4/lib/glade3/modules/ came into existance. This seems like a bug?
<bavier>jmd: I don't see that .so in my glade installation
<jmd>Maybe then it is just mine!
<bavier>would anyone have an objection to upgrading the gtk+ source version?
<jmd>So long as a gtk+-2 remains I don't care.
<civodul>bavier: fine with me, if it's a minor upgrade
<bavier>3.10 => 3.12
<civodul>i guess it should be ok
<bavier>some supporting libraries might also need upgrading
<bavier>such as glib, pango, atk, gobject-introspection
<civodul>upgrading GLib is never completely peaceful though
<civodul>and we're approaching a release, hopefully ;-)
<civodul>maybe you can give it a try and it it works well then we can go for it?
<jmd>How can I force a rebuild of glade?
<bavier>civodul: I'll give it a try
<jmd>Bed time
<civodul>bavier: great!
<civodul>you might want to take it as an opportunity to tackle :-P
<davexunit>civodul: what resources will we need in order to have an ARM port of guix?
<davexunit>I'm going to be receiving my novena motherboard around christmas time, and I will be itching to run guix on it.
<civodul>davexunit: the main resource is developer time :-)
<civodul>then porting itself can start even before we have the hardware
<civodul>because it's about cross-compiling the bootstrap toosl
<davexunit>civodul: cool. have we not added an arm build because of limited resources on hydra?
<davexunit>I currently have a raspberry pi that I could test arm stuff on.
<dsmith-work>sneek: later tell civodul testing
<sneek>Got it.
<civodul>welcome, sneek!
<sneek>Welcome back civodul, you have 1 message.
<sneek>civodul, dsmith-work says: testing
<civodul>dsmith-work: perfect :-)
<s4ff32i>oh, sneek is here, that's neat.
<civodul>davexunit: there are other issues, lemme see
<dsmith-work>sneek: later tell civodul another test
<sneek>Will do.
<dsmith-work>civodul: Now say something in #guile
<civodul>sneek: botsnack
<sneek>Welcome back civodul, you have 1 message.
<sneek>civodul, dsmith-work says: another test
<civodul>ah sorry
<davexunit>civodul: okay. I'm just curious. I don't know how the ports work.
<dsmith-work>sneek: later tell civodul another another test
<sneek>Got it.
<davexunit>gotta go!
<civodul>tschwinge: the Cauldron seems like the right moment to devise a roadmap to merge both libcs, WDYT? :-)