&dhemail;
&dhfirstname;
&dhsurname;
gbp-import-orig
&dhsection;
gbp-import-origImport an upstream source into a git repository
&gbp-import-orig;
&man.common.options.synopsis;
version[merge|replace]branch_namebranch_nametag-formatgpg-keyidtag-formatpatterncomponentupstream-sourceDESCRIPTION
&gbp-import-orig; imports upstream-source into
the &git; repository. upstream-source can either
be a gzip, bzip2, lzma or xz compressed tar archive, a zip 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 tarball's filename, otherwise it can be given
on the command line via . If the source
package name or version can't be determined, &gbp-import-orig; will prompt
for it unless is given.
The sources are placed on the upstream branch (default:
upstream), tagged and merged onto the debian
branch (default: master).
OPTIONS
&man.common.options.description;
=versionversion
The upstream version number
Merge the upstream branch to the &debian; branch after import
[merge|replace]
How to fold the newly imported upstream source to the
&debian; packaging branch after import.
The default mode
merge does a
&git; merge leaving you on your own in
case of merge conflict resolution.
replace mode on the
other hand makes the head of the &debian; packaging branch
identical to the newly imported tree but preserves the
content of the debian/ directory
while keeping the current head as well as the newly
important trees as parents of the generated commit. This is
similar to a merge strategy while
preserving debian/.
=branch_name
The branch in the &git; repository the upstream sources are put
onto. Default is upstream.
=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, &gbp-import-orig;
will try to merge the new version onto this branch.
=tag-format
Add tag-format as additional parent to the
commit of the upstream tarball. Useful when upstream uses git and you
want to link to its revision history. The
tag-format can be a pattern similar to
what supports.
GPG sign all created tags
gpg-keyid
use this keyid for gpg signing tags
tag-format
use this tag format when tagging upstream versions,
default is upstream/%(version)smsg-format
use this format string for the commit message when importing upstream
versions, default is
New upstream version %(version)spattern
filter out files glob-matching pattern. Can be given multiple times.
COMPONENT
When importing the upstream tarball also look for an additional tarball
with component name COMPONENT. E.g. in
hello-debhelper_1.0.orig-foo.tar.gz
the component would be foo. The additional
tarball is expected to be in the same directory than the upstream tarball
and to use the same compression type.
Using additional original tarballs is a feature of the 3.0
(quilt) source format. See
the dpkg-source manpage for
details. Note that this option can't be set via &gbp.conf;
since it's considered an experimental feature and might
change incompatibly.
generate pristine-tar delta file
if using a filter, also filter the files out of the tarball
passed to pristine-tar
Whether to create and keep a symlink from the upstream tarball
to a &debian; policy conformant upstream tarball name located in
../.
This is a good idea if not using pristine-tar
since it avoids creating a new tarball with a different md5sum.
run cmd after the import.
Use uscan to fetch new upstream version.
Download the tarball from the given HTTP URL. This needs
python-request installed.
Run command interactively, i.e. ask package name and version if
needed.
EXAMPLES
Download and import a new upstream version using the information from debian/watch
&gbp-import-orig; --uscan
After downloading an upstream tarball by hand, import it
&gbp-import-orig; ../upstream-tarball-0.1.tar.gz
&man.gbp.config-files;
SEE ALSO,
,
,
,
,
&man.seealso.common;
AUTHOR
&dhusername; &dhemail;