<danderson>
lovesegfault: ohai, I'm from the internet and I'm here to help
<danderson>
sup?
<danderson>
(and just as I say that I step away for a minute because the cats are VERY adamant that it is dinner time and I am committing a crime by not serving it right now)
h0m1 has quit [Ping timeout: 250 seconds]
<lovesegfault>
danderson: sorry, had to step away myself :D
<lovesegfault>
Just curious behavior I'd like to report, I can't ssh into any of my hosts anymore using their tailscale IPs
h0m1 has joined #nixos-chat
<danderson>
That is weird. This on nixos? What tailscale version? Got a tailscale IP for one of the machines so I can peek?
<danderson>
(can /query if you want to keep it private)
<lovesegfault>
On it
<lovesegfault>
sorry, delayed messages I'm on a war with some neighbors
<lovesegfault>
talyz, etu, and myself collab'd on it :D
<lovesegfault>
it's in nix-community
<gchristensen>
nice
<gchristensen>
this is why I should learn to use flakes :)
<lovesegfault>
I learned and it's a PITA
<lovesegfault>
happy to hop on a call and share what I know whenever
<lovesegfault>
ROI is dubious TBH
<gchristensen>
I think the ROI will be high eventually
<samueldr>
you don't need to use flakes to use that right now if you don't need to
<cole-h>
lovesegfault: A little heartbroken you didn't mention me
<samueldr>
could be a git submodule
<cole-h>
I *did* come up with the name, after all :P
<cole-h>
(/s)
<lovesegfault>
it's true, without cole-h we'd never have gotten to making it public or actually collaborating on anything :D
<lovesegfault>
cole-h++
<{^_^}>
cole-h's karma got increased to 143
<cole-h>
As we all know, the hardest thing is naming things
<gchristensen>
samueldr: or builtins.fetchGit
<samueldr>
yeah
<lovesegfault>
gchristensen: if you think it's worthwhile I'd love to do a "converting my NixOS config to flakes" workshop
<gchristensen>
but I think there are real advantages to flakes that submodules and builtins.fetchgit can't provide, once they've become really usable
* elvishjerricco
doesn't know much about what flakes are and at this point is too afraid to ask
<samueldr>
AFAIUI it's multiple concepts built together, but one of it is strict declaration of dependencies
<samueldr>
and another is a strict interface
<samueldr>
so you should know how to get the nixos module from a flake, as it will always be named the same way
<samueldr>
I don't really _know_ flakes, so I might be a bit off
<gchristensen>
standards around interop + support for sharing and external dependencies
<lovesegfault>
my main gripe with flakes is it's basically eelco's stream of consciousness code at this point
<lovesegfault>
after the RFC debacle
<gchristensen>
yes that is regrettable
<elvishjerricco>
`nixos-rebuild --flake .#mymachine` wtf is this syntax
<lovesegfault>
using # is the most insane portion of the design
<lovesegfault>
like, _why_
<lovesegfault>
you really
<lovesegfault>
*gotta pick the comment char?
<elvishjerricco>
So if A depends on nixpkgs and B, and B depends on nixpkgs, will each of them be given a different nixpkgs version if they've pinned different versions in flake.lock?
<elvishjerricco>
I don't like that... I much prefer trying to get everything on the same versions of dependencies when possible.
<gchristensen>
I'm pretty sure you can do that elvishjerricco
<gchristensen>
with "follows"
<lovesegfault>
you can with follows
<lovesegfault>
(see the last link I sent)
<elvishjerricco>
gchristensen: yea, but that's going to require a lot of follows boilerplate :P
<gchristensen>
I'm not sure that is true in practice but I dunno
<elvishjerricco>
Plus it requires investigating the inputs of all your dependencies, which is just annoying
<lovesegfault>
sort of thing that could be solved by an RFC-driven design
<cole-h>
the only real problem (which IIRC was solved recently?) was when follows wouldn't let you override a dependency to a different name or something
<cole-h>
e.g. someflake.inputs.nixpkgs.follows = "asdf" wouldn't cascade to the nixpkgs in flakes *it* depends on
<cole-h>
(and would error out)
<lovesegfault>
gchristensen: every person I've recommended that mouse to, by the way, has thanked me and never gone back
<lovesegfault>
highly recommend it :D
<lovesegfault>
I own 3
<gchristensen>
good to know :)
<gchristensen>
my mice are all, uh, 11 years old now
<gchristensen>
kensington slimblade and rollermouse red
<lovesegfault>
the MX Ergo is phenomenal
<elvishjerricco>
For something like nixpkgs, I feel like it'd be better for a flake to output an overlay rather than declare nixpkgs as an input.
<cole-h>
flakes can do that :P
<samueldr>
I don't think I'll ever stop using logitech mice
<samueldr>
their warranty service is wonderful, and the warranty being long (but shrinking) is (was) great for someone like me who... really uses... computer hardware
<samueldr>
I probably could buy that one switch that gave up the ghost, and service those mice... but then again I don't have the need for more than two
<gchristensen>
good to know :) off to bed ... g'night y'all
<cole-h>
o/ good night
waleee-cl has quit [Quit: Connection closed for inactivity]
<aaronjanse>
Aaah I just spend an hour tracking down the cause of a function being called that should never be called in a special scenario
<aaronjanse>
Turns out I was calling that function in a debugging statement :(
<aleph->
Heheh
endformationage has quit [Quit: WeeChat 2.9]
<elvishjerricco>
oh good. patching systemd requires rebuilding git and cargo and who knows what else just to build a nixos image. Why??
<infinisil>
elvishjerricco: Might be related to udev
<infinisil>
(since udev = systemd)
<elvishjerricco>
infinisil: Why would git depend on udev?
<infinisil>
Hm, no idea
<infinisil>
But I wouldn't be surprised for udev to be a deep dep in general
<elvishjerricco>
Is there a why-depends for .drv?
<lovesegfault>
git depends on the whole universe IIRC
<lovesegfault>
because it depends on something for docs
<infinisil>
elvishjerricco: nix-store -q --tree $(nix-instantiate '<nixpkgs>' -A git)
<lovesegfault>
Maybe I'm misremembering
<infinisil>
So yeah, git does transitively depend on systemd
<elvishjerricco>
openssh depends on libfido which depends on systemd-minimal
<elvishjerricco>
this is why other distros don't like us :P
<infinisil>
lovesegfault: What would that do?
<lovesegfault>
infinisil: I'm just horsing around, there's a lot more stuff that would need to exist for something like that to work
<lovesegfault>
Have you ever used Gentoo / do you know about USE flags?
<infinisil>
Nope!
<elvishjerricco>
I guess content addressable builds will be pretty good at preventing these mass rebuilds for stuff like this. My systemd package will be changed, so libfido will be rebuilt, but as long as its reproducible then it'll produce the same output and everything else stays the same
<elvishjerricco>
AFAIU use flags are basically configuration options for telling gentoo how to build and install stuff. So !docs would mean don't bother building docs
<lovesegfault>
TL;DR: Gentoo package "derivations" can be passed USE flags that toggle build features, and these flags are unified across the ecosystem. So for any package, if I pass !X I know for sure it won't build any GUI stuff
<lovesegfault>
(assuming it was written properly)
<infinisil>
Ah so like nixpkgs' config
<lovesegfault>
because of that you can set _global_ USE flags, like !X systemwide to never have any GUI anything on your system
<supersandro2000>
⋮ 2 │<head><title>301 Moved Permanently</title></head>
<supersandro2000>
⋮ 3 │<body>
<samueldr>
that's odd
<samueldr>
I always have the same HTML though
<supersandro2000>
🤔
<supersandro2000>
oh I think I know what happens. The bottom part is from my website when I tested if the diff works at all 😂
<supersandro2000>
derp
<samueldr>
haha
<samueldr>
but still, good catch on the headers!
<supersandro2000>
so let me disclose that
<samueldr>
be transparent that it was discussed publicly here, that if it would have warranted a bounty, but this made it so it is not eligible anymore, that they consider donating the bounty equivalent to the nixos opencollective
<supersandro2000>
yeah I should add that
rajivr has quit [Quit: Connection closed for inactivity]
waleee-cl has joined #nixos-chat
neeasade has joined #nixos-chat
<ar>
am I the only one who thinks it's weird to implement in kernel something networking-related that's completly non-standard and has no support anywhere else? >Add support for TCP over UDP https://reviews.freebsd.org/D29469
tomberek has joined #nixos-chat
__monty__ has quit [Quit: leaving]
<Irenes>
that's really strange
<Irenes>
I'm not confident that I fully understand what the kernel's role in it is
jess has joined #nixos-chat
<samueldr>
is it me or does it feel like a missed opportunity that at the highest log level, kernel modules being loaded are not part of the logs?
Synthetica has quit [Quit: Connection closed for inactivity]
<supersandro2000>
>> Support for this is already available in Wireshark, packetdrill, and uperf.
supersandro2000 has quit [Killed (hitchcock.freenode.net (Nickname regained by services))]