justanotheruser has quit [Ping timeout: 260 seconds]
cole-h has quit [Quit: Goodbye]
alp has joined #nixos-dev
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
__monty__ has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
ris has joined #nixos-dev
alp has joined #nixos-dev
misuzu_ has quit [Quit: leaving]
misuzu has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
FRidh has joined #nixos-dev
alp has joined #nixos-dev
orivej has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
roberth has joined #nixos-dev
orivej has quit [Ping timeout: 258 seconds]
FRidh has quit [Quit: Konversation terminated!]
ixxie has joined #nixos-dev
AlwaysLivid has quit [Read error: Connection reset by peer]
ixxie has quit [Quit: Lost terminal]
ixxie has joined #nixos-dev
ixxie has quit [Quit: Lost terminal]
ixxie has joined #nixos-dev
ixxie has quit [Quit: Lost terminal]
kloenk has joined #nixos-dev
ixxie has joined #nixos-dev
noonien has joined #nixos-dev
ixxie has quit [Remote host closed the connection]
ixxie has joined #nixos-dev
ixxie_ has joined #nixos-dev
ixxie_ has quit [Quit: Lost terminal]
ixxie has quit [Remote host closed the connection]
ixxie has joined #nixos-dev
ixxie_ has joined #nixos-dev
ixxie has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-dev
ixxie_ has quit [Remote host closed the connection]
peelz has joined #nixos-dev
bennofs_ has joined #nixos-dev
bennofs__ has quit [Ping timeout: 264 seconds]
cole-h has joined #nixos-dev
noonien has quit [Quit: Connection closed for inactivity]
AlwaysLivid has joined #nixos-dev
rajivr has quit [Quit: Connection closed for inactivity]
teto has joined #nixos-dev
vcunat has joined #nixos-dev
<vcunat>
worldofpeace: here?
<vcunat>
(in this channel, I mean)
<vcunat>
I'm not sure what the "infra" team is supposed to mean.
<vcunat>
I don't think I really have significant privileges there, but I can restart/cancel jobs and create/modify jobsets.
<worldofpeace>
oh, then I guess it wouldn't make sense for u to be in that group. Though it still stands that it would be nice to have a team of people that we know can create/modify jobsets
AlwaysLivid has quit [Ping timeout: 272 seconds]
<worldofpeace>
vcunat: So I guess you saw from the post that we'd need to make the jobsets sometime on monday. And I believe I can imply from your response that jobsets can't be made beforehand?
<vcunat>
Maybe more people should have the capability. I have no idea what fraction of those with push access can do this.
<vcunat>
I have to point the jobset to some git branch.
<vcunat>
Sure, it can be changed later, but in that case I don't see much use creating the jobset yet.
<vcunat>
Anyway, I should be available to do it during most of tomorrow.
<vcunat>
And Monday as well; it's not much work.
<worldofpeace>
gotcha, I think since jon said he's available monday then that would be the day.
<worldofpeace>
and I guess we're going to have to push through that staging-next thing as well?
sascha has joined #nixos-dev
sascha is now known as Guest46292
<worldofpeace>
Do you have permissions to nixos-org-configurations vcunat ?
<vcunat>
No, I don't think so.
<vcunat>
Confirmed.
<vcunat>
From repos I only have nixpkgs and probably still nix.
<vcunat>
(though the "Nix core" team has been officially disbanded)
<vcunat>
Approaching release (just fork-off now, fortunately) tends to motivate people to rush more changes in... and thus more stuff breaks.
<worldofpeace>
yeah, I'm hoping that, in the future, we fork-off earlier (like this should have been last month) and then we approach beta carefully to encourage people to be more careful? that does involve a lot more backporting, though
<worldofpeace>
when it all happens at once it just makes the word "beta" wholly meaningless as there's no criteria for such a milestone
<worldofpeace>
cole-h: well, with the current "I'm pending but I'm failing check" :D
<cole-h>
worldofpeace: 😬
<vcunat>
I thought the tags like 20.03-beta didn't really have more meaning than marking the fork-off point.
<vcunat>
Some have been filled retrospectively, I suspect.
<cole-h>
worldofpeace: This is the only reason I can't merge and deploy that PR
<cole-h>
Deployer has been broken since 10 Aug :')
<worldofpeace>
vcunat: we do actually announce a "beta" but the tag was just used to mark a branch point. the idea then is to have two distinct freezes, one for beta and the final release.
<worldofpeace>
cole-h: that reminds me of the error when u try to use builtins.fetchGit without git in path?
<worldofpeace>
what the deployer has been broken since aug 10?!
<cole-h>
worldofpeace: I think it's just that something ofborg/infra depends on changed branches or something
<cole-h>
e.g. that commit is no longer a descendant of the `master` (default) ref
<{^_^}>
nix#2431 (by sgraf812, 1 year ago, open): fetchGit fails with a not very helpful error message when fetching a revision not in the remote's HEAD
<ehmry>
speaking of infra, do many people have logins at hydra.nixos.org, or just a few?
<worldofpeace>
ehmry: I believe it's mostly highly trusted contributors. So I have one, though there's no place to find out who has one or not
<cole-h>
Anybody who wants one can have one, I believe. I don't now the permissions afforded, though.
<cole-h>
s/now/know/
<cole-h>
e.g. I can "Sign in with Google"
<ehmry>
maybe I don't want to know how many packages I should be fixing
<worldofpeace>
ehmry: yeah, the portal that shows u the jobs u own is very useful.
<samueldr>
yeah, anyone can have a login, but there are different level of accesses
<samueldr>
many nixpkgs contributor can restart jos
<samueldr>
jobs*
<samueldr>
some can bump up priorities
<samueldr>
and then some can edit some projects
<samueldr>
finally, few can create new projects
<samueldr>
one neat, almost unknown feature, is that you can make your dasboard public (your starred jobs and jobsets)
<worldofpeace>
would it cause an issue if I backported a hash to 20.03 that's sri like "sha256-8r0DlmG8xlCQ1uFHZQjXG2ls4VBrsRzrVY8Ey3/OYAU=";
teto has quit [Quit: WeeChat 2.9]
justanotheruser has joined #nixos-dev
<samueldr>
IIRC yes, the minimum nix version to eval is too low
<samueldr>
but in practice it would be likely to slip by
<worldofpeace>
samueldr: but does that mean that existing users of 20.03 wouldn't be able to eval?
<samueldr>
of 20.03 no, I think its version of nix is fine, but evaluating from the previous version yes, in that case
<samueldr>
(I'm unsure about that)
<samueldr>
but also, unable to eval *if* the hash ends up in their evaluated closure!
<samueldr>
which is not a given!
<worldofpeace>
*facepalm woe is me. I updated pantheon's hashes on master, and I'm in a position where I'd like to backport that but as u said, a pantheon user of 19.09 upgrading to 20.03 (they should have already did this!) will not be able to
<worldofpeace>
I barely have the patience to fix that :D