Today I made a 'cut and paste' error and ended up Googling for the word "Time". This is not a great deal, but the result surprised me:
They even know where I am!!
Entering things like "Time India" even gave the correct results. Nice.
It has been a while since the last entry, but I've been busy like hell and on a holiday as well.
But a short update was in order.
I'm now running a PFSense server on a Lanner netbox (FW-7530) as my firewall. My old Soekris 4801 could not keep up with my 90Mbps internet connection. The Soekris could only cope with about 45Mbps so that's not very good. The Lanner gives me 88.9Mbps and that's about the limit of the internet connection. Very nice.
In the meantime I also updated the Git RPMs (1.7.1.1) and I guess by now you know where they are.
asciidoc: FAILED: [tabledef-default] missing section: [tabletags-header]
asciidoc version 8.5.1 and at work I have asciidoc version 8.5.3.
So, at home I saved the current /etc/asciidoc/asciidoc.conf and upgraded the package. What a surprise, the docs did not build anymore. So I found the program that messes up things. But why?
Diffing the new config file with the old one I found two lines with the text
header-style=tags="header"
asciidoc I am not hindered with knowledge, so I commented out these lines. I do not have any idea if I break other things, but now my Git RPM's build correctly and the documentation looks good.
As far as I'm concerned: Problem Solved.
On my own server I tried to build the Git RPM's and that worked, but on the server at work it borked on building the documentation.
The message I got was
asciidoc: FAILED: [tabledef-default] missing section: [tabletags-header]
and Google has never heard of it.
Both servers are running CentOS 5.4 i386, so no differences
there. I started looking for the responsible program and I found
out that at home I have asciidoc version 8.5.1 and at work I have
asciidoc version 8.5.3.
So, at home I saved the current /etc/asciidoc/asciidoc.conf and upgraded
the package. What a surprise, the docs did not build anymore. So I found the
program that messes up things. But why?
Diffing the new config file with the old one I found two lines with the text
header-style=tags="header"
Knowing almost nothing about asciidoc I am not hindered with knowledge,
so I commented out these lines. I do not have any idea if I break other
things, but now my Git RPM's build correctly and the documentation
looks good.
As far as I'm concerned: Problem Solved.
It's been a while, but now there is a new version of the MySQLBackup script.
This version has a few enhancements and some configuration options were added.
The main new feature is that it now supports multiple dumps per day. The old backups will be removed, of course, but only when they are over a day old.
An added configuration option is that it's no possible to choose whether you want the databases locked during the backup.
I will try to see if it's possible to create an option to specify if you this for every backup or not.
Have fun with it. It's in the files section.
Today I saw that git version 1.7.0.1 was out and while I missed out on 1.7.0 I decided it was time for some RPM's again.
Well, NOT. The sources built like a charm and I'm using 1.7.0.1 now for the daily work.
The big problem is the documentation, as always. When I want to build
the docs, the build proces fails with some strange table-header and
table-definition error, that even Google has never heard off.
All I know now that it has something to do with asciidoc being the
wrong version. It does build on Debian Lenny and Ubuntu 9.10 though.
Update:
It took some time, but I did get it working. For some way or another
after a make clean it all worked. So I repacked the sources and
built the RPM.
You will know. It's in the files section.
Today I saw that a new version of Nanoblogger was released, so I decided to update.
I thought this would be a breeze, but it turned out that Kevin (the maintainer of Nanoblogger) changed a lot between the last two versions. Nanoblogger calls (in my setup) Markdown to format the webpages and that's where it stopped. A little debugging got things going again and I mailed Kevin the patch.
I guess it will be resolved in the next release.
But I am running version 3.4.2 now.
This morning a git (1.6.6.1) arrived with a copule of nice
bug fixes.
I created complete CentOS5 RPM's for this again.
These new RPM's can be found in the files section.
They have started again, those EU nitwits. When does the EU just stop with this madness?
Stop them now and (re)sign the petition against software patents.
Today I upgraded my NanoBlogger software from version 3.3 to version 3.4.1.
This whole process was completely painless. Just installed Nanoblogger 3.4.1 and regenerated everything and that was it.
A quick 'side by side' compare of the old and the new one revealed nothing special.
If you see any errors, please let me know.
