Home Home > Build-service
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Archive for the ‘Build Service’ Category

Call for testing: unzip feature

April 7th, 2010 by

Hello Planet!

Have you ever faced a bug like this bnc#540598 ?

When you create  zip archive with non-English filenames and try to unpack it on openSUSE, filenames within archive become unreadable. It can irritate, isn’t it?

It seems as if we found a solution for Russian language. We tested it and it works for us.

It would be helpful if some of you could test your local language. And check whether core functionality still works 😉

Here is a list of  languages that are potentially affected by this bug: Ukrainian,Belorussian, Bulgarian, Croatian, Czech, Estonian, French, German,Hungarian, Italian, Lithuanian, Latvian, Polish, Slovak, Spanish,Slovenian, Swedish.

So it is worth to test them in the first place.

The reproducer is pretty simple:

  • create zip archive on windows with file named in you local language
  • transfer archive to openSUSE system
  • unpack it
  • see if filenames are readable

What needs to be tested:

  • if this bug applicable to you language
  • if core functionality of unzip still works

Please share your experience by commenting on bug.

Package to test located in Lazy_Kent home project

Thanks in advance

Annuncing KIWI-LTSP package updates

March 31st, 2010 by

Hello Community

openSUSE packages are updated to use the latest LTSP. Here are the highlights of this release:

* LTSP 5.2.1
* LDM 2.1.1
* LTSPFS 0.6.0
* kiwi-ltsp-prebuilt 0.8.2
* kiwi-ltsp-bootimage 0.8.2

Follow the Quick Start guide here: http://en.opensuse.org/LTSP

Give it a test and let me know your feedbacks.

On the side note,  jury verdict in the Novell vs SCO Group trial, Novell wins. Good news for Novell, for Linux and for OSS

Have a lot of fun…

The KDE Plasma Reference

March 17th, 2010 by

Two days ago the KDE Plasma community announced that they are providing a live image of the Plasma Netbook Reference Platform. They provide this image to make it easy for all interested developers, users, journalists and geeks to check it out, work with, talk about and and improve it. The reference image is the result of an KDE effort utilizing the openSUSE Buildservice and it’s based on the openSUSE distribution.

What does that mean for us the openSUSE community? First of all it makes us very happy and proud. And we think it proves once again that the openSUSE projects’ distribution and its tools have the level where they stand the production pressure which comes with this kind of use cases. The Plasma Netbook Reference Edition is a lot of code to build and has many potential contributors, testers and users. Enabling people to fullfil these jobs can not be done with some script found lying around on the internet. It requires a high level of experience, professionality and stability in development and operation of the toolchain. We always have these factors in mind and many hands and brains produce high quality products reproduceably. We have the build engine, the collaboration tools, notification systems, download infrastructure and the distribution on this level. For the KDE Plasma Netbook Reference Edition we can provide the tools to build the packages and the distribution image plus the linux distribution neccessary to test the interactions between the UI and the rest of the hardware on a netbook system. That way people can experience a whole system, which is way more useful than testing the UI in isolation.

But what is most important, many people in the community are around who wholeheartedly work on achieving these great results while having fun. Again, we are proud that the team selected our distribution as a base and our tools to work with. Thank you guys for your trust. It is a great move for all, the users, KDE and openSUSE.

openSUSE Boosters update: build.opensuse.org improvements

March 16th, 2010 by

In January, the Build Service squad of openSUSE Boosters worked to improve the openSUSE Build Service web client experience.

One focus was to make it easier for project maintainers to review and accept package submissions from contributors.  As explained in detail in the Collaboration article, when a contributor has made a local change to a package in her branch of a project, she then submits a request to merge the changes back to the original project (‘osc submitrequest’).  This request is received by the maintainers of the original project, who review it, and then submit it onwards towards openSUSE:Factory, for example, where it is reviewed again.  This distributes the workload of assembling a distribution by using the ‘many eyes’ typical of Free Software development in a structured way.

Until now, the list of requests waiting to be handled was very basic, only showing that a request was made regarding a particular package.  It was necessary to use the osc command line client to actually review and accept or reject requests.

Accepting a submitrequest from the web client

The Boosters’ sprint resulted in a fully-featured web frontend, where the reviewer can check if a submitted package actually builds, the differences in the request, accept or reject with comment, and also immediately submit the changes onward to openSUSE Factory.

Checking that submitrequests build

Showing the changes in a submitrequest

Showing the changes in a submitrequest

Another focus has been to make the overall process of preparing an openSUSE release easier.  The release manager’s job involves bringing together the output of many Build Service development projects, making sure that they all build, and that they have submitted their latest versions from the development projects to openSUSE:Factory.  This is the Build Service collaboration model.  If packages don’t build for a milestone release, or are not submitted, then the release manager can only take the previous version or choose to exclude a package from the release, which doesn’t help in getting the distribution tested.

Factory Status showing packages from GNOME:Factory

Factory Status showing progress from GNOME:Factory

The new project status page gives a project maintainer, for example the openSUSE release manager, a bird’s eye view of what needs to be done in his project: a list of packages that are currently failing; where there is an outstanding submit request, where there are unsubmitted changes in the development project, and where there is a newer version available upstream.  With quick links to projects and packages of interest, and a powerful set of filters, a project maintainer can quickly see where there are problems then drill down into the details.

