!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

211 Members
67 Servers

Load older messages


SenderMessageTime
30 Sep 2023
@lovesegfault:beme.ems.hostlovesegfault Artturin: when you're around, lmk what needs uploading, I'll make time to get everything uploaded 17:54:55
@artturin:matrix.orgArtturin
In reply to @lovesegfault:beme.ems.host
Artturin: when you're around, lmk what needs uploading, I'll make time to get everything uploaded

All the linux bootstrap files have to be updated

mips64el-n32.nix
loongson2f.nix
mips64el.nix
armv5tel.nix
armv6l-musl.nix
armv6l.nix
armv7l.nix
i686.nix
mipsel.nix
powerpc64le.nix
riscv64.nix
x86_64-musl.nix
x86_64.nix
aarch64-musl.nix
aarch64.nix
18:08:57
@artturin:matrix.orgArtturinwhich is why i'd like to make a script to help you18:09:14
@artturin:matrix.orgArtturinhttps://github.com/NixOS/nixpkgs/issues/253713#issuecomment-171237308718:09:19
@artturin:matrix.orgArtturin * https://github.com/NixOS/nixpkgs/issues/253713#issuecomment-1712373087 please check18:09:37
@lovesegfault:beme.ems.hostlovesegfaultHeh, yeah, we'll need some automation for that to be viable, for sure18:09:41
@artturin:matrix.orgArtturin

in #151399 (comment) you asked for the sha256sum of all the on-server components, however shouldn't it be okay to directly upload the packages from bootstrapFiles

18:10:04
@lovesegfault:beme.ems.hostlovesegfaultLet me grab my notes on the process, one second18:10:05
@artturin:matrix.orgArtturini can work with the notes to make a script18:10:19
@lovesegfault:beme.ems.hostlovesegfault
In reply to @artturin:matrix.org

in #151399 (comment) you asked for the sha256sum of all the on-server components, however shouldn't it be okay to directly upload the packages from bootstrapFiles

Yup, it should be, I ask for the sha as an extra verification step to be uber-sure I have the right thing
18:10:43
@lovesegfault:beme.ems.hostlovesegfaultBecause I can upload tarballs, but I cannot delete them18:10:51
@lovesegfault:beme.ems.hostlovesegfaultSo I err on the side of being too cautious 18:11:06
@lovesegfault:beme.ems.hostlovesegfaultRedacted or Malformed Event18:27:16
@lovesegfault:beme.ems.hostlovesegfault

Uploading tarballs

  1. Look at the Hydra build linked on GH, make sure nothing is off (built the
    right thing, on the right pkgs intance/channel/etc)
  2. Check the build logs on Hydra, make sure there are no glaring issues that did
    not end up failing the build
  3. Get the nix-store path, and sha256's from GH
  4. nix build -L $storePath
  5. Get the nixpkgs commit which generated the tarball
  6. Check it out, build it, make sure it's reproducible
  7. Figure out the correct subpath for this tarball
    1. x86_64-darwin -> stdenv-darwin/x86_64
  8. Check that the hashes within match the ones from GH
  9. Construct the upload path
    1. s3://nixpkgs-tarballs/$os/$arch/$nixpkgs_commit
    2. e.g. s3://nixpkgs-tarballs/stdenv-darwin/x86_64/05ef940b94fe76e7ac06ea45a625adc8e4be96f9
  10. Upload it
    1. e.g. aws s3 cp --recursive --acl public-read /nix/store/9h4d7s313wv3gkfwi493yr1wvdsz9lf2-stdenv-bootstrap-tools/on-server/ s3://nixpkgs-tarballs/stdenv-darwin/x86_64/05ef940b94fe76e7ac06ea45a625adc8e4be96f9
18:27:33
@lovesegfault:beme.ems.hostlovesegfault Artturin: there ya go, that's what I do 18:27:42
@artturin:matrix.orgArtturin

Look at the Hydra build linked on GH, make sure nothing is off (built the
right thing, on the right pkgs intance/channel/etc)

Maybe we should merge https://github.com/NixOS/nixpkgs/pull/256439 after all, then we can get hydra builds for the bootstrap files

18:49:40
@lovesegfault:beme.ems.hostlovesegfault
In reply to @artturin:matrix.org

Look at the Hydra build linked on GH, make sure nothing is off (built the
right thing, on the right pkgs intance/channel/etc)

Maybe we should merge https://github.com/NixOS/nixpkgs/pull/256439 after all, then we can get hydra builds for the bootstrap files

Sounds good, merged :)
19:17:54
@lovesegfault:beme.ems.hostlovesegfaultI'm sorry for reverting that, I was having a chaotic week and didn't fully understand what the PR was doing. Now I see that it was AOK to have been merged and I was wrong19:18:37
@lovesegfault:beme.ems.hostlovesegfaultCan someone review this before I upload it? https://github.com/NixOS/nixpkgs/pull/25545119:46:00
@lovesegfault:beme.ems.hostlovesegfault

trofi: Regarding https://github.com/NixOS/nixpkgs/pull/188544

Is there a flag I can pass for it to find the plugins?

21:39:31
@trofi:matrix.orgtrofi --plugin should do it, but i don;t know what it does to existing plugins and how it handles multiple ones 21:40:54
@trofi:matrix.orgtrofi And the typical problem if trying to guarantee that both gcc and binutils use the same libstdc++.so library. 21:42:00
@lovesegfault:beme.ems.hostlovesegfault

Interesting:

cc1: fatal error: plugin /nix/store/h5kvfrjmpw792v8jg7nrzfkffmn0iyy8-gcc-12.3.0/libexec/gcc/x86_64-unknown-linux-gnu/12.3.0/liblto_plugin.so is not licensed under a GPL-compatible license /nix/store/h5kvfrjmpw792v8jg7nrzfkffmn0iyy8-gcc-12.3.0/libexec/gcc/x86_64-unknown-linux-gnu/12.3.0/liblto_plugin.so: undefined symbol: plugin_is_GPL_compatible
21:45:09
@lovesegfault:beme.ems.hostlovesegfaultOhhhhh21:49:35
@lovesegfault:beme.ems.hostlovesegfaultWe must accidentally strip that symbol lol21:49:43
@lovesegfault:beme.ems.hostlovesegfaulthrm, I wish I could easily set a list of paths to exclude from stripping in the fixupPhase21:57:45
@artturin:matrix.orgArtturin
In reply to @lovesegfault:beme.ems.host
hrm, I wish I could easily set a list of paths to exclude from stripping in the fixupPhase
You can
22:01:48
@artturin:matrix.orgArtturinstripExclude22:02:00
@artturin:matrix.orgArtturinThere was a pr which I rebased and merged a few weeks ago22:02:29
@artturin:matrix.orgArtturinShould be in master by now22:02:34

There are no newer messages yet.


Back to Room ListRoom Version: 9