Home Home > Distribution
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 ‘Distribution’ Category

Hackweek IV: Novell Bugzilla access from command line

July 29th, 2009 by

During a last Hackweek I decided to work on some tool which will helps users with submitting a new bug. My idea is to create something like reportbug from Debian, but targeted to SUSE. So the first step was find the way how to communicate with a bugzilla (especially to bugzilla.novell.com – bnc). Fortunately I found several libraries, which should be used for it:

perl-SUSE-BugzillaClient is written by Thomas Schmidt especially for bnc, so it is able to login using iChain. It also provides few functions for bugzilla communication, but unfortunately only for querying. Pybugz is written by Alastair Tse for Gentoo development in Python. But it is not able to login through iChain and I did not extended it for bnc, because it uses a plain GET/POST communication with parsing of HTML using regexes.

The reason why I have used the python-bugzilla written by Will Woods from RedHat is simple. It uses XMLRPC API, which bugzilla provides. And it’s also written with a flexibility in mind, so writing of another type of Bugzilla was easy. Just some subclassing and reimplementing of few methods and voila, the NovellBugzilla type is here. Because it uses iChain, it was necessary to reimplement login/logout methods – I spend a lot of time to understand how it works. Osc uses a HTTP authentication, which should be supported too, but even if it works with api.opensuse.org, it did not work with bnc. So I used a Firefox and LiveHTTP headers extension to track a communication and implemented the login according it.

The useful advantage of Novell bugzilla is that I extended a method readconfig, which reads a config file. Novell Bugzilla can read the username/password from ~/.oscrc, so you don’t need to have a same password in another config file, if you use osc.

So on the end those few lines of Python code

import bugzilla

bnc = bugzilla.NovellBugzilla(url="https://bugzilla.novell.com", user="mvyskocil", password="XXXXX")
kwargs = {
    'product': 'openSUSE 11.2',
    'severity': 'Normal',
    'cc': [],
    'rep_platform': 'x86-64',
    'component': 'Java',
    'summary': '[Java:packages/ant]: Cannot find a Java virtual machine',
    'version': 'unspecified',
    'assigned_to': 'mvyskocil@novell.com',
    'op_sys': 'Linux',
    'description': 'This is a testing bug report\n'
    }
bug = bnc.createbug(**kwargs)
print bug.bug_id

Have created this bug#525549. Even if Python is readable for regular programmers, the **kwargs should be expressed. It maps the dictionary to named function arguments (called keyword arguments – kwargs – in a Python world), so both calls in following snippet are equivalent.

d = {'name' : 'value')
call(**d)
call(name='value')

The python-bugzilla comes also with a simple command line tool called bugzilla, so this tool should be used also from shell scripts. It is sometimes little bit raw. For example listing of all products returns an output as a Python dictionary

bugzilla --bztype NovellBugzilla --user mvyskocil --password xxxxxx info -p
...
{'description': 'openSUSE 11.1', 'internals': {'disallownew': 0, 'classification_id': 7340, 'name': 'openSUSE 11.1', 
'votestoconfirm': 0, 'milestone_required': 0, 'id': 651, 'votesperuser': 20, 'maxvotesperbug': 5, 'defaultmilestone': '---',
'milestoneurl': '', 'description': 'openSUSE 11.1'}, 'name': 'openSUSE 11.1', 'id': 651} 
{'description': 'openSUSE 11.2', 'internals': {'disallownew': 0, 'classification_id': 7340, 'name': 'openSUSE 11.2',
'votestoconfirm': 0, 'milestone_required': 0, 'id': 755, 'votesperuser': 20, 'maxvotesperbug': 5, 'defaultmilestone': '---',
'milestoneurl': '', 'description': 'openSUSE 11.2'}, 'name': 'openSUSE 11.2', 'id': 755}
...

which might be hard to parse in other language. But it provides a lot of functionality, so for other informations about usage, please use man bugzilla.

SUSE Studio Launch – and openSUSE

July 28th, 2009 by

Today the SUSE Appliance program was launched by Novell. The interesting part for openSUSE is the launch of  SUSE Studio.  SUSE Studio is a web-based tool to build complete software appliances based on SUSE Linux Enterprise and also openSUSE. A software appliance is a ready-to run image that you can copy on your harddisk and start directly – or it comes packaged as a virtual image that you can boot using e.g. Xen. Normally software appliances are custom made for a specific purpose, e.g. a database server.

I just build on top of openSUSE 11.1 a git server appliance. The interface is very intuitive so that most of the time used was waiting for the image to be created – and building the images is extremely fast  (the LiveDVD image took 4:21min to build, the hard disk image only 2:35mins)! The SUSE Studio folks have created a great product – congratulations!

(more…)

Call for openSUSE Core Test Team

July 24th, 2009 by

In addition to well-developed code, testing is a major part of ensuring a rock-solid openSUSE Linux distro. To make sure testing of openSUSE 11.2 (and beyond) are done in a well-organized way, we’re improving the way the openSUSE Core Test Team works together to ensure top quality for openSUSE.

In the next couple of days Milestone 4 of openSUSE 11.2 will be available. This is a very good moment to have a closer look into the next openSUSE release: some new features are already implemented and there is enough time to fix reported problems.

Thus we are looking for 15 members of the openSUSE Community that are willing to contribute to the openSUSE project by joining the openSUSE Core Test Team and operate in the following areas:

  • Check if new features are implemented and working as requested
  • Have a deeper look into the install and update system of openSUSE and ensure a broad hardware coverage
  • Creating, improving and executing test cases for various areas of the distribution

Repository for test cases and tracking system for all test results will be Testopia, the test case management extension of Novell’s Bugzilla. Members of the Core Test Team will get access to the openSUSE test plans and will so be able to contribute. Beside storing test results they are also able to create or modify test cases.

If you are really interested in joining the openSUSE Core Test Team and willing to spend a reasonable amount of time to move the openSUSE project forward please get in contact with Holger Sickenberg <holgi at suse.de> providing following information:

  • Your Linux experience
  • Previous testing experience, if any
  • Areas you are interested in testing

The number of members is limited to 15 at the moment to ensure we are able to adequate support everyone of them. We will add more once we’ve figured out in the smaller group whether everything works.

Of course everybody is still able to contribute to the openSUSE project by testing parts of the distribution. Enabling the openSUSE Core Test Team will not have any impact on that. Further information on testing is available at www.opensuse.org/Testing.

We are looking forward to your application. Deadline for applications is August, 15th 2009.

Build Service for Package Testing – and Making Factory Updates Smaller

July 24th, 2009 by

I’ve blogged already about the work done by Coolo and Michael on reducing the size of factory updates.  Looking into some  of the packages that did not get filtered out due to timestamps, I decided to use that as my hackweek project – and learn some more about the openSUSE Build Service.

Coolo told me that I could create a small project in OBS with packages I wanted to look at and with my testing version of build-compare.  So, I created a project and set it up to build against openSUSE:Factory and linked some packages from factory into the project.

(more…)

New Package: kpassgen

July 20th, 2009 by

Today i’ve released the kpassgen Package in KDE:KDE4:Community. It is planned to publish in Contrib too. (more…)

Package Review in the Build Service

July 15th, 2009 by

If you are responsible for a package and somebody else changes  it (see my post on fixing packages in openSUSE Factory), you will receive an email from the openSUSE Build Service with a subject like “[obs undefined-request 14149] network:time/ntp: created by a_jaeger”.  The email contains instructions on what you can do with the request, let me just show the normal way (everything is fine) and refer to the documentation on the wiki about Collaboration in the Build Service and the short email.

(more…)

Reducing Size of Factory Updates

July 14th, 2009 by

Stephan Kulow, Michael Matz and others have been working on reducing the size of updates of factory (see feature #303532), so that less packages need to be downloaded each time and after Gerald pointed out two problems, I talked a bit with Stephan today about the current state.

(more…)

Official X11:lxde project now open! We need you!

July 13th, 2009 by

Thanks to Pavol Rusnak, the official project X11:lxde is now open, first packages are already there available for testing, but, some of them just fail because of code and security checks, we need some patches than, before provide you the best packages you can imagine for that DE.

WE NEED YOU!!!

if any of you want to help us providing patches and various fixing you are welcome, and of course you can begin using OBS collaboration way: http://en.opensuse.org/Build_Service/Collaboration

A fast review of the problems we have are available on that post into LXDE forum.

Right now than, if you want to use LXDE you should continue to follow instructions provided on my previous blog post here

Waiting for you and you help

Andrea

Lightweight X11 Desktop Environment, A.K.A. LXDE

July 11th, 2009 by

Lightweight X11 Desktop Environment“, is an extremely faster, performing and energy saving desktop environment. It comes with a beautiful interface, multi-language support, standard keyboard short cuts and additional features like tabbed file browsing. LXDE uses less CPU and less RAM the other DE. It is especially designed for cloud computers with low hardware specifications like netbooks, mobile devices (e.g. MIDs) or older computers. It provides a fast desktop experience connecting easily with applications in the cloud. LXDE supports a wealth of programs. The source code of LXDE is licensed partly under the terms of the General Public License and partly under the LGPL.

(more…)

Linuxtag 2009 in Berlin

June 29th, 2009 by

I’m back now from attending Linuxtag 2009 in Berlin. On Saturday I gave a presentation about openSUSE 11.2 and we had some good discussions about it.  I demoed WebYaST which will be an exciting addition to openSUSE.  WebYaST allows remote – and also local – administration of your system.  The participants of the talk mentioned also that  “zypper dup” to update from 11.1 to 11.2 is an important addition.

Btw. to learn more about openSUSE 11.2, check this wiki page which is regularly updated.

Adrian took some photos and uploaded them to the gallery.

It was great to see the momentum behind the education project, I talked a bit with Jan (and listened to his excellent talk) and Lars about it.