efraim has quit [Remote host closed the connection]
efraim has joined #nixos-aarch64
{`-`} has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 248 seconds]
vcunat has joined #nixos-aarch64
Bogdacutu has joined #nixos-aarch64
<sphalerite> samueldr: the narinfos contain signatures
<sphalerite> samueldr: so it's all good :)
<sphalerite> oh wait "outside channel" never mind me
<sphalerite> yay it works, thanks for the mirror
<sphalerite> aww, gfortran isn't included in it
orivej has joined #nixos-aarch64
Bogdacutu has quit [Ping timeout: 240 seconds]
LnL has quit [Quit: exit 1]
LnL has joined #nixos-aarch64
<Dezgeg> it should be given that it's a dependency of boost
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 255 seconds]
vcunat has quit [Ping timeout: 264 seconds]
<grw> has anyone looked at creating DTB overlay module for nixos?
<grw> it seems like more peripherals on sbcs need activating via overlay
<grw> maybe we can merge original DTBs with overlays into a new directory, and point extlinux's FDTDIR to it?
<grw> could also just apply overlay when first copying dtb i suppose
<Dezgeg> ideally you would leverage U-Boot's capability to merge DT overlays
<Dezgeg> but I'm not sure if that possibility is exposed in any way in the extlinux.conf files
<Dezgeg> and I have a fear that doing that opens a can of bikeshedding
<Dezgeg> so having a NixOS module to do the overlay application sounds quite good
<grw> yeah would be nice to have uboot support too
<grw> if dtoverlay configfs module is ever merged, it could even work on nixos-rebuild switch
<samueldr> sphalerite, Dezgeg, normally my mirror should be complete; there weren't any errors and it syncs hourly. if gfortran isn't there, I don't think it should be in the upstream one ?
<samueldr> (I may be wrong)
<sphalerite> huh, it's there after all
<sphalerite> maybe I just did somethign wrong
<samueldr> there were files synchronized during the last 6 hours
<samueldr> maybe your channel was more up to date than the built artifacts?
<samueldr> (but between 2 and 6 AM, your message being at 2AM, no files were synchronized during the (successful) attempts)
<sphalerite> ¯\_(ツ)_/¯ it works now regardless
<sphalerite> weird, linux also didn't come from the cache at the time although I'm pretty sure that gets built
<sphalerite1> Nope it's still not coming from the cache
orivej has joined #nixos-aarch64
s33se has joined #nixos-aarch64
<samueldr> sphalerite1: and using Dezgeg's cache?
<sphalerite> samueldr: is it back up?
<sphalerite> nope
<sphalerite> so I have no way of checking really
<samueldr> weirdly enough, I don't seem to have trouble reaching dezgeg's cache, either at home or my dedicated server
<sphalerite> I'm still getting 503s from it
<samueldr> I mean, I hope lftp would tell me if it got 503s
<sphalerite> warning: unable to download 'https://www.cs.helsinki.fi/u/tmtynkky/nixos-arm/channel/ssb1a9l5m7r0hr43zh385m3b4bi2rh1w.narinfo': HTTP error 503 (curl error: No error); retrying in 306 ms
<samueldr> hmmmmmmmmmmm, though I think I have an understanding of the situation
<samueldr> could the 503 stem from a 404 that would normally be handled by the drupal website?
<sphalerite> iirc the narinfos were working fine before, and the nars weren't \:|
<samueldr> drupal-based*
<samueldr> because I *cached 62GB of nar and narinfos* less than 24h ago, during the time people were hitting 503s
<samueldr> but this was done using the apache directory listing by lftp
<sphalerite> ah
<samueldr> so my guess is that 503s are really 404s
<samueldr> (in that particular case)
<sphalerite> of course nix doesn't actually handle that case well :(
<samueldr> if the host can use .htaccess, maybe set a specific 404 for the nixos-arm bits?
<samueldr> a static 404*
vcunat has joined #nixos-aarch64
bkchr[m] has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
vcunat has quit [Quit: Leaving.]
tomberek has joined #nixos-aarch64
<tomberek> Howdy, I'm getting NixOS working on a TinkerBoard. At the moment I've got most things working (HDMI, console output, WiFi), still working on bluetooth. Some of this becomes a DTB rebuild all the time. Is there a faster way to ask NixOS to only rebuild the dtbs folder vice all of the kernel? At the moment I'm using the boot.kernelPatches to patch the dtb.