!9IQChSjwSHXPPWTa:lix.systems

Lix

624 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms195 Servers

Load older messages


SenderMessageTime
19 Oct 2024
@blitz:chat.x86.lolblitz
In reply to @darohan:tchncs.de

Anyone else having a hard time installing the new Lix release? Both on a device that previously didn't have Lix, and one upgrading from 2.91.0, I get the error error: attribute 'stable_upstream' missing - both using a NixOS Flake. Scrolled up a ways in this chat, and did some googling, but it doesn't seem like anyone else is having this?

I get the same. Updating from 2.91.0 to 2.91.1 breaks the eval
11:22:40
@blitz:chat.x86.lolblitzit's this change: https://git.lix.systems/lix-project/nixos-module/commit/b3457b78ac65e9c4b2702b9b37f01c8355a82cb511:22:45
@blitz:chat.x86.lolblitzAlso in general it would be nice not to have to manually update version numbers. Maybe we could have a "stable" branch in lix/nixos-module that always points to the latest version?11:24:05
@jade_:matrix.org@jade_:matrix.orgthis has been suggested months ago and i have been too busy fighting other fires to do it. there is now a stable branch on the module, which i guess is about to force implementing more releng.17:57:51
@jade_:matrix.org@jade_:matrix.org * this has been suggested months ago and i have been too busy fighting other fires to do it. there (oops let me actually push it) is a stable branch on the module, which i guess is about to force implementing more releng.17:58:41
@jade_:matrix.org@jade_:matrix.orgpart of the resistance to implementing this (which i just ran into now) is that git does not like the idea of refs that are constantly force pushed, especially if they are in the tags namespace, but the most accurate thing to put into that ref is the id of an annotated tag18:02:39
@jade_:matrix.org@jade_:matrix.orgso it is a branch, but i expect people to be confused by the branch :/18:03:02
@antifuchs:asf.computerantifuchs yea, that's a very valid worry. I think this might be a case where having a "messy" history would be fine: whenever there's a new stable release, make a merge commit into stable (or whatever the branch is called) 18:24:48
@jade_:matrix.org@jade_:matrix.orgtrue, and i know exactly how to do that18:39:44
@jade_:matrix.org@jade_:matrix.orggit merge -s ours18:39:47
@jade_:matrix.org@jade_:matrix.orgit just would be more releng code and i am simply burned out completely on releng code18:40:12
@jade_:matrix.org@jade_:matrix.org left the room.18:40:36
20 Oct 2024
@kitten:plushie.cloudEvelyn joined the room.06:38:27
@darohan:tchncs.deDarohan
In reply to @blitz:chat.x86.lol
it's this change: https://git.lix.systems/lix-project/nixos-module/commit/b3457b78ac65e9c4b2702b9b37f01c8355a82cb5

Ah, was wondering where the source was. Would it be better for me to open an issue there?

07:54:49
@darohan:tchncs.deDarohan

Scrap that, looks like a fix has already been merged to main

07:56:58
@colons:vscary.cocolonscannot find Git revision.png
Download cannot find Git revision.png
11:56:11
@colons:vscary.cocolonsthis revision absolutely does exist in that repo. i've tried to wipe out .cache/nix/gitv3 and this still happens. idk what to do here11:56:38
@colons:vscary.cocolons(im using npins in a way similar to what https://jade.fyi/blog/pinning-nixos-with-npins/ recommends, if that matters)11:57:42
@aloisw:kde.orgaloisw The repo does contain the revision, but not the main branch. 11:58:20
@colons:vscary.cocolonsoh. im unsure why npins would have updated it then11:58:58
@colons:vscary.cocolonswhat do i do about this?11:59:09
@aloisw:kde.orgaloisw I'm not sure how npins works exactly, but that revision is on the stable branch, so maybe you specified that somewhere (and need to specify it in some other place too to apply during fetching). 12:00:00
@colons:vscary.cocolonsi'll have a look at my configs, thanks12:00:30
@colons:vscary.cocolonsbaffled that a pin would update outside of the branch it has been asked to track, but maybe i've got different branches specified in different places? i don't know how that would have happened12:00:59
@aloisw:kde.orgaloisw Can you show the entry in your npins/sources.json corresponding to the module? 12:01:25
@colons:vscary.cocolons
"lix": {
  "type": "GitRelease",
  "repository": {
    "type": "Git",
    "url": "https://git.lix.systems/lix-project/lix"
  },
  "pre_releases": false,
  "version_upper_bound": null,
  "release_prefix": null,
  "version": "2.91.1",
  "revision": "ad9d06f7838a25beec425ff406fe68721fef73be",
  "url": null,
  "hash": "0ibpbvc6871bqyab0msml2g2y3c6jvg6yb169lykg4257izss8c6"
},
12:03:08
@colons:vscary.cocolonsi tried setting 'branch' to 'stable' and it just removed it again12:03:32
@aloisw:kde.orgaloisw That's not the nixos-module. 12:03:37
@colons:vscary.cocolonsoh heck sorry12:03:49
@colons:vscary.cocolons
"lix-nixos-module": {
  "type": "GitRelease",
  "repository": {
    "type": "Git",
    "url": "https://git.lix.systems/lix-project/nixos-module"
  },
  "pre_releases": false,
  "version_upper_bound": null,
  "release_prefix": null,
  "version": "2.91.1",
  "revision": "6478f624b2a00367e0e3d750a2c7a9f3afb72712",
  "url": null,
  "hash": "1mq5741iwa10r93shg1y8q6cxa2zjppc2w10hsrv1gfac76p8nmj"
},
12:04:15

Show newer messages


Back to Room ListRoom Version: 10