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
ris has quit [Ping timeout: 256 seconds]
justanotheruser has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-dev
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #nixos-dev
AlwaysLivid has joined #nixos-dev
orivej has joined #nixos-dev
AlwaysLivid has quit [Remote host closed the connection]
AlwaysLivid has joined #nixos-dev
AlwaysLivid has quit [Client Quit]
orivej has quit [Ping timeout: 240 seconds]
zarel_ has joined #nixos-dev
zarel has quit [Ping timeout: 260 seconds]
rajivr has joined #nixos-dev
atriq is now known as Taneb
cole-h has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-dev
AlwaysLivid has joined #nixos-dev
<etu> ryantm: Hmm, would it be possible for the updater bot to update packages inside of phpPackages and phpExtensions so I don't have to do PR's like this #101535 when I remember about it?
<{^_^}> https://github.com/NixOS/nixpkgs/pull/101535 (by etu, 2 minutes ago, open): phpPackages and phpExtensions updates
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
thoughtpolice has quit [Ping timeout: 272 seconds]
thoughtpolice has joined #nixos-dev
betawaffle has quit [Ping timeout: 272 seconds]
aria has quit [Ping timeout: 272 seconds]
kalbasit has quit [Ping timeout: 272 seconds]
aria has joined #nixos-dev
betawaffle has joined #nixos-dev
bridge[evilred] has quit [Ping timeout: 258 seconds]
bridge[evilred] has joined #nixos-dev
kalbasit has joined #nixos-dev
callahad87074 has quit [Ping timeout: 258 seconds]
callahad87074 has joined #nixos-dev
feepo has quit [Ping timeout: 272 seconds]
jared-w has quit [Ping timeout: 272 seconds]
nh2 has quit [Ping timeout: 272 seconds]
jared-w has joined #nixos-dev
feepo has joined #nixos-dev
claudiii has quit [Ping timeout: 272 seconds]
nh2 has joined #nixos-dev
claudiii has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
__monty__ has joined #nixos-dev
ris has joined #nixos-dev
<das_j> Probably illegal question, but is it possible to run nix in stage 1?
<das_j> I need nix-env to uodate a profile and nix-store to import a dump into the database
alp has joined #nixos-dev
<MichaelRaskin> I mean, you could always just build your own initramfs from scratch. Multi-hundred-MiB initramfs works, I use such stuff
alp has quit [Ping timeout: 272 seconds]
<sphalerite> das_j: of course it is :D
dstzd has quit [Quit: ZNC - https://znc.in]
dstzd has joined #nixos-dev
dstzd has joined #nixos-dev
dstzd has quit [Changing host]
<das_j> alright, I'll just try
<das_j> mass-bootstrapping of systems is always annoying
<sphalerite> das_j: if you want to keep it minimal, you can use only nix-store and manage profile symlinks yourself
<sphalerite> das_j: did you see the bringing-nixos-to-school talk from nixcon?
dstzd has quit [Client Quit]
<das_j> sphalerite: Yeah, but I'll need the nix package anyway
<das_j> no, but I was told it was great
<das_j> but it's not that big of a deployment for me ;) just installing 60 raspis
<das_j> (once)
<das_j> but I want to do as much in parallel as possible
<gchristensen> I would not wish that on anyone
<sphalerite> that sounds quite similar
dstzd has joined #nixos-dev
<sphalerite> ok I guess once is a bit different
<das_j> gchristensen: It's not too bad. It's worse to install 240 feet and 60 poe shields ;)
dstzd has quit [Client Quit]
<sphalerite> sounds like a cool project though.
<das_j> yeah, maybe I'll do write some blog posts if I find the time
<das_j> -do
dstzd has joined #nixos-dev
dstzd has joined #nixos-dev
dstzd has quit [Changing host]
dstzd has joined #nixos-dev
dstzd has joined #nixos-dev
dstzd has quit [Changing host]
<das_j> `error: --- 'build-users-group' not found --- nix-store`
<das_j> probably not running too good
avn has quit [Ping timeout: 260 seconds]
<ryantm> etu definitely! It's a matter of getting the update versions. Where do you get them from?
AlwaysLivid has quit [Read error: Connection reset by peer]
AlwaysLivid has joined #nixos-dev
orivej has joined #nixos-dev
cole-h has joined #nixos-dev
Baughn has joined #nixos-dev
Baughn has quit [Client Quit]
alp has joined #nixos-dev
Baughn has joined #nixos-dev
<etu> ryantm: I usually look at the list of outdated packages that I maintain: https://repology.org/projects/?maintainer=elis%40hirwing.se&inrepo=nix_unstable&outdated=1 it's not always complete because it's not always perfectly mapped with other distros, but it covers most of it.
<ryantm> @etu okay, that should already be covered by the repology fetcher, so we just need to figure out why it is failing to update by looking at the logs https://r.ryantm.com/log/
<etu> ryantm: I don't see anything in that log mentioning php what so ever... hmm...
<etu> ryantm: Other than random hash mentions and URL mentions though
<ryantm> I'll run the repology fetcher to see if it is picking them up.
<etu> ryantm: It's very recent that we put most of the packages as separate files, before they were all inline. But it was suggested that the updater tend to work better if it's split out
<ryantm> Yeah, it skips files with multiple hashes in them.
Baughn has quit [Quit: ZNC 1.6.2+deb1 - http://znc.in]
<ryantm> The Repology fetcher is definitely finding php stuff.
<ryantm> I'll try updating one to see what happens.
<etu> Thanks :)
Baughn has joined #nixos-dev
<ryantm> @etu unfortunately you already updated all of the things it found except for php-oci8
<etu> ryantm: yeah, the PR just got merged... Is it possible to try it on a git repo that is slightly out of date just to see how it would apply the changes?
<ryantm> etu: Yeah, I don't have a way to fake what is on the master branch currently. Maybe we can find some other php update easily by looking around a bit?
<etu> ryantm: Sadly I think I went through it all for that PR... I can get back to you when I find something and we'll try the bot way before I do it by hand :)
<worldofpeace> If someone could look over this backport for me at https://github.com/NixOS/nixpkgs/pull/101565 u'd save me 😸
<{^_^}> #101565 (by worldofpeace, 29 seconds ago, open): [20.09] nixos/tools: add desktopConfiguration option (to seed configuration into configuration.nix)
<ryantm> Is that oci8 version on Repology wrong?
<ryantm> etu: okay sounds good. It looks promising that it will just work, but maybe the bot is too slow compared to you :)
<etu> ryantm: yeah, it's confused :) There's several packages named oci8. One is from the PHP upstream (which we provide) and one is a pecl which is entierly separate.
<ryantm> etu: Maybe report a split needed then.
<etu> ryantm: Hmm, can you request merges/splits at repology? Didn't know that... I have several cases of that :D
<ryantm> etu: Yeah just click "report" on the page I linked
kalbasit__ has joined #nixos-dev
kalbasit_ has quit [Ping timeout: 240 seconds]
qyliss has quit [Quit: bye]
qyliss has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
supersandro2000 has joined #nixos-dev
jdnixx-M1 has joined #nixos-dev
<makefu> hey all, without reading the backlog in this channel i just wanted to say thanks for setting hacktoberfest topic in nixpkgs. i did a couple of package bumps based on my repology stats and added two packages which i had in NUR before
cole-h has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
orivej has quit [Ping timeout: 258 seconds]
justanotheruser has quit [Ping timeout: 260 seconds]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
<andi-> Do we actually have NixOS VM tests that use wayland yet (maybe GNOME/KDE)? I just noticed we didn't have any for some applications on wayland and thought there could be something to copy from already.
tilpner has quit [Ping timeout: 240 seconds]
<pbogdan> I think Wayland is the default for GNOME, there's a separate test that uses Xorg session
<pbogdan> no clue how re-usable it would be though
justanotheruser has joined #nixos-dev
tilpner has joined #nixos-dev
<andi-> Well I guess for my case I can just run the application on gnome and that makes it pretty re-usable :D
justanotheruser has quit [Ping timeout: 260 seconds]
__monty__ has quit [Quit: leaving]
<worldofpeace> andi-: those tests are crude tbh
<worldofpeace> like we had to use an xdg autostart and then check with the shell api that it's running
<andi-> yeah, I am currently looking at how I can mirror our X11 primitives to wayland.. someone from intel write a functional test framework for wayland a few years ago. Looking at that now. Maybe we just need a few userspace utils to assist us
<worldofpeace> just a call to gdbus that it's running https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/gnome3.nix#L56
<worldofpeace> andi-: the one I really know of that's used for gnome which uses the accessability bus is dogtail https://gitlab.com/dogtail/dogtail
<worldofpeace> they're just python programs
<worldofpeace> aargh, it seems their wayland support isn't mainline
alp has joined #nixos-dev
<andi-> worldofpeace: awwh :/ I guess I'll just do keypresses for now
justanotheruser has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
<Raito_Bezarius> I'm trying to understand how mature are flakes with nixops, is it even an option?
<Raito_Bezarius> Apparently, there is a branch nixops/flake-support which uses nixopsConfigurations in the flakes
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
scott has joined #nixos-dev
<scott> i just found this problem and i'm curious about the nixpkgs merge policy https://github.com/NixOS/nixpkgs/pull/100040#discussion_r511524306
<scott> is it intentional that the build failures did not block the merge, and were apparently easy for the maintainer to miss?
<samueldr> IIRC yes, there is a great difficulty in knowing whether it _should_ build or not in that build step
<samueldr> in addition to other things like timeouts
<samueldr> the decision has been made that × failure is only for YES IT'S BROKEN FOR REAL
<samueldr> while for builds it's quite nuanced
<samueldr> nuanced to determine outright
<scott> you definitely wouldn't want false negatives blocking the merge (if they're hard to correct)
<samueldr> yeah, and more importantly, you don't want to make it routine to merge through the red ×
<scott> i just thought i'd raise this issue in case there is anything in this process that can be improved, aside from "every be more careful"
<scott> everyone*
<samueldr> yeah, we need a yellow "CAUTION READ CAREFULLY" status in GitHub
<samueldr> as of right now there is only gree "all okay", grey "uh" and red NO
<scott> yeah, i was kind of disappointed to find the failures shown in grey. yellow would be good
<colemickens> https://www.tweag.io/blog/2020-10-22-nickel-open-sourcing/ <- is there possibly a s/server/host/ that needs to happen with the first example?
<colemickens> actually, I'm also confused. The `urls` field seems to be holding the output of makeURL (a string) but also a split-out record as well?
<supersandro2000> I need to agree with scott. This should never have been merged like this.
<samueldr> I don't think anyone disagrees
<drakonis> oh interesting
<drakonis> that blog post that is
<MichaelRaskin> Now I wonder what exactly the submitter has allegedely built and even executed
<supersandro2000> samueldr: you're right. That grey there should probably be red
<samueldr> if it was possible to do so, it would have been
<samueldr> note that if a build times out, it needs to not be red
<samueldr> and build failures coming from dependencies [possibly from master branch changes] need also to not be red