Bloggy

kdesvn-build 1.10

October 24th 2009 10:58 pm

Another season, another kdesvn-build release.

Big things in this release:

The run-tests option, as suggested, tested, and improved by David Faure.
Git support, so that you can build qt-copy and amarok (and more KDE modules if/when they switch). You need to add the repository option and possibly also the branch option to select what code to clone/update. See the sample configuration file for details.
All KDE 3 support has been removed.
Various bugfixes.

I expect you may find bugs with the git support, if so please let me know so I can fix. There are sadly still a couple of reported bugs, but the only reason I went and released this was because I had nice people prompting me via e-mail. I will fix them though, I promise. ;)

Now back to my research papers…

Posted by mpyne under KDE & kdesvn-build & Programming | 6 Comments »

6 Responses to “kdesvn-build 1.10”

ianjo responded on 25 Oct 2009 at 04:02 #

Great!

I’ve been expecting this since the switch to git qt-copy :) . Now I can easily rebuild trunk again, woo-hoo!

Thanks.
Hans responded on 25 Oct 2009 at 08:08 #

Your work is much appreciated. I think I’ll build trunk again; Git support sounds wonderful. :)
Hans responded on 25 Oct 2009 at 15:23 #

So I tried to compile trunk today, but ran into two problems with qt-copy:

1. I can confirm this: http://lists.kde.org/?l=kde-core-devel&m=125451835012203&w=2
Strange, because it works when I clone manually. Do you want me to report to bko?

2. Installing qt-copy fails: http://pastebin.com/m6e16ff9a
I have no idea about this one. qtdir is set to ~/qt4 (default) in .kdesvn-buildrc, and the prefix seems to be passed to configure:

# kdesvn-build running: ‘/home/kde-devel/kdesvn/qt-copy/configure’ ‘-qt-gif’ ‘-no-exceptions’ ‘-fast’ ‘-qdbus’ ‘-nomake’ ‘examples’ ‘-nomake’ ‘demos’ ‘-phonon’ ‘-confirm-license’ ‘-opensource’ ‘-prefix’ ‘/home/kde-devel/qt4′

Any ideas what’s causing this? Is it Qt’s fault?
mpyne responded on 25 Oct 2009 at 18:10 #

Hans: I think your first issue is a problem with gitorious to be honest. I often have it fail to clone and/or update (whether I run git manually or via kdesvn-build). That may be why using http:// instead of git:// works, but kdesvn-build doesn’t do anything with the repository URL, it just gets passed onto git. So I would say don’t submit it unless you can get it to always fail with kdesvn-build when it always works manually or something.

For your second issue, it seems like a Qt bug to me. :( Given that the prefix was passed correctly there’s no reason it should be trying to install to /usr/local/Trolltech. Perhaps it’s related to a XDG environment variable, that’s the only thing I can think of.
slashdevdsp responded on 25 Oct 2009 at 23:45 #

I think its the same problem about adding git remote alias for qt-copy, the one you mentioned in email:

The solution to the first problem, about not being able to update qt git, try solution below:

change to the qt-copy source directory (~/kdesvn/qt-copy) and then run:

git remote add __kdesvn-build-remote git://gitorious.org/+kde-
developers/qt/kde-qt.git

That should add the missing alias and enable kdesvn-build to work in the
future.
Hans responded on 27 Oct 2009 at 08:55 #

@mpyne:
“I think your first issue is a problem with gitorious to be honest.”

Wouldn’t it be better to use http:// in the sample file instead of git://, even if it’s gitorious’ “fault”?

“For your second issue, it seems like a Qt bug to me. :(”

I’ll try to look deeper into it when I have time (or ask other trunk users). The whole “Trolltech” part seems strange to me – do they still use that name for anything? Anyway, thanks for your answers! :)