git-import-orig(1) [debian man page]
GIT-IMPORT-ORIG(1) git-buildpackage Manual GIT-IMPORT-ORIG(1) NAME
git-import-orig - Import an upstream source into a git repository SYNOPSIS
git-import-orig [ --verbose ] [ --upstream-version=version ] [ --[no-]merge ] [ --upstream-branch=branch_name ] [ --debian- branch=branch_name ] [ --upstream-vcs-tag=tag_name ] [ --[no-]sign-tags ] [ --keyid=gpg-keyid ] [ --upstream-tag=tag-format ] [ --fil- ter=pattern ] [ --[no-]pristine-tar ] [ --[no-]filter-pristine-tar ] [ --postimport=cmd ] [ --uscan ] upstream-source DESCRIPTION
git-import-orig imports upstream-source into the Git repository. upstream-source can either be a gzip or bzip2 compressed tar archive or an already unpacked source tree. If it is already of the form package-name_version.orig.tar.gz, the version information is read from the tar- ball's filename otherwise it can be given on the command line via --upstream-version. The sources are placed on the upstream branch (default: upstream), tagged and merged onto the debian branch (default: master). OPTIONS
--upstream-version=version -uversion The upstream version number --merge Merge the upstream branch to the debian branch after import --upstream-branch=branch_name The branch in the Git repository the upstream sources are put onto. Default is upstream. --debian-branch=branch_name The branch in the Git repository the Debian package is being developed on, default is master. After importing the new sources on the upstream branch, git-import-orig will try to merge the new version onto this branch. --upstream-vcs-tag=tag_name Add tag_name as additional parent to the commit of the upstream tarball. Useful when upstream uses git and you want to link to it's revision history. --verbose -v verbose execution --[no-]sign-tags GPG sign all created tags --keyid=gpg-keyid use this keyid for gpg signing tags --upstream-tag=tag-format use this tag format when tagging upstream versions, default is upstream/%(versions)s --import-msg=msg-format use this format string for the commit message when importing upstream versions, default is Imported Upstream version %(version)s --filter=pattern filter out files glob-matching pattern. Can be given multiple times. --pristine-tar generate pristine-tar delta file --filter-pristine-tar if using a filter also filter the files out of the tarball passed to pristine tar --postimport=cmd run cmd after the import. --uscan Use uscan to fetch new upstream version. CONFIGURATION FILES
Several gbp.conf files are parsed to set defaults for the above commandline arguments. See the [XRef to GBP.MAN.GBP.CONF] manpage for details. SEE ALSO
git-buildpackage(1), git-import-dsc(1), git-import-dscs(1), git-dch(1), gbp.conf(5), debuild(1), git(1), pristine-tar(1), The Git-Build- package Manual <URL:file:///usr/share/doc/git-buildpackage/manual-html/index.html> AUTHOR
Guido Guenther <agx@sigxcpu.org> 01 June 2012 GIT-IMPORT-ORIG(1)
Check Out this Related Man Page
GBP.CONF(5) gbp.conf Manual GBP.CONF(5) NAME
gbp.conf - git-buildpackage configuration file SYNOPSIS
/etc/git-buildpackage/gbp.conf system wide ~/.gbp.conf per user .gbp.conf per branch, can be published with the repository (deprecated) debian/gbp.conf per branch, can be published with the repository .git/gbp.conf per repository DESCRIPTION
The gbp.conf provides default global options and specific options for git-buildpackage commands. All have the same format and are parsed in the above order. The file consists of several sections, one for each command. Comments start with a hash sign (#). The generic file syntax is: [DEFAULT] # This is section for global settings. Affects all commands key = value [<command>] # Specific sections for each command, like git-buildpackage key = value [remote-config <name>] # Specific sections for a remote configuration. This can be used several # times to set up remote configuration for gbp-create-remote-repo key = value key=value pairs of the command sections reflect the command line options and their settings. For example git-buildpackage(1) manualpage contains the --git-export-dir=diirectory option which can be turned into configuration file setting by dropping the --git prefix with: [git-buildpackage] export-dir = directory Notice that some option are actually repeatable, or take Python lists. For example the git-import-orig(1) commmand has the --filter=pat- tern option which can be truned into a configuration file option like this: [git-import-orig] filter = .svn filter = .hg An alternative way is to write it using Python list syntax: [git-import-orig] filter = [ '.svn', '.hg' ] Boolean options can bei either True or False. For example git-import-orig(1); has the --pristine-tar and --no-pristine-tar options which translate to: [git-import-orig] pristine-tar = True and [git-import-orig] pristine-tar = False respectively. Note: To see the current set of values that would be applied after parsing the configuration files run the command with --help and check it's output. Note: git-import-dscs and git-pbuilder can't be configured via gbp.conf. gbp-create-remote-repo(1) can additionally parse remote site configurations from gbp.conf. For example a configration like: [remote-config pkg-libvirt] # Location of the repository remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s # Template dir to passed to git-init template-dir = /srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-template Can be used to create remote repositories for the pkg-libvirt project using: gbp-create-remote-repo --remote-config=pkg-libvirt This can be useful if you're often creating new remote repositores for different projects. EXAMPLES
An example set up for packaging work: # $HOME/gbp.conf [DEFAULT] pristine-tar = True cleaner = fakeroot debian/rules clean [git-buildpackage] export-dir = ../build-area/ [git-import-orig] dch = False filter = .svn filter = .hg filter = .bzr filter = CVS filter = debian/* filter = */debian/* filter-pristine-tar = True [git-import-dsc] filter = [ 'CVS', '.cvsignore', '.hg', '.hgignore' '.bzr', '.bzrignore', '.gitignore' ] # End of file ENVIRONMENT
GBP_CONF_FILES Colon separated list of files to parse. The default is the above list of configuration files. FILES
See See /etc/git-buildpackage/gbp.conf for an example. STANDARDS
The at The Git-Buildpackage Manual <URL:file:///usr/share/doc/git-buildpackage/manual-html/index.html> at /usr/share/doc/git-buildpack- age/manual-html/index.html SEE ALSO
gbp-clone(1), gbp-create-remote-repo(1), gbp-pq(1) gbp-pull(1), git-dch(1), git-import-dsc(1), git-import-orig(1), git-buildpackage(1) AUTHORS
Guido Guenther <agx@sigxcpu.org> This manual page is based on a POD version by Jari Aalto <jari.aalto@cante.net>. Released under license GNU GPL version 2 or (at your option) any later. version. 01 June 2012 GBP.CONF(5)