!LemuOOvbWqRXodtSsw:nixos.org

NixOS Reproducible Builds

544 Members
Report: https://reproducible.nixos.org Project progress: https://github.com/orgs/NixOS/projects/30124 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
26 May 2021
@gytis-ivaskevicius:matrix.orgGytis IvaskeviciusAnyways, what you guys think next steps are with this? https://github.com/NixOS/nixpkgs/issues/12346708:13:02
@gytis-ivaskevicius:matrix.orgGytis IvaskeviciusShould I just start working on POC with additional stage?08:13:34
@zimbatm:numtide.comJonas Chevalierwe don't really have a team that owns the bootstrap phase08:20:10
@zimbatm:numtide.comJonas Chevalierusually the best thing to do is to present a clean plan with motivation08:21:30
@gytis-ivaskevicius:matrix.orgGytis Ivaskevicius

Could you elaborate on that? Here are few questions that come up:

  • How should it be shaped? Is issue enough or should it be RFC?
  • Does it need to include POC?
08:23:33
@gytis-ivaskevicius:matrix.orgGytis Ivaskevicius *

Could you elaborate on that? Here are few questions that come up:

  • How should it be shaped? Is github issue file or should it be RFC?
  • Does it need to include POC?
08:24:01
@gytis-ivaskevicius:matrix.orgGytis Ivaskevicius *

Could you elaborate on that? Here are few questions that come up:

  • How should it be shaped? Is github issue fine or should it be RFC?
  • Does it need to include POC?
08:24:08
@zimbatm:numtide.comJonas ChevalierI'm still not sure what problem it's solving. I get that the previous GCC version is leaking, but why is it a problem.08:28:15
@zimbatm:numtide.comJonas ChevalierI know I'm being annoying :)08:29:34
@raboof:matrix.orgraboofRFC seems overkill in this stage, a GitHub issue might not be noticed - perhaps a discourse topic seem most suitable? I agree a clear motivation (or even better, an assessment of pro's and con's?) is important.08:30:19
@gytis-ivaskevicius:matrix.orgGytis Ivaskevicius
In reply to @zimbatm:numtide.com
I'm still not sure what problem it's solving. I get that the previous GCC version is leaking, but why is it a problem.

Motivation:
Avoid nixpkgs lieing, especially with glibc and to gain latest compiler optimizations. In addition to these two points - this will allow us to pretty much never update bootstrap tools.

Technically nothing major, just super not nice from my point of view

08:31:18
@gytis-ivaskevicius:matrix.orgGytis Ivaskevicius
In reply to @raboof:matrix.org
RFC seems overkill in this stage, a GitHub issue might not be noticed - perhaps a discourse topic seem most suitable? I agree a clear motivation (or even better, an assessment of pro's and con's?) is important.
Will do!
08:31:41
@andi:kack.itandi-Wait, we didn't bump the bootstrap tools to GCC10 when we did the upgrade? Was it simply skipped or did we run into actual problems?09:37:23
@andi:kack.itandi-In any case didn't we have the bootstrapTarballs jobs to exactly get rid of the manual tasks with bumping them? We have to put the files on a bucket but that is about it, no?09:38:48

Show newer messages


Back to Room ListRoom Version: 6