<ekleog>
samueldr: about https://github.com/NixOS/nixpkgs/pull/47859#issuecomment-427575798 , do you think you'll have time to look into it? it's basically the bump to 14.0.1 (which you said was likely OK), addition of the nextcloud module (with everything under mkIf cfg.enable so no backwards-compatibility risk), and these changes to nginx (likely the only part that requires inspection for a backport as it's the
<ekleog>
hmm… I was advocating for a nixpkgs-18.09 here last time, and was pointed to the fact that nixos-18.09-small updated just as often… however, I just remembered that nixos-18.09 bumps before hydra has finished building all of nixpkgs, so it wouldn't fit the bill… do I consider this correctly?
<srhb>
ekleog: Not sure what you're asking exactly. All of them will bump despite package failures, if the package isn't (transitively) depended upon by the tested set.
<ekleog>
srhb: I mean, nixpkgs-unstable waits for attempt of the build of all the packages in all-packages, isn't it?
<ekleog>
I'd like basically this, but tracking the 18.09 branch
<ekleog>
(basically nixos-18.09 but bumping even when there are test failures)
<srhb>
ekleog: Yeah they all wait for the evaluation to be complete.
<srhb>
(That's the nixpkgs-unstable blocking tests)
<ekleog>
srhb: well, I'd like a channel based on release-18.09 that bumps as often as possible as soon as all the builds have been completed, be it in a pass or fail manner (ie. I need no test, can do my own, but I need the binary cache to not drown under rebuilds)
* ekleog
hasn't investigated yet how hydra exactly does things, so can't comment further on the test set, sorry :/
orivej has joined #nixos-dev
<mic921>
Did pkgs/top-level/aliases.nix not generate warnings in the past?
<mic921>
when you use an alias?
<mic921>
Or is this just the case for nixos/modules/rename.nix
pie___ has joined #nixos-dev
pie__ has quit [Ping timeout: 244 seconds]
<srhb>
ekleog: Ah, ok. No jobs like that exist today for any channel, and the analog would certainly not be nixpkgs-unstable. :)
<srhb>
ekleog: (So I guess it should be called nixpkgs-1809-notests or something like that)
<ekleog>
srhb: oh, so nixpkgs-unstable doesn't wait until all builds have been attempted? :/ maybe nixpkgs-unstable-cached / nixos-18.09-cached ?
<ekleog>
(I don't really care about the nixpkgs tests, tbh if they don't pass it's most likely some of my tests wouldn't pass either anyway, but I do care about -18.09 / -unstable complete tests because they break just so often)
<srhb>
ekleog: Yes it DOES wait, but it also has those tests I listed above, that you explicitly want gone.
<ekleog>
oh, didn't understand. So yeah, ideally there'd be no tests, but something that updates once a day still sounds reasonable :) I wonder if it'd be possible to get the latest commit fully attempted-to-be-built by hydra, maybe I'd be better off implementing it myself anyway :)
<srhb>
ekleog: So you want some sort of job that essentially always succeeds to be your hypothetical "main job"
<ekleog>
yeah
<ekleog>
(but waits until all packages have been attempted, even if an earlier package already failed -- don't know if that's actually done by hydra by default)
<srhb>
fwiw it seems very useless to me. Every package could have failed and it'd still bump. :)
<srhb>
ekleog: That's handled by latest-finished
<ekleog>
well, the idea is I'm running the tests outside of hydra and would be bumping my own channel if my tests pass :)
<srhb>
ekleog: Seems like you should just set up your own hydra then.
<ekleog>
well, maybe… but I don't have the money to have one that actually builds everything, I think :/
<srhb>
If you allow it to grab upstream artifacts, you just need decent hard drive space.
<srhb>
Anyway, I think this moved beyond the realm of nixos-dev :)
<ekleog>
indeed, let's move to… #nixos-chat? :)
<srhb>
Sure!
mic921 has left #nixos-dev ["User left"]
sir_guy_carleton has quit [Remote host closed the connection]
Mic92 has joined #nixos-dev
vcunat has joined #nixos-dev
drakonis1 has joined #nixos-dev
copumpkin has joined #nixos-dev
vcunat has quit [Ping timeout: 276 seconds]
<domenkozar>
do nixos containers setup networking with access to the public internet?
<cransom>
iirc, if you set up a privateNetwork, they don't unless you set up nat for that network. otherwise, they share the host network space and have the same access.
<domenkozar>
do imperative containers have privateNetwork set to true?
<domenkozar>
By default, containers cannot talk to the outside network. If you want that, you should set up Network Address Translation (NAT) rules on the host to rewrite container traffic to use your external IP address. This can be accomplished using the following configuration on the host:
drakonis has quit [Ping timeout: 268 seconds]
drakonis_ has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 252 seconds]
<domenkozar>
buffer #hercules-team
<domenkozar>
blah
orivej has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 246 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 250 seconds]
sir_guy_carleton has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 252 seconds]
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-dev
phreedom_ has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
drakonis_ has quit [Ping timeout: 252 seconds]
copumpkin has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
drakonis_ has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 260 seconds]
primeos has joined #nixos-dev
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
drakonis1 has joined #nixos-dev
copumpkin has joined #nixos-dev
copumpkin has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]