gbp-clonegbp-clone — Clone a Git repository from a remote and set up the necessary branch tracking |
gbp clone
[--version
] [--help
] [--verbose
] [--color=
[auto|on|off]] [--color-scheme=
COLOR_SCHEME
] [--all
] [--[no-]pristine-tar
] [--debian-branch=
branch_name
] [--upstream-branch=
branch_name
] [--depth=
depth
] [--reference=
repository
] [--postclone=
COMMAND
] [--[no-]hooks
] [--defuse-gitattributes=
[auto|on|off]
] [--repo-user=
[GIT|DEBIAN]
] [--repo-email=
[GIT|DEBIAN]
] [--[no-]aliases
] [--[no-]add-upstream-vcs
] repository
[directory
]
Unlike a regular git clone, the gbp clone will parse the debian/gbp.conf options and clone the remote repository with correct branches tracked.
Likewise, it is recommended to use gbp pull and gbp push to later update the repository as it will spare from having to run git pull and git push multiple times or with lenghty arguments to sync each tracked branch.
|
Print version of the program, i.e. version of the git-buildpackage suite |
|
Verbose execution |
|
Print help and exit |
|
Whether to use colored output. |
|
Colors to use in output (when color is enabled). The format for
COLOR_SCHEME is
'<debug>:<info>:<warning>:<error>'.
Numerical values and color names are accepted, empty fields imply
the default color. For example,
|
|
Track all branches, not only |
|
The branch in the Git repository the Debian package is being
developed on, default is |
|
The branch in the Git repository the upstream sources are put
onto. Default is |
|
Git history depth, for creating shallow git clones. |
|
Local repository to use as alternate instead of re-copying data from remote repository. |
|
Track pristine tar branch. |
|
Enable running hooks. |
|
Execute
Exported environment variables are: Note that if you clone a repository that contains a
hook configuration in |
|
Disable Git attributes that may interfere with building packages. Works
by updating
If set to |
|
When set to |
|
When set to |
|
Whether to expand gbp specific aliases for remote repos like salsa:. |
|
Whether to add the upstream git repository as additional remote. The repository url is read from
the "Repository" field in
|
|
The (possibly remote) repository to clone from. This is usually a Git URL but some shortcuts are supported (see below). |
|
The directory to clone to. |
Clone the Debian packaging repository and the upstream repository in one go:
gbp clone -add-upstream-vcs vcs-git:entr
The branches, tags and pristine-tar will be automatically setup correctly following the contents of debian/gbp.conf in the package, and there will be an additional git remote with the name upstreamvcs that points to the upstream Entr repository on GitHub.
A parameter on the command line would override anything in the debian/gbp.conf file. For example, clone a repository and setup a tracking branch for pristine-tar as well:
gbp clone --pristine-tar git://honk.sigxcpu.org/git/git-buildpackage.git
Clone from the Git-Vcs URL of a package:
gbp clone vcs-git:libvirt
Clone a repository from Salsa (Debian's code hosting):
gbp clone salsa:agx/git-buildpackage
Clone from a GitHub repository:
gbp clone github:agx/git-buildpackage
Several gbp.conf
files are parsed
to set defaults for the above command-line arguments. See the
gbp.conf(5) manpage for details.