Apart from post-COVID syndrome there were some other setbacks lately, but those were mostly software-centered. Like the fact that I can not build a 32bit Chromium package for instance.
But also the realization that the latest LibreOffice 24.2.0 can no longer be compiled on Slackware 15.0 – its gcc 11.2.0 compiler is considered “too old”.
With the help and insight of Pat Volkerding I was able to compile LibreOffice on Slackware 15.0 anyhow:
I need to test the resulting binaries, and I still need to see whether I can repeat this on 32bit Slackware of course… but it looks promising.
More to follow.
Wed Feb 21 12:41:50 UTC 2024
libreoffice: updated to 24.2.0 for Slackware 15.0 and -current.
Depends on openjdk17.
openjdk17: added v17.0.10_7 for Slackware 15.0 and newer.
Only install one version of Java!
I somehow avoided getting infected with COVID for all these past four years, but this week unexpectedly it hit me after all – and that while being inoculated multiple times. Oh well, they say that the inoculations keep the more severe symptoms at bay.
Still, this feels like a very bad flu, I have been in bed for two days, feeling delirious in the beginning but just nauseous and dizzy now, accompanied by the father of all headaches.
I have no energy left in me, meaning package updates may be delayed. Pay supplied me with the sources for the to-be updated glibc package in Slackware, so that the computer can do all the compiling when I return to bed. That will be about all.
Stay healthy! Eric
Chromium 121 sources were released yesterday, and as much as I would like to tell you that the Slackware packages are ready, in fact it appears that you will have to wait for them for an unspecified amount of time.
I found out that the build of Chromium now needs Google’s custom version of the Rust compiler, next to Google’s custom version of the Clang compiler. Those Rust and Clang versions are intertwined and Google advises packagers to simply use their own pre-compiled binaries which they provide for download.
You guessed… those binaries are not available for a 32bit OS. Nothing new, and it is for that exact reason that as part of compiling Chromium for Slackware, the complete LLVM toolchain is built from Google’s sources first. For every package I release. Tweaking the LLVM/Clang compilation so that they work for 32bit Slackware took a lot of time – after all, no one at Google tests their sources for 32bit build compatibility. So I patch here and there and every time feel lucky that it still works.
Until today, when I ran into the new Rust requirement. And after the umptiest iteration of a Chromium package build using a variety of changing options, I still fail to even start compiling a Rust binary.
I am taking a break from this to consider my options. My aim is to keep supporting the 32bit Slackware package. I just need to figure out how Google messed this up again and find a way around it. In the meantime, don’t hold your breath – I only have a few hours each evening to do the troubleshooting. A new package will appear when it’s ready.
All the best, Eric
Update 2024-jan-29: I have buillt 64bit packages for Chromium (also -ungoogled) version 121.0.6167.85 and uploaded them to my repository.
Note that I can not currently compile their 32bit versions because until now I have not been successful in building Google’s custom llvm and rust from source. I had to revert to downloading and using Google’s pre-compiled binaries which they only supply for 64bit systems.
I am still determined to find a way to compile these llvm and rust compilers from Google’s own sources. But I have no ETA on that unfortunately.
Last week I told you about the change of theme which I applied to my personal blog. It seems that I was not done then.
On a different server I host the SlackDocs Wiki (https://docs.slackware.com/) and a lot more than that Wiki actually; docs.slackware.com is the same host which also provides you with the slackware.nl mirrors. This host is a physical server running in a datacenter on Slackware64 15.0 – nice and stable.
For an unrelated service I decided to upgrade the stock PHP 7.x to the 8.x version you can find in the ./extra directory because that is a version which offered better support and speed for that particular service.
Only the next day I found out that the PHP upgrade broke the Dokuwiki software which is what SlackDocs Wiki is actually based on. I could not use the Wiki’s admin interface to repair what got broken (afterwards I assumed I may have been thwarted by old cached PHP code; Dokuwiki obtains its rendering speed by caching the compiled PHP code so that it does not have to retrieve the script code all the time). Anyway, on the commandline I was able to upgrade the Dokuwiki to its latest version and along with that, all the plugins that I installed to extend the Wiki syntax or providing community editing capabilities.
So far so good, but the Wiki was still not rendering correctly with persistent errors in the browser and in the Apache httpd logs. They turned out to be caused by the Wiki theme (in Dokuwiki it is actually called a ‘template‘ not a ‘theme‘ like the blog). For SlackDocs I have been using the “MonoBook” template since its inception. The MonoBook template for Dokuwiki is inspired by the look and feel of the original MonoBook ‘skin‘ for MediaWiki (the wiki engine powering Wikipedia) which was replaced by the Vector skin in 2010.
This MonoBook template has not been updated since 2014 and is no longer supported by the latest Dokuwiki. Eventually I was able to fix the ‘bad code’ in the template and now the Wiki renders just fine using it.
But it got me thinking that it might be wise to switch to a supported theme. That sounds trivial, but I chose MonoBook for a reason: it supports Discussion pages. When you open a SlackDocs page, you will find a couple of tabs above the article, called “Article“, Discussion“, “Read“, “Edit“, “Old revisions” and “PDF export“. The Discussion tab allows anyone to comment on the actual article and thus hopefully spark a discussion – with the author or with other readers.
So I needed another template with that same Discussion capability. That was not so hard in the end; the same person responsible for the MonoBook template is also maintaining a Dokuwiki port of Mediawiki’s Vector skin. And even though it has not been updated either since 2014, Vector is fully supported by the latest Dokuwiki – no errors in its code.
I have ported the SlackDocs configuration for MonoBook to Vector and enabled it. The result can be seen on the current instance of SlackDocs Wiki. Most notable change is that the search entry field is now located at the top right of the page instead of halfway the left sidebar. Well, and it looks subtly different than MonoBook of course.
I hope you like it… but it’s not that I would go back to MonoBook if you don’t.
A blog is something personal, and theming it just right is a challenge. You’ll surely have noticed that the theme of Alien Pastures has been changed overnight.
This blog started out with a theme by Andreas Viklund (wp-andreas01) but that did not scale well on mobile devices, also it did weird stuff with user comments. I liked its visual quality a lot but the usability challenges were not fixable even by rummaging around in its code.
Eventually I replaced that with a new theme by Rajeeb Banstola (techism) but during my recent WordPress blog-code update I realized that this techism theme had not been updated for years, the author’s website has disappeared and the Freemius SDK from which that theme is created has a XSS vulnerability. Real shame because I thought it was beautiful, light, responsive and it fixed the user comment issues I mentioned previously.
So I have used my December holiday to look for another theme, experimenting with several, but I wanted to end with one that at a minimum allows me to have two columns: one for the articles and one as a sidebar with widgets showing all kinds of permanent info. Three columns was what I had with wp-andreas01 and techism, but I could live without one of the two sidebars.
I finally found a theme collection created by Anders Norén. On his page teman he showcases several that I find appealing, but after some experimenting I chose his Lovecraft and Hemingway themes over Baskerville. I kept the visual style of the new theme as close as possible to the old one (header image, top menu, sidebar widgets etc).
A note about the header image – that one has changed a few times over the years. I always use a picture I have taken myself and I rotate them on occasion.
At the bottom I was able to add three widgets that otherwise would have gone into a left sidebar. I think it’s cleaner now. Plus, one of these bottom widgets shows posts that have been most popular during recent weeks. That’s always interesting information to you (visitors), previously I would be the only one with that overview – it shows in the blog’s admin dashboard.
I am still undecided whether Hemingway or Lovecraft will make it as my final choice. Hemingway theme shows the number of comments to each article and it’s visually somewhat more condensed. Lovecraft on the other hand is aesthetically more pleasing to my eye.
I hope you like and appreciate the change and the new interface does not pose any difficulty writing and posting your comments. Feel free to comment below of course!