git.kde.org will be back and what you should be aware of

As you might have been aware of by now, git.kde.org broke down. Sysadmins are working hard to get it back online.

And soon it will. Now here is the problem: It could be possible that the last commit on git.kde.org for your repo isn’t that up to date as it should. If that happens and you try to force an update to your local clone and you notice an issue, then

please immediately notify the sysadmins without doing anything else

So they can try to find the difference between your local version and the git version.
Ideally you should also stay away from scratch repos until further notice.

It would look like this:

[email protected]:~/dev/src/kf5{frameworks}$ git fetch
From git://anongit.kde.org/kdelibs
+ abd4e22...6ae50bc frameworks -> origin/frameworks (forced update)
+ 67939b1...9c6a5be master -> origin/master (forced update)

You can reach them on freenode via IRC on channel #kde-sysadmin or on their internal mailinglist [email protected]

git.kde.org down…

Shrek.kde.org is a powerful server that hosts git.kde.org and svn.kde.org. Both are virtual machines. Shrek’s operating system was dated and had run out of security updates, it needed to be updated. We planned that for the end of the week and this morning got the confirmation that the work could be done today.

We took down the virtual machines. Upgraded Shrek without problems. Then the 2 virtual machines were started again to resume normal operations. A few seconds later it became clear that the virtual machines had file system corruptions. We took down the machine’s and run fsck’s on the images. It reported double used blocks for ~300 files. The result is that some git repo’s are damaged beyond repair on the master server. SVN has been fixed and is running fine.

You would probably think that it’s not that bad, we have like four anongit mirrors around the world from which we can restore from. But there is a problem. A consequence of powering up the git server for a few minutes have been that the anongit mirrors have synced the corrupted repo’s, hence corrupted repo’s on the mirrors.

Luckily it seems we can restore bits and pieces from each mirrors and other tricks our git experts are implementing. All the sysadmins that have knowledge about this are on it and working hard to complete this difficult task. This includes Dirk Muller, Nicolas Alvarez, Jeff Mitchell and Ben Cooksley.

I’ll try to give more updates via identi.ca: http://identi.ca/kdesysadmin

Neverland can be build

Cranes In The Sky.Some of you dear readers might know about Neverland. The theme “engine” that drives a lot of our current KDE websites.

It is basically a design that is based on the Bootstrap CSS Framework, for which we write themes for the nearly dozen CMS we have. That includes phpBB, Drupal, Mediawiki, WordPress and others.

And that is the pain point basically. You have to maintain a lot of different theme files, all of them written in a different way, on top of a different CMS, with a different markup as well.

So we end up with one core css file on our CDN, and nearly a dozen customized css files for each of them. Plus the theme files.

That made me wonder if the situation could be improved with a custom build system. And after some fiddling – surprise surprise – i can proudly say i found a way to automate the build of each of those themes!

It – as of now – basically consists of a simple Makefile, which builds the CSS out of the less files, and fetches skeleton files to output theme files for each CMS, done with the help of node.js . The best is, not matter of what language the theme file is based on, it can be written.

It is extendable, every CMS gets its own build file. But the important thing is, you change your markup in one place, and each CMS theme can reflect that change.

Of course it is in a very early stage, and not finished, but once done maintenance mode goes down to just a single command and the server sync 😛

That might sound quite boring for some, especially those who are used to build systems, but for me that is an exciting step forward. So exciting that i write such a blogpost.

Learn something new every day – Done for today 

 

 

KDE will start using SNI starting July 1st.

This is an announcement that the KDE Sysadmins will start using SNI on the KDE servers starting from July 1st. If you don’t know what SNI is, here is a small explanation:

This allows a server to present multiple certificates on the same IP address and port number and hence allows multiple secure (HTTPS) websites to be served off the same IP address without requiring all those sites to use the same certificate. It is the conceptual equivalent to HTTP/1.1 virtual hosting for HTTPS.

Simply put: IP-addresses (the old v4 ones) are starting to run out. Up to now we needed each and every https-site to run on a different IP-address. SNI makes it possible to run multiple https-sites on one IP-address. But if your browser does not support SNI, you get to see a certificate error.

We’ve pushed SNI to Qt  long ago, that way Konqueror supports it (from KDE 4.9.0), and all other main browsers we care about support it. If you run Konqueror with an earlier version of KDE, we suggest you reserve some time before July to upgrade.

If you want to test if your browser supports it, go to https://sni.velox.ch/. If you get certificate errors, then your browser does not support it. If the page says ‘Great’, than you can safely read the next blog now…

How much does KDE care for its bugs?

Good question. Let’s reveal some stats.

All time top commenters
Name Number of Posts
Dario Andres 34082
Myriam Schweingruber 23019
Christoph Feck 16342
Gilles Caulier 14737
David Faure 13684
FiNeX 12637
Stephan Kulow 12174
Aaron J. Seigo 11648
Christophe Giboudeaux 11289
Thiago Macieira 10167

Impressive activity there, i would say. But one more, the activity for only this year:

Top Commenters 2013
Name Number of Posts
Jekyll Wu 1062
Thomas Lübking 684
Christoph Feck 654
Myriam Schweingruber 503
Martin Gräßlin 495
Alex Fiestas 443
Frank Reininghaus 309
Laurent Montel 234
David Edmundson 227
Gilles Caulier 225

It is up to you to decide on a conclusion. But to me, this seems like someone really does care.