On local builds we shouldn't upload errors to Sentry. The
`build-utils.sh` script sets the `UPLOAD_SENTRY` environment variable
for that purpose. Also, Sentry doesn't like having an empty string
as pkgversion (which should no longer happen with the rest of this
change, but...)
If we try to install a keyboard that's missing some metadata
we shouldn't crash.
Fixes#5384, #5385. Cherry-pick of #5414.
(cherry picked from commit 3bd0173954)
When installing in the shared area the user has to run
`km-package-install` with sudo so that he has sufficient permissions.
In that case we have to do extra work to restart ibus for the
logged-in user instead of root.
Fixes#5309. Partial cherry-pick of #5371.
(cherry picked from commit 0a2dd29e53)
Converting some bitmaps fail with a truncation error. This change
allows to successfully convert the bitmap files.
Fixes#5400. Cherry-pick of #5401.
(cherry picked from commit f519c2447d)
When we update/reinstall an existing keyboard we don't want to
add a new entry to the list of keyboards.
Fixes#5308.
(cherry picked from commit 70b88790df)
# Conflicts:
# linux/keyman-config/keyman_config/install_kmp.py
It turns out that the Debian package build system only considers
the first alternative; python3-raven isn't available on the current
Debian version, however we still need it on Ubuntu 18.04 Bionic where
python3-sentry-sdk is not available. This change swaps the
alternatives and so should work both on Debian as well as for
Bionic.
(cherry picked from commit 4dd0a48b2b)
- don't log regular errors - those are handled and we report them
to the user, but don't want to create a Sentry error
- report some errors, which we want to see on Sentry, as critical
- log hash of username in crash report
(cherry-pick of PR #4914)
If the network is down or the server name can't be resolved we
shouldn't crash. This change logs an error instead.
(cherry picked from commit 1c04d5200c)
When running from source we set the environment to `local` when
reporting to Sentry. This change also adds the package version and
the tier as additional Sentry tags.
This is a follow-up of PR #4581.
This change modifies the reported version number for km-config:
if km-config is installed from a debian package, the package
version will be output as well, e.g.:
`km-config version 14.0.252-beta (package version 14.0.252-1+bionic1)`
Otherwise the output will be identical to before:
`km-config version 14.0.252-beta-local`.
This change also modifies the script that sets the version number so
that builds on Jenkins are now detected in addition to TC.
This fixes#4579.
