You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release is published untested on real machines. CI installs
it in a VM; a VM exposes no NPU, one graphics device and no firmware
quirks, so a VM install passing says very little about a laptop.
Real installs have failed where every check was green.
The flake route (nixos-rebuild against this repo, see the
README) is the mature one and is what to use on a machine you care
about. The ISO installer is the least mature part of the project
and it partitions the disk before it can fail.
If you install from this image, please say how it went on the
release discussion — success as much as failure. The experimental
label comes off a release only once someone has reported a
successful install on physical hardware.
Upstream's install lists, v4.0.2 → v4.0.3. Each line is a decision
this port either mirrors or knowingly does not.
Added
broadcom-wl-dkms
Removed
broadcom-wl
A removal is the one worth reading twice: upstream dropping a package
is often a security decision, and a comment in this repo may still be
citing it as a reason for something.
Seeded config files that changed. A machine installed from this
release starts with these. One you already run keeps the copies in
your ~/.config, which are yours.
config/kitty/kitty.conf
default/hypr/apps/hermes.lua
Configuration changes
Defaults that changed. These take effect on a machine whose configuration.nix says nothing about them.
NixOS defaults this port sets. Not options of ours -- these are
settings nixarchy chooses on your behalf, and a machine that never
mentioned them follows the new value.
now services.nixi.enable = lib.mkDefault true; in modules/home.nix
now gpu-screen-recorder.enable = lib.mkDefault true; in modules/nixos.nix
now zramSwap.enable = lib.mkDefault true; in modules/nixos.nix
Package changes
Packages this repo pins by hand, rather than taking from nixpkgs.
aether 4.29.8, packaged here for the first time
Everything else
Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.
Omarchy 4.0.3, packaged for NixOS. One image this time.
nixarchy-v4.0.3-1-net.iso — 1.6G, downloads the desktop as it installs.
One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable. This is the image people
have been installing from, and it works.
The offline image is not in this release. It carried the whole
system closure and promised an install with no network at all, and
it stopped keeping that promise: the machine it produces evaluates a
closure the image does not carry, so it tries to build the world and
cannot, with no network to fall back on. The installer notices and
refuses rather than leaving a half-installed disk, but an image whose
only reason to exist is "no network needed" is not worth shipping
while it needs one. It returns when the check that installs from it
offline is green again.
sha256sum -c --ignore-missing SHA256SUMS
(--ignore-missing because one SHA256SUMS covers both images, and
nobody downloads both.)
Then write one to a USB stick and boot it. See Fresh-machine install
for what happens next.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What this release is
Omarchy
v4.0.3, packaged for NixOS, up fromv4.0.2inv4.0.2-12. Upstream's notes for it:https://github.com/basecamp/omarchy/releases/tag/v4.0.3
Packages v4.0.3 changes
Upstream's install lists, v4.0.2 → v4.0.3. Each line is a decision
this port either mirrors or knowingly does not.
Added
broadcom-wl-dkmsRemoved
broadcom-wlA removal is the one worth reading twice: upstream dropping a package
is often a security decision, and a comment in this repo may still be
citing it as a reason for something.
Seeded config files that changed. A machine installed from this
release starts with these. One you already run keeps the copies in
your
~/.config, which are yours.config/kitty/kitty.confdefault/hypr/apps/hermes.luaConfiguration changes
Defaults that changed. These take effect on a machine whose
configuration.nixsays nothing about them.programs.nixarchy.package:"store:omarchy-4.0.2"→"store:omarchy-4.0.3"programs.nixarchy.tree:"store:omarchy-4.0.2/share/omarchy"→"store:omarchy-4.0.3/share/omarchy"New options.
programs.nixarchy.apps.aether(default{})programs.nixarchy.apps.openclaw(default{})NixOS defaults this port sets. Not options of ours -- these are
settings nixarchy chooses on your behalf, and a machine that never
mentioned them follows the new value.
services.nixi.enable = lib.mkDefault true;inmodules/home.nixgpu-screen-recorder.enable = lib.mkDefault true;inmodules/nixos.nixzramSwap.enable = lib.mkDefault true;inmodules/nixos.nixPackage changes
Packages this repo pins by hand, rather than taking from nixpkgs.
aether4.29.8, packaged here for the first timeEverything else
Every merged change, grouped by where in the tree it landed. This repo
writes commit subjects as full sentences, so they are already the notes.
The desktop and what it configures
Installing, and the ISO
Packaged programs and the vendored tree
Checks and CI
Documentation
Elsewhere
24 changes since
v4.0.2-12.Getting it
Omarchy 4.0.3, packaged for NixOS. One image this time.
nixarchy-v4.0.3-1-net.iso— 1.6G, downloads the desktop as it installs.One file, no reassembly, and it needs a working network: its first
screen offers Wi-Fi if there is no cable. This is the image people
have been installing from, and it works.
The offline image is not in this release. It carried the whole
system closure and promised an install with no network at all, and
it stopped keeping that promise: the machine it produces evaluates a
closure the image does not carry, so it tries to build the world and
cannot, with no network to fall back on. The installer notices and
refuses rather than leaving a half-installed disk, but an image whose
only reason to exist is "no network needed" is not worth shipping
while it needs one. It returns when the check that installs from it
offline is green again.
(
--ignore-missingbecause one SHA256SUMS covers both images, andnobody downloads both.)
Then write one to a USB stick and boot it. See
Fresh-machine install
for what happens next.
What's Changed
New Contributors
Full Changelog: v4.0.2-12...v4.0.3-1
This discussion was created from the release v4.0.3-1 (experimental).
All reactions