www.michael-jansen.biz

I released Version 0.5.5 of build-tool to rubygems. The version is just a bugfix release and some small enhancements. Hang on for the changelog

Update: Seems my long offline time made me rusty. v0.5.7 is now what 0.5.5 was supposed to be. 0.5.5 and 0.5.6 should be ignored. Even if they should work they are not what i intended to release.

Just a short note that i am back online again after my three month internet timeout caused by deutsch telekom ag beeing unable to actually provide the service they sold me.

I will blog about the hilarious ... i you weren't me ... turn of events at a later date. I have never in my live seen a company that indifferent to their customers apart from taking my phone calls. But as i said. Full story later.

I missed nearly everything the last three month so i am absolutely behind on the efforts i wanted to join. Namely the cmake effort going on (ecm) and general build stuff. So if you wanted something from me and still wait for an answer please resend.

Mike

Hi All

Just a short status update. I am still offline courtesy of Deutsche Telekom. A simple provider switch from another provider to them seems to totally overwhelm their infrastructure. For now 2 month i am without any landline connection and there is no end to be seen. They kept blaming my old provider until last week when someone noticed the problem is on their side. Easy to be seen if someone is willing to look for solutions instead of blaming others.

I hope to come back to anyone contacting me during this time but if you did please resend the messages after my hopefully coming soon 'I am back' message. I am not sure i will be able to recover everything from that pile of spam, scam and mailing list stuff that is building up on my email account.

Mike

I just pushed the changes necessary to build kdeutils after it was moved to git and splitted.

Update the recipe and then remove the old kdeutils checkout and its build directory. Then rebuild kdeutils with kde-build build -u kdeutils/. This applies naturally only if you have the feature utils activated.

Mike

As recently announced in kde-core-devel mailing list kdelibs master is now frozen. Development will happen in the branches

frameworks

The modularization effort for kdelibs

KDE/4.7

Bugfixes for the 4.7 branch

Since this is not about announcing this change but the implications for build-tool users i won't go into details here. I made the following changes to the build-tool recipe for your convenience:

I just pushed the next bugfix release of build-tool to rubygems. Hang on for the changelog.

If you use build-tool to compile kde from sources you most likely encountered the current confusion around soprano and its dependencies. It requires a fairly recent raptor version which is not yet packaged for many distros. And it needs recent rasqal and redland version too. If you need to compile the from sources use the following snippet. Add it to your recipe override file.

Dear KDE

I guess this is the proper opening here since kde is now the community. And i want to address the community. All of you. Whenever you feel the need to move your application from one source code repository to the next, which these days is mostly from our subversion repository to git.kde.org, please be nice to your users. Which are developers too in this case. Source code users. So be nice to your fellow developers. Or if you need it more personal. Be nice to me.

Do not just remove the old repository and let me find out the hard way you moved. Getting a subversion error message when trying to update something is not nice. And did you now git-svn just fails silently if you remove the cloned subversion directory? I did not know either. But thanks to you i found out. It spits out something about not seeing source files at the path and about trying harder. But obviously it does not try hard enough! It does not succeed in finding your moved sources so it just returns zero. Most likely in shame over its failure. It does not want to confess it. Poor tool. And my build script thinks that means the update was successful. I built for month the same version over and over again. Silly, isn't it? I mean my build script naturally. I have written it myself so i should have guessed.

So after i eventually found out something isn't right i tried to follow you. You didn't move to get rid of me? See i obviously missed the announcement on kde-devel or kde-core-devel about the move. My attention span is really short. You did inform the mailing list about your move i am sure. Especially where you moved the sources. And i need that info. But since i missed that announcement anyway it would have been a nice touch - just to show you care - to NOT remove your root directory we are used to checkout. Instead just delete all sources in it. Add a README file with the new repositories url. For people like me who miss the announcements. Others did it too!

But you didn't. So i went to search your project on git.kde.org. But it was not there. This is a nice touch. Every time before this happened i would find the sources there. But you guys love to surprise me. I hate it when things get predictable and boring. So i applaud your effort. With a bit of googling i found your sources. On gitorious, or was it github? I forgot. Wherver it was, i could have guessed.

Living in the kde community. Where we all strive to make live a bit more unpredictable.

Mike

As an update to the last article here my latest changes to the setup that finally make it work without the hassle of crashing at login once.

Additionally i forgot to mention a script i found that checks certain settings to see how your system scores in terms of low latency.

I just finished one of those long fights we sometimes accept just to get some really minor problem solved. I got myself an usb microphone. After successfully getting it to run under alsa and recordmydesktop i went and looked for some graphical sound level meter (or however that is correctly named). There is apparently no such thing in kde and a google search was unsuccessful too. Some pulseaudio based solution ... thanks but no thanks. And some jack based ones.

So i finally looked into jack. I remembered from some attempts long time ago the need for realtime kernel. Not anymore. So i decided to give it a try. Feel free to learn from my feeble (and successful) adventures that follow.