<colemickens>
lovesegfault: I've got an intel igpu I'm on now and access to a gtx1080.
<colemickens>
I also don't like commits without PRs but it's not a universal opinion, apparently. It's also really frustrating to see it lodged as a complaint against nixpkgs/nixos and not be able to argue against it.
<colemickens>
I'd feel a lot better with "yes, everything is PR'd, yes, committers are required to have 2FA".
<ashkitten>
colemickens: i understand that some workflows need direct commit but it scares me that maintainers won't get pinged about it like with prs.. i think a good compromise might be to have the bot ping maintainers in the comments of all direct commits
<ashkitten>
that way they always see when changes are made, whether it's a pr or direct commit
<lovesegfault>
what workflows need commit-to-master?
<colemickens>
mailing list patches
<colemickens>
(I think)
<lovesegfault>
We have a mailing list?
<ashkitten>
i'm not sure what workflows exactly, honestly
<colemickens>
idk there's a discourse post about it. someone ... ports patches from some ML to nixpkgs I think.
<colemickens>
So, there's sort of another pipeline for getting changes into nixpkgs, in a way. Not sure how I feel about that.
<ashkitten>
this stuff is terrifying considering so much infra from commit to deploy is entirely automated
<colemickens>
We ("someone") should write an RFC.
<colemickens>
Of course, then I'd have to write an RFC forcing people to use GH and I'm not in the least bit interested in doing that right now, so.
<ashkitten>
right now, if someone pushed a change to master and release that turned every nixos machine into a botnet... how many machines have auto updates enabled?
<colemickens>
It would sort of be inappropriate to joke about "TIAS"...
ky0ko has joined #nixos-chat
<ashkitten>
what's that?
<colemickens>
TIAS = "try it and see"
<ashkitten>
heh, oof
<colemickens>
I feel sort of strongly about this, but don't know what to realistically do about it.
<colemickens>
I don't know what I'm supposed to say when... a certain someone happily reminds everyone that nixpkgs has a long committer list and no 2FA requirements. Because it's true and it's a bad look.
<ashkitten>
try to convince as many people as possible that it's a real problem that needs fixing
<colemickens>
(well, those things plus the lack of branch protection)
<colemickens>
supersandro2000: alright, my bad. very happy to hear that.
<supersandro2000>
I don't care about mailing lists but if people want to use it then we can't forbit that
<supersandro2000>
but patches from there must be proxied into a PR and if there is more changes required the PR creator needs to take care of that
<colemickens>
Maybe instead of mirroring the PRs from the ML into GH, there could be something like https://nixpk.gs that just indexes all PRs and the ML "PRs".
<colemickens>
At least to document the metadata.
<colemickens>
Plus it could give us a metadata backup for when our source platform disappears our data.
<ashkitten>
maybe we should move to something besides gh that everyone can be more okay with, and that we can more tightly control while respecting workflows
<colemickens>
Because I also just hate winding up on a nixpkgs commit and wondering "where the heck did this come from"
<aleph->
ashkitten: I'd agree with that. Too many core platforms tied to GH.
<colemickens>
lots of bikeshedding, lots of potential hiccups along the way. I have gripes with all of the self-host options too.
<{^_^}>
rfcs#79 (by dasJ, 17 weeks ago, closed): [RFC 0079] No more direct pushes to master and release branches
<cole-h>
There already was an RFC
tilpner has quit [Read error: Connection reset by peer]
tilpner_ has joined #nixos-chat
<cole-h>
(oh, heh, this was already posted in -dev)
<colemickens>
I missed it, thanks for posting it. I didn't have much to add though, hard to argue with too much with anything in it.
tilpner_ is now known as tilpner
BaughnLogBot has quit [Ping timeout: 240 seconds]
BaughnLogBot has joined #nixos-chat
<supersandro2000>
I think a few low hanging fruits to make it harder to sneak something in would be to disallow fetching commits which do not belong to the mentioned github repo and changing node2nix to only allow fetches from npmjs
supersandro2000 has quit [Disconnected by services]
supersandro20002 has joined #nixos-chat
<supersandro20002>
also we could maybe label PRs from people who have less than 10, 30 or 50 commits in nixpkgs
supersandro20002 is now known as supersandro2000
supersandro2000 has quit [Client Quit]
supersandro2000 has joined #nixos-chat
<cole-h>
Hard -1 on that.
<cole-h>
Gatekeeping doesn't seem like something we'd want to do.
<cole-h>
"Oh, you don't have 38921080 commits in Nixpkgs yet and you made this simple mistake? Shows how much you know, loser."
<cole-h>
Of course, (I'd hope) our community isn't like that. But I don't think it's a good idea to add something with the potential to alienate people like that.
<cole-h>
From the last couple days of playing with zrepl, I think the only thing I don't like about it is that the `grid` specification isn't easy (for me) to understand, compared to znapzend's plan configuration
<gchristensen>
me too
<gchristensen>
though I find znapzend's a bit confusing too, but only in terms of syntax
<supersandro2000>
not gatekeeping but making reviews and mergers more easily aware that this user new
<supersandro2000>
maybe only for people with less than 10
<supersandro2000>
this could encourage people to take a closer look and guide new contributors more closely
<cole-h>
I think the "first-time contributor" is more than enough. People should be taking a close look and guiding contributors (kindly) regardless, IMHO.
<lovesegfault>
Reading RFC79 made me wish we used `bors` like rust does
<lovesegfault>
just rollup daily and merge the rollup
<cole-h>
For the casual observer: bors isn't actually bors-ng. It's actually https://github.com/rust-lang/homu, but the bot user (or whatever) is named bors.
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner_ has joined #nixos-chat
tilpner_ is now known as tilpner
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
BaughnLogBot has quit [Ping timeout: 260 seconds]
BaughnLogBot_ has joined #nixos-chat
BaughnLogBot_ is now known as BaughnLogBot
Dotz0cat has quit [Ping timeout: 240 seconds]
Dotz0cat has joined #nixos-chat
krkini has joined #nixos-chat
kini has quit [Ping timeout: 264 seconds]
BaughnLogBot has quit [Ping timeout: 264 seconds]
BaughnLogBot has joined #nixos-chat
krkini has quit [Ping timeout: 240 seconds]
kini has joined #nixos-chat
abathur has quit [Ping timeout: 272 seconds]
waleee-cl has quit [Quit: Connection closed for inactivity]
<supersandro2000>
I don't think we even need this
<supersandro2000>
just create a PR, have the tab open for 20 minutes and then merge it if you can't wait
<supersandro2000>
or just eval everything locally if you have the RAM
kini has quit [Quit: bye]
kini has joined #nixos-chat
omnd has quit [Ping timeout: 265 seconds]
BaughnLogBot has quit [Ping timeout: 260 seconds]
BaughnLogBot_ has joined #nixos-chat
BaughnLogBot_ is now known as BaughnLogBot
kini has quit [Ping timeout: 264 seconds]
kini has joined #nixos-chat
numkem5 has joined #nixos-chat
numkem has quit [Ping timeout: 265 seconds]
numkem5 is now known as numkem
FRidh has joined #nixos-chat
kini has quit [Excess Flood]
kini has joined #nixos-chat
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-chat
<cole-h>
gchristensen: if https://github.com/zrepl/zrepl/issues/92 is ever fixed, zrepl would be much less confusing. I like how znapzend's snapshots happen at set times in the specified plan, rather than "5 minutes after the daemon happened to start"
<eyJhb>
Always nice to just do a `nix-build && ./result`, and then seeing all systems being successfully updated!
<eyJhb>
Fun little game to play while having online lectures, see if your router can update without loosing connection :D
Mic92 has quit [Quit: WeeChat 3.0.1]
Mic92 has joined #nixos-chat
<siraben>
eyJhb: your router runs NixOS?
<eyJhb>
siraben: It sure does! :D
<eyJhb>
#nixos-on-your-router :D
BaughnLogBot has quit [Ping timeout: 265 seconds]
BaughnLogBot has joined #nixos-chat
<Taneb>
I'd like to ask, in the least dismissive way possible, why I should care about the OS my router runs
<eyJhb>
Taneb: Security
<eyJhb>
Is a simple answer to that
<eyJhb>
Multiple other nice things, but you don't need to CARE as such, but if you need anything more advanced NixOS is nice. But vendors have a history of being.. Shitty :p
<srk>
unified configuration management :)
<srk>
I've considered generating openwrt configs recently
<srk>
I would prefer to run nixos on omnia if I manage to get its bootloader crunch extlinux.conf tho
<eyJhb>
ie. the router in my laundry room where I live is hackable :D
<Taneb>
To summarize: improved security and flexibility compared to vendor-shipped operating system
<hexa->
confidence in the thing :)
<hexa->
since it sits at the very core of your network
<philipp[m]1>
I went the other way: Don't trust the network and use wg locally with the ipv6 local link addresses. Works beautifully.
Jackneill has quit [Ping timeout: 264 seconds]
abathur has joined #nixos-chat
Jackneill has joined #nixos-chat
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-chat
FRidh has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-chat
<eyJhb>
srk: Can't remember :(
<eyJhb>
NetGear maybe...
<srk>
x86?
<eyJhb>
Taneb: Yes, also, up-to-date stuff so bugfixes etc.
<eyJhb>
Might be. not sure :p It is 2 years ago I tried it
<srk>
check uname -a :D
<eyJhb>
Maybe some other time :p Don't want to exploit it :p
* srk
demands a NixOS router proof :D
FRidh has quit [Ping timeout: 272 seconds]
FRidh has joined #nixos-chat
omnd has joined #nixos-chat
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-chat
<Ke>
also nixos router config can migrate to new hw
<cransom>
i don't do my main routing on the embedded stuff, i like cpu to do other stuff than only move packets. but, the barest of features thats i require are rollback and a single config file.
<gchristensen>
zfs's nopwrite feature is cool... it lets me run `sudo qemu-img convert -p mac_hdd_ng.img -O raw /dev/zvol/macos/installs/catalina`, then make a change to the .img in the middle of the file, re-run the same command and only have a few bytes of the zvol actually be considered changed
omnd has quit [Ping timeout: 256 seconds]
<veleiro>
i would also like nixos on omnia, but i'm pretty much done with nixos and armv7
<veleiro>
even containers
<Ke>
is that useful?
omnd has joined #nixos-chat
<gchristensen>
veleiro: armv7 being slow to compile for makes it so hard to do :(
<veleiro>
it will change with the intensional store model and more advancements with arm64 i assume
<veleiro>
but i dont know when that will be
<veleiro>
re-compiling whole trees with the majority of the content not changing is what kills utility
<veleiro>
especially if you're on 3 mbit connection like i am
<infinisil>
Ahhh my github notifications are piling up
<aanderse>
so have fooPackages which contains a bunch of packages
<aanderse>
i want the packages inside of fooPackages to be overridable, composable, all that good stuff
<aanderse>
packages within my fooPackages will depend on each other, and i want it so i can override packages in fooPackages and have all that properly work out
<FRidh>
Its heavily based on the Python packaging. How I wish our stdenv was in say Python, so we could abstract out hooks more easily, and share more structure along languages/frameworks.
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-chat
<lovesegfault>
So, more on that sway issue
<lovesegfault>
I've overlayed kernelPackages to try and pinpoint where the problem happened
<lovesegfault>
it's somewhere between 5.10.15(working) and 5.10.17(not working)
<infinisil>
It's interesting how the video feed from the drone cuts out right around the time as it cuts the cables (because of course, the drone crashes in a bit)
<infinisil>
gchristensen: Looks like the drone is flying pretty near to the ground
<philipp[m]1>
It's their raw image feed for the nerds. I rather have them publish everything than "just the good ones".
<etu>
Isn't it like something that they are a "publicly founded organization" and therefore kinda "have to" publish "all the things"? Not sure how that works but I've read that at some point.
<samueldr>
philipp[m]1: sure, I'm definitely not against it
<samueldr>
just incredibly funny they have "garbage" in there
<philipp[m]1>
One man's garbage...
<samueldr>
see the quotes :)
<samueldr>
it's art!
<samueldr>
the lush green skies of mars!
FRidh has quit [Quit: Konversation terminated!]
<lovesegfault>
samueldr: what do I do if I need a clone of the kernel repo starting at a given hash
<lovesegfault>
I'm doing a bisect and I want to use remote builds, but uploading the whoel 4.7GB of repo on every step is coconuts
<samueldr>
uh, use `src = builtins.fetchGit /path/to/checkout`...
<lovesegfault>
huh
<lovesegfault>
TIL
<samueldr>
IIRC that will only bring the revision it's currently at on the remote builder
<samueldr>
well, in the store
* lovesegfault
tries
<samueldr>
I assume you had `src = /path/to/checkout`
<lovesegfault>
yup
<samueldr>
otherwise, I'm not sure about what kind of git shenanigans you can do
<lovesegfault>
now it only copies 932MiB :P
<lovesegfault>
solution, bisect on both the local and remote machine and pray the hashes are the same
<lovesegfault>
brain size: big
slack1256 has joined #nixos-chat
<ashkitten>
maybe with the upcoming xwayland release separate from xorg, the xwayland build in nixpkgs will be easier to work with
aleph- has quit [Ping timeout: 246 seconds]
__monty__ has quit [Quit: leaving]
aleph- has joined #nixos-chat
<aanderse>
adisbladis++ thanks again for sharing your thoughts on `makeScope`, nice and simple, got exactly what i wanted 👍
<{^_^}>
adisbladis's karma got increased to 141
<infinisil>
aanderse: Link?
<infinisil>
Ohh, irc logs
<aanderse>
infinisil: i'm not a functional programmer and there isn't great documentation on makeScope/newScope stuff if you aren't a functional programmer
<aanderse>
at least i assume thats the disconnect :)
<infinisil>
Yeah, very valid, and I've also had trouble with this before because of no docs. Was able to muddle through with a bunch of source research, which is not ideal..
<aanderse>
well... thanks no adisbladis i have it working now