3
0
Fork 0
forked from mirrors/nixpkgs

Remove references to the nixpkgs-channels repo

Channel branches are now provided in the nixpkgs repo.

Issue #71176.
This commit is contained in:
Eelco Dolstra 2019-10-17 19:43:07 +02:00
parent fc6706f126
commit 5b324c1825
No known key found for this signature in database
GPG key ID: 8170B4726D7198DE
4 changed files with 13 additions and 23 deletions

View file

@ -51,9 +51,7 @@ system, [Hydra](https://hydra.nixos.org/).
Artifacts successfully built with Hydra are published to cache at Artifacts successfully built with Hydra are published to cache at
https://cache.nixos.org/. When successful build and test criteria are https://cache.nixos.org/. When successful build and test criteria are
met, the Nixpkgs expressions are distributed via [Nix met, the Nixpkgs expressions are distributed via [Nix
channels](https://nixos.org/nix/manual/#sec-channels). The channels channels](https://nixos.org/nix/manual/#sec-channels).
are provided via a read-only mirror of the Nixpkgs repository called
[nixpkgs-channels](https://github.com/NixOS/nixpkgs-channels).
# Contributing # Contributing

View file

@ -47,5 +47,5 @@ which also builds binary packages from the Nix expressions in Nixpkgs for
The binaries are made available via a [binary cache](https://cache.nixos.org). The binaries are made available via a [binary cache](https://cache.nixos.org).
The current Nix expressions of the channels are available in the The current Nix expressions of the channels are available in the
[`nixpkgs-channels`](https://github.com/NixOS/nixpkgs-channels) repository, [`nixpkgs`](https://github.com/NixOS/nixpkgs) repository in branches
which has branches corresponding to the available channels. that correspond to the channel names (e.g. `nixos-19.09-small`).

View file

@ -115,19 +115,12 @@
<para> <para>
It is possible to rebase the changes on nixos-unstable or nixpkgs-unstable for easier review by running the following commands from a nixpkgs clone. It is possible to rebase the changes on nixos-unstable or nixpkgs-unstable for easier review by running the following commands from a nixpkgs clone.
<screen> <screen>
<prompt>$ </prompt>git remote add channels https://github.com/NixOS/nixpkgs-channels.git <co <prompt>$ </prompt>git fetch origin nixos-unstable <co xml:id='reviewing-rebase-2' />
xml:id='reviewing-rebase-1' />
<prompt>$ </prompt>git fetch channels nixos-unstable <co xml:id='reviewing-rebase-2' />
<prompt>$ </prompt>git fetch origin pull/PRNUMBER/head <co xml:id='reviewing-rebase-3' /> <prompt>$ </prompt>git fetch origin pull/PRNUMBER/head <co xml:id='reviewing-rebase-3' />
<prompt>$ </prompt>git rebase --onto nixos-unstable BASEBRANCH FETCH_HEAD <co <prompt>$ </prompt>git rebase --onto nixos-unstable BASEBRANCH FETCH_HEAD <co
xml:id='reviewing-rebase-4' /> xml:id='reviewing-rebase-4' />
</screen> </screen>
<calloutlist> <calloutlist>
<callout arearefs='reviewing-rebase-1'>
<para>
This should be done only once to be able to fetch channel branches from the nixpkgs-channels repository.
</para>
</callout>
<callout arearefs='reviewing-rebase-2'> <callout arearefs='reviewing-rebase-2'>
<para> <para>
Fetching the nixos-unstable branch. Fetching the nixos-unstable branch.

View file

@ -13,17 +13,16 @@
<screen> <screen>
<prompt>$ </prompt>git clone https://github.com/NixOS/nixpkgs <prompt>$ </prompt>git clone https://github.com/NixOS/nixpkgs
<prompt>$ </prompt>cd nixpkgs <prompt>$ </prompt>cd nixpkgs
<prompt>$ </prompt>git remote add channels https://github.com/NixOS/nixpkgs-channels <prompt>$ </prompt>git remote update origin
<prompt>$ </prompt>git remote update channels
</screen> </screen>
This will check out the latest Nixpkgs sources to This will check out the latest Nixpkgs sources to
<filename>./nixpkgs</filename> the NixOS sources to <filename>./nixpkgs</filename> the NixOS sources to
<filename>./nixpkgs/nixos</filename>. (The NixOS source tree lives in a <filename>./nixpkgs/nixos</filename>. (The NixOS source tree lives in a
subdirectory of the Nixpkgs repository.) The remote subdirectory of the Nixpkgs repository.) The
<literal>channels</literal> refers to a read-only repository that tracks the <literal>nixpkgs</literal> repository has branches that correspond
Nixpkgs/NixOS channels (see <xref linkend="sec-upgrading"/> for more to each Nixpkgs/NixOS channel (see <xref linkend="sec-upgrading"/> for more
information about channels). Thus, the Git branch information about channels). Thus, the Git branch
<literal>channels/nixos-17.03</literal> will contain the latest built and <literal>origin/nixos-17.03</literal> will contain the latest built and
tested version available in the <literal>nixos-17.03</literal> channel. tested version available in the <literal>nixos-17.03</literal> channel.
</para> </para>
<para> <para>
@ -40,15 +39,15 @@
Or, to base your local branch on the latest version available in a NixOS Or, to base your local branch on the latest version available in a NixOS
channel: channel:
<screen> <screen>
<prompt>$ </prompt>git remote update channels <prompt>$ </prompt>git remote update origin
<prompt>$ </prompt>git checkout -b local channels/nixos-17.03 <prompt>$ </prompt>git checkout -b local origin/nixos-17.03
</screen> </screen>
(Replace <literal>nixos-17.03</literal> with the name of the channel you want (Replace <literal>nixos-17.03</literal> with the name of the channel you want
to use.) You can use <command>git merge</command> or <command>git to use.) You can use <command>git merge</command> or <command>git
rebase</command> to keep your local branch in sync with the channel, e.g. rebase</command> to keep your local branch in sync with the channel, e.g.
<screen> <screen>
<prompt>$ </prompt>git remote update channels <prompt>$ </prompt>git remote update origin
<prompt>$ </prompt>git merge channels/nixos-17.03 <prompt>$ </prompt>git merge origin/nixos-17.03
</screen> </screen>
You can use <command>git cherry-pick</command> to copy commits from your You can use <command>git cherry-pick</command> to copy commits from your
local branch to the upstream branch. local branch to the upstream branch.