fendor_ has quit [Remote host closed the connection]
cosimone has quit [Ping timeout: 260 seconds]
gustavderdrache has joined #nixos
civodul has quit [Quit: ERC (IRC client for Emacs 27.1)]
<colemickens>
cole-h: you around?
aswanson has joined #nixos
eoli3n has quit [Remote host closed the connection]
eoli3n has joined #nixos
<colemickens>
I am trying to add a flake.nix to a project and am getting `flake ... does not provide attribute 'packages.x86_64-linux.test', 'legacyPackages.x86_64-linux.test' or 'test'` but I think that's true of all of my flake.nix files, so I'm confused why I'm getting it.
<colemickens>
cole-h: but I noticed you've accounted for this in pass-rs by adding a test attribute but I Don't really get why it's needeD?
<jophish>
But I care about line length in URLs, especially when they contain antiquities.
growpotkin has joined #nixos
SomeoneS1 has joined #nixos
<jophish>
supersandro2000: What's wrong with using let bindings?
<supersandro2000>
jophish: nothing if it is not blown up
<supersandro2000>
eg if you are using let in for pname and version and then inherit you just increase complexity
<supersandro2000>
use pname and version in rec is simpler and easier to understand
<jophish>
Ok sure, but that's not what's happening here
<jophish>
I thought that at a glance it's easier to see that these string manipulations are removing the dots if it's named appropriately
<supersandro2000>
and in your PR we just make it more complex than necessary
<supersandro2000>
for me it is clear in both cases but the later is just a bit shorter
<supersandro2000>
and 111 line length is fine
<supersandro2000>
let in should probably be used if you replace it multiple times or you need to replace many variables and the string is like 200 chars long
fooker has quit [Remote host closed the connection]
fooker has joined #nixos
davidv7 has joined #nixos
davidv7_ has quit [Ping timeout: 240 seconds]
<veleiro>
hello
<simpson>
Evening.
srk has quit [Remote host closed the connection]
srk has joined #nixos
czer00 has quit [Ping timeout: 272 seconds]
iqubic has joined #nixos
<iqubic>
I am quite perplexed now. A recent update to Firefox has completely removed all my extensions. Appearantly something changed, and I now can't have manual extensions with nix extensions?!?! I'm on Unstable if that helps anyone.
<steveeJ>
I'm looking for something that I can share maintenance over and not build and maintain for myself
<raghavsood>
iqubic: Are you pulling from nixpkgs-unstable or nixos-unstable?
veleiro has quit [Ping timeout: 256 seconds]
<iqubic>
nixos-unstable
<raghavsood>
That channel hasn't been updated in a couple of days, you could try pulling from nixpkgs-unstable, which was updated 8 hours ago and should include the discord version bump: https://status.nixos.org/
<samueldr>
but I know the general feeling with NixOS maintainers, steveeJ, is that handling partitioning/formatting automatically is scary enough that it needs to be more than rock solid before it's part of NixOS outright :)
<iqubic>
I see.
<samueldr>
be careful!
<samueldr>
never use nixpkgs-* channels for NixOS
<samueldr>
(for building the OS)
<steveeJ>
samueldr: I see, and agree. I think that the nix-community is the place where we can have something stable enough to opt into ;-)
<iqubic>
samueldr: I don't plan on doing that.
<samueldr>
they have not gone through the tests, so recommending its use for the OS could (probably won't) but could have dire consequences
<samueldr>
that was more for raghavsood
<{^_^}>
[nixpkgs] @github-actions[bot] pushed 18 commits to staging-next: https://git.io/JIcuC
<{^_^}>
[nixpkgs] @github-actions[bot] pushed 86 commits to staging: https://git.io/JIcu8
sss2 has quit [Quit: Leaving]
<raghavsood>
samueldr: Yes, of course - should be totally fine for just pulling in the discord package however. Wasn't my intention to ask iqubic to switch the whole system over, should have probably been more explicit
<samueldr>
steveeJ: yep, hopefully at some point there will be confidence in something to handle that
<raghavsood>
Then again, what's the point of having such great rollback mechanics if we never get to use them :D
<samueldr>
but here's the rub
<samueldr>
the failure could be nuking the rollback mechanism!
<iqubic>
What's the url for nixpkgs-unstable, so that I can use "nix-channel --add"?
<samueldr>
(or, more realistically, the boot entries, without actually touching the profiles)
<raghavsood>
samueldr: Yeah, I've done that a few times, unfortunately always on servers in another country - makes for some fun support calls
<raghavsood>
On the bright side, I did convince our team their to by some IP KVMs, so maybe it wasn't so bad
<samueldr>
hah
kalbasit has joined #nixos
<samueldr>
but yeah, it's quite important to be crystal clear when recommending usage of non-nixos channels on NixOS to *never* build the system outright with them, since the tests are the important difference between nixos and non-nixos channels
<iqubic>
Why am I getting this error from "nix-env -iA nixpkgs.Discord": error: attribute 'nixpkgs' in selection path 'nixpkgs.Discord' not found
<iqubic>
Look, I'm explicitly not using this to build my entire system.
pumpy has joined #nixos
<pumpy>
what package can i install to update firmware of my seagate nvme drive pls?
<samueldr>
iqubic: I know, this wasn't aimed at you
<samueldr>
just finishing the thought
<iqubic>
Ah. I see.
<iqubic>
Do you know what's up with the error I'm getting from nix-env?
<samueldr>
because I'm pretty sure many people read the channel, even if they don't actually interact
pjt_tmp has joined #nixos
<samueldr>
I don't recall if you need to do something after --add
<samueldr>
I would --update nixpkgs-unstable
<iqubic>
Yeah.
<samueldr>
ah, the man page explicitly says to update after adding
<iqubic>
I just got another attribute not found error. But this time it was telling me that Discord should be spelled with a lowercase D. The error had the same format, so I assumed it was the exact same error again.
LnL has joined #nixos
<raghavsood>
I've honestly never had much luck with getting channels to work with nix-shell and nix-env at a cli level - I usually just end up pinning them in my system or home-manager config (or shell.nix) and letting it build from there, picking the right package for each channel
<raghavsood>
Well, right channel for each package, rather
<iqubic>
Alright, thanks all for helping me with my issues. I'll be off now.
iqubic has left #nixos ["ERC (IRC client for Emacs 28.0.50)"]
cole-h has quit [Ping timeout: 256 seconds]
jonatanb has joined #nixos
sangoma has quit [Ping timeout: 272 seconds]
jonatanb has quit [Ping timeout: 240 seconds]
<pumpy>
nixos have any tools that'll let me burn an iso to flash drive?
<pumpy>
need to make bootable
lortiz has joined #nixos
<raghavsood>
Regular old `dd` has worked for me in the past
kalbasit has quit [Ping timeout: 272 seconds]
sangoma has joined #nixos
<pjt_tmp>
pumpy: dd if=foo.iso of=/dev/sdax bs=4k status=progress should be good
xelxebar has quit [Remote host closed the connection]
xelxebar has joined #nixos
clever has quit [Ping timeout: 256 seconds]
ddellacosta has quit [Ping timeout: 240 seconds]
Sigma has quit [Ping timeout: 265 seconds]
ishan has joined #nixos
<ishan>
I was trying to build wayfire as package but it is failing.
<ishan>
[72/201] Compiling C++ object src/wayfire.p/main.cpp.oFAILED: src/wayfire.p/main.cpp.o
<ishan>
[73/201] Compiling C++ object src/wayfire.p/util.cpp.oFAILED: src/wayfire.p/util.cpp.o
<ishan>
[74/201] Compiling C++ object src/wayfire.p/core_output-layout.cpp.oFAILED: src/wayfire.p/core_output-layout.cpp.o
notgne2 has joined #nixos
<ishan>
builder for '/nix/store/nbs6cqfxrm7qpxrg5pwk7d79vfr28314-wayfire-8aa8260972edaba6d237e1a61217a4d2303edc3e.drv' failed with exit code 1; last 10 log lines: In file included from /nix/store/dnlimk9bci1r3c42l1x1319rkny8k1gc-wlroots-0.12.0/include/wlr/types/wlr_input_device.h:27,
<{^_^}>
[nixos-hardware] @Mic92 pushed 2 commits to master: https://git.io/JICsR
lblasc[m] has joined #nixos
jschievink has joined #nixos
Spockz has joined #nixos
michaelpj has joined #nixos
aanderse has joined #nixos
axx has joined #nixos
NickHu has joined #nixos
maralorn has joined #nixos
stites[m] has joined #nixos
Dandellion has joined #nixos
alexfmpe has joined #nixos
M0[m] has joined #nixos
wak-work has joined #nixos
felschr[m] has joined #nixos
berberman[T] has joined #nixos
zuh0 has joined #nixos
callahad[m] has joined #nixos
ryantm has joined #nixos
redcedar[m] has joined #nixos
bbigras has joined #nixos
sectrect[m] has joined #nixos
piotrszegda[m] has joined #nixos
leons has joined #nixos
hcnelson has joined #nixos
yurb has joined #nixos
nh2[m] has joined #nixos
scheibenkleister has joined #nixos
ebbertd[m] has joined #nixos
Ericson2314 has joined #nixos
M-GNU-[m] has joined #nixos
hiroshi[m] has joined #nixos
Piece_Maker has joined #nixos
mcbits[m] has joined #nixos
trajanus[m] has joined #nixos
awwayaya24hours[ has joined #nixos
iensu[m] has joined #nixos
anderscs[m] has joined #nixos
princemachiavell has joined #nixos
qbit[m] has joined #nixos
aynish has joined #nixos
kaziemazie[m] has joined #nixos
ptotter[m] has joined #nixos
ongy[m] has joined #nixos
jonatanb has joined #nixos
ky0ko1 has joined #nixos
jdnixx[m] has joined #nixos
sethmdoty[m] has joined #nixos
rednaZ[m] has joined #nixos
davidak[m] has joined #nixos
domenkozar[m] has joined #nixos
znello[m] has joined #nixos
marco[m]3 has joined #nixos
nikola[m] has joined #nixos
fgaz has joined #nixos
superherointj[m] has joined #nixos
a4wc6n[m] has joined #nixos
gcher has joined #nixos
mica[m] has joined #nixos
TekShifter[m] has joined #nixos
NobbZ[m] has joined #nixos
axxoldaccount[m] has joined #nixos
matthewkenigsber has joined #nixos
srid has joined #nixos
lasadd[m] has joined #nixos
kraem has joined #nixos
faya01[m] has joined #nixos
omasanori[m] has joined #nixos
ericsagnes has joined #nixos
cushingar[m] has joined #nixos
stuebinm[m] has joined #nixos
psibi[m] has joined #nixos
beandipper[m] has joined #nixos
manveru[m] has joined #nixos
aflatter[m] has joined #nixos
arcnmx has joined #nixos
inquisitiv3 has joined #nixos
us3r[m] has joined #nixos
DenisLehmann[m] has joined #nixos
crazazy[m] has joined #nixos
tuelz has joined #nixos
templollete[m] has joined #nixos
ronny has joined #nixos
andreas[m]3 has joined #nixos
JaakkoLuttinen[m has joined #nixos
madnat has joined #nixos
badmutex[m] has joined #nixos
luke[m]3 has joined #nixos
krauser-tan[m] has joined #nixos
keithy[m] has joined #nixos
ms[m] has joined #nixos
aquarial has joined #nixos
wenngle[m] has joined #nixos
jbal[m] has joined #nixos
McSinyx[m] has joined #nixos
chreekat[m] has joined #nixos
mindtree[m] has joined #nixos
jonatanb has quit [Ping timeout: 246 seconds]
Notkea[m] has joined #nixos
worldofpeace has joined #nixos
foxxxx[m] has joined #nixos
esclear_m has joined #nixos
jtojnar has joined #nixos
ram19890[m] has joined #nixos
govanify has joined #nixos
peeterss[m] has joined #nixos
mitchty[m] has joined #nixos
Kanashimia[m] has joined #nixos
tmeres[m] has joined #nixos
tejing has quit [Quit: WeeChat 2.9]
tlater[m] has joined #nixos
denbrahe[m] has joined #nixos
bohan[m] has joined #nixos
phirsch has joined #nixos
siraben has joined #nixos
Bla[m] has joined #nixos
hazel[m] has joined #nixos
pinage404[m] has joined #nixos
Alex[m]5 has joined #nixos
jojosch[m] has joined #nixos
ht60309[m] has joined #nixos
jakeisnt[m] has joined #nixos
swanson123[m] has joined #nixos
as3ii[m] has joined #nixos
punsha[m] has joined #nixos
eadwu has joined #nixos
<{^_^}>
[nixpkgs] @ehmry pushed to master « glow: remove ehmry from maintainers »: https://git.io/JICZn
annemarie[m] has joined #nixos
<gentauro>
on the nixos site it states that 20.09 is the stable (therefore the active one right?) while on GH it's states that it's still 20.03 that's active https://github.com/NixOS/nixpkgs-channels/branches
<mrt[m]1>
Hi. My first try of Nixos today and I am completely lost. Could someone give me a quick hint how to change the keyboard layout for the console (no X)?
<patagonicus>
Not sure if switch will automatically set it or if you'll have to reboot, though.
<mrt[m]1>
Thanks!
<LilleCarl>
patagonicus: sudo systemctl isolate rescue; sudo systemctl isolate default <- i like using this one in case i don't need a full reboot
<patagonicus>
LilleCarl: Oh, didn't know that one. Still not super familiar with systemd, I used to avoid it as much as I could. :)
<patagonicus>
mrt[m]1: sudo loadkeys de (or whatever language you want) should also work as a one off, but the setting will auto-apply it on boot.
<LilleCarl>
patagonicus: I don't know too much either to be honest, but i embrace anything that brings distos together towards THE YEAR OF THE LINUX DESKTOP :p
<mrt[m]1>
<patagonicus "mrt: sudo loadkeys de (or whatev"> Thanks! I'm farther away from the default (using dvorak) which makes me really slow on anything but that. With you tip I can check the configuration.nix option faster!
<patagonicus>
mrt[m]1: I'm using NEO2 myself. :)
sss2 has joined #nixos
<fendor>
why does `nix search nixpkgs discord` find a different version than `nix-env -qaP discord` where both channel 20.09 und unstable (with latest updates)?
<{^_^}>
[nixpkgs] @github-actions[bot] pushed 18 commits to staging-next: https://git.io/JIC4s
<patagonicus>
I can still use German (and also US if I have to), but I'm really slow …
<{^_^}>
[nixpkgs] @github-actions[bot] pushed 24 commits to staging: https://git.io/JIC4Z
<LilleCarl>
My colleagues think I'm hardcore becuase i use the US keymap on a Swedish keyboard :p
<seku>
heh, my friends think i am hardcore because i use a Model F Battleship keyboard
<seku>
it's the greatest keyboard i ever used. a bit unwieldy though
<seku>
also using US-Int on swiss french keyboards. drives coworkers mad when they ever use my computer
<seku>
at least i stopped using colemak
<mrt[m]1>
O.k. `nixos-rebuild switch` produced an out of memory! My VM seems a bit small with 1gb RAM (wanted so see, how small it manages to work with :-)
<LilleCarl>
fendor: I wish i could help, but I'm as new to this as anyone else. Everyone ever who uses nixos would advise against using nix-env to install packages though
<LilleCarl>
Do you have a problem that nix isn't giving you an up2date enough discord? Because i had and solved that issue using configuration yesterday
<fendor>
LilleCarl, well, yes, nix-env only gives me an older discord version. How did you solve it?
<seku>
wow, i'd go 4gbyte minimum for VMs
<LilleCarl>
fendor: so i cloned the nixpkgs git repo (huge, 1.2GB). Then i added this before my main configuraton
<dutchie>
if you have a source code checkout, you can do `git branch --all --contains <commit id>`
<dutchie>
where <commit id> is the one updating discord
orivej has quit [Ping timeout: 264 seconds]
<dutchie>
(you may need also to do `git fetch --all` to update things)
<fendor>
Yaniel, thanks! still struggling with the nix infrastrucutre
<Yaniel>
after tests pass it takes a while before the actual branch on the nixpkgs repo is updated
<fendor>
So, then the answer to my initial question is, that flakes use master while nix-env uses channels?
<Yaniel>
(it seems like that is done by hand)
<Yaniel>
flakes use whatever you want to use
Darkmatter66 has quit [Ping timeout: 240 seconds]
jonatanb has quit [Remote host closed the connection]
<Yaniel>
nix-env uses whatever you have configured with nix-channel yes
jonatanb has joined #nixos
veleiro`` has joined #nixos
<seku>
i just tried nix on-off during the last months, but flakes seem so new to me
<seku>
is there a point to use channels now?
<Yaniel>
yes
<Yaniel>
channels are still the thing you get out of the box AFAIK
jonatanb has quit [Remote host closed the connection]
<fendor>
Yaniel, how do I configure the flakes then correctly?
<Yaniel>
I haven't looked into that
<fendor>
ok
<seku>
thanks Yaniel
<Yaniel>
but it's something similar to the snippet LilleCarl posted I think
<fendor>
thanks everyone for your help!
<Yaniel>
there's some documentation for it on the wiki IIRC
veleiro` has quit [Ping timeout: 256 seconds]
<LilleCarl>
dutchie: If you wanna track multiple nixpkgs branches you can use git-worktree to have multiple branches checked out at the same time without duplicating space consumed
<{^_^}>
[nixpkgs] @mdorman opened pull request #106059 → pytest_xdist: make version conditional on python interpreter → https://git.io/JICE0
<seku>
LilleCarl: what kind of magic is that
whatisRT has quit [Ping timeout: 246 seconds]
Guillaum has quit [Ping timeout: 256 seconds]
<LilleCarl>
seku: It's dark magic, but it's in the git docs so it's approved dark magic. Don't let it consume you though.... Anakin! https://git-scm.com/docs/git-worktree
Negher has joined #nixos
<seku>
really dark magic. especially it not consuming more space. has to be some linking magic
<MichaelRaskin>
LilleCarl: yeah, but Git was not advanced technology even when it was first written
<guisanpea>
I am missing to undestand if the `all-packages.nix` file is something that I must create or is something that it is there by default
<MichaelRaskin>
all-packages.nix is a file in the Nixpkgs repository
<guisanpea>
So to create the package I only need the `builder.sh` and `default.nix` files right?
<LilleCarl>
MichaelRaskin: "Everything is relative" - Albert Einstein; For peasants like myself Git is indeed quite complex, not to say that it is for everyone :d
<MichaelRaskin>
It is _more_ complex than more advanced technology having existed at the same time
<guisanpea>
So at the end in my `hello` folder I have two files https://pastebin.com/8nGK2QX9 which is default.nix and https://pastebin.com/AxYeQ8fm which is builder.sh as the guide recommends. However when I try to run `nix-build -A hello`I run into this failure
<guisanpea>
error: cannot auto-call a function that has an argument without a default value ('stdenv')
<guisanpea>
Am I missing something from the guide in order to build the package? I appreciate the help because after following it I have no clue :*
<guisanpea>
Am I missing something from the guide in order to build the package? I appreciate the help because after following it I have no clue :(
<dminuoso>
pinpox: Did you manually enable the extensions?
<pinpox>
dminuoso: where?
<dminuoso>
" Note that it is necessary to manually enable these extensions inside Firefox after the first installation. "
<dminuoso>
" Extensions listed here will only be available in Firefox profiles managed through the programs.firefox.profiles option. This is due to recent changes in the way Firefox handles extension side-loading. "
<{^_^}>
[nixpkgs] @holymonson opened pull request #106070 → webkitgtk: drop wayland dependency on Darwin → https://git.io/JICHc
jonatanb has joined #nixos
rurt91 has quit [Quit: Leaving]
m1cr0man has quit [Ping timeout: 240 seconds]
<LilleCarl>
fendor_: It seems like you can get Discord from Flathub now. I have no idea since when Flathub supported proprietary packages, but there's Steam on there as well (65wat)
<dminuoso>
liminal18_: while evaluating the option `environment.etc.systemd/user.source':
<dminuoso>
mmm
<dminuoso>
ah no while evaluating the attribute 'sources' of the derivation 'etc' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/system/etc/etc.nix:12:5:
<liminal18_>
dminuso not following. is there an upgrade guide I need to use?
<dminuoso>
liminal18_: Mmm, this is strange indeed
<dminuoso>
liminal18_: can you share your entire config?
<liminal18_>
let me see
<liminal18_>
dminuoso: ok I added my nixos configuration
<liminal18_>
my install is 5 years old
davidv7 has joined #nixos
<liminal18_>
so it is probably out of date
<dminuoso>
liminal18_: I guess its your compton setting
<dminuoso>
inactiveOpacity = "0.9";
<dminuoso>
I have no idea why the traceback is that bad
<liminal18_>
also the ssh keys I would like to auto-add are not working. I have to do ssh-add after every reboot to be able to commit git etc.
<liminal18_>
removed the ""s trying it now
<{^_^}>
[nixpkgs] @ilmari-lauhakangas opened pull request #106076 → subtitleeditor: add more gst-plugins → https://git.io/JIWk8
<liminal18_>
looks like that was it
<liminal18_>
dminuoso: thanks man
<dminuoso>
liminal18_: I'd file a bug report, though.
est31 has quit [Remote host closed the connection]
est31 has joined #nixos
m1cr0man has quit [Ping timeout: 272 seconds]
m1cr0man has joined #nixos
<{^_^}>
[nixpkgs] @Ma27 opened pull request #106080 → nixos/nginx: improve documentation for `config` → https://git.io/JIWY2
<inquisitiv3>
Is there any documentation on how to get NixOS running on a PPC system? I'll build my Blackbird (from Raptor CS) system in a couple of weeks.
<inquisitiv3>
Can't find anything in the manual or in the forum.
m1cr0man has quit [Read error: Connection reset by peer]
m1cr0man has joined #nixos
txt has joined #nixos
<{^_^}>
[nixpkgs] @Ma27 merged pull request #106050 → spotifyd: workaround panic with older rust version → https://git.io/JICOY
<txt>
I'm having a problem installing texlive.combined.scheme-basic via home-manager. It errors with a conflict for "/bin/dvipdfmx". https://paste.debian.net/1175834/
charles84 has joined #nixos
u0_a128 has joined #nixos
Darkmatter66 has joined #nixos
charles84 has quit [Ping timeout: 245 seconds]
m1cr0man has quit [Quit: G'luck]
m1cr0man has joined #nixos
<Yaniel>
inquisitiv3: presumably it'll work a lot like running it on ARM
<genevino>
so i'm just trying to pin down a bug in alacritty and noticed that the version in nixos is pretty old (0.5.0). can i somehow easily check if another nix packages channel would ship 0.6.0 already?
<hexa->
yet I cannot find the "wanted" hash anywhere in my nixpkgs checkout
sudoforge has joined #nixos
<hexa->
time to comment out libreoffice I guess
<infinisil>
hexa-: It could be in a different format
<infinisil>
See `man nix-hash`
<hexa->
tru :<
respawn_ has quit [Quit: Leaving]
PBabebu[m] has joined #nixos
vidbina_ has quit [Ping timeout: 272 seconds]
<stevenroose>
I'm trying to create a nix package for an app that is built with yarn. Now I know nothing about JS development. I see 2 yarn2nix projects and a node2nix project. The yarn2nix projects don't seem to work (they can't build it), but node2nix can. Would that work?
lunasspecto has joined #nixos
zangi has quit [Quit: WeeChat 2.9]
<lunasspecto>
Hi NixOS folks
<lunasspecto>
I have been enthusiastically using NixOS on my personal machines for a while and have decided to migrate the VPS that hosts my web site to NixOS. I've hit a little snag, though; When I use the Nixos 18.03 ISO provided by my hosting provider (old, I know), it doesn't start with network connectivity; I can't connect to nixos.org etc.
<lunasspecto>
I'm wondering if the NixOS 18.03 manual would be any help; does anyone know where I can find older versions of the manual?
<{^_^}>
[nixpkgs] @rnhmjoj opened pull request #106082 → nixos/uwsgi: add support for POSIX capabilities → https://git.io/JIWlf
<eyJhb>
Which provider do you use lunasspecto ?
<Emantor>
lunasspecto: man configuration.nix on your 18.09 machine will have the info for that version.
<txt>
lunasspecto, please specify "no network connection" a bit more detailed
<ivan>
lunasspecto: can you ping 1.1.1.1
werner291 has joined #nixos
zebrag has quit [Quit: Konversation terminated!]
<lunasspecto>
If I try to ping 1.1.1.1 it hangs much longer than I care to wait
zebrag has joined #nixos
<lunasspecto>
When the ping returns it says 100% packet loss
<lunasspecto>
I'm not super adept at networking
<lunasspecto>
My hosting provider is HostWInds
<Yaniel>
ping probably doesn't hang, it just doesn't print its progress in some configurations
<Yaniel>
you can ctrl+c and it should print what it got so far
<lunasspecto>
Yeah, it did eventually complete (I passed "-c1") and said it lost the packet
<srhb>
lunasspecto: For starters, maybe you can pastebin (or screenshot, if you're in console land) the output of `ip a`
<ivan>
if you can install another linux with working networking on your server, you can then use emergency-kexec (from another machine with decent upstream) to reboot it into a nixos installer
<srhb>
I don't really think that 18.03 shouldn't have networking. Sounds weird.
<srhb>
It may be some missing vm networking module I suppose...
<lunasspecto>
Ooh, ivan, that sounds like it might be a decent option.
<ivan>
install the latest debian on the server if that is available, then take a look at emergency-kexec and make it install 20.09
<lunasspecto>
I will try to grab a screenshot of `ip a`. I'm using a VNC without copy/paste
<lunasspecto>
I was so excited because I had a .nix file with everything I want all ready. I did not count on networking not being available to start
<srhb>
lunasspecto: Yeah, that's a bit of a showstopper :P
<patagonicus>
So, with pkgs.closureInfo I can get the list of packages that a system needs (I'm currently using something close to pkgs.closureInfo { rootPaths = (import <nixpkgs/nixos> { configuration = … }) } - can I get a closure that also includes build dependencies?
<lunasspecto>
Hmm, tried emergency-kexec on a fresh Debian installation and it seemed to be going fine until it tried to extract the tarball it had copied over and claims to have run out of space
<patagonicus>
Looks like using config.system.drvPath instead of config.system works, although I don't (yet?) understand why.
<lunasspecto>
Okay, I"m still trying to install NixOS on my VPS. I discovered that I can actually provide my own installation ISO, so now I'm finally working with NixOS 20.09 instead of 18.03, but I still lose all packets and can't connect to nixos.org
<lunasspecto>
I managed to screenshot the output of `ip a` in my VNC https://ibb.co/BVtpHhB
<ryantm>
Does your VPS support an IPv4 internet connection?
<lunasspecto>
What I could do is temporarily install a different OS on my VPS, run mtr, and report back
Lord_of_Life has joined #nixos
Lord_of_Life has quit [Changing host]
<LilleCarl>
If you could boot a "rescue distro" to trial these things that'd be great
<LilleCarl>
Well thing is you should run a rescue dist from the same rescue mode
OneLegend has joined #nixos
<hexa->
lunasspecto: ip route
<hexa->
look for a default route
<LilleCarl>
There's a possibility that your VPS provider puts your VPS on a different network segment with DHCP and NAT when you're in rescume mode (seems weird but who knows). Where's this VM hosted?
<hexa->
next try to ping the nexthop
<LilleCarl>
lunasspecto: It'll look something like this: default via 192.168.87.1 dev eno1 proto dhcp src 192.168.87.221 metric 203
<LilleCarl>
What hexa- described
<lunasspecto>
LilleCarl, I'm on HostWinds, in "ISO Install" mode. I already started booting an Alpine ISO, so I'll see if I have connectivity in that and if I do I'll trace some routes
<hexa->
Also, as a customer, nag them to provide something less horribly outdated
<LilleCarl>
If your server IP is 81.82.83.84 you should configure your first interface with that ip address. Set the subnetmask to /24 (255.255.255.0) and the default gateway to 81.82.83.1
<LilleCarl>
Dns you can use whatever public recursive resolved you want :d
<hexa->
A /24, shady
<lunasspecto>
Ah thanks, I'm not used to configuring networking at this level, I use ifconfig ?
Mozart_ has joined #nixos
<LilleCarl>
hexa-: Why shady? It's quite common
<Mozart_>
sesto senso
<hexa->
LilleCarl: because it is likely a shared L2 network
<LilleCarl>
lunasspecto: ip address add 81.82.83.84/24 dev eth0
<lunasspecto>
sweet, thank you, LilleCarl
<hexa->
And that opens up a can of worms like arp spoofing, rogue router adverts
<LilleCarl>
ip route add default via 81.82.83.1 dev eth0
<LilleCarl>
hexa-: dminuoso Nothing wrong with that. They're probably using some overlay to span the L2 across multiple nodes, this along with rstp guards makes the network loop free and you save ip addresses and can provide a configuration people are used to when they're installing their own isos (like above) :p
Heirlung has quit [Read error: Connection reset by peer]
<LilleCarl>
Said overlay is probably VXLAN tunnels managed with EVPN.
<hexa->
LilleCarl: /32 + onlink gw is the proper wqy
Mozart_ has quit [Quit: Going offline, see ya! (www.adiirc.com)]
<LilleCarl>
While i do agree, It's "harder" to configure. If you're providing VPS's to potatoes you've got to take that into consideration too
Heirlung has joined #nixos
<lunasspecto>
Am
<lunasspecto>
Am I a potato? XD
<LilleCarl>
Nah, you'll figure this out ;)
<hexa->
I mean there is still the point that you have a /24 and it will do ARP and NDP for those neighbors
OneLegend has quit [Quit: yeeting off]
liminal18_ has quit [Quit: Leaving]
noudle has joined #nixos
<hexa->
I wouldn't want to share a L2 with untrusted machines
<hexa->
you suddenly need DHCP Snooping/Guard to prevent rogue DHCP
<hexa->
Maybe MAC Filters
ericsagnes has quit [Ping timeout: 264 seconds]
<hexa->
certain Source Address Filters
<hexa->
certainly*
<hexa->
You really do need to also filter Router Advertisments
gustavderdrache has joined #nixos
<hexa->
so, the best move is not to play :)
<hexa->
LilleCarl: btw: if you ever want to toy around with tc/mangos on nix, I have some packages ready :p
<LilleCarl>
hexa-: These are usually solved by blocking these protocols between the hosts. On the defgw they might proxy arp :p
<LilleCarl>
Type ip link and you'll see all devices you have
OneLegend has joined #nixos
<lunasspecto>
I have lo and ens3
<LilleCarl>
ens3 is your device
<LilleCarl>
lo is loopback, that's where 127.0.0.0/8 resides
<lunasspecto>
Right! I just remembered that because I'm on 20.09 now I'm nixos, not root, so I've got to sudo
<dminuoso>
20:28:01 hexa- | LilleCarl: /32 + onlink gw is the proper wqy
<dminuoso>
Indeed.
<dminuoso>
That's the only proper way.
<hexa->
and it's really easier
<hexa->
do routed networking instead of switched
<hexa->
and when the vm starts route that ip that way
<hexa->
you are basically done, no L2 shenanigans
<LilleCarl>
There's the IPv6 + ENHE way too. We use it to route traffic internally. "BGP Unnumbered"
<dminuoso>
For VPS, if you have good control over the hypervisor, you can inject DHCP helpers to auto configure your IP. Think that's what Hetzner does?
<dminuoso>
LilleCarl: That's just for the underlay...
<hexa->
LilleCarl: ENHE is mellanox-speak for IPv4 via IPv6 Nexthops, correct?
malook has joined #nixos
<LilleCarl>
hexa-: Not Mellanox specific. Can be done in Linux
<{^_^}>
undefined variable 'Extended' at (string):440:1
* LilleCarl
laughs
waleee-cl has joined #nixos
<dminuoso>
BGP unnumbered (that is link-local IPv6, with automatic peer discovery, and then ENHE) is the only way to build spine/leaf in my opinion.
<dminuoso>
Anything else is just error prone and silly
<dminuoso>
Assuming you're running EVPN anyway
<LilleCarl>
Yeps
nullheroes has quit [Quit: WeeChat 2.9]
<dminuoso>
I mean we're a mellanox.. *cough*.. nvidia.. shop. So it just works out of the box? :>
<hexa->
riiiight.
malook has quit [Client Quit]
<hexa->
you people are aware of #nixos-on-your-router? :)
<dminuoso>
No!
<hexa->
you are now!
<dminuoso>
But we do want to run nixos on our nvidia switches.
<hexa->
not yet
<dminuoso>
What not yes? No we do!
ericsagnes has joined #nixos
<dminuoso>
Maybe Ill just try and nixos-infect one of our switches tomorrow. Brilliant idea.
<LilleCarl>
dminuoso: If you're running Mellanox i assume you're already running Cumulus. What does Nix have to offer in terms of switch management? Are you thinking nixops?
<hexa->
networkd? :P
<dminuoso>
LilleCarl: well not nixops, but something like that yeah.
<dminuoso>
Right now we have a custom haskell stack that orchestrates our SDN.
<dminuoso>
We're toying with the idea of running the switches on nixos to talk about the entirety of it
<hexa->
LilleCarl: you honestly need to hope the linux kernel has a driver/firmware for that
<dminuoso>
LilleCarl: Using ifupdown2 with switchd and so forth
<dminuoso>
When I say nixos, I mean nixos + derivations for all the cumulus python stuff
<dminuoso>
Part of the reason is our cumulus switches are running quite a bit of custom software already
<hexa->
yeah, that's a good reason
<dminuoso>
Like we have a custom tranceiver exporter running on each switch
<hexa->
does cumulus support telemetry?
<dminuoso>
Sure if you buy NetQ
<dminuoso>
But we're a prometheus shop
<hexa->
sure, we're using the openconfig-telemetry-exporter :)
<hexa->
but yeah, largely due to being a mostly junos network
<dminuoso>
The exporter wasnt so difficult, its just a bunch of golang code to talk to Linux via ethtool, and then scrape SNIA standardized things off.
<LilleCarl>
hexa-: It's Debian 10 with some pixie dust sprinkled on top. Anything you can do on your linux host you can do on your switch.... ish
OneLegend is now known as OneLegend
<dminuoso>
hexa-: Ah I see, Ill check that out
<hexa->
LilleCarl: well, yes and no. For bcm switches a mainline kernel wouldn't do.
<dminuoso>
All routers here are being switched to Juniper MX204
<hexa->
not sure about mlnx, they're usually more open
<dminuoso>
Think currently we're running a custom junos exporter too
<hexa->
yup, our borders are mx204 as well
<dminuoso>
bcm switches
<dminuoso>
haha
<dminuoso>
Has NVidia finally talked about broadcom support btw?
<hexa->
dminuoso: well, you do need *some* software for them now :P
<dminuoso>
Because for the past 6 months it was silently canned..
<dminuoso>
Rumors of licensing fights between broadcom and nvidia
m1cr0m4n has joined #nixos
<hexa->
your support contract for bcm on cumulus isn't worth jack shit
<dminuoso>
*shrugs*
<dminuoso>
We have Mellanox switches.
<LilleCarl>
We're really small, but we bought some bcm and we're not very impressed with the information :p
<dminuoso>
Or well. Nvidia.
<lunasspecto>
Had to attend to non-tech stuff, but I got back to to running those ip commands, LilleCarl. Do you think there's any service I have to restart now
<hexa->
broadcom pulled their sdk when cumulus was bought
m1cr0man has quit [Ping timeout: 256 seconds]
<dminuoso>
hexa-: Yeah, the worst part is, there's still no information on either side.
<LilleCarl>
lunasspecto: No. But your dns isn't configured most likely
<dminuoso>
At least it wasnt a few weeks ago
<dminuoso>
Only things I kept hearing from nvidia folks was "a press release is coming out soon"
<LilleCarl>
lunasspecto: try ping 1.1.1.1
<hexa->
dminuoso: there is some, if you find the proper twitter thread, and it's not pretty :P
<dminuoso>
hexa-: do you have a link by any chance?
<lunasspecto>
I still can't ping 1.1.1.1 -- 100% packet loss
<hexa->
hm, lmtal
<dminuoso>
Anyhow. We're glad we wont that lottery, because we decked out our entire core network with mellanox switches.
<dminuoso>
In hindsight, it was a real irony. Our previous switching fabric was brocade, and the purchase by extreme networks was an obvious move to just slaughter brocade to pieces - it was one major reason to move to mellanox+cumuulus.
<lunasspecto>
Ah, I think I put my gateway in wrong, rebooting and trying again
<LilleCarl>
lunasspecto: you don't need to reboot for that
<dminuoso>
Just to get the news 6 months later that both cumulus and mellanox got bought..
<dminuoso>
Of course it wasnt the same situation, but it did cause some confused faces
<LilleCarl>
hexa-: You're creepy AF RN
<hexa->
how so? :P
<dminuoso>
hexa-: ah yeah I got that hn bit.
<LilleCarl>
LilleCarl == carlhjerpe
<dminuoso>
LilleCarl: Oh I think you and I talked on slack.
<hexa->
lmao
<dminuoso>
Yes we did.
<dminuoso>
Heh small world.
<LilleCarl>
dminuoso: CT?
<dminuoso>
CT?
<LilleCarl>
Initials
<dminuoso>
No. VN. It was just some short conversation bits now and then.
<LilleCarl>
Ic
<dminuoso>
Let's do the proper introduction round. AS9136 here *waves*
<LilleCarl>
I'm ashamed, don't wanna :p
<hexa->
dminuoso: and not in #denog? :P
<LilleCarl>
32 bit AS, single /22, 2 transit providers. Nothing to show off
<dminuoso>
hexa-: Yeah I know.
<dminuoso>
Maybe I should.
<LilleCarl>
So now that we're all friends, care to take a look at something NixOS related? https://pastebin.com/0fCYAd9y
<dminuoso>
LilleCarl: Well, it's not like I couldn't figure out what AS you are if I wanted to..
<LilleCarl>
dminuoso: You probably could considering my name, it'd be quite some stalking though :p
fuzzypixelz has quit [Read error: Connection reset by peer]
fuzzypixelz has joined #nixos
fuzzypixelz has quit [Read error: Connection reset by peer]
simukis_ has joined #nixos
<LilleCarl>
There's something inherently German about NixOS. So far everyone I've talked to about NixOS that I've gotten to know the location of has been German
<LilleCarl>
Like litterally 100% so far
hugolgst has quit [Read error: Connection reset by peer]
<etu>
LilleCarl: And your nickname tells me that you're from the nordic countries :)
<evils>
)
<LilleCarl>
etu: Indeed. Sweden
<etu>
LilleCarl: Cool, I'm in Stockholm :>
<LilleCarl>
I'm in the metropolitan Skövde :p
<LilleCarl>
etu:
m4tsa_ has quit [Ping timeout: 240 seconds]
<etu>
LilleCarl: Nix is spreading :)
m4ts has joined #nixos
<LilleCarl>
etu: Oh cmon that's mean. There's probably at least one other person in my city who use Nix
<etu>
LilleCarl: Yeah, probably, just hard to find :)
<LilleCarl>
Anyone care to take a look at https://pastebin.com/CenARern error: cannot auto-call a function that has an argument without a default value ('stdenv')
<LilleCarl>
Looking at other nix packages I can't see where I'm wrong
<stevenroose>
Am I alone to find that there's a great lack of (discoverable) documentation or examples on how to do some specific things?
<stevenroose>
I've been trying to find out how to use/run a nodejs app in NixOS. I feel that documentation is always very narrow to a specific part of the problem but I fail to understand how things fit together.
<stevenroose>
(I read nix pills and the manual before, I might have forgotten things over some months, but I usually learn better by example and doing things.)
kyren_ has joined #nixos
demize has quit [Quit: Do Androids Dream of Electric Sheep?]
<stevenroose>
LilleCarl: hmm, thanks will check out :)
<LilleCarl>
stevenroose: Oh sry it's not like good docs, it's just discussion about that the "first step" into nix is kinda hard
<stevenroose>
Hmm, LilleCarl I have used NixOS in the past for various machines and I know how to *use* existing NixOS services, programs etc. I just don't know what to do if an app is not in nixpkgs and I need to provide it myself.
<colemickens>
There is a node section of the manual.
<stevenroose>
There's guides to "package an XXX app to nixpkgs". But what then? Then I get a default.nix that represents a package, but I don't know how to "use" it as a service/program from configuration.nix
<colemickens>
That having been said, I also struggle with nodejs in nixos sometimes (though that usually has to do with unspeak^H^H^H^H creative things happening inside npm packages.)
<colemickens>
stevenroose: this is good feedback, I've had this conversation with a a folk or two in the past.
<stevenroose>
colemickens: yeah I always try to find non-JS based solutions to any problem first :D But it is unavoidable sometimes
<colemickens>
stevenroose: first question is, do you plan to contribute this back to nixpkgs?
<stevenroose>
colemickens: probably not. not because I don't want to do the effort, but because I'm just learning and it's probably gonna suck
<LilleCarl>
stevenroose: The good thing about nix is that if it works, it works :p
<stevenroose>
:D
<LilleCarl>
And the best way to get help on the internet is ofc to state something wrong (which could be interpreted as providing kinda bad code that someone will improve) :p
<colemickens>
stevenroose: but understandable. There's a non-GH workflow you can use here, to submit patches apparently, if that's any more appealing: https://lists.sr.ht/~andir/nixpkgs-dev
<colemickens>
stevenroose: but anyway, if you're going to keep it out-of-tree anyway, then you'll probably wind up with another file that imports nixpkgs and calls `pkg.callPackage ./path/to/your/default.nix` which will give you the actual package.
<colemickens>
let me find an example for you
* colemickens
resists the urge to send a flake.nix.
<stevenroose>
colemickens: hmm that helps. and then how cna oyu "use" the package?
<stevenroose>
it's just adding it to the environment.systemPackages at that point, right?
<colemickens>
yeah, that's what I'd do anyway
<colemickens>
if you're going to do that though, it's even easier :)
<stevenroose>
well no I mean to ask, at that point we "just" have the binary available, or the callable anyway
<MichaelRaskin>
If it goes to systemPackages, it's better to callPackage directly without a second import of Nixpkgs
<colemickens>
just literally stick `(pkgs.callPackage path/to/your/pkg/default.nix)` in as a new entry in environment.systemPackages.
simukis_ has joined #nixos
<colemickens>
+1 to what MichaelRaskin said, forget what I said about importing nixpkgs in another file.
<infinisil>
Don't forget the {} as the second callPackage argument
<stevenroose>
I suppose to turn it into a service, I could do 2 things? do a manual system.services.<name> = { }; by doing a systemd unit or try to do a nixos module thing with config?
<colemickens>
and that too :/ just saw it
z0k has quit [Quit: WeeChat 3.0]
<colemickens>
stevenroose: if you want to go through that process, it's a bit more involved, you'll need to write a NixOS module and then similarly make that known to your configuration.
Moonspell has left #nixos ["Leaving"]
<stevenroose>
but if I want it to be a permanent part of my nixos machine/conf, that's the best way, right?
<stevenroose>
so that I can also have some way there to provide a config file
<stevenroose>
hmm, I think I did something like that with a non-nodejs program in the past
<colemickens>
stevenroose: putting it in environment.systemPackages just makes it available to you via PATH. It doesn't automatically activate/install any systemd services.
<stevenroose>
colemickens: okay so if I have some packages in ./pkgs/XX/XX.nix and a module in ./modules/XX.nix, how can I get those into my configuration.nix? where/how are these imported?
roobs has joined #nixos
aswanson has joined #nixos
bitmapper has joined #nixos
<veleiro>
what's a good directory to store secrets in NixOS?
<LilleCarl>
colemickens: I do have a package that i intend to upstream. https://pastebin.com/9uxaFf4a Here's the diff of where i'm at right now. But when i run nix-build . -A stremio i get
<LilleCarl>
error: attribute 'stremio' in selection path 'stremio' not found
<energizer>
roobs: you might have more luck posting on discourse
<LilleCarl>
I've been staring myself blind at other packages for quite awhile now
<stevenroose>
LilleCarl: I'm not running NixOS as my main machine, I'm trying to get this into a server impl
<lukegb>
LilleCarl: if this is a diff of nixpkgs, then you'll need to add your new package to top-level/all-packages.nix (or whatever it's called) as well
cyphase has joined #nixos
landon has quit [Quit: Leaving]
jozefk has quit [Quit: Konversation terminated!]
<roobs>
energizer: thanks, I will
roobs has left #nixos [#nixos]
lejonet has quit [Ping timeout: 256 seconds]
<LilleCarl>
lukegb: Goshdarn, I've been searching "handbrake" in github https://github.com/NixOS/nixpkgs/search?q=handbrake but it doesn't include that file in search results for some reason. Should've grepped :p
<lukegb>
yeah, most search things don't do a good job of indexing that file because it's humongous
<lukegb>
I think sourcegraph omits it too
<LilleCarl>
Handbrake was just a reference package to see wth i've done wrong
<lukegb>
also it's in a "random" "order"
<LilleCarl>
Thanks for the tip, now back to nixing
<LilleCarl>
I might not disturb you all more today, kinda bedtime. But i'll sure be back tomorrow :p
<LilleCarl>
lukegb: Is there any supposed order in that file or just insert wherever? For PR's sake
<lukegb>
I think there's a comment somewhere that says they're in a grouping
<lukegb>
some of them are actually inside another attrset which you probably don't want
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<colemickens>
stevenroose: there's three pieces, there's the package, the nixos module that needs to reference the package, and your end user config that needs to reference probably just the module.
<lukegb>
stevenroose: e.g. you can do `environment.systemPackages = with pkgs; [ (callPackage /foo/bar/baz.nix {}) ];`
<lukegb>
oh, I'll let colemickens answer :P
<colemickens>
lukegb: I think stevenroose wants a systemd service as well though
<lukegb>
ahhhh
<stevenroose>
oh I can do that inside the module definition?
<colemickens>
yeah!
<gentauro>
xmonad wants me to use `X11-1.9.2`, but current `libX11` is `libX11-1.6.12`. How do I upgrade to 1.9?
<stevenroose>
yeah I have a module definition
<stevenroose>
where I do the service
<stevenroose>
ok so I can just do the `environment.systemPackages = with pkgs; [ (callPackage /foo/bar/baz.nix {}) ];` inside the module?
<gentauro>
it's in my /etc/nixos/configuration.nix
<colemickens>
remember the waybar module I linked that had the systemd service?
<stevenroose>
colemickens: yeah I saw. but that one didn't add the pkg
<colemickens>
where it says "pkgs.waybar" that's it referencing the package, so you could put "${(callPackage /foo/bar/baz.nix {})}" in there instead.
shorberg has quit [Quit: Konversation terminated!]
pumpy has quit [Ping timeout: 260 seconds]
veleiro has quit [Ping timeout: 260 seconds]
<colemickens>
or pkgs.callPackage, but you get the idea, hopefully
<stevenroose>
colemickens: hmm, ok I understand that :) so what is a normal place to "append to pkgs"?
<colemickens>
stevenroose: okay, so if you want to do multiple things, like reference the package in a systemd definition AND add it to system packages..
<stevenroose>
would `pkgs.myPkgs = pkgs.callPackage "..." {};` work? inside configuration.nix?
<colemickens>
stevenroose: uh, let's hold off.
<stevenroose>
k k, I'll shut up and listen :)
<colemickens>
stevenroose: I think it'd be better to have your module automatically install it in the system. I didn't realize you wanted that earlier :)
<colemickens>
so in your module, you'd start it out with `let mypkg = pkgs.callPackage /your/pkg.nix; in ...` and then you could do `env.sysPacakges = [ mypkg ];` AND you can use ${mypkg} in place of ${pkgs.waybar} in the waybar example.
fendor has quit [Remote host closed the connection]
<stevenroose>
ooh k yeah that makes sense
<colemickens>
stevenroose: so that makes a reference to your custom package (`mypkg`) and then uses it in two different ways, one to install a system package for all users, and the other to setup a systemd service however you configure.
<{^_^}>
[nixpkgs] @cdepillabout pushed 2 commits to haskell-updates: https://git.io/JIlvm
oxalica1 has joined #nixos
supersandro2000 has joined #nixos
oxalica has quit [Ping timeout: 240 seconds]
oxalica1 is now known as oxalica
<andi->
Wulfsta: questionable how it works and why it was done the way it was done. Super rushed IMHO. Switched to qutebrowser now. Maybe less mainstream thus less people randomly breaking packages.