<quiliro>j31: maybe i can guide you based on what i know, from the point where you need help
<j31>I've written the image on 3 different flash drives and none is working
<rekado_>j31: I’ve had problems with two new USB sticks (with 0.13 and 0.14); it worked without problems on an older stick (both 0.13 and 0.14).
<j31>I'll try and see if using an old usb can help
<g_bor>rekado_: It seems that no other interesting output is there.
***Guest31815 is now known as sturm
<rekado_>g_bor: cross-module inheritance is not a good idea. It can lead to top-level loops.
<rekado_>g_bor: better put the riscv-binutils in the same module as binutils itself.
<g_bor>rekado_: Yes, building the bootstrap binaries would be fine, except the standard toolchain doesn't support riscv. They practially work with a fork of the toolchain, no easy patch available, and no standalone tarballs.
<sturm>I'm attempting to package PostGIS and GDAL - but seems like the requirement json-c is missing a file called "json_object_private.h". It seems to be part of the json-c source, so any ideas why it wouldn't be coming through in the built package?
<g_bor>rekado_: I currently decided not to inherit from binutils, but what you say is worth considering.
<g_bor>rekado_: my biggest concern is, once I can build the cross toolchain the gnu build system will require additional logic to select the correct gcc,glibc,binutils...
<g_bor>rekado_: I still don't know what would be the best approach here...
<j31>hey guys, every time I write the 0.14 i686 I get this error after an fdisk -l, gpt pmbr size mismatch ..., parted automaticaly fixes this but the usb can't boot, before and after the fix
<rekado_>sneek: later tell sturm The name “json_object_private.h” indicates that this is not part of the public API, which is why the build system does not install it. You may need to add the sources of json-c to the package to be able to access it.
<quiliro>I think that the most efficient way to get and give guix support would be to program a bot to check the relevant parts of the manual regarding the question asked and print the lines and sections which are of interest
<wigust>quiliro: There is no reloading services support currently, so you should stop them before 'reconfigure' to reload them during 'reconfigure'.
<str1ngs>reconfigure will still upgrade the service no? it just requires a reboot to activate the system profile?
<catonano>I was going to ask thhe exact same question
<quiliro>If the manual is correct it will not upgrade running services: "The command [reconfigure] starts system services specified in FILE that are not currently running; if a service is currently running, it does not attempt to upgrade it since this would not be possible without stopping it first."
<rekado_>apteryx_: the root user’s profile is not the system profile.
<apteryx_>rekado_: right. root profile is just another user profile ;)
<str1ngs>but.. with foreign disto root profile is important
<apteryx_>yeah, it contains the guix-daemon package, or so I understand.
<pkill9>hey, i dunno if it's a glitch, but `guix build` couldn't find a patch in my $GUIX_PACKAGE_PATH, so I copied it to ~/.config/guix/latest/gnu/packages/patches (I'd prefer not to as you're not supposed to modify anything in the guix store right?) and it found it. Does nayone know where I may have gone wrong?
<pkill9>the patch came from my $GUIX_PACKAGE_PATH/gnu/packages/patches
<str1ngs>pkill9: ~/.config/guix/latest is not the store