Filtering problem packages by development project

Build your own Google Earth rpm

March 9th, 2010 by

The last days I’ve spent some time to investigate how to package Google Earth into an rpm. There was already a script called make-google-package available on the internet, but this one creates a debian package only. However, it was a good start to get me going to create a Google Earth (GE) rpm. Although I met quite some obstacles, which is not to uncommon in package building, I was still able to come up with a procedure a get GE packaged. The biggest problem I encountered were incorrect library dependencies, for which I opened issue 702 in the Google Earth issue tracker. Anyway to make a long story short: the rpm installs Google Earth system wide, corrects file permissions, for openSUSE_11.2 it takes care that the font is rendered correctly, the rpm takes care that Google Earth integrates nicely with the rest of the openSUSE system.

The procedure to build the rpm can be found in the openSUSE wiki. One word of caution about the procedure, you need to be an experienced linux user and you need to have access to the openSUSE Build Service (OBS) to be able to build the rpm. This is due to library dependency problem, which prevents it to build without modification to the base system.

If you like and you have the knowledge how to build an rpm with the tool ‘build’, it would be great if you can extend the howto with steps how to do this (build a GE rpm with ‘build’) to the before mentioned page. The same is valid for a procedure that uses VirtualBox to build the rpm.

Last but not last; a procedure or even a script, that uses ”’rpmbuild -ba”’ to build the rpm, would be very welcom as well.

new “osc config” command

March 8th, 2010 by

Hi,

recently I implemented a “osc config” command to set or get a configuration option.

Syntax: osc config <section> <option> [<value>]
(<section> is either an apiurl (see sections in the configfile) or an apiurl alias or ‘general’)

Here are some small examples how to use it:
# get the current value
marcus@linux:~> osc config general build-root
‘general’: ‘build-root’ is set to ‘/var/tmp/build-root-%(repo)s-%(arch)s’
# set an option
marcus@linux:~> osc config https://api.opensuse.org aliases obs
‘https://api.opensuse.org’: ‘aliases’ is set to ‘obs’
# remove an option
marcus@linux:~> osc config obs aliases –delete
‘obs’: ‘aliases’ got removed
# remove/reset an option
marcus@linux:~> osc config general build-root –delete
‘general’: ‘build-root’ is set to ‘/var/tmp/build-root’

Feedback, comments etc. are always welcome 🙂

http://software.opensuse.org/stage

March 3rd, 2010 by

Part of our “umbrella” milestone, Pavol and Robert ported software.opensuse.org to the Bento theme. To get more feedback for it, I now deployed it as http://software.opensuse.org/stage.

Please note two things:

  • it also includes a new feature from the Education project: a link to openSUSE derivates
  • the language box is experimental and we kind of decided already to kill it again

On top of that of course: the Bento theme is not yet finished – it’s only a stage deployment to get feedback.

Have fun!

new osc feature to review requests

February 11th, 2010 by

Hi,

darix asked me to implement a new feature (and to blog about it 🙂 ) to review requests interactively. How it works:

osc request show <request id> –interactive. Example:
marcus@linux:~> osc rq show 32152 –interactive
Request #32152:

submit:   home:Marcus_H/bar(r1)(update) -> home:Marcus_H/foo

Message:
foo bar

State:   new          2010-02-11T02:40:20 Marcus_H
Comment: None

d(i)ff/(a)ccept/(d)ecline/(r)evoke/(c)ancel > a -m “reviewed and accepted”
marcus@linux:~>

If you just specified “a” or “d” or “r” osc will run $EDITOR to enter a message. To enable this interactive mode permanently add “request_show_interactive = 1” to the “[general]” section in your ~/.oscrc.

Comments, feature requests etc. are always welcome.

AstroGarrobo Beta

February 10th, 2010 by

Space, the Final Frontier! This is the tale of one Amateur Astronomer that have found in openSUSE a terrific tool for public outreach, self-learning and teaching platform.

Ok, that was a bit exagerated.

But the truth is that I am enjoying the new SUSE Studio suite. And that’s because it is facilitating my job as an educator. I work with the Nicaraguan Amateur Astronomers Society (ANASA) in teaching basic astronomy to the public. Obviously, my workhorse is an openSUSE laptop, loaded with Stellarium, Celestia, KStars and Xephem (and many other tools for my personal job as an astronomer).

(more…)

Hermes Twittering about openSUSE Factory

February 1st, 2010 by

I'm going to FOSDEM, the Free and Open Source Software Developers' European Meeting

Last week we updated Hermes on our production servers, they’re running a version now which will become a first Hermes release. I hope to get it packaged and released this week to present it on FOSDEM where I’ll give a talk about Hermes. Don’t miss it if you’re interested in this useful technology.

There went in a lot of technical improvement and bugfixes which one gets aware of if a system like Hermes runs in production for quite some time, such as missing indexes here and there which slow down the database and stuff like that. But that is another story.

What I actually wanted to talk about is the the fact that Hermes now is twittering now for you. You can follow it under the OBSHermes Twitter account. Hermes currently twitters about version updates of all packages in the openSUSE Factory project, so this is your tweet if you want to be at the bleading edge of Factory.

It is configurable for the administrator what actually is twittered. Is there other useful information around the openSUSE project which you would like to see twittered about? If so, please let me know.