makara
June 23, 2020, 2:54am
1
I’m trying to install Keyman for Linux on my VM running Ubuntu 14.04 LTS.
The following lines have been run successfully:
sudo add-apt-repository ppa:keymanapp/keyman
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install keyman ibus-keyman onboard
But the last line gave these.
E: Unable to locate package keyman
E: Unable to locate package ibus-keyman
Have I missed anything in the installation process?
Marc
June 23, 2020, 3:10am
2
Ubuntu 14.04 is not supported We support 16.04 and later.
makara
June 23, 2020, 1:10pm
3
I’ve upgraded to Linux 16.04, but when running the third line, it says “the packages have been kept back”. (See the details below)
makara@makara-VirtualBox:~$ sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-image-4.4.0-72-generic linux-image-extra-4.4.0-72-generic
Use ‘sudo apt autoremove’ to remove them.
The following packages have been kept back:
libparse-debianchangelog-perl onboard onboard-data
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Marc
June 23, 2020, 10:00pm
4
You should be able to upgrade those kept-back packages with the following:
sudo apt-get install onboard onboard-data
See this topic for more information: https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it
darcy
June 23, 2020, 11:45pm
5
I think we still ran into issues getting Launchpad to build the packages for 16.04, and opted to support 18.04 and 20.04
opened 03:06AM - 13 Feb 20 UTC
closed 02:29AM - 23 Mar 20 UTC
wontfix
compatibility
linux/
common/
afaict, keyman-keyboardprocessor packaging builds on Launchpad have always faile… d for Xenial.
The buildlog has numerous warnings
```
../src/utfcodec.hpp:22:21: warning: attributes at the beginning of statement are ignored [-Wattributes]
#define fallthrough [[clang::fallthrough]]
```
A local `meson build --werror` gives the same fails
From the [gcc](https://gcc.gnu.org/gcc-7/changes.html#cxx) documentation
> -Wimplicit-fallthrough warns when a switch case falls through. This warning has five different levels. The compiler is able to parse a wide range of fallthrough comments, depending on the level. It also handles control-flow statements, such as ifs. It's possible to suppress the warning by either adding a fallthrough comment, or by using a null statement: `__attribute__ ((fallthrough));` (C, C++), or `[[fallthrough]];` (C++17), or `[[gnu::fallthrough]]`; (C++11/C++14). This warning is enabled by -Wextra.
Syntax | Standard | Compiler version
----------------------- | ----------------- | -------------------
[[clang::fallthrough]]; | clang | Clang 3.9
[[fallthrough]]; | C++17 | gcc 7.0
[[gnu::fallthrough]]; | C++11/C++14 | gcc 7.0* (needed for attributes)
* I tried [[gnu::fallthrough]]; but the attribute required gcc 7
Older compilers can suppress the warning with a null statement or fallthrough comment.
The LTS releases have
LTS | gcc Version | clang Version
------ | ------------ | ---------------
Xenial | 5.4.0 | 3.9
Bionic | 7.3.0 | 6.0
The issue with Xenial is buried at the end of Keyman 16.0 for Linux
Note: there’s currently a limitation where the Keyman packages are incomplete on the Xenial ppa.
Of the two options:
Recompile Keyman for Linux on your existing 16.04 VM (should work)
Make a 20.04 VM and install the Keyman package
I recommend 20.04
Nyny
Closed
February 1, 2024, 6:33am
6
This topic was automatically closed after 14 days. New replies are no longer allowed.