!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

228 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture53 Servers

Load older messages


SenderMessageTime
19 Mar 2024
@philiptaron:matrix.orgPhilip Taron (UTC-8)code velocity ++00:49:47
@philiptaron:matrix.orgPhilip Taron (UTC-8) Gotta run to dinner. Good working with you today infinisil . 00:50:01
@infinisil:matrix.orginfinisil Philip Taron (UTC-8): Same, have a nice dinner! I'll be sleeping soon 😄 00:50:31
@fgaz:matrix.orgfgazThis kind of system does exist... just not for GH :-/08:40:20
@fgaz:matrix.orgfgaz For example GitLab, Phorge... 08:41:30
@jade_:matrix.org@jade_:matrix.org
In reply to @fgaz:matrix.org
This kind of system does exist... just not for GH :-/
we need custom stuff anyway
08:42:44
@jade_:matrix.org@jade_:matrix.org
In reply to @jade_:matrix.org
we need custom stuff anyway
extracting package metadata from prs and notifying and such
08:43:07
@philiptaron:matrix.orgPhilip Taron (UTC-8)💯14:56:46
@philiptaron:matrix.orgPhilip Taron (UTC-8) It shouldn't be too hard with curl and jq and .timer unit. 14:57:07
20 Mar 2024
@infinisil:matrix.orginfinisil(context: https://matrix.to/#/!RROtHmAaQIkiJzJZZE:nixos.org/$TgaZeLfUQ7rNQSwa93nXpK06rUPKQ7hK2dl_m_O4tOA?via=nixos.org&via=matrix.org&via=nixos.dev)22:58:03
@infinisil:matrix.orginfinisil

reverting to the original build process, that used the newly built nixpkgs-check-by-name as the source for the check

Philip Taron (UTC-8) What do you mean by that?

22:58:23
@infinisil:matrix.orginfinisil Currently, the /nix/store path is pinned here, which allows CI to fetch it directly from Hydra here 23:00:10
@philiptaron:matrix.orgPhilip Taron (UTC-8) In check-by-name.yml, there's a pinned version of nixpkgs-check-by-name. 23:00:18
@philiptaron:matrix.orgPhilip Taron (UTC-8)Yeah23:00:20
@philiptaron:matrix.orgPhilip Taron (UTC-8) * Yeah, exactly.23:00:24
@infinisil:matrix.orginfinisilOh you mean to not do the pinning anymore?23:00:55
@infinisil:matrix.orginfinisilOh right you said that23:01:04
@philiptaron:matrix.orgPhilip Taron (UTC-8) Yes. The version in nixpkgs is the pinned version. 23:01:10
@philiptaron:matrix.orgPhilip Taron (UTC-8)And hence cached and build however is right for running in nixpkgs CI!23:01:37
@philiptaron:matrix.orgPhilip Taron (UTC-8) Can absolutely be static if need be. 23:01:49
@infinisil:matrix.orginfinisilThat's problematic for PRs that change dependencies of the tool and would take a long time to build23:02:15
@infinisil:matrix.orginfinisilI think the pinning is very necessary, see https://github.com/NixOS/nixpkgs/pull/28137423:02:23
@infinisil:matrix.orginfinisilWell not sure if that's the right thing to link to actually23:03:04
@philiptaron:matrix.orgPhilip Taron (UTC-8)Yeah, I think that's covered by the move to a separate repo.23:03:26
@infinisil:matrix.orginfinisilOh it's here: https://github.com/NixOS/nixpkgs/tree/master/pkgs/test/nixpkgs-check-by-name/scripts#update-pinned-toolsh23:03:37
@infinisil:matrix.orginfinisilSee the "Why not just build the tooling right from the PRs Nixpkgs version?" part23:03:46
@philiptaron:matrix.orgPhilip Taron (UTC-8)OK, those are pretty compelling.23:04:21
@infinisil:matrix.orginfinisilOh what would work is to also pin the Nixpkgs version for the tool23:05:14
@infinisil:matrix.orginfinisil So it's (import pinnedNixpkgs {}).callPackage instead of pkgs.callPackage 23:05:38
@infinisil:matrix.orginfinisilWell you'd still need to have it be cached somewhere though..23:06:19

Show newer messages


Back to Room ListRoom Version: 9