| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Thanks: Sandro Tosi
Closes: #748339
|
|
|
|
|
| |
This allows us to build an internal list of valid options and print
these.
|
|
|
|
|
|
| |
This only allows to print single config values so far.
Closes: #733470
|
|
|
|
|
|
| |
revealing another bug where we overwrote parsed values with defaults
Closes: #733759
|
|
|
|
|
|
| |
mostly reverting e1780f0.
Closes: #742907
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first line lacked the subcommand like:
$ gbp pull --help
Usage: gbp [options] - safely update a repository from remote
instead of
$ gbp pull --help
Usage: gbp pull [options] - safely update a repository from remote
^^^^
|
|
|
|
|
|
| |
This would otherwise overwrite values set in the legacy config sections.
Closes: #733759
|
|
|
|
|
|
| |
This would otherwise overwrite values set in the legacy config sections.
Closes: #733759
|
|
|
|
|
|
|
|
|
| |
Running a clean command within version control by default nowadays
causes more trouble than it helps. It's unnecessary with
pbuilder/cowbuilder/sbuild and with export-dir. So change the default
from 'debuild clean' to a noop ('/bin/true').
Closes: #670624
|
|
|
|
|
|
|
|
|
|
|
| |
Always read the legacy command's config file section prior to the
subcommand's config file section.
Until now 'gbp <subcommand>' would read '[subcommand]' as well as
'[gbp-<subcommand>]' sections while 'gbp-<subcommand>' would only read
'[gbp-<subcommand>]' sections.
Closes: #733759
|
|
|
|
|
|
|
| |
Otherwise the mangled GBP_CONF_FILES affects also other doctests when
run with python-nose.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's no need to fill the parser with all the built in defaults since
we can simply copy them to the config from the class dict. This allows
us to first set the values from the old {git,gbp}-* commands and then
only overwrite changed values from the newer "gbp <command>" versions.
Otherwise we'd overwite all old style config with the new style one.
This also fixes the problem where the default section wouldn't be read
at all if the command doesn't even have an empty section in any gbp.conf
file.
|
|
|
|
| |
and robustify against invalid modules names.
|
|
|
|
|
| |
For backward compatibility between {gbp,git}-<subcommand> and "gbp
<subcommand>" make sure we parse the former sections if using the later.
|
|
|
|
|
| |
and not the one from the OptionParser. The instance's default dict this
gets reset to empty when invoking OptionParser.__init__.
|
|
|
|
|
|
|
| |
For enabling/disabling all hooks. This option does not affect the
builder command, though.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
|
|
|
|
|
| |
so introdice --git[-no]-purge which is consistent with the other
boolean options and deprecate --git-dont-purge.
Closes: #702200
|
|
|
|
|
|
|
| |
Adds a new command line and config file option 'color-scheme' for
selecting the colors used in log output.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
|
|
|
|
| |
that's used make pristine-tar see the correct orig tarball name.
Closes: #692401
|
| |
|
| |
|
|
|
|
| |
Closes: #670623
|
|
|
|
| |
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
|
| |
Closes: #669145
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
| |
This specifies an additional config file section that can be used
to preconfigure different remote locations.
|
|
|
|
|
|
|
| |
This makes it possible to parse additional mandatory sections
from config files to prefill defaults.
Git-Dch: Ignore
|
|
|
|
| |
Git-Dch: Ignore
|
|
|
|
| |
to git init so it's possible to set up remote hooks.
|
|
|
|
| |
by setting the GBP_CONF_FILES environment variable.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Split GbpOptionParser in to a common base class and a Debian
specific subclass, as a preparation for upcoming RPM support.
This allows having different default values (and help texts) for common
options between different package types, and, clearer separation of
package type specific options.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
|
|
|
|
|
| |
This option allows to auto commit a generated tarball to the
pristine-tar branch to simplify building non-dfsg clean packages and to
make it easier to track uptream git.
|
| |
|
|
|
|
| |
via commandline or gbp.conf
|
|
|
|
| |
without the indirection to --upstream-branch.
|
|
|
|
| |
to pass GIT_PBUILDER_AUTOCONF=no to git-pbuilder.
|
|
|
|
|
|
| |
Heavily based on a patch by Jan Čapek
Closes: #640982
|
|
|
|
| |
This allows us to build on non Debian systems with setup.py only.
|
|
|
|
| |
The python2.7 OptionParser chokes otherwise.
|
|
|
|
| |
to find the last commit the patch-queue applies to.
|
|
|
|
| |
Git-Dch: Ignore
|
|
|
|
| |
Git-Dch: Ignore
|
|
|
|
|
|
|
|
|
| |
to specify where the upstream tarball should be created from. The
default is to create the upstream tarball from the exact tag and fail
otherwise. To create the upstream tarball from the tip of the upstream
branch use 'branch'.
Based on a patch by Ricardo Salveti de Araujo
|
|
|
|
|
| |
Thanks: Ritesh Raj Sarraf
Closes: #632897
|
|
|
|
| |
Closes: #601298
|
|
|
|
| |
Git-Dch: Ignore
|
| |
|
| |
|
|
|
|
| |
Git-Dch: Ignore
|