Usually a good idea to have a really high timeout to avoid
spurious failures on slow arch and busy buildds.

Update to upstream version '3.3.0+ds1'
with Debian dir 62b7770fdccdfd5bf3ded18683966b968a3de70a

This is needed because of the new API offered by the signer's
artifact.NewPKIVerifier.

We specifically need the following commit (which just barely made it
into the 1.5.0 release):

https://github.com/gorilla/websocket/commit/9111bb834a68b893cebbbaed5060bdbc1d9ab7d2

" Dialer: add optional method NetDialTLSContext (#746) "

Update to upstream version '3.2.1+ds1'
with Debian dir 958c50d99e2fb0e716545afafd8d31026f43144d

```
=== RUN   TestMutualTLSClientConnection
    mender_test.go:1037:
                Error Trace:    mender_test.go:1037
                Error:          Received unexpected error:
                                open ../client/test/server.key: no such file or directory
                Test:           TestMutualTLSClientConnection
--- FAIL: TestMutualTLSClientConnection (0.00s)
```

Add all found *.key files while at it... not just the
client/test/server.key.

The support/demo.crt is needed by:

```
=== RUN   TestInstallDemoCertificateLocalTrust

The device type property is used to determine which Mender Artifact are compatible with this device.
Enter a name for the device type (e.g. raspberrypi3): [xps]
Are you connecting this device to hosted.mender.io? [Y/n]
Demo mode uses short poll intervals and assumes the default demo server setup. (Recommended for testing.)
Do you want to run the client in demo mode? [Y/n]
Set the IP of the Mender Server: [127.0.0.1]     setup_test.go:309:
        	Error Trace:	setup_test.go:309
        	Error:      	Received unexpected error:
        	            	open ../support/demo.crt: no such file or directory
        	Test:       	TestInstallDemoCertificateLocalTrust
    setup_test.go:312:
        	Error Trace:	setup_test.go:312
        	Error:      	Not equal:
        	            	expected: 2
        	            	actual  : 0
        	Test:       	TestInstallDemoCertificateLocalTrust
--- FAIL: TestInstallDemoCertificateLocalTrust (0.00s)
FAIL
FAIL	github.com/mendersoftware/mender/cli	2.744s
```

The client/* paths where apparently outdated since the files
that where mentioned no longer exists, so remove/replace
them with all crt files found under client (new paths) while at it.

The dbus/dbus_test.go code explicitly tries to execute `dbus-daemon`
from PATH, so build-depend on the package (and the explicit
implementation rather than a virtual package as
default-dbus-session-bus as the tests use a specific binary).

See: https://salsa.debian.org/go-team/infra/pkg-go-tools
Gbp-Dch: Ignore

Only the test code seems to actually need godbus for now.
All other (dbus) code simply uses pkg-config: gio-2.0....

Also godbus seems to be known by many names:
github.com/godbus/dbus
github.com/godbus/dbus/v5
golang-dbus

Mender 3.0.0 uses a function new in mender-artifact 3.5.0.
Without bumping this build-dep we get:

src/github.com/mendersoftware/mender/datastore/datastore.go:302:28: undefined: utils.StringsMatchingWildcards
src/github.com/mendersoftware/mender/datastore/datastore.go:346:26: undefined: utils.StringsMatchingWildcards

- no longer needed. Test dropped upstream.

Gbp-Dch: Full

Update to upstream version '3.0.0+ds1'
with Debian dir ba0c171618eac956257e5a55b02e25e04ef0e3e5

We strip out the vendor, etc dirs.

fw_printenv/fw_setenv command moved from being provided by u-boot-tools
package to instead be provided by libubootenv-tool (which is a new
implementation based on libubootenv).

Versions less than 0.3-3 of libubootenv-tool's fw_printenv missed
disabling debug output, which caused other tools who parses the output
to break (including mender). We thus have a versioned recommends on that
version (or alternatively the old u-boot-tools version before
fw_printenv/fw_setenv was dropped).

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>

And convert tabs to spaces in d/control for consistency.

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>

Update to upstream version '2.4.1'
with Debian dir 3f98a3199be8e2e0e936b4cfcde8f7139be62e2d

Apparently there's been an incompatible API change...

src/github.com/mendersoftware/mender/installer/installer.go:219:2: cannot use map[string]interface {} value as type map[string]string in return argument
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 5 -ldflags "-X github.com/mendersoftware/mender/conf.Version=2.3.0-1" github.com/mendersoftware/mender github.com/mendersoftware/mender/app github.com/mendersoftware/mender/cli github.com/mendersoftware/mender/client github.com/mendersoftware/mender/client/test github.com/mendersoftware/mender/conf github.com/mendersoftware/mender/datastore github.com/mendersoftware/mender/device github.com/mendersoftware/mender/installer github.com/mendersoftware/mender/inventory github.com/mendersoftware/mender/log/syslog github.com/mendersoftware/mender/statescript github.com/mendersoftware/mender/store github.com/mendersoftware/mender/system github.com/mendersoftware/mender/system/testing github.com/mendersoftware/mender/tests github.com/mendersoftware/mender/utils returned exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/mender-client-2.3.0'
make: *** [debian/rules:15: build] Error 2