russet repo-update
russet repo-update updates one or more recipe repositories by running
git pull in each one.
Syntax
Section titled “Syntax”russet repo-update [OPTIONS] REPOSITORY [REPOSITORY ...]Replace the following:
OPTIONS: any of the options in the following table.REPOSITORY:allto update every recipe repository that you added, or a recipe repository’s local path, URL, or short form, such asrecipes.
Description
Section titled “Description”For each recipe repository, Russet prints
Attempting git pull for PATH... and then the output from Git. If the local branch
is master and the remote has only a main branch, Russet switches the local
branch to main before it pulls. If anything changed, Russet refreshes the
recipe map.
Russet runs the Git executable that the GIT_PATH preference names, or git
from your PATH. If Git fails or Russet can’t find a recipe repository,
Russet prints the error and continues, so check the output.
After an update, recipe overrides whose parent recipes changed fail trust verification until you review the changes. For details, see Recipe trust.
Options
Section titled “Options”| Option | Description |
|---|---|
--prefs FILE |
Reads preferences from FILE on top of Russet’s preferences. |
Exit status
Section titled “Exit status”| Status | Meaning |
|---|---|
0 |
Russet finished. Git errors and unknown recipe repositories don’t change the status. |
1 |
Russet couldn’t read the --prefs file. |
2 |
Russet couldn’t parse an option. |
255 |
You didn’t name a recipe repository. On Windows, the status is -1. |
Examples
Section titled “Examples”To update every recipe repository that you added, run the following command:
russet repo-update allWhen a recipe repository has no changes, the output looks like the following:
Attempting git pull for /Users/alex/Library/Russet/RecipeRepos/com.github.autopkg.recipes...Already up to date.