IRC channel logs
back to list of logs
<luis-felipe>vivien: I haven't tried your patches, but one thing that have helped me deal with test errors is changing the test phase to run the test as indicated by each project. <luis-felipe>vivien: Another thing is that when the origin is not a git repository, sometimes (or almost always?) the test suites are not even included, so the test phase fails.
***NoClu_ is now known as NoClu
<podiki[m]>okay, think I have a minimal example that builds something that tries to refer to the old (non-grafted) version <podiki[m]>I don't know if it is this specific package building or perhaps a bug in how it is being build (not in the usual "guix build" way)...but should this be sent to the security email since it involves perhaps a problem with grafts? <marusich>However, I don't understand how it accomplishes that task. When I invoke "make -j", what stops Make from running make-core-go, make-packages-go, make-system-go, and make-cli-go in parallel? <marusich>I'm just curious. Does someone hre understand how it is that this Makefile.am hackery causes the .go files to not get built all at once? I don't understand it, but I would like to. <marusich>I get that it creates multiple targets, and each of the targets builds smaller groups of files. But I don't understand what is stopping Make from just building all of those targets in parallel when I run "make -j". <AIM[m]>Hey, Is there Gnome Tweaks Tool for Guix? <AIM[m]>I searched online and found that it's gnome-tweak-tool <AIM[m]>But it ain't installing for some reason
***califax- is now known as califax
***w1gz_ is now known as w1gz
<faust45>ifam: oh thanks! i was confused, i thought that i can setup guix on top any linux distro <lfam>Then Guix will erase your old OS <lfam>And, you'll use shepherd <faust45>lfam: i flash usb with sdb +conv=fsync and it works! thanks! <podiki[m]>lfam: just sent in a patch to fix piper, same as what we did for syncthing-gtk (librsvg propagation) and libratbag among others (meson no longer propagates python) <lfam>Thanks, podiki[m]. I pushed it <podiki[m]>wonder how many more meson/python and gtk+/librsvg fixes need to be done... <podiki[m]>probably not hard to have a script that looks for gtk+ and librsvg as inputs for the same package <podiki[m]>or maybe some general tool like that to help track down packages meeting certain criteria <lfam>It's exactly the kind of thing that Scheme allows us to do well <podiki[m]>I guess the problem there is that gtk+ propagates librsvg-bootstrap, so you wouldn't get some sort of "an input propagates a different input" <lfam>We don't have to scrape text or anything like that <podiki[m]>maybe some utility the is easy to adapt to exploring the package tree in different ways <tribals>luishgh`: found your hint in chat log, it helped. Thank you a lot! <tribals>now next question: how to resolve path relative to source file where it is mentioned? <tribals>like this, in ~/foo/bar.scm, i want to refer to ~/foo/baz/quix.txt, but relatively to ~/foo - "baz/quix.txt"? <robin>sneek, later tell lfam: https://rufus.ie/en/ is a good gplv3+ usb-drive flashing tool, but for ms windows only (still possibly useful for windows users installing guix, maybe worth recommending in the manual) <lfam>gnome-multi-writer is packaged <sneek>Welcome back lfam, you have 1 message! <sneek>lfam, robin says: https://rufus.ie/en/ is a good gplv3+ usb-drive flashing tool, but for ms windows only (still possibly useful for windows users installing guix, maybe worth recommending in the manual) <robin>SeerLite[m], oh, that would be nifty, assuming signature verification and such could be integrated (perf-wise rufus > unetbootin, according to the rufus author, but there are zero plans to make rufus cross-platform) <lfam>But, it's not part of Guix <lfam>Nor is it part of Debian <lfam>So, hard to recommend :) <SeerLite[m]>Oh Ventoy is great, yes. I didn't think of that. But I think it's harder to set up than just using a GUI program <podiki[m]>It has been rather hit or miss for me, ventoy, in what distro isos boot and work, not sure why <lfam>I don't see why the tool used to flash the USB would make a difference to whether or not the OS boots afterwards <lfam>As long as it writes the data to the storage medium faithfully, shouldn't it work? <robin>lfam, for methods that boil down to 'cat > /dev/sdX && sync', i'd think so. some tools like ventoy are apparently much more complicated though (e.g. ventoy lets you put multiple ISOs on a disk and has a custom bootloader to choose one, afaict?) <lfam>Well, I was hoping to recommend a GUI that would be simpler than dd. Not more complicated :) <lfam>gnome-multi-writer doesn't seem to have any options, which makes it perfect <jgart>hi would someone be able to help me debug an elisp package I packaged? <jgart>nice-defaults is a fork of better-defaults <jgart>but the nice-defaults guix package does not produce nice-defaults-autoloads.el and nice-defaults-autoloads.elc in the store <podiki[m]>yeah, ventoy lets you (supposed to) keep a bunch of different bootable images and I think even some storage? anyway, hit or miss for me, like I said. i guess some images play nicer with that set up than others <dcunit3d>what tools are available to plot out the PCIe bus topology in guix? <dcunit3d>i can't remember the name of the tools that i've used in archlinux <drakonis>ventoy makes it pretty trivial to have multiple images stored <drakonis>but not every iso lets you mount ventoy's device while it is booted up, so you can't access any data <drakonis>no need to format anything, just throw the isos in there and any data you might need to store or access from a running OS <dcunit3d>no i have lspci. i just remember a tool that would plot the topology using graphviz or something <dcunit3d>if i could remember what it's called then i should be able to find it <lfam>Like, outside of the build chroot?
***Reventlov1 is now known as Reventlov