worldofpeace changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 20.09 Nightingale ✨ https://discourse.nixos.org/t/nixos-20-09-release/9668 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.09 RMs: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
raboof has quit [Ping timeout: 272 seconds]
raboof has joined #nixos-dev
<catern> is there a good bug/issue/document anywhere documenting why NixOS/Nix packages on foreign distros need nscd? (I understand why myself but wondering if there's something I can link to)
rajivr has joined #nixos-dev
leungbk has quit [Ping timeout: 256 seconds]
teto has quit [Ping timeout: 244 seconds]
leungbk has joined #nixos-dev
cole-h has quit [Ping timeout: 260 seconds]
ris has quit [Ping timeout: 256 seconds]
justanotheruser has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-dev
leungbk has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 256 seconds]
leungbk has joined #nixos-dev
Jackneilll has quit [Ping timeout: 272 seconds]
abathur has joined #nixos-dev
Jackneilll has joined #nixos-dev
leungbk has quit [Ping timeout: 272 seconds]
<samueldr> Ericson2314: updated #93368 with binutils 2.34, it all *seems* to work, though built products untested for the time being
<{^_^}> https://github.com/NixOS/nixpkgs/pull/93368 (by samueldr, 16 weeks ago, open): Initial support for OpenRISC 1000
<Ericson2314> samueldr: nice!
<Ericson2314> i took a look, looks good
<Ericson2314> just let me know when you remove the WIP :)
<samueldr> you're fine with the way we're bringing in multiple binutils?
<samueldr> I mean, I guess it's fine
<samueldr> though I really had no idea how to do it
<samueldr> I wonder if it'd be preferable to have a crust built with it before we merge it, but at the same time, waiting will only make it take longer before or1k support is in Nixpkgs
<Ericson2314> samueldr: yeah I'm fine
<Ericson2314> you can add a TODO for removing the old one or something
<abathur> if anyone has thoughts/dreams/nightmares/cravings related to a Nix uninstaller, I could use some feedback on a proof-of-concept in https://github.com/NixOS/nix/pull/4181#issuecomment-724419256
<abathur> maybe not if you've been deeply wounded by shell :)
<siraben> abathur: I recently reinstalled Nix on macOS Catalina to see what the process was like, it was more involved than I'd like it, I also have FileVault on
<abathur> nod
leungbk has joined #nixos-dev
stoile has quit [Ping timeout: 256 seconds]
leungbk has quit [Ping timeout: 258 seconds]
stoile has joined #nixos-dev
kalbasit has quit [Ping timeout: 272 seconds]
justanotheruser has quit [Ping timeout: 244 seconds]
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-dev
Emantor has quit [Remote host closed the connection]
Emantor has joined #nixos-dev
justanotheruser has joined #nixos-dev
orivej has joined #nixos-dev
cole-h has joined #nixos-dev
lopsided98 has quit [Ping timeout: 260 seconds]
lopsided98 has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
saschagrunert has joined #nixos-dev
teto has joined #nixos-dev
tom39291 has quit [Ping timeout: 256 seconds]
tom39291 has joined #nixos-dev
harrow has quit [Quit: Leaving]
harrow has joined #nixos-dev
FRidh has joined #nixos-dev
<zimbatm> samueldr: noted, I will avoid bridging more IRC channels to Discourse. I think for low-volume channels the bridge can actually help add more people to the conversation. And I also agree that the bridge is favouring Discord which is why I haven't added it to #nixos and #nixos-dev.
<zimbatm> one of the best thing about Discord in terms of UX is that every user can see all the channels, whereas IRC, each user has to put in the effort to find and join. And poll for new channel existence.
<zimbatm> but that's also why double-puppettering is not really possible between IRC and Discord. Contrary to Matrix which has the same channel-joining approach than IRC.
<zimbatm> which is unfortunate
ehmry has joined #nixos-dev
__monty__ has joined #nixos-dev
taktoa[c] has quit [Ping timeout: 260 seconds]
jkkm has quit [Read error: Connection reset by peer]
ghuntley has quit [Read error: Connection reset by peer]
ghuntley has joined #nixos-dev
manveru has quit [Ping timeout: 272 seconds]
jkkm has joined #nixos-dev
taktoa[c] has joined #nixos-dev
manveru has joined #nixos-dev
srhb has quit [Ping timeout: 272 seconds]
<roberth> niksnut: please merge this 1-line fix for the recent nixUnstable/hydra issue https://github.com/NixOS/nix/pull/4242/files
srhb has joined #nixos-dev
orivej has joined #nixos-dev
cole-h has quit [Ping timeout: 272 seconds]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
alp has quit [Ping timeout: 244 seconds]
alp has joined #nixos-dev
<Ericson2314> zimbatm: FWIW i think matrix has some things to group channels so the listing mechanism could be more useful; I'd say this is more a client than protocol issue
<Ericson2314> not that that helps you in the medium turn, though :)
<qyliss> they're working on that for Element IIRC
<symphorien[m]> there is a concept of community that can regroup channels iirc
<Ericson2314> * not that that helps you in the medium term, though :)
<Ericson2314> :) matrix is eventually-perfect
<worldofpeace> symphorien: I've always wondered how to do this, like I want to group the bridged nix channels into a Nix community
<worldofpeace> the feature feels a bit unloved idk, I enjoy the "switching" it can evoke
<symphorien[m]> I've no idea. Someone invited me to such a community one day, but I don't know how to create one.
AlwaysLivid has quit [Quit: We are a collection of 7 billion codependent atoms. Stop hating based on constructs and come along for the ride.]
AlwaysLivid has joined #nixos-dev
<siraben> file hello_new gives me this,
<siraben> hello_new: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /nix/store/3s2x09bbl1xss1lcx7a6dbw69zmip3gx-glibc-2.32-armv7l-unknown-linux-gnueabihf/lib/ld-linux-armhf.so.3, for GNU/Linux 2.6.32, not stripped
<siraben> It's a dynamic executable that I cross-compiled but failed to run on the target
<siraben> Looks like the interpreter is set to the nix store?
<clever> siraben: you must use nix-copy-closure to copy hello_new to the target
<clever> and nix will copy the ld-linux.so over as well
<siraben> clever: but the target doesn't have nix?
<clever> then you need to either use static binaries, or install nix
<clever> or use a namespace'd chroot
<siraben> here's the current toolchain https://github.com/NixOS/nixpkgs/pull/102503/files , do I need to modify it or does it look ok?
<siraben> it's similar to the other ARM-based cross targets, so I don't think it needs modifying
<siraben> I built GNU hello with `nix-build . --argstr system "x86_64-linux" -A pkgs.pkgsCross.remarkable1.hello`
<clever> in general, any binary built by nix, must be copied with nix, and the target must have nix to run it
<siraben> Isn't Nix quite space-heavy? I only have 4 GB on the target
<clever> du -hsc $(nix-store -qR ./result) | sort -h
<clever> siraben: this will tell you how much space the package will use, when copied to the target
<siraben> clever: I need to install Nix first, right?
<clever> yeah
<siraben> Yeah, is that base installation space-heavy?
alp has quit [Remote host closed the connection]
<siraben> Hm, but how does cross-compilation to targets like AVR work without a Nix install on target?
<clever> its fairly light
<clever> AVR uses static linking, not dynamic linking
<clever> so everything you need is in a single file
alp has joined #nixos-dev
<clever> 2020-11-10 11:00:16 < clever> then you need to either use static binaries, or install nix
<siraben> I see.
<siraben> How would I compile it statically without needing to write the full derivation?
<siraben> Just a `nix-build . --argstr system "x86_64-linux" -A pkgs.something.remarkable1.hello`
<siraben> Oh also, the only user on my tablet is `root`, is that file?
<siraben> fine*
<clever> yeah, that should be fine
<clever> you can try adding pkgsStatic into the mix
<clever> > pkgsCross.raspberryPi.pkgsStatic.hello
<{^_^}> "<derivation /nix/store/g49amhvzdkljcrmj5ljx1ga53p3fajsq-hello-2.10-armv6l-unknown-linux-musleabihf.drv>"
<clever> for example
<siraben> Ok
<siraben> trying to install Nix: "sh: sorry, there is no binary distribution of Nix for your platform"
<siraben> armv7l for the record
<siraben> clever: this didn't happen before with the previous cross system that used the company's provided toolchain, i.e.
<siraben> ```
<siraben> ```
<siraben> hello-old: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=59ad6b3b75276504561252315dc61584d36420da, not stripped
<siraben> Appears to still be dynamically linked but used the provided linker
alp has quit [Ping timeout: 260 seconds]
<clever> siraben: you can also install nix manually
<clever> one sec
<siraben> Ah, ok.
<clever> finding the expr...
<clever> siraben: it just uses pkgsCross to build a tar containing the nix binary, and then you manually import the db.sqlite backup after unpacking the tar
<siraben> I see.
<siraben> I'll try to get it to work without needing to install Nix on the target first and see.
<clever> you can also just make a tar around hello instead
<clever> and unpack that to / to get the full /nix/store it needs
<siraben> Oh, how so?
<clever> exactly the same way, just read arm-tar.nix
<clever> but you wont have any tools to manage /nix
<siraben> Also, would it be beneficial to eventually write some documentation regarding adding cross targets?
<siraben> I see.
<clever> that could be useful
<siraben> clever: what could be a way to make it work using dynamic linking? Is it a matter of missing the appropriate Linux kernel headers?
<siraben> custom kernel at https://github.com/reMarkable/linux/
<clever> its a matter of you not copying glibc to the target
<clever> /nix/store/3s2x09bbl1xss1lcx7a6dbw69zmip3gx-glibc-2.32-armv7l-unknown-linux-gnueabihf has to also exist on the target
<clever> and if you use nix-copy-closure, thats fully automatic
<siraben> Right, but only if Nix is installed on target as well?
<clever> you can use a tar file to cheat around that
<clever> but then you have no way to know what you can safely delete, when you get 20 copies installed
<siraben> Ah, and I suppose because I was using the prebuilt linker before, it properly linked glibc
alp has joined #nixos-dev
<clever> siraben: you can build your own with this expr
<siraben> clever: ok
leungbk has joined #nixos-dev
<siraben> the statically linked binary worked, but it's 98684 bytes vs. 34332 bytes over the old one, hm.
<clever> thats what static linking does
<siraben> Yeah
<siraben> I'm wondering how I could do it without statically linking, like before
<clever> nix-copy-closure and remove pkgsStatic
kalbasit has joined #nixos-dev
saschagrunert has quit [Remote host closed the connection]
alp has quit [Ping timeout: 272 seconds]
<abathur> repeat from last night: if anyone has thoughts/dreams/nightmares/cravings wrt a Nix uninstaller, I could use feedback on a partial proof-of-concept. Screencast @ https://asciinema.org/a/zzFgKW03XFA89aBLFa29ZGAYa?t=54 and discussion at https://github.com/NixOS/nix/pull/4181#issuecomment-724419256
alp has joined #nixos-dev
<siraben> abathur: i'd love to review it sometime
<siraben> though I don't have another partition so I'll need to clear some time to test
alp has quit [Ping timeout: 240 seconds]
saschagrunert has joined #nixos-dev
<abathur> yeah; frustrating limitation of the form :)
<siraben> abathur: how would you nixpkgs-review that?
<siraben> I haven't tested Nix PRs before
<abathur> assuming I'm not missing something, it's a little cumbersome
saschagrunert has quit [Quit: Leaving]
<abathur> though there is a little movement towards making installer tarballs available for PRs and such
<abathur> so I'm just building a darwin-only tarball myself, and self-hosting a modified install script that points to it
<siraben> so do you reinstall Nix using that?
<abathur> I'll point CI installs at them, and I have a spare macbook at the moment
<abathur> so on the macbook I'll take an apfs snapshot before install with `tmutil localsnapshot`
<abathur> install, test, rollback
<siraben> I see.
<abathur> unfortunately macos "forgets" user-taken snapshots after 24h, so I've had to learn to be careful with it to avoid reinstalling
<siraben> macOS snapshots that are not Time Machine?
<siraben> I haven't used those before
<abathur> though, with the proto-uninstaller code in this one, it's a little more feasible to install/uninstall
<abathur> yeah
<siraben> How do I access that?
<abathur> it's still timemachine taking them, but it's slightly different
<siraben> Ah, `tmutil`
<abathur> I can take one with `tmutil localsnapshot`, and then reboot into recovery with command + r, and there's an option to restore from time machine there
<siraben> Nice. Why would macOS delete them after 24h?
<abathur> I assume they're trying to avoid them piling up, not really sure
rajivr has quit [Quit: Connection closed for inactivity]
<abathur> I found an option somewhere about specifying that it should restore a snapshot on reboot, but I haven't figured out how/if it can be used here
<siraben> Do you dual boot? What's do you use for backup between macOS/Linux? I'm using borgbackup ATM
<abathur> I don't, I have a separate nixOS system
<abathur> I use restic to back up some farily narrow slices of project/user data, and my dotfile repo for config/settings stuff
<siraben> I see
<siraben> clever: http://ix.io/2DGa
<abathur> if you don't have a spare system, the post includes an asciinema cast and CI logs; not the same, but better than nothing
<abathur> I've also seen something going around about macOS VMs, but I haven't used it yet myself
abbe is now known as abbe__
justanotheruser has quit [Quit: WeeChat 2.9]
justanotheruser has joined #nixos-dev
ris has joined #nixos-dev
cole-h has joined #nixos-dev
supersandro2000 has quit [Read error: Connection reset by peer]
supersandro2000 has joined #nixos-dev
costrouc has joined #nixos-dev
<cole-h> Hi niksnut -- I hate to bother you like this, but is there any chance you could take a look at https://github.com/NixOS/nix/pull/3961/? I think it would be nice to get it merged before you're done with the work on your progress-bar branch.
leungbk has quit [Ping timeout: 256 seconds]
leungbk has joined #nixos-dev
alp has joined #nixos-dev
AtnNn has quit [Ping timeout: 240 seconds]
julm has quit [Remote host closed the connection]
julm has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
AtnNn has joined #nixos-dev
<infinisil> cole-h: I think this might actually be the reason for not merging it. Since the whole output format is going through some major changes right now
<infinisil> Didn't look all too closely at the PR though, maybe I'm mistaken
<ivan> wireguard doesn't seem to build with the linux 5.4.76 in 20.09 git
leungbk has quit [Ping timeout: 258 seconds]
<infinisil> Isn't wireguard in-tree?
<qyliss> not in 5.4
<qyliss> I think it was 5.6
<qyliss> yeah
leungbk has joined #nixos-dev
<infinisil> Ah
erictapen has joined #nixos-dev
<cole-h> infinisil: I see; fair enough.
supersandro2000 has quit [Ping timeout: 264 seconds]
__monty__ has quit [Quit: leaving]
jonringer has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
erictapen has quit [Ping timeout: 256 seconds]
erictapen has joined #nixos-dev