Gbp-Dch: Ignore

Not everyone just puts built debs to ../

No changes required

Closes: #1023379

Gbp-Dch: Ignore

This works around #1020024

Debian defaults to installing to /usr/local, unless told otherwise. This
is usually done by passing --install-layout=deb to setup.py, when called
directly. But that's only an option on Debian systems that have this
patch. Set the environment variable equivalent, instead.

Debian uses the posix_local scheme by default, since Python 3.10,
causing the rpm to be built with the incorrect layout.

This makes sure we don't export very generic vars while still being able
to make decisions based on what was passed to gbp.

While "gbp import-orig" supports "--upstream-vcs" since some time to
link to the upstream git history however setup of the upstream remoet
repo so far was manual.

To make this more automatic add "--add-upstream-vcs" to "gbp clone"
(defaulting to False) and set up the upstreamvcs remote in case there's
sufficient information in debian/upstream/metadata. Once added fetch
from that remote initially.

No reason to restrict this to build-package

Closes: #1012717

See #1005873, #1010061

Closes: #879495

The error message mistakenly talks about the upstream branch when it
should be talking about the debian branch. Logs:

	# initial failure
	$ gbp import-dsc apt:desktop-base/sid
	gbp:info: Downloading 'desktop-base/sid' using 'apt-get'...
	gbp:info: Tag 11.0.2 not found, importing Debian tarball
	gbp:error:
	Repository does not have branch 'master' for upstream sources. If there is none see
	file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT
	on howto create it otherwise use --upstream-branch to specify it.

	Also check the --create-missing-branches option.

	# trying as suggested
	$ gbp import-dsc --upstream-branch=debian apt:desktop-base/sid
	gbp:info: Downloading 'desktop-base/sid' using 'apt-get'...
	gbp:info: Tag 11.0.2 not found, importing Debian tarball
	gbp:error:
	Repository does not have branch 'master' for upstream sources. If there is none see
	file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT
	on howto create it otherwise use --upstream-branch to specify it.

	Also check the --create-missing-branches option.

	# in fact it's the debian branch!
	$ gbp import-dsc --debian-branch=debian apt:desktop-base/sid
	gbp:info: Downloading 'desktop-base/sid' using 'apt-get'...
	gbp:info: Tag 11.0.2 not found, importing Debian tarball
	gbp:info: Version '11.0.2' imported under '/home/user/src/desktop-base'

Closes: #984516

Closes: #934200

It's not even in oldoldoldstable anymore

Just enough to make mypy happy

Ignore rpm and libnotify for the moment

Just enough to  make mypy happy.

Add an option that allow to skip exansion of aliases like salsa:
by gbp so that git can do that.

Closes: #983085

Thanks: Tino Mettler

This can resolve ambiguity when generating the rev list.

Closes: #966627

No attempt is being made to ensure this is a local branch.

We shouldn't just replace any occurence since we otherwise might also
substitute in the submodule.

Based on a patch by "ushen <yshxxsjt715@gmail.com>".
See https://github.com/agx/git-buildpackage/pull/82

$(MAKE) GBP_NETWORK_TESTS=1
was setting a Make variable in the sub-Make, but not exporting it for
test/*.py subprocesses.