!VRULIdgoKmKPzJZzjj:nixos.org

Nix Package Manager development

837 Members
For people hacking on Nix: https://github.com/NixOS/nix Nix maintainers can be reached here.180 Servers

Load older messages


SenderMessageTime
21 Jul 2025
@jovalie:matrix.org@jovalie:matrix.org joined the room.23:47:51
22 Jul 2025
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Seems ok after skimming through the fetchGit code. Though it'd be nice if someone more knowledgeable wrt to fetchers would also take a look (seems like Tom reviewed the PR prior to this one).00:03:23
@fzakaria:one.ems.hostfzakariaThanks for the review; yea okay -- i'll bug him :P03:03:38
@fzakaria:one.ems.hostfzakariait's a test case -- I actually found it trying to look into another bug.. the whole caching thing via git... is kind of whacky03:03:57
@fzakaria:one.ems.hostfzakariaNot sure how to tamp down the complexity though03:05:07
@fzakaria:one.ems.hostfzakariaFeeling good 💪 got another bug fixed https://github.com/NixOS/nix/pull/13521 (with a unit test rather than a functional test!)05:01:40
@fzakaria:one.ems.hostfzakariabug since 2.18.505:02:03
23 Jul 2025
@mrdev023:matrix.orgmrdev023Someone can review my MR https://github.com/NixOS/nixpkgs/pull/42174207:50:32
@mrdev023:matrix.orgmrdev023Please ^^07:50:44
@dramforever:matrix.orgdramforeverwrong channel, #nixpkgs-review:nixos.org07:51:21
@mrdev023:matrix.orgmrdev023Thx, i didn't know this room exist ^^07:51:48
@dramforever:matrix.orgdramforeveruh wait07:51:49
@dramforever:matrix.orgdramforeveryeah it doesn't i typo'd07:51:58
@dramforever:matrix.orgdramforever#review-requests:nixos.org07:52:10
@dramforever:matrix.orgdramforeverthis07:52:12
@mrdev023:matrix.orgmrdev023Thx #2 ^^07:52:24
@basum:matrix.orgmaharshi joined the room.14:53:48
24 Jul 2025
@keetonbrewster:matrix.orgKeeton Brewster joined the room.00:11:02
25 Jul 2025
@fzakaria:one.ems.hostfzakariaWhen changing CppNix code; i'm surprised tests don't cause a recompiling03:29:54
@fzakaria:one.ems.hostfzakaria I've caught myself forgetting to meson build after some change and thinking : why are my tests still failing 03:30:07
@fzakaria:one.ems.hostfzakaria(for the functional tests)03:30:24
@fzakaria:one.ems.hostfzakariaim sure this is :spicy: https://github.com/NixOS/nix/pull/1355003:49:07
@pveierland:matrix.orgpveierland

I'm working on some URL design to navigate packages within repositories and flakes, where /owner/repo/package/ref-or-rev/<attr-path> can seem sensible when dealing with packages in the root flake. What would be good ways of dealing with navigating to packages in subflakes? Some ideas:

  1. /owner/repo/package/ref-or-rev/<attr-path>?dir=sub (maching flakerefs)
  2. /owner/repo/flake/ref-or-rev/<flake-dir>/package/<attr-path> (using an explicit flake resource type, however this requires resolving possible ambiguity for cases where the subflake resource part may contain / for some reason, or e.g. use a delimiter symbol.
    Any opinions? :)
05:17:02
@pveierland:matrix.orgpveierland *

I'm working on some URL design to navigate packages within repositories and flakes, where /owner/repo/package/ref-or-rev/<attr-path> can seem sensible when dealing with packages in the root flake. What would be good ways of dealing with navigating to packages in subflakes? Some ideas:

  1. /owner/repo/package/ref-or-rev/<attr-path>?dir=sub (maching flakerefs)
  2. /owner/repo/flake/ref-or-rev/<flake-dir>/package/<attr-path> (using an explicit flake resource type, however this requires resolving possible ambiguity for cases where the subflake resource part may contain / for some reason, or e.g. use a delimiter symbol.
05:17:11
@pveierland:matrix.orgpveierland *

I'm working on some URL design to navigate packages within repositories and flakes, where /owner/repo/package/ref-or-rev/<attr-path> can seem sensible when dealing with packages in the root flake. What would be good ways of dealing with navigating to packages in subflakes? Some ideas:

  1. /owner/repo/package/ref-or-rev/<attr-path>?dir=sub (Matching flakerefs)
  2. /owner/repo/flake/ref-or-rev/<flake-dir>/package/<attr-path> (Using an explicit flake resource type, however this requires resolving possible ambiguity for cases where the subflake resource part may contain / for some reason, or e.g. use a delimiter symbol. It could also provide more flexibility wrt. supporting other mechanisms in addition to flakes)
05:19:50
@jovalie:matrix.org@jovalie:matrix.org left the room.05:26:10
@fzakaria:one.ems.hostfzakariaFound another bug + minor improvement to libgit2 https://github.com/NixOS/nix/pull/1355105:33:25
@fzakaria:one.ems.hostfzakaria Can someone let me know how I can test the flake input attrs like "ref" via nix eval 16:33:10
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @fzakaria:one.ems.host
Found another bug + minor improvement to libgit2 https://github.com/NixOS/nix/pull/13551
As a part of the flakeRef? Those can be specified as a URI query paremeter.
16:50:40
@dramforever:matrix.orgdramforever ah, test, you mean git+https://something/something.git?ref=somebranch? 16:52:40

Show newer messages


Back to Room ListRoom Version: 6