Channel branches: Difference between revisions
imported>Raboof →Channel update process: what to do when nixos-unstable is blocked and you want a particular fix |
imported>Raboof link to channel history |
||
| Line 59: | Line 59: | ||
To find out when a channel was last updated, check [https://status.nixos.org/ this] page. | To find out when a channel was last updated, check [https://status.nixos.org/ this] page. | ||
== When unstable lags behind master == | |||
As https://status.nixos.org shows, a downside of nixos-unstable is that when the channel is blocked due to hydra failures, other (security) fixes will also not get in. While of course we try to keep hydra green, it is expected that this happens every once in a while. When you want to upgrade or downgrade a single package while leaving the rest of your system on nixos-unstable, you could use [[User:Raboof#using_a_fork_of_a_packaged_project|this approach]]. | As https://status.nixos.org shows, a downside of nixos-unstable is that when the channel is blocked due to hydra failures, other (security) fixes will also not get in. While of course we try to keep hydra green, it is expected that this happens every once in a while. When you want to upgrade or downgrade a single package while leaving the rest of your system on nixos-unstable, you could use [[User:Raboof#using_a_fork_of_a_packaged_project|this approach]]. | ||
== Channel history == | |||
You can find the channel history at https://channels.nix.gsc.io/ | |||