Android Studio, SDK and NDK on Linux laptop

In recent days, I installed the Android Studio, Android SDK and Android NDK on my Linux laptop named ‘Klystron’. Rather arbitrarily, I decided not to reinstall my Android-building capabilities on the Windows 7 Desktop ‘Mithral’, which were based on the antiquated practice of using Eclipse to build Android apps. It continues in the same vane it started in, with SDK updates.

But the approach of using Android Studio on the laptop suits me, instead of setting up Eclipse in this way again.

Also, I have had to install JDK 8 on the laptop, which under Debian / Jessie means we have to resort to backports. But that was a straightforward task to accomplish.

Dirk

 

Corrected WordPress.org Update, Situation Normal

According to This Earlier Posting, there had been an update to the WordPress.org blogging engine – which I am using – which had specific problems as issued by Debian Team.

I am happy to observe, that as of now, the latest update from Debian Team has taken their earlier mistake into account, so that a new update was pushed through, which runs fine. Not only was I able to apply the new update easily, but I believe I was even able to keep my blog showing the Maintenance Mode image throughout, to warn people of this undertaking. This Maintenance Mode image should have been visible to potential readers, from 14h37 until 14h45.

Everything seems to be working fine with the blogging engine.

Again, the response of the blog might be slightly slow for the next time being, because anything which requires me to display the Maintenance Mode image, also requires that I flush my cache, on the server. But all of what happened today was completely routine.

It was also completely normal, that Debian Team repaired the error in a previous update, by issuing a new update immediately on the heels of that one. I am now on WordPress version

 


4.1+dfsg-1+deb8u11

 

 

It was the version containing ‘+deb8u10‘ at the end of its name, that contained the original problem.

Dirk

 

I just custom-compiled Tupi.

While I have spent a lot of time pursuing the subject of 3D graphics, obviously, 2D graphics also exist. And there exists an application named ‘Tupi’, which is a toolkit for creating 2D animations, in a cel- or storyboard- kind of way.

I had tried to install the version of Tupi which comes from the package manager for Debian / Jessie, but apparently the Debian Maintainers compiled that, and then did not make sure that it works. This version had a bug, which caused the application to crash, as soon as a new project was created.

So I felt that the only solution – just on the laptop I name ‘Klystron’ – was to custom-compile a later version, which is ‘version 0.2-git07′. This time around, the custom-compilation was somewhat difficult.

One reason for this difficulty was the fact, that the developers specifically neglect Debian builds, and focus on Ubuntu builds. This fact may also have thwarted the Debian Maintainer this time around.

Yet, with much effort, I was able to get the higher version of this application to compile, and also to launch, and to create a new project without crashing. Yaay!

Dirk

 

Whether It Is Easy To Debian-ize A Kanotix Installation

One question which people often ask me, is “What is the advantage of Kanotix over Debian?” Kanotix is in fact a Debian-based distribution, but has been bundled to include advantages over straight Debian, including the ease with which certain features recognize our hardware and install.

The next question people typically ask me is, “Suppose I had installed Kanotix. What would I do if I no longer want it to be Kanotix, but rather want to revert it to a standard Debian installation?”

The answer to that question is twofold. Firstly, it is easy to remove the specific Kanotix repositories from our Debian Sources list, which ‘apt-get’ queries, to download packages. But there is a slightly more subtle side to this question, which is best answered with a concrete example.

As an example, Kanotix / Spitfire, which is based on Debian / Jessie, currently comes with LibreOffice 5.1.3.2-2. I just updated mine tonight. This differs from standard Debian / Jessie, which is only supposed to come with LibreOffice 4.4.4.3-3. The LibreOffice version that comes with Kanotix works 100%, even though it is a higher version number than what is standard.

But from time to time, both the Kanotix distribution and the Debian distribution will update the LibreOffice version we have installed, either way. This could be because certain security-related flaws have been discovered, as if we had not heard of enough zero-days yet. But if what we had was Kanotix, and if we had installed the version of LibreOffice that it offers as an advantage, then the version number would stay at 5.1.3.2-2 in my case. Any subsequent, incremental updates to LibreOffice, which standard Debian had to offer, would come as slight version increases over 4.4.3-3 – for example, standard Debian might come up with a LibreOffice 4.4.4.4 . In this case our problem would be, that our package manager would see that we have version 5.1.3.2-2 installed, and would not offer us the (slightly newer) version 4.4.4.4 , because that updated version would still be lower, than 5.1.3… So our version would stay frozen for some time, at least until the Debian team started to publish a version higher than 5.1.3.2-2 . Which would be, effectively never for Debian 8.

So in order really to get Kanotix off our system, we would next also have to uninstall LibreOffice 5.1.3.2-2 completely, which consists of numerous packages. And then we could reinstall OpenOffice 4.4.3-3 from the standard Debian repositories.

Doing so might also mean, that we had LibreOffice documents in our home partitions (user data), which happened to take advantage of LibreOffice 5.1.3 features, and which LibreOffice 4.4.3-3 does not know how to display correctly… And so what some of us might do, is just keep the LibreOffice version installed, that was once installed.

Something similar happens with VirtualBox, which is a GUI-oriented Virtual Machine, on which some of us will install Windows… Kanotix bundles a version of it, which combines all the features in one package, that package being of a higher version-number than standard Debian. Standard Debian will publish VirtualBox as a set of packages, but typically with a lower version number. In theory, the question could be more urgent here, of having to revert the version to the standard Debian version, before we install our virtual Windows, because major version mismatches here can stop our “Guest Machine” (that again being user data in its entirety) from running outright.

Dirk