I talked yesterday with Coolo about the openSUSE Build Service and mentioned that I have now a lot of branched projects in my home project since I looked at many different packages that have different devel packages.  He showed me his script and also gave another hint that I wanted to share (thanks Coolo for sharing this with me!).

(more…)

With many packages, it’s easy to test that the package itself builds after a major change, e.g. a version update.  But once you add the package to your devel project or to factory, you notice that other packages do not build anymore due to your new package.

So, what can you do? You can create your own project in the openSUSE Build Service that contains your package and create links for those packages that need your package during build. That way you can find out which packages fail and fix them – instead of submitting your package to the devel project or factory and get lots of failures.

Do you have other tips about the Build Service?  Please post them!

During the past few weeks I spend most of my time on implementing a basic user interface to manage oauth tokens. Again I’m quite impressed about this powerful rails framework 🙂

Additionally I worked on the “Accept-Authentication” stuff (see my last post for the details).

I also found a small bug in osc when doing a POST request. For every POST request it used “application/x-www-form-urlencoded” which is wrong when e.g. POST’ing a specfile which isn’t urlencoded. For now we use “application/octet-stream” if we have POST request + POST data.

The plan for this week is some code restructering, testing and bugfixing.