<etu>
Nope, we didn't have that one under that name
<gchristensen>
,escape''
<{^_^}>
'' two single quotes: ''' bash curly bois: ''${} newline: ''\n tab: ''\t any character x: ''\x ''
v0|d has quit [Ping timeout: 268 seconds]
orivej has joined #nixos-dev
__monty__ has joined #nixos-dev
FRidh has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
Jackneill has joined #nixos-dev
jonringer has quit [Ping timeout: 265 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 276 seconds]
__Sander__ has joined #nixos-dev
drakonis has quit [Ping timeout: 265 seconds]
drakonis has joined #nixos-dev
orivej has joined #nixos-dev
kreisys has quit [Read error: No route to host]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 268 seconds]
page has joined #nixos-dev
<ekleog>
Thoughts about releases and backporting: I feel like we should split the “release” set into what we really support as stable, and what we don't. Things like linux-latest, non-ESR firefox, or other programs for which backporting security patches would be too much effort should not necessarily be unavailable from the release channel, but just be marked as “this is unstable” over there. Any
<ekleog>
thoughts on the idea?
<ekleog>
ie. something like `meta.stable = (true|false);`, which would default to `false`, and to install a package on a nixos release you'd need to do like with `allowLicenses` or similar
<infinisil>
ekleog: During the hackday there was a meeting for improving the release process, and one thing we discussed was to somehow assign priorities to packages
<infinisil>
Which then get used to decide how to focus the effort, for issue, prs and hydra failures
<infinisil>
Similar to your idea
<FRidh>
nixpkgs-unstable is not being updated despite several successfull evaluations
drakonis_ has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 276 seconds]
<ekleog>
infinisil: Right, missed that meeting, thanks for the feedback :)
<worldofpeace>
infinisil: I think we'd call this critical chain released packages. From an outside perspective these packages get expedited support and we can say we guarantee this, and if there's an issue with them before or during the branch off the release can't happen until they're in good shape and qa'd
<infinisil>
worldofpeace: Hm yeah, but I'd say the channel constituters are there for this
<worldofpeace>
infinisil: there's definitely things missing from the channel constituants that should be there, and I'm not sure you could represent everything through this because it can become manual
<infinisil>
worldofpeace: How would a set of things blocking a channel not be manual?
<infinisil>
And I don't think it's hard to add more of those, looks like nixpkgs/pkgs/top-level/release.nix is for that
<worldofpeace>
I meant like we're tracking a ux breaking bug in firefox but the channel constitutant firefox test isn't going to break to block the channel because of this
<infinisil>
Soo we should improve our firefox test to do more image detection? :P
<worldofpeace>
But that's literally impossible, you can't write a test as fast as a program deteriorates to block a channel. it would someone manually noticed the thing and it's an issue on github
drakonis_ has joined #nixos-dev
drakonis has joined #nixos-dev
Jackneill has quit [Remote host closed the connection]
<ashkitten>
gchristensen: that escape pattern is absolutely awful ngl
drakonis_ has quit [Ping timeout: 264 seconds]
* gchristensen
shrugs
<ashkitten>
it's just confusing
drakonis_ has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis has quit [Ping timeout: 265 seconds]
drakonis_ has quit [Ping timeout: 245 seconds]
drakonis has joined #nixos-dev
drakonis1 has quit [Ping timeout: 276 seconds]
<tilpner>
worldofpeace: Regarding your comment on rfc 55: I agree that the committer process needs more transparency, and a process, but I'm not in any position to fulfill either of your demands
<tilpner>
worldofpeace: It would be inconsistent of me to mandate public announcements when the current nixpkgs-committers team isn't public, and making it public is far out-of-scope
drakonis_ has joined #nixos-dev
<worldofpeace>
Can there be "public" announcements that are only visable to all members of nixpkgs-committers?
<tilpner>
I have no idea what you people do :)
* tilpner
is not part of nixpkgs-committers
<tilpner>
Do you use the team discussion tab?
<tilpner>
I assume the notifications would be annoying people similarly to discussion in nixpkgs-maintainers
<worldofpeace>
Well I guess the point of it is to notify everyone so they all should get notifications
<niksnut>
I don't know of any reason why it should be private
<niksnut>
but I also don't think we should be using it for team discussions
<tilpner>
worldofpeace: I guess my point is that I will not be able to make progress on those points on my own, because they both touch on issues I considered out-of-scope
<worldofpeace>
I honestly don't know how you go about a change like this when you can't grant or remove commit access with transparency. It's almost like being transparent about one thing in a specific circumstance, where someone is inactive.
<worldofpeace>
while totally reasonable, I kinda leaves my conflicted because I'm conflicted about the current situation.
<worldofpeace>
atm, I'm not sure I can formulate an actionable request tilpner. I might need more time to think on this.
<tilpner>
worldofpeace: I'm all for more transparency, but that's not the core point of this RFC. It doesn't need to provide any transparency, all it does is cull commit bits
<gchristensen>
I don't think we need an RFC to make the commiters list public
__Sander__ has quit [Quit: Konversation terminated!]
page has quit [Quit: leaving]
psyanticy has joined #nixos-dev
LnL has joined #nixos-dev
LnL has joined #nixos-dev
LnL has quit [Changing host]
drakonis has joined #nixos-dev
page has joined #nixos-dev
drakonis_ has joined #nixos-dev
<tazjin>
gchristensen: I can now do the popularity count for an entire Nix channel in ~10 seconds
<tazjin>
is there a way I can see all historical commits a channel was at?
drakonis_ has quit [Read error: Connection reset by peer]
<cransom>
i used to work for a factory that would get holidays orders that involved glitter. it took months before the aerosolized glue and glitter particles got covered up by the regular grime again.
ris has joined #nixos-dev
<clever>
cransom: ive heard it refered to as the herpes of arts&crafts
<cransom>
sure is.
psyanticy has quit [Quit: Connection closed for inactivity]
FRidh has quit [Quit: Konversation terminated!]
page has quit [Remote host closed the connection]
kreisys has joined #nixos-dev
drakonis_ has quit [Ping timeout: 264 seconds]
drakonis has quit [Ping timeout: 268 seconds]
nurelin has joined #nixos-dev
__monty__ has quit [Quit: leaving]
drakonis has joined #nixos-dev
<infinisil>
Aw, seems like environment variables set in `environment.variables` aren't available without restarting the x session
<infinisil>
I think it's supposed to not need that
<gchristensen>
I don't think it can?
<gchristensen>
since it is set in the profile
<infinisil>
gchristensen: I don't see how that would make it an impossibility
<infinisil>
Looking into it a bit more
<infinisil>
The shell would actually source the new env vars
<infinisil>
But it doesn't because __NIXOS_SET_ENVIRONMENT_DONE is set
<samueldr>
would that propagate to sub-processes?
<samueldr>
(I don't think so)
<infinisil>
And that's set because /etc/profile is sourced when the xsession starts
<infinisil>
I guess it can't apply the new vars for the session without restarting the session (which makes sense), but it could certainly do it for shells
<infinisil>
samueldr: And in shells it would propagate to sub-processes I'm pretty sure