Add "latest release" branch

perchunpak commented

2024-10-12 10:13:55 +00:00

I would like to be able to update my Lix with just nix flake update, and not changing version in flake.nix manually. Currently, I have to use main branch and daily drive dev version for this.

I would like to be able to update my Lix with just `nix flake update`, and not changing version in flake.nix manually. Currently, I have to use main branch and daily drive dev version for this.

perchunpak commented

2024-10-13 09:15:09 +00:00

Author

I just had to reinstall the entire system, because dev version had some problems with checking if path existed in the store, and --repair just rm -rfed my system derivation...

But at least all data is safe and everything works fine after updating

EDIT: this is the fix 8e05cc1e6c

I noticed that if I rerun nixos-rebuild with --repair flag, it would fix the errors sometimes. So I did while ! sudo nixos-rebuild ...; do; end (basically rerun command until it successes) and left it for the entire day. Next time I checked, there wasn't nixos-system-perchun-pc-24.11.20241012.476bcb4 derivation in the store.

Anyway, I would like to use the stable version with auto updates

I just had to reinstall the entire system, because dev version had some problems with checking if path existed in the store, and `--repair` just `rm -rf`ed my system derivation... But at least all data is safe and everything works fine after updating EDIT: this is the fix https://git.lix.systems/lix-project/lix/commit/8e05cc1e6c5eb1729e06835baf9114c4be8b82ee I noticed that if I rerun `nixos-rebuild` with `--repair` flag, it would fix the errors sometimes. So I did `while ! sudo nixos-rebuild ...; do; end` (basically rerun command until it successes) and left it for the entire day. Next time I checked, there wasn't `nixos-system-perchun-pc-24.11.20241012.476bcb4` derivation in the store. Anyway, I would like to use the stable version with auto updates

attilaolah referenced this issue

2024-10-19 10:48:21 +00:00

How are releases tagged? #40

perchunpak commented

2024-11-17 20:56:07 +00:00

Author

BTW this is not hard to implement at all. Just whenever a new release comes out, do git reset --hard vX.Y.Z && git push -f

BTW this is not hard to implement at all. Just whenever a new release comes out, do `git reset --hard vX.Y.Z && git push -f`

jade commented

2024-11-18 21:19:33 +00:00

Owner

"not hard to implement", obviously, yes, but we have a releng system for lix itself and a particular way that everything works and that writing a separate releng for this would maybe not be so smart. it's not hard, it's that the wider task is more complex.

and in fact, git push -f is not necessarily the right way to implement this if you want e.g. history of which release tag it pointed to. fixing this (adding a new requirement) properly in a way that does not add more stuff to be fixed up later when we clean up releng is a little more complicated.

"not hard to implement", obviously, yes, but we have a releng system for lix itself and a particular way that everything works and that writing a separate releng for this would maybe not be so smart. it's not *hard*, it's that the wider task is more complex. and in fact, *git push -f* is not necessarily the right way to implement this if you want e.g. history of which release tag it pointed to. fixing this (adding a new requirement) properly in a way that does not add more stuff to be fixed up later when we clean up releng is a little more complicated.

Add "latest release" branch #39