Search guix IRC channel logs

These are the channel logs matching your query nick:civodul

2025-11-27[11:01:44] <civodul> cbaines: how does berlin���s config depend on guile-drmaa?
2025-11-27[11:01:49] <civodul> for GWL?
2025-11-27[11:02:21] <civodul> i reconfigured it last week i think, and guile-drmaa was already broken
2025-11-27[11:58:40] <civodul> cbaines: guix.info is owned by rekado currently, as mentioned in https://codeberg.org/guix/maintenance/issues/13#issuecomment-8322698
2025-11-27[11:59:02] <civodul> cbaines: when you say ���downgrade���, you don���t mean ���--allow-downgrades���, do you?
2025-11-27[11:59:43] <civodul> hm?
2025-11-27[11:59:53] <civodul> oh you had an old copy of maintenance.git?
2025-11-27[11:59:57] <civodul> i see
2025-11-27[12:00:18] <civodul> is there a PR for the guix.gnu.org migration?
2025-11-27[12:01:31] <civodul> why not, i thought the whole thing would be a PR but anything is good :-)
2025-11-27[12:05:25] <civodul> generally speaking, i think Codeberg is an opportunity to increase transparency on what happens on the infra
2025-11-27[12:05:39] <civodul> and that in turn is a good way to enable others to jump in and give a hand
2025-11-27[12:18:34] <civodul> ����
2025-11-27[14:27:24] <civodul> uh, Codeberg is pretty slow today
2025-11-27[15:30:29] <civodul> kestrelwx: what problem do you experience with ���reboot --kexec���?
2025-11-27[15:58:12] <civodul> kestrelwx: see https://issues.guix.gnu.org/76554
2025-11-27[15:58:27] <civodul> there���s actually a solution: ensuring non-zero screen brightness at boot time
2025-11-27[15:58:33] <civodul> but nobody has implemented it yet :-)
2025-11-28[10:05:56] <civodul> Hello Guix!
2025-11-28[10:09:51] <civodul> last Sunday it was 13y since the first Guix announcement: https://lists.gnu.org/archive/html/gnu-system-discuss/2012-11/msg00000.html
2025-11-28[10:10:08] <civodul> who could have thought?
2025-11-28[10:43:14] <civodul> csantosb: heh :-)
2025-11-28[10:43:21] <civodul> cbaines: yay, thank you!
2025-11-28[10:44:06] <civodul> DNS changes have yet to propagate
2025-12-01[11:51:56] <civodul> Hello Guix!
2025-12-01[12:07:01] <civodul> apteryx: go-team was still pulling from Savannah, hence the Savannah link
2025-12-01[12:07:07] <civodul> i���ve updated the spec now
2025-12-01[17:13:14] <civodul> wizard: i think it should work that way
2025-12-01[17:13:54] <civodul> in ���guix package -I ~/.guix-home/profile -A icecat���, i have a bunch of extensions like this one
2025-12-01[17:14:07] <civodul> ieure may know better tho!
2025-12-03[10:22:39] <civodul> ����
2025-12-03[10:37:55] <civodul> ibu: the ���incompatible bytecode version��� warning suggests that some .go files were compiled by a Guile version different from that you���re now using
2025-12-03[10:38:25] <civodul> this could happen if you���re say using guile@3.0.9 but previously compiled with a newer version, like ���guile-next���
2025-12-03[10:45:07] <civodul> hmm Codeberg is down?
2025-12-03[10:45:32] <civodul> damnit
2025-12-03[10:45:59] <civodul> cbaines: oh good, i totally overlooked that
2025-12-03[10:46:15] <civodul> Rutherther: i���m planning to tag shepherd 1.0.9 today
2025-12-03[10:46:44] <civodul> bacs: tx!
2025-12-03[10:49:42] <civodul> going to be more difficult if Codeberg is down tho :-)
2025-12-03[10:52:40] <civodul> heh
2025-12-03[10:54:42] <civodul> yeah
2025-11-26[10:12:35] <civodul> attila_lendvai: every generation listed is a ���GC root���, so whatever it refers to cannot be garbage-collected
2025-11-26[21:25:06] <civodul> old: we could do that! in hindsight though, i have mixed feelings about monads for Scheme
2025-11-24[11:06:38] <civodul> hi there!
2025-11-24[11:07:03] <civodul> i noticed the email for Saturday���s release meeting just today :-)
2025-11-24[11:18:51] <civodul> Rutherther: yup, pity; i wonder if we should start thinking about a backup plan for mailing lists
2025-11-24[11:43:58] <civodul> Rutherther: we could add alternate URLs for ftp.gnu.org to guix-install.sh, that should be easy
2025-11-24[11:44:15] <civodul> for the keyring, i���m not sure, maybe we could host a copy elsewhere
2025-11-24[11:44:50] <civodul> maybe for now just set up a Shepherd timer on the web site that downloads it from Savannah and serves it as guix.gnu.org/keyring.asc for instance
2025-11-24[12:02:18] <civodul> Rutherther: OpenPGP key servers became very unreliable a few years ago
2025-11-24[12:02:18] <civodul> major key servers like sks disappeared
2025-11-24[12:02:18] <civodul> (sks-keyservers.net)
2025-11-24[12:02:18] <civodul> keys.openpgp.org came up with its own policy of not including user IDs unless key owners explicitly consent to it
2025-11-24[12:02:18] <civodul> which is good, but gpg cannot import keys without a user ID packet
2025-11-24[12:02:18] <civodul> so overall, it���s become very messy
2025-11-24[12:02:18] <civodul> and downloading from Savannah became more reliable
2025-11-24[12:02:18] <civodul> of course today, that���s no longer the case :-)
2025-11-24[12:46:22] <civodul> Rutherther: ���system*��� does fork + waitpid; but when invoking ���halt���, changes are that ���halt��� will be terminated before it���s had a chance to get a reply from shepherd
2025-11-24[12:48:53] <civodul> Rutherther: ���root-unmount��� was meant to catch unclean unmounts, and i think it does that well, but it only checks for a bare-bones kind of OS config
2025-11-24[15:01:21] <civodul> Rutherther: so you have the reconfigure-then-halt problem where root is not cleanly unmouted? i think that bug was eventually closed and i don���t think i have this problem, but it���s never been totally clear to me what the situation is
2025-11-20[08:37:29] <civodul> Hello Guix!
2025-11-20[09:05:24] <civodul> hey Rutherther
2025-11-20[09:06:11] <civodul> there���s a weird ext4 issue on pulls.ci: https://codeberg.org/guix/maintenance/issues/51
2025-11-20[09:06:35] <civodul> does that ring a bell to anyone here?
2025-11-19[10:40:11] <civodul> rekado: howdy! just stumbled upon https://codeberg.org/guix/guix/commit/a77f4fb279b96f2707b475531b60ca36417bde69 and i think it should use ���package/inherit��� (to get the libxml2 replacement)
2025-11-19[10:40:56] <civodul> rekado: i noticed because of an r-future build failure when ungrafting: https://ci.guix.gnu.org/build/15640682/details
2025-11-19[21:03:46] <civodul> FuncProgLinux: not conveniently, you have to use ���module-map��� for instance to iterate over the bindings of the (guix licenses) module
2025-11-19[21:03:56] <civodul> but yeah, M-x guix-licenses :-)
2025-11-19[21:15:46] <civodul> hey janneke! the list of pending merges is still at https://qa.guix.gnu.org/
2025-11-19[21:16:02] <civodul> apparently there���s no request to merge ���rust-team���
2025-11-19[21:17:09] <civodul> pjmg: i use BitlBee but only through the Guix System service; maybe that could serve as inspiration?
2025-11-18[08:52:44] <civodul> Hello Guix!
2025-11-18[10:25:30] <civodul> apteryx: hey! i don���t know, do you have a link to the build?
2025-11-18[10:25:45] <civodul> ISTR gcc-mesboot does take ages to build
2025-11-18[10:26:28] <civodul> apteryx: re .info, does ���info-reader��� know how to handle ztsd-compressed files?
2025-11-18[10:27:26] <civodul> ah yes, just saw the commit :-)
2025-11-18[10:28:37] <civodul> oh, that���s not an actual build
2025-11-18[10:28:51] <civodul> so the ���timeout��� property isn���t honored
2025-11-18[10:29:56] <civodul> yeah
2025-11-18[10:30:21] <civodul> (isn���t this PR the kind of thing should go on ���core-packages-team���?)
2025-11-18[10:30:52] <civodul> so the problem is that gcc-mesboot really needs more than 21k seconds to build
2025-11-18[10:31:11] <civodul> this build happens as part of the evaluation (on berlin, but it���s offloaded)
2025-11-18[10:31:37] <civodul> one way would be to change the default timeout for guix-daemon on all the build machines
2025-11-18[10:32:09] <civodul> and a quick workaround is to ���guix build --timeout=0 --no-offload ���/gcc-mesboot��� on berlin
2025-11-18[10:32:26] <civodul> yes
2025-11-18[10:32:44] <civodul> right
2025-11-18[14:49:55] <civodul> apteryx: i like that BTW, been spending too much time waiting for tests :-)
2025-11-18[14:50:33] <civodul> i think some of them are poorly written (like they invoke the GC just to remove one store item)
2025-11-18[14:51:00] <civodul> but others are inherently expensive (like those that actually test the GC)
2025-11-18[15:05:35] <civodul> apteryx: yes, that makes sense to me
2025-11-18[23:41:44] <civodul> PSA: pulls.ci.guix.gnu.org has been redeployed; rebase your PRs if you want to trigger it (details at https://codeberg.org/guix/maintenance/pulls/49 )
2025-11-14[08:46:58] <civodul> Hello Guix!
2025-11-14[14:54:18] <civodul> pranav: hi! maybe you���ll need to define that old version for yourself, either in your OS config file or in a channel?
2025-11-14[14:54:46] <civodul> you could also file a bug to see whether ���kernel��� could be changed to accept an inferior package
2025-11-13[09:38:04] <civodul> Hello Guix!
2025-11-13[16:07:25] <civodul> ArneBab: hi! ci.guix runs ���guix publish��� while bordeaux.guix runs nar-herder
2025-11-13[16:07:30] <civodul> both are behind nginx
2025-11-13[16:07:43] <civodul> but nginx doesn���t do any caching
2025-11-13[16:08:05] <civodul> supporting code is in (guix substitutes) and (guix narinfo)
2025-11-12[17:48:10] <civodul> yelninei: usually that���s a pretty bad sign :-)