sphalerite changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS stable: 20.03 ✨ | 20.09 ZHF: https://discourse.nixos.org/t/nixos-20-09-zero-hydra-failures/8928 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.03 RMs: worldofpeace, disasm; 20.09: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
alp has joined #nixos-dev
ris has quit [Ping timeout: 258 seconds]
alp has quit [Ping timeout: 272 seconds]
jdnixx has joined #nixos-dev
justanotheruser has quit [Ping timeout: 272 seconds]
jdnixx_ has joined #nixos-dev
jdnixx has quit [Ping timeout: 260 seconds]
jdnixx_ is now known as jdnixx
orivej has quit [Ping timeout: 272 seconds]
jdnixx_ has joined #nixos-dev
LnL has quit [Ping timeout: 240 seconds]
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
jdnixx_ has quit [Ping timeout: 260 seconds]
rajivr has joined #nixos-dev
jdnixx_ has joined #nixos-dev
jdnixx_ has quit [Ping timeout: 240 seconds]
<MichaelRaskin> julm: what you definitely do not want, is querying the entire binary cache catalog. It's large for cache.nixos.org
MichaelRaskin has quit [Quit: MichaelRaskin]
jdnixx_ has joined #nixos-dev
bk1603 has joined #nixos-dev
Jackneill has quit [Ping timeout: 240 seconds]
Jackneill has joined #nixos-dev
bk1603 has quit [Ping timeout: 240 seconds]
saschagrunert has joined #nixos-dev
alp has joined #nixos-dev
bk1603 has joined #nixos-dev
cole-h has quit [Ping timeout: 260 seconds]
<julm> ok, then maybe the queries could be grouped together or.. made over dns :s
jdnixx_ has quit [Read error: Connection reset by peer]
Jackneill has quit [Ping timeout: 240 seconds]
ekleog_ has joined #nixos-dev
ekleog has quit [Ping timeout: 240 seconds]
bk1603 has quit [Ping timeout: 272 seconds]
bk1603 has joined #nixos-dev
Jackneill has joined #nixos-dev
sgrunert has joined #nixos-dev
bk1603 has quit [Ping timeout: 240 seconds]
saschagrunert has quit [Ping timeout: 240 seconds]
bk1603 has joined #nixos-dev
__monty__ has joined #nixos-dev
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
bk1603 has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
bk1603 has joined #nixos-dev
justanotheruser has joined #nixos-dev
orivej has joined #nixos-dev
bk1603 has quit [Ping timeout: 240 seconds]
justanotheruser has quit [Ping timeout: 240 seconds]
<pie_> not having this means not having a way to notify the user of anything, is that something we want? i guess if all packages are always magically perfect its fine <pie_> or at least something like "trace: please look at the packager notes for ..." would also be a start
<pie_> am i setting up a false dichotomy here?
<pie_> committers cna use theirjudgement anyway
<pie_> currently theres no way to say something like "do your do diligence with this package"
<pie_> which is i think a valid thing because most people dont check literally everything
<pie_> oreilly books have warning signposts for a reason
<pie_> anyway on a slightly rather related note, what i actually wanted to ask was, for https://github.com/NixOS/nixpkgs/issues/99535#issuecomment-703217903 , i need to pass an enumeration of syscalls to --system-call-filter (which counter to the name, lets me whitelist them)
<pie_> is there any expectation for containers to be portable or something, is there anything i should pay attention to?
bk1603 has joined #nixos-dev
bk16031 has joined #nixos-dev
bk1603 has quit [Ping timeout: 244 seconds]
bk16031 is now known as bk1603
bk1603 has quit [Ping timeout: 240 seconds]
bk16031 has joined #nixos-dev
bk16031 is now known as bk1603
justanotheruser has joined #nixos-dev
bk1603 has quit [Quit: WeeChat 2.9]
<rajivr> I've written this `flake.nix` https://gist.github.com/rajivr/714dda28d40a60b87df724264d66130d I was wondering it there as a more canonical way of specifying `nixos-generators.defaultPackage.x86_64-linux` to `pkgs.mkShell`?
alp has quit [Ping timeout: 258 seconds]
alp has joined #nixos-dev
Mic92 has quit [Quit: WeeChat 2.9]
Mic92 has joined #nixos-dev
hloeffler has joined #nixos-dev
hloeffler has quit [Ping timeout: 245 seconds]
cole-h has joined #nixos-dev
ris has joined #nixos-dev
alp has quit [Ping timeout: 240 seconds]
<gchristensen> Is there a way to point nix-channel at a different profile than the user's "channels" profile?
<gchristensen> I could hijack it with HOME=... but mehh
<eyJhb> When a build problem like this - https://status.nixos.org/ comes for the -unstable, how can one aid in fixing that?
rajivr has quit [Quit: Connection closed for inactivity]
<cole-h> Figure out what's broken and fix it :P
<eyJhb> Yeah, but I have no clue how I see what build that breaks :P
<eyJhb> I hoped "bulid problem" would be clickable to lead me to the failing builds page
<cole-h> Click on the "Hydra job for tests" link
<cole-h> Then click on one of the failed jobs and see why it failed
<cole-h> The most recently failed job (https://hydra.nixos.org/build/128074893) failed because it was "cancelled by user"
<cole-h> The previous job (https://hydra.nixos.org/build/128074665) failed because of a test failure
<eyJhb> `vm-test-run-installer-simpleUefiSystemdBoot` hmm...
<eyJhb> And I am guessing that if there is any PR for it, it will be labeled something like that?
<cole-h> Maybe. However, sometimes test failures are spurious.
<cole-h> Just have to wait until the next eval/build and see if it's still broken.
<eyJhb> Running it locally sucks I am guessing?
<cole-h> Sure, you could do that.
<samueldr> shouldn't really suck for a test
<samueldr> not like it's an stdenv rebuild :)
<cole-h> But as I said, sometimes test failures are spurious. It may very well succeed on your machine and not on Hydra. (e.g. one of the gnome3 tests used to fail on Hydra, but worked fine on my machine)
hax404 has quit [Remote host closed the connection]
hax404 has joined #nixos-dev
hax404 has quit [Client Quit]
hax404 has joined #nixos-dev
<gchristensen> hrm. I'd like to create a separate set of channels for my user, but the defexpr / channel list code seems a bit obtuse to make this easily sensible
alp has joined #nixos-dev
<worldofpeace> hey, just want to mention if you're like "where did the 20.09 blocker project go?" it has been moved into an org project https://github.com/NixOS/nixpkgs/issues/95269#issuecomment-703820008
<worldofpeace> If someone could also give permissions to nixos-search and nixos-artwork for the team https://github.com/orgs/NixOS/teams/nixos-release-managers that would be great. I think it should be write access like it is already for nixos-homepage (so we can merge stuff)
<worldofpeace> niksnut: ^
<niksnut> worldofpeace: done
<worldofpeace> thanks a lot ✨ niksnut
<{^_^}> niksnut's karma got increased to 26
<niksnut> btw I installed my new thinkpad from the 20.09 plasma iso and it worked fine
<worldofpeace> niksnut: good good, and we also got that issue with the lockscreen and logout fixed today with a patch to systemd
<worldofpeace> if anyone else feels like QA'ing the images look at https://github.com/NixOS/nixpkgs/issues/99648
<{^_^}> #99648 (by worldofpeace, 6 minutes ago, open): QA ISO images
<eyJhb> niksnut: Which Thinkpad have you aquired?
noonien has quit [Quit: Connection closed for inactivity]
alp has quit [Ping timeout: 272 seconds]
bk1603 has joined #nixos-dev
alp has joined #nixos-dev
{`-`}_ has joined #nixos-dev
angerman_ has joined #nixos-dev
chrisaw has quit [Ping timeout: 244 seconds]
mjsir911 has quit [Ping timeout: 244 seconds]
DamienCassou has quit [Ping timeout: 244 seconds]
joepie91 has quit [Ping timeout: 244 seconds]
bridge[evilred] has quit [Ping timeout: 244 seconds]
jtojnar has quit [Ping timeout: 244 seconds]
codyopel has quit [Ping timeout: 244 seconds]
angerman has quit [Ping timeout: 244 seconds]
{`-`} has quit [Ping timeout: 244 seconds]
greizgh has quit [Ping timeout: 244 seconds]
Ericson2314 has quit [Ping timeout: 244 seconds]
mkg20001 has quit [Ping timeout: 244 seconds]
samueldr has quit [Ping timeout: 244 seconds]
janneke has quit [Ping timeout: 244 seconds]
worldofpeace has quit [Ping timeout: 244 seconds]
<bk1603> If I want to include a linux-kernel patch from lkml in nixpkgs, can I use fetchpatch for it? In the existing `patches.nix` file I saw that a patch from lkml was copied to the directory and then used, instead of being directly used from the link. Is there a reason behind it?
chrisaw_ has joined #nixos-dev
<qyliss> (i.e. a lore.kernel.org one)
<qyliss> not really, i think, if you have a stable URL to the raw patch
janneke_ has joined #nixos-dev
msirabella has joined #nixos-dev
<qyliss> possibly the one you're seeing didn't apply cleanly and had to be fixed up or something
<qyliss> does that get you the raw email?
<qyliss> oh, lkml.org
<qyliss> I don't immediately see a way to get that
<qyliss> It is definitely stable
<bk1603> Oh I see, I have the lkml.org one, I think that is stable? (Unless the logs are compressed/deleted after sometime)
<qyliss> so I'd be very surprised
<bk1603> (There was a get diff link right next to the actual mail)
<qyliss> gchristensen: I don't think so? It's run by the Linux Foundation sysadmin.
<bk1603> [Here](https://lkml.org/lkml/diff/2020/9/4/259/1) is the link. I think it gets the patch.
<gchristensen> isn't lore hosted in some guy's closet?
<gchristensen> some really important Linux mailing list server rebooted when some guy's power got cut while he was on vacation and he couldn't start it for a week, or something
<gchristensen> :) yeah
<qyliss> not lore.kernel.org
<qyliss> that's lkml.org
greizgh_ has joined #nixos-dev
chrisaw_ is now known as chrisaw
<qyliss> bk1603: I'd advise finding the patch on lore.kernel.org regardless in that case (which is easy if you have the Message-ID), although the lkml.org link you have there will probably work.
bridge[evilred] has joined #nixos-dev
<bk1603> I did find #nixos, but not this
<bk1603> Also I was trying to look for this channel on the matrix freenode bridge. But couldn't find this one. Is it not bridged?
<bk1603> I see, I'll try and find the lore.kernel.org link then.
worldofpeace has joined #nixos-dev
codyopel has joined #nixos-dev
angerman_ has joined #nixos-dev
<qyliss> bk1603: try !join
angerman_ has quit [Changing host]
samueldr has joined #nixos-dev
<qyliss> (I don't use Matrix but this comes up a lot for Matrix users)
joepie91 has joined #nixos-dev
joepie91 is now known as Guest350
<bk1603> Oh okay. Thanks!
jtojnar has joined #nixos-dev
<qyliss> gchristensen: IME there's a pretty strong correlation between how close somebody is to kernel development and how likely they are to use lore.kernel.org over lkml.org
DamienCassou has joined #nixos-dev
janneke_ is now known as janneke
<qyliss> (which I attribute to lkml.org being much better at SEO and much worse at being nice to use)
mkg20001 has joined #nixos-dev
Ericson2314 has joined #nixos-dev
Guest350 has joined #nixos-dev
Guest350 has joined #nixos-dev
Guest350 has quit [Changing host]
Guest350 has quit [Changing host]
bk1603[m] has joined #nixos-dev
bk1603 has quit [Quit: WeeChat 2.9]
Guest350 is now known as joepie91
justanotheruser has quit [Ping timeout: 240 seconds]
<bk1603[m]> I found the message on lore.kernel.org. But how do I get only the raw diff from there?
<niksnut> eyJhb: an X1 carbon
<qyliss> bk1603[m]: click "raw"
justanotheruser has joined #nixos-dev
<qyliss> that gets you the raw email, which happens to be a valid patch, because all git patches are emails
<qyliss> so you can fetchpatch that
sgrunert has quit [Remote host closed the connection]
<bk1603[m]> I thought the `X-Proofpoint-Spam_Detaisl` part would interfere. ([Here](https://lore.kernel.org/lkml/20200904091653.1014334-1-riteshh@linux.ibm.com/raw) just in case you wanna take a look)
<bk1603[m]> * qyliss: I thought the `X-Proofpoint-Spam_Detaisl` part would interfere. ([Here](https://lore.kernel.org/lkml/20200904091653.1014334-1-riteshh@linux.ibm.com/raw) just in case you wanna take a look)
<qyliss> bk1603[m]: don't see any reason it would
<qyliss> looks like a properly formatted mail header
<qyliss> but you can test it with git am if you're non confident
<qyliss> *not
<bk1603[m]> Oh okay. Thanks once again! (TIL :P I've never used mailed patches before.)
<qyliss> if you do git format-patch what you actually get is an email, with Subject and From headers and stuff :)
<qyliss> btw -- if you'd sent a PR with the lkml.org, that would have been totally fine, just to be clear
<qyliss> This is a little nicer for somebody trying to understand what the patch does, but your original link would have got the job done and been totally acceptable
<qyliss> anyway, thanks for your diligence :)
zarel has joined #nixos-dev
justan0theruser has joined #nixos-dev
justanotheruser has quit [Ping timeout: 260 seconds]
<bk1603[m]> :)
NinjaTrappeur has quit [Ping timeout: 240 seconds]
NinjaTrappeur has joined #nixos-dev
dmj` has quit [Ping timeout: 272 seconds]
elvishjerricco has quit [Ping timeout: 272 seconds]
dmj` has joined #nixos-dev
elvishjerricco has joined #nixos-dev
__monty__ has quit [Quit: leaving]
davidtwco has quit [Ping timeout: 272 seconds]
davidtwco has joined #nixos-dev
carter has quit [Ping timeout: 272 seconds]
Scriptkiddi has quit [Quit: killed]
ajs124 has quit [Quit: killed]
das_j has quit [Quit: killed]
carter has joined #nixos-dev
ajs124 has joined #nixos-dev
Scriptkiddi has joined #nixos-dev
das_j has joined #nixos-dev
ghuntley has quit [Ping timeout: 272 seconds]
ghuntley has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]