I came across a debian application by the name JavaPackage which can create a debian installation file (.deb) form a java binary (.tar.gz) which you can then install using dpkg -i application_name.deb. With Ubuntu being a debian-based linux distribution, it is possible that it can be installed on ubuntu as well.
How do I go about installing it on Ubuntu/Kubuntu 16.04.2 LTS?
java-package is available in the official ubuntu repositories. All you need to do is update the repository with the latest version then install it as shown below:
sudo apt-get update
sudo apt-get install java-package
Related
Can someone explain me how I can upgrade a running gitlab CE on Ubuntu 16.04 to Ubuntu 18.04?
I could not find any relevant documentation for this upgrade path
It is clear to upgrade ubuntu with
sudo apt update
sudo apt upgrade
sudo do-release-upgrade
But what is needed to tell rerun the setup/upgrade on gitlab?
If you upgrade your Ubuntu Version from 16.04 to 18.04, you also need to alter the repository path for debian packages provided by GitLab Inc.
If you inspect the installation/configuration script available on GitLab.com, you will see that there should be a file in /etc/apt/sources.list.d/ which contains gitlab in its filename.
Simply replace its content with the following lines:
deb https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ bionic main
deb-src https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/ bionic main
You are now able to upgrade GitLab using the new package repository for your upgraded Ubuntu System:
sudo apt update
sudo apt upgrade
If you mean update Ubuntu from 16.04 to 18.04 then here's the steps:
I did that a couple of days ago.
lsb_release -a # This is just to check the. Ubuntu version
sudo apt update
sudo apt upgrade
This will make sure that you have all the packages updated. The upgrade will not start if you don't have them upgraded.
Then for the actual upgrade
sudo do-release-upgrade
NOTE
1 - The above command might fail because "you have to upgrade all the packages before" please inspect the output of sudo apt upgrade maybe you have a dependency issue & not all the packages are upgraded
2- Please make sure you have all your data backed up before doing the upgrade. I'm assuming that you doing the upgrade via SSH which may be troublesome.
For me, the upgrade got stuck while trying to update the openSSH config files. What I did is that I closed the current SSH session ( tmux ) opened a new session & rebooted the server.
After the server is rebooted
lsb_release -a
Should show
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
I trying to install VirtualBox on Ubuntu 14.04. I've installed VirtualBox from Ubuntu repository:
sudo apt-get install virtualbox
Then I added my user to vboxusers:
sudo usermod -G vboxusers -a user
I also installed an extrapack for my vb vsion:
wget http://download.virtualbox.org/virtualbox/5.0.10/Oracle_VM_VirtualBox_Extension_Pack-4.3.36-105129.vbox-extpack
sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.0.10-104061.vbox-extpack
But when I trying to start vm, I get an error:
RTR3InitEx failed with rc=-1912 (rc=-1912)The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/etc/init.d/vboxdrv setup'may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
where: supR3HardenedMainInitRuntime
what: 4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.
And I have no /etc/init.d/vboxdrv file.
How can I fix this problem?
I've removed all the virualbox packages:
sudo apt-get purge 'virtualbox*'
Then I've installed virtualbox v.5
sudo apt-get install virtualbox-5.0
After that I've enabled virtualization in BIOS.
Now it works.
Check what version of virtualbox you installed
dpkg --list 'virtualbox*'
may be it's not aligned with the Extension pack.
Remove your installation
sudo apt-get autoremove 'virtualbox*'
Don't install fron Ubuntu repositories but run a fresh installation following the instuctions from official Oracle Virtualbox Download page about Debian-based Linux distributions.
Check that Virtualbox is running before installing the Extension pack.
I had the same error starting a vm client in ubuntu 16.4 .
Coincidentally I noticed in the file /var/crash/_usr_lib_virtualbox_VirtualBox.0.crash the following message:
Title: VirtualBox crashed with SIGABRT in QMessageLogger::fatal()
UnreportableReason: Sie haben einige veraltete Paketversionen
installiert. Bitte aktualisieren Sie die folgenen Pakete und prüfen
Sie, ob das Problem danach noch auftritt:
virtualbox-dkms
Translated: You have some outdated package versions installed. Please update the following packages and check, if the problem still occurs after that:
After the command:
sudo apt-get install --only-upgrade virtualbox-dkms
all was OK :)
I downloded android studio and I tried to install on ubuntu 16.04 64 bit but it has "unable to run mksdcard sdk tool" error.
I checked all solutions but they produce errors too.
Seems that the only package you need is lib32stdc++6 for ubuntu 16.04
sudo apt-get install lib32stdc++6
I just stumbled upon this issue myself.
I guess that you found this topic from 2015?
Well, the given solution is a bit outdated but still pertinent: the 64bit Ubuntu 16.04 is indeed missing the 32bits version of the libraries and the
lib32z1 lib32ncurses5 lib32bz2-1.0 lib32stdc++6 libraries advised to be installed seems to have been removed from the official repos.
However You can still get them with using this command:
sudo apt-get install libz1:i386 libncurses5:i386 libbz2-1.0:i386 libstdc++6:i386
Then the installer should work just fine
Hope it will be of any help.
take a look at https://developer.android.com/studio/install.html
Select Linux...
Required libraries for 64-bit machines:
If you are running a 64-bit version of Ubuntu, you need to install some 32-bit libraries with the following command:
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 lib32z1 libbz2-1.0:i386
If you are running 64-bit Fedora, the command is:
sudo yum install zlib.i686 ncurses-libs.i686 bzip2-libs.i686
For Ubuntu 18.04 and above versions, the following will work
sudo apt-get install libstdc++6:i386 libgcc1:i386 zlib1g:i386 libncurses5:i386
Ubuntu18.04
CentOS 7 has been out nearly a year now. Has anyone installed RedHawk on CentOS 7? I do not see binaries available on the RedHawk download page. Has anyone successfully built it from sources? Are there issues?
I also do not find RPMs for omniORB-servers or omniORB-devel. Has anyone succeeded in building these on CentOS7?
Terry, Ive built redhawk yum repositories for CentOS7 which you can find below however a few things to note:
As Ryan pointed out, currently redhawk only officially supports CentOS6 and Ubuntu, these rpms are not offically built and distributed by redhawksdr.org. However if you do have any issues with them or find any problems please feel free to feed this back to me.
These RPMs were originally built prior to Fedora packaing omniORB 4.2. To account for this, I built and packaged omniORB 4.1 for CentOS7 which is the same version redhawk uses on CentOS6. My omniORB41 package and EPEL's omniORB (v4.2) package conflict so you cannot have the epel package installed. I have not tested redhawk with omniORB 4.2 which is why I packaged the older 4.1 version.
You can find the 1.10.1 yum repository here:
http://yum.axiosengineering.com/redhawk/1.10.1/el7/x86_64/
I will hopefully soon update with 1.10.2
You will also need the dependency repository here:
http://yum.axiosengineering.com/redhawk-deps/1.10/el7/x86_64/
To install via yum, create the file /etc/yum.repos.d/redhawk_axios.repo
With the following text:
[redhawk]
name=UNOFFICIAL REDHAWK 1.10.1
baseurl=http://yum.axiosengineering.com/redhawk/1.10.1/el7/x86_64/
enabled=1
gpgcheck=0
[redhawk-deps]
name=UNOFFICIAL REDHAWK DEPS
baseurl=http://yum.axiosengineering.com/redhawk-deps/1.10/el7/x86_64/
enabled=1
gpgcheck=0
Then from a terminal:
sudo yum clean all
sudo yum install redhawk* frontendInterfaces* bulkioInterfaces* GPP-*
REDHAWK is only officially supported on CentOS 6 and Ubuntu 14.04. omniORB should now be in Fedora EPEL 7:
https://apps.fedoraproject.org/packages/omniORB
I recently installed Redhawk 2.3.0 on Centos 7.9 by following these instructions https://redhawksdr.org/2.3.0/manual/installation/
The exact commands I used:
mkdir ~/Documents/Redhawk
cd ~/Documents/Redhawk
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
wget https://github.com/RedhawkSDR/redhawk/releases/download/2.3.0/redhawk-yum-2.3.0-el7-x86_64.tar.gz
tar xzvf redhawk-yum-2.3.0-el7-x86_64.tar.gz
cd redhawk-2.3.0-el7-x86_64
sudo yum install -y redhawk-release*.rpm
sudo nano /etc/yum.repos.d/redhawk.repo
Content of /etc/yum.repos.d/redhawk.repo:
[redhawk]
name=REDHAWK Repository
baseurl=file:///home/causer/Documents/Redhawk/redhawk-2.3.0-el7-x86_64
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhawk
Once the file is saved (ctrl+x, y), in the same directory as before:
sudo yum groupinstall "REDHAWK Runtime"
. /etc/profile.d/redhawk.sh
. /etc/profile.d/redhawk-sdrroot.sh
sudo /usr/sbin/usermod -a -G redhawk causer
sudo nano /etc/omniORB.cfg
sudo $OSSIEHOME/bin/cleanomni
sudo systemctl enable omniNames.service
sudo systemctl enable omniEvents.service
Copy redhawk.desktop to the desktop and run it (rpm -qpl on the redhawk-ide-xyz.rpm its near the bottom of the list)
sudo yum install java-1.8.0-openjdk-javadoc
I did apt-get install wkhtmltopdf on my mac and it installed 12.2.1 and works well. I've now deployed to the ubuntu server, and require wkhtmltopdf on that server. apt-get install wkhtmltopdf only installed 0.9. I followed this explination and it kind of worked, I now have 12.1 installed. But it is not behaving the same as version 12.2.1 on my mac.
And when I do apt-get install wkhtmltopdf again on the ubuntu server it says the latest version is already installed, even though it's only 12.1.
How do I get version 12.2.1 onto the ubuntu server?
Purge the added PPAs:
sudo apt-get install ppa-purge
sudo ppa-purge ppa:<user/ppa_name>
And use the official packages.