<supersandro2000>
the great part is: it is under a trustable org and repo
<supersandro2000>
so you could inject malicious patches like this and make them seem legit
cole-h has joined #nixos-chat
<andi->
Never trust GitHub?
<samueldr>
rather: understand its failure modes
danderson has quit [Remote host closed the connection]
danderson has joined #nixos-chat
cjpbirkb1 has joined #nixos-chat
cjpbirkbeck has quit [Ping timeout: 240 seconds]
cjpbirkbeck has joined #nixos-chat
cjpbirkb1 has quit [Ping timeout: 272 seconds]
<energizer>
i want to run a raspi with nixos. is this what i should use? https://github.com/Robertof/nixos-docker-sd-image-builder I just tried it and got "Service 'setup-qemu' failed to build: cgroups: cgroup mountpoint does not exist: unknown" so I'm wondering if I should try to debug or look at another solution.
<thefloweringash>
eyJhb: oh wow, I’d forgotten about that
<eyJhb>
Yay ! Do you use it yourself thefloweringash ?
<eyJhb>
Would be so cool to upstream it at some point, even if it is a BIG change
<thefloweringash>
No. That’s not immediately usable. It was mean to be the basis for upstreaming to nixos that kept the old interface and was bug-for-bug compatible
<thefloweringash>
So it has a bunch of test cases that use nixos vms to generate old and new and compare them... somehow. I’ve forgotten a lot of the details
<eyJhb>
Always the nice "bug-for-bug" :p
<eyJhb>
Also, 1 commit, but it still seems nice
<eyJhb>
Wondering if I should still switch to nftables, or just stay with iptables. Seems eaiser to just stay...
<thefloweringash>
I think there are (or were?) problems with docker not supporting nftables
<eyJhb>
Luckily (and maybe unluckily), it is on my router, so it has no Docker on it
<thefloweringash>
I use a different nftables for my router, which is a bit special, but just use iptables for host firewalls
<eyJhb>
But that also adds a lot more complexity
<eyJhb>
Pinged you in router instead :p Seems on-topic there
slack1256 has quit [Ping timeout: 260 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
<MichaelRaskin>
I have a strong feeling that Android alarms might have had a problem with alarm-set time and alarm-goes time on the different sides of DST change
aminechikhaoui has joined #nixos-chat
<samueldr>
MichaelRaskin: Apple's did for a good while
<samueldr>
if it's not still
<MichaelRaskin>
I even _have_ remind in the Debian chroot on Android, but I guess background-process-killing can always go crazy…
<infinisil>
cole-h: Nice
slack1256 has joined #nixos-chat
<cole-h>
infinisil: Nice
<evanjs>
Why are node packages so difficult on nixpkgs. Or in general 😢
<evanjs>
5,000,000 build systems, what could go wrong
<cole-h>
Yeah, nodePackages is a mess
<cole-h>
(I've said this before, but) it's why I moved my iosevka customizations into my config instead of overlaying the package
<cole-h>
Much easier to copy the package.json and run node2nix on it
<joepie91>
I use yarn2nix and that's been pretty much painless
<evanjs>
trying to package hyve right now...
<evanjs>
it has multiple components
<evanjs>
one uses vue
<evanjs>
which calls `vue-cli-service`
<evanjs>
which seems to be part of `@vue/cli`, but I can't manage to get it packaged with the generate.sh/node2nix infra
<evanjs>
it's failing to resolve vue-loader-v16
<evanjs>
but that alone resolves/builds fine
<evanjs>
just not when I try to package `@vue/cli-service`
<evanjs>
ughhhh
<evanjs>
The dev "advised against" packaging as it proved difficult for them to do so, and I mentioned that it would probably be trivial as a nixos module. at least the "not running in docker" part
<evanjs>
it's just the JS stuff that's tripping me up atm
<evanjs>
joepie91: yeah it worked great for this package, but currently I'm blocked on another thing a component of the package calls
<evanjs>
unless there's a better way to manage projects with multiple yarn sub-projects that I'm not seeing
lopsided98_ has quit [Quit: Disconnected]
lopsided98 has joined #nixos-chat
FRidh has quit [Quit: Konversation terminated!]
Synthetica has joined #nixos-chat
<andi->
As long as there is a npm-lock.json in the repo it is trivial to just use npm in the build.
<andi->
I've written a yarn.lock parser (in Nix) some weeks ago but that is still buggy..
neeasade has quit [Ping timeout: 265 seconds]
<aminechikhaoui>
evanjs https://github.com/nix-community/yarn2nix is pretty good, it also handles yarn workspaces which is I guess what you're calling sub-projects?
monsieurp has quit [Quit: Lost terminal]
monsieurp has joined #nixos-chat
slack1256 has quit [Remote host closed the connection]
lopsided98_ has joined #nixos-chat
lopsided98 has quit [Ping timeout: 260 seconds]
hmpffff has quit [Ping timeout: 240 seconds]
hmpffff has joined #nixos-chat
__monty__ has quit [Quit: leaving]
* colemickens
wonders if he should call it "the flowchart of NIX_PATH hell" or the "the impure eval tree of sorrow"
<joepie91>
the former is more self-descriptive but the latter would definitely do better as the title of a novel
<samueldr>
The impure eval tree of sorrow: NIX_PATH hell
<joepie91>
heh
<joepie91>
yes
<samueldr>
could be episodic!
<samueldr>
(continuing here MichaelRaskin) because hosted software these days really wants to not show you everything
<samueldr>
who in their right mind would want a result from over two years ago?
<joepie91>
where's that discussion cont. from?
<samueldr>
#nixos
<MichaelRaskin>
answer: an unprofitable user
<samueldr>
joepie91: further explanations, this is combined with my recent bad experience with both gitlab [software] and github
<samueldr>
where search results are not constant!
<samueldr>
sure, it's **hard**
<joepie91>
ah yes
<samueldr>
but when sending the same query literally seconds after gives you maybe more, maybe less results
<samueldr>
IIRC github tells you in a way that there could be more
<samueldr>
gitlab IIRC doesn't
<joepie91>
honestly I don't care about github's inconsistency since its results are usually useless anyway, consistent or not :D
<samueldr>
I have recently found way more relevant results for _specific_ bits with GitHub than any other search engine
<samueldr>
like if I'm searching for a specific driver from OEM source code dump, I can search identifying strings on it and it *generally* gives good results when unique enough
<samueldr>
(and assuming the source is on github)
<samueldr>
that can be strings that are sussed out from a binary even!
hmpffff has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hmpffff has joined #nixos-chat
hmpffff has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]