Home Home
Sign up | Login

Author Archive

Factory Progress 2011-08-05

August 5th, 2011 by

The last few weeks have seen some a lot of package updates thus keeping our review and checkin team busy. I’d like to mention Sascha Peilicke who reviewed alone this week lots of packages. Have a look at just two numbers: In all of July we had 1001 check-ins and just from August 1st to 4th we had already 276 checkins.

The legal team has also gone through the long list of new packages and package updates during the legal reviews and reduced this week the list from over 100 packages to 12 packages now. Thanks Ciaran and Christoper for your legal review!

(more…)

Factory Progress 2011-07-18

July 18th, 2011 by

I’ve noticed the following changes that might interest people using and developing openSUSE Factory:

Package changes

GNOME 3.1.3

The GNOME team plans to have GNOME 3.2 in for openSUSE 12.1 and thus have updated to the current development release 3.1.3. They have also started removing old GNOME 2 packages that are not needed anymore.

systemd

Frederic gave an update on systemd integration. The graphical bootloader allows now to switch during boot between systemd, SysVinit and also shell code.

Also, Lennart Poettering wrote in his “systemd for developers” series about socket activation where he uses cups as example.

(more…)

Factory Progress 2011-07-01

July 1st, 2011 by

Here’s with some delay the next incarnation of Factory Progress. I’ve noticed the following changes that might interest people using and developing openSUSE Factory:

Package changes

Linux 3.0

Linux kernel 3.0 rc5 is currently on its way to factory and the header files (in package linux-glibc-devel) have already been updated for it. If your software reads the Linux kernel version, please check that it can cope with the two digits instead of the three of the new version. Best would be to not read the version at all.

Systemd

Frederic has proposed a “Road to systemd for openSUSE 12.1″. Systemd is a replacement of the SysVinit scripts that we have been using and improving in the past with many new – including some controversial – ideas. Check his blog post for additional references about systemd. The majority of the distributions are moving to systemd as well and standarizing on it, will allow to share some more code and development in this area.

We’re now in phase 1 – which means: Get systemd running as an option. Once this is working satisfactory, we can switch the default (phase 2) and decide what to do with SysVinit support.

(more…)

Factory Progress 2011-06-03

June 3rd, 2011 by

This week saw the release of the first milestone of openSUSE 12.1 and work on factory is continuing, I’ve found the following changes important:

GNU C Library (glibc) 2.13

We’ve updated glibc from version 2.11 to 2.13 which brings many bug fixes and AFAIK no major breakages to packages. The package itself got cleaned up a little bit as well, so please report any problems.

GO Programming Language

Factory now contains a compiler for the GO language which is “is an expressive, concurrent, garbage collected systems programming language that is type safe and memory safe.”. More details about GO are available on the openSUSE Wiki, the devel project with additional packages is devel:languages:go.

Packaging: Source Processing

The usage of _service files in Factory confused many packagers and resulted in broken packages so that these will be deprecated. As a replacement, Adrian implemented now a new source processing method and asks for testers.

Packaging: Adding useful Provides to cups drivers

Vincent “updated python-cups to a new version, and it is now shipping
files to automatically add Provides tag to packages that are shipping
cups drivers.”. This allows desktop packages to install the right printer driver – or users to do it via zypper. Packages with cups drivers just need to add a “BuildRequires: python-cups”.

Open Build Service Improvement

The “My Work” view has been updated to better show packages that are in review state and need your review. I suggest everybody to check out the page and cleanup your list.

Multiple Buildroots with osc

If you like to use more than one build at the same time, there are several options like pointed out on the opensuse-packaging mailing list:

  • Use of the environment variable OSC_BUILD_ROOT to define a build root.
  • Editing of the osc config file ~/.oscrc and setting build-root to contain the variables %(repo), %(arch),  %(project) or %(package).

Correction on auto-legal build service check

Jürgen corrected my report from last week: He would love to see the checks for auto-legal moved and welcomes any help.

Thanks

Thanks for the words of encouragement to my first blog post. I’ll try to continue this series. If there’s anything you think should be added to it, please contact me via email at aj at opensuse dot org.

Factory Progress

May 27th, 2011 by

A lot of things are happening in our Factory distribution that will be released in November 2011 as openSUSE 12.1 and I’d like to point out a few things from the last few weeks that users and developers of factory shouldn’t miss.

Roadmap openSUSE 12.1

Stephan “Coolo” Kulow has updated the openSUSE 12.1 Roadmap, the next milestone is Milestone 1 which is delayed and targeted now for release on Tuesday, 30th May. The next paragraphs highlight some of the updates for this versions.

GCC 4.6

The GNU Compiler Collection has been updated to version 4.6, the list of  changes includes the following new warning that will be visible while compiling packages for openSUSE Factory:

  • “New -Wunused-but-set-variable and -Wunused-but-set-parameter warnings were added for C, C++, Objective-C and Objective-C++. These warnings diagnose variables respective parameters which are only set in the code and never otherwise used. Usually such variables are useless and often even the value assigned to them is computed needlessly, sometimes expensively. The -Wunused-but-set-variable warning is enabled by default by -Wall flag and -Wunused-but-set-parameter by -Wall -Wextra flags.”

Some packages have been failing by the new GCC due to new warnings and new optimizations and most have been fixed already but please double check that your packages are building and running fine.

RPM 4.9

Michael Schröder announced RPM 4.9 for Factory. He explains the main packager visible changes as:

“Besides some bug fixes and an update to a newer BerkeleyDB
library rpm-4.9.0 contains plugin architecture for dependency
generation. In older rpms, the internal dependency generator
was pretty much hardcoded in C, so we always used the old
external one to generate dependencies. With rpm-4.9.0, the
internal generator has become flexible enough so that we
can use it.

This means for you, that rpm will no longer use the %__find_provides and %__find_requires macros. Some packages redefined those macros to be able to filter the generated dependencies.
This will no longer work in rpm-4.9.0. Instead, support for
dependency filtering was added to rpm…”

GNOME 3

GNOME 3 has now hit Factory as well and Vincent Untz explained how to fix failures due to the large push.

Linux Kernel 2.6.39

This update was a “boring” update – nothing broke AFAIK ;), so I hope it’s a solid version. Users will benefit from the new features in it. 2.6.39 is the first kernel without the Big Kernel Lock at all!

Packaging Changes

Besides new software, also new ways of handling it get introduced. The following catched my eyes:

Rpmlint update

Ludwig Nussel updated rpmlint to version 1.2 and explained the new warnings about packaging of rpm packages – and what to do about them.

Changing the process of Factory submissions with the Open Build Service

Now with every submission to Factory scripts are run automatically that do two different reviews before the package goes to human check-in review:

  • The “legal-auto” review checks the updated package for changes in licenses.
  • The “factory-auto” review checks that the updated package builds actually in the devel project – and if not, rejects it.

The “legal-auto” review has quite a long backlog at the moment and Jürgen is working on moving some of the checks to rpmlint or osc checks – so that the packager notices and fixes them before submission to Factory.

Also, you can now submit packages to Factory even if you are not the maintainer of the package but in this case the maintainer (packager) gets a review request to review that the package really can go to factory and thus a plea to packagers to handle their review requests.

openSUSE Conference

The openSUSE Conference is this year co-located with the SUSE Labs conference. Join us to present and discuss also Factory related topics. The Call for papers is open now!

I’m interested on feedback on this article – should I start a series?

Versionitis

April 6th, 2011 by

The voting on how to do the versioning is over and the “old school” has won by 55 per cent (of 98 participants). Thanks to all that participated in the two votes and the discussion around the topic.

As Coolo said in on the project list,  we’d like to make a small change to the numbering:

We will not have a .0 release but only .1, .2, .3 release. Since we have releases in three months, the November
release is always the .1 release, the July release the .2 and the March release the .3.

So, the plan is that the next release will be called openSUSE 12.1 and launched on the 10th of November, 2011! Two years later – on the 14th of November, 2013 – we will then have the openSUSE 13.1 release.

So, the next four releases are called:

  • November 2011: openSUSE 12.1
  • July 2012: openSUSE 12.2
  • March 2013: openSUSE 12.3
  • November 2013: openSUSE 13.1

Detailed results for logged-in openSUSE members are available at the connect poll page and I have reproduced them here as well:

  • A: “old school”: Like currently but only counting the right number until 3:
    55% (54 votes)
  • B: “Fedora style”: Just integers:
    29 % (28 votes)
  • C: “Ubuntu style”: YY.MM:
    16 % (16 votes)

This is also consistent with the results of the first public voting.

Note that openSUSE does not have a major and minor numbering, even if it seems so. There is right now no difference in any way between what we would do for openSUSE 11.4 or 12.0 or 12.1 – and no sense to speak about openSUSE 11 or openSUSE 11 family. We also had in the past no process on how to name the next release (when to increase which parts of the number).

I think this new versioning is still consistent with the old one but also an improvement since it’s now clear that we change the first digit every two year. The first poll showed that half of our users prefer a date based versioning and the other a consecutive numbering. So, depending on your point of view, you can see this as a mixture of both or as consecutive numbering ;)

So, time now to make openSUSE 12.1 a great release!

openSUSE Release versioning – Poll on last three options

March 28th, 2011 by

The poll on SurveyMonkey on how to version the openSUSE distribution release is now closed, you can see the results here. The winner is the “old school” (like currently but only counting the right number until 3), followed by “Fedora style” (just integers) and “Ubuntu style” (2 digits year “.” 2 digits month).

The openSUSE members only poll is now live on connect.opensuse.org until April 04, 2011. Please select your favorite option!

First Survey on openSUSE Version naming is open now

March 16th, 2011 by

Following my last blog post on “how to name the distribution release“, I’ve opened up a public survey and look forward to your votes. There is also a good discussion going on on the opensuse-project mailing list.

This is the first iteration. Coolo and myself discussed to use a second survey with the group of winners on connect.opensuse.org.

How to name the distribution releases?

March 11th, 2011 by

We had this week a discussion on IRC on how to name the next release and I took the action item to do a poll on connect.opensuse.org now to help us solve the naming of openSUSE distribution releases. I’ve started earlier today a discussion on the opensuse-project list and already incorporated some comments I received in this text.

openSUSE does not have a major and minor numbering, even if it seems so. There is right now no difference in any way between what we would do for openSUSE 11.4 or 12.0 – and no sense to speak about openSUSE 11 or openSUSE 11 family. We also have no process on how to name the next release (when to increase which parts of the number).

Here are some options, if I miss some, please tell me and I will then soon setup a poll. I’m listening the next version we would use as well as how the following would be called as an example. Remember we have releases every 8 months, so the next releases will be in:
November 2011, July 2012, March 2013, November 2013, July 2014, March 2015.

Here are the options I collected so far:

(more…)

Please note…

November 22nd, 2010 by

I’m going on parental leave from December 14th to February 13th, 2011. My son was born in January and now it’s my time to help a bit more out at home. My wife has many plans for me and I have some myself as well including changing diapers, some work at the house, celebrating christmas, showing off our kids to their grandparents, aunts and uncles, getting my son settled in the daycare, building a snow man…

I hope some days of vacation will be in there as well so that I can be refreshed again when I return back to the Novell office to continue working for openSUSE.

Right now, I try to find some people that take over some of my responsibilities.

I will take care that everything I do which is important will be handled during the time, e.g. even better reaction to PromoDVD shipping – and silently hope that after the parental everything works far better without me than right now ;)

So, you all have a short break from me.  I don’t know how much time I’ll spend online but I know I will not be in the office and don’t want to be fully engaged during my leave.  I’m looking forward to both
the parental leave and also to return – and will read regularly the openSUSE planet to see what’s happening!

During my absence, Jacqueline Junghanns will take over and handle most of my responsibilities. Some of you might know Jacqueline from the openSUSE conferences which she helped to organize. I hand over the virtual mikrophone to Jacqueline to introduce herself:

Jacqueline

Jacqueline

“Hi, my name is Jacqueline Junghanns and I can say that I am a SUSE dinosaur as I had my ten year anniversary just a couple of weeks ago and I do not plan to extinct any time soon ;).  I am very much looking forward to dive into the openSUSE project because I already got the chance to help out “backstage” and I am glad about this new opportunity.  During my ten years I gathered experience in various areas such as hardware certification and right now as a team assistant for OPS.”

Sending of PromoDVDs

One thing I have handled in the past, is sending out of PromoDVDs and other promotional material for events. We do have a good stock of openSUSE 11.3 DVDs available and happily send them out for events. Please start using the address promodvds@opensuse.org to request them – and right now Jacqueline and myself will answer, later only Jacqueline.