Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.

12 February, 2016

Michael Meeks: 2016-02-12 Friday.

22:29 UTCmember

  • Up rather early; prayer breakfast @ NCC; mail chew; sync. with Kendy & Andras, mail chew; customer call; poked at some ugly bugs and reviewed tender documents until late.
  • Really thrilled by the Gravity Waves discovery - and more thrilled that an old LibreOffice (in spirit) hacker friend Volker Quetschke is listed among the authors as wellas in our very early git logs. I still have fond memories of his passionate descriptions of the problems of high power laser inferometry in a Hamburg bar many years ago.

11 February, 2016

Michael Meeks: 2016-02-11 Thursday.

21:00 UTCmember

  • Built ESC stats; better late than never. Poked at project planning and some bugs; closed a number of issues. ESC call.

The first OpenStack Summit this year will take place in Austin (TX, US) from April 25-29, 2016. The "Call for Speakers" period ended some days ago and now the community voting for presentation started and will end 17th February, 11:59 PST (18th February 7:59 UTC / 08:59 CEST). 

I've submitted this time one talk this time:
  • "From Hardware to Application - NFV@OpenStack and Ceph" - This talk will provide insight into NFV cloud specific hardware and data center design, preferred setup and requirements to OpenStack and Ceph and also important design implications and requirements for applications and developers on this platform. 

You can vote, if you are interested to see my talk at the summit, every vote is highly welcome. The full abstract can be found at the voting page.

There is a long list of interesting Ceph related talks, simply use the search field on the voting page. I may provide a list in an additional post later as last time.

Michal Čihař: Weblate 2.4

04:30 UTC


Weblate 2.4 has been released today. It comes with extended support for various file formats, extended hook scripts, better keyboard shortcuts and dozen of bug fixes.

Full list of changes for 2.4:

  • Improved support for PHP files.
  • Ability to add ACL to anonymous user.
  • Improved configurability of import_project command.
  • Added CSV dump of history.
  • Avoid copy/paste errors with whitespace chars.
  • Added support for Bitbucket webhooks.
  • Tigher control on fuzzy strings on translation upload.
  • Several URLs have changed, you might have to update your bookmarks.
  • Hook scripts are executed with VCS root as current directory.
  • Hook scripts are executed with environment variables descriping current component.
  • Add management command to optimize fulltext index.
  • Added support for error reporting to Rollbar.
  • Projects now can have multiple owners.
  • Project owners can manage themselves.
  • Added support for javascript-format used in Gettext PO.
  • Support for adding new translations in XLIFF.
  • Improved file format autodetection.
  • Extended keyboard shortcuts.
  • Improved dictionary matching for several languages.
  • Improved layout of most of pages.
  • Support for adding words to dictionary while translating.
  • Added support for filtering languages to be managed by Weblate.
  • Added support for translating and importing CSV files.
  • Rewritten handling of static files.
  • Direct login/registration links to third party service if that's the only one.
  • Commit pending changes on account removal.
  • Add management command to change site name.
  • Add option to confiugure default committer.
  • Add hook after adding new translation.
  • Add option to specify multiple files to add to commit.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on http://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is also being used https://hosted.weblate.org/ as official translating service for phpMyAdmin, Gammu, Weblate itself and other projects.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far!

PS: The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments


Weblate is not only useful for translating software, it can help in translating any content. Let's look where our users are using it.

Software translation is the most usual use case. This is actually where Weblate was used for first time and still provides great support for that. As an example (and oldest project hosted in Weblate) you can look at phpMyAdmin, where Weblate also helps to keep in sync translation for different maintenance branches. It can also help you in using same terminology in command line utility and graphical one like it is done in Gammu and Wammu translations.

Weblate also supports localization of mobile application. Android support was originally implemented for OsmAnd project, but now they also translate iOS application using Weblate.

Another use case is for translating documentation. You need to have some infrastructure to do, but there are several free software project to help here as well. For phpMyAdmin documentation or documentation for python module Odorik the Sphinx documentation generator is used, which has support for translation of the documentation. I've recently published quick howto for this setup. Another great tool for translating documentation is Publican, it is Docbook based tool and is used for translating The Debian Administrator's Handbook.

Last but not least, you can use Weblate to translate your website. For example website for Weblate itself is translated this way.

Did you miss your use case for Weblate? Please let me know.

PS: I've heard that one Linux distribution will start using Weblate soon.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments


Up to recently, the only social presence for Weblate was my personal Twitter account. It's time to change that.

You can now follow news and information about Weblate on Twitter, Facebook or Google+.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments

Michal Čihař: Weblate 2.3

04:30 UTC


Weblate 2.3 has been released today. It comes with better features for project owners, better file formats support and more configuration options for users.

Full list of changes for 2.3:

  • Dropped support for Django 1.6 and South migrations.
  • Support for adding new translations when using Java Property files
  • Allow to accept suggestion without editing.
  • Improved support for Google OAuth2.
  • Added support for Microsoft .resx files.
  • Tuned default robots.txt to disallow big crawling of translations.
  • Simplified workflow for accepting suggestions.
  • Added project owners who always receive important notifications.
  • Allow to disable editing of monolingual template.
  • More detailed repository status view.
  • Direct link for editing template when changing translation.
  • Allow to add more permissions to project owners.
  • Allow to show secondary language in zen mode.
  • Support for hiding source string in favor of secondary language.

You can find more information about Weblate on http://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user.

Weblate is also being used https://hosted.weblate.org/ as official translating service for phpMyAdmin, Gammu, Weblate itself and other projects.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far!

PS: The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: English phpMyAdmin SUSE Weblate | 0 comments


After recent porting python-gammu to Python 3, it was quite obvious to me that new release will have some problems. Fortunately they have proven to be rather cosmetic and no big bugs were found so far.

Anyway it's time to push the minor fixes to the users, so here comes python-gammu 2.2. As you can see, the changes are pretty small, but given that I don't expect much development in the future, it's good to release them early.

Filed under: English Gammu python-gammu SUSE Wammu | 0 comments


After Monday release of separate Gammu and python-gammu, the obvious task was to get the new package to distributions.

First I've started with Debian packages, what was quite easy as from quite complex CMake + Python package it is now purely CMake and it was mostly about removing stuff. Soon the updated Gammu package was uploaded to experimental. Once having that ready, I've also update the backports for Ubuntu and these are available in Gammu PPA. Creating new python-gammu package was a bit harder as this is the first Python 3 compatible package I've created, but it's now ready and sitting in the NEW queue.

While working on python-gammu package, I've realized that some of the data used in testsuite are missing in the tarball. While not being critical, this is definitely not nice, so I've decided to release python-gammu 2.1 today. It also includes fixes for some corner cases found by coverity.

For openSUSE the packaging was quite easy as well, stripping out unneeded parts of Gammu package went smoothly and it's now in hardware project, SR to Factory is pending. With python-gammu it turned out to be much harder as the testsuite had failed there with some strange error coming out of libdbi. After looking deeper into it, the problem is in new return type available in Git snapshot openSUSE is shipping. Fortunately producing fix was quite easy, so next Gammu upstream will handle that properly and package in hardware project is already patched. You can now use python-python-gammu from devel:languages:python and SR to Factory is pending as well.

Filed under: Debian English Gammu python-gammu SUSE Wammu | 0 comments

Kohei Yoshida: mdds 1.1.0

02:25 UTCmember


I’m pleased to announce the availability of mdds 1.1.0. As always, the source package can be downloaded from the project’s home page.

This release includes the addition of 2 new data structures – trie_map and packed_trie_map, significant performance improvement on sorted_string_map, general bug fixes on some of the existing data structures, enhancement on multi_type_matrix, and support for user-defined event handlers for multi_type_vector.

Huge thanks to Markus Mohrhard for sorted_string_map’s performance improvement as well as the bug fixes and the enhancement on multi_type_matrix’s walk() method.

In addition, thanks to David Tardon, we now use automake as our build system which will simplify the process of package generation and integrity check among other things.

Here is the full list of changes since version 1.0.0:

  • all
    • switched our build system to using automake.
  • packed_trie_map (new)
    • new data structure that implements a trie also known as a prefix tree. This implementation requires all key values be known at construction time, after which its content is considered immutable. Internally it packs all its nodes in a single contiguous array for space and lookup efficiencies.
  • trie_map (new)
    • new data structure that implements a trie. It works similar to packed_trie_map except that this version is mutable.
  • multi_type_matrix
    • added a variant of walk() that takes the upper-left and lower-right corners to allow walking through a subset of the original matrix.
  • multi_type_vector
    • fixed incorrect return values of the increment and decrement operators of in-block iterators. They would previously return a value_type pointer which did not conform to the behaviors of STL iterators.
    • added support for custom event handlers for element block acquisitions and releases.
  • flat_segment_tree
    • fixed incorrect return values of the increment and decrement operators of its leaf-node iterators as in multi_type_vector’s fix.
  • sorted_string_map
    • significantly improved the performance of its find() method by switching from using linear search to using binary search. The improvement is especially visible with a large number of elements.


I’ve also added Doxygen documentation for this library for those who are more used to the Doxygen style comprehensive code documentation. The official API documentation has also received some love in the code examples for multi_type_vector. I plan on adding more code examples to the documentation as time permits.

10 February, 2016

Michael Meeks: 2016-02-10 Wednesday.

21:00 UTCmember

  • Up lateish; still not terribly well. To action; read mail, patches, chat with Jos. Plugged away at bugs, and piled up admin tasks.



Actually, I think you can make fire from the moonlight -- it just won't be easy. All you need is square inch (or so) of mirrors on moon. If there was not enough of mirros on moon hundred years ago, I'm pretty sure we put enough junk there in last 100 years.. probably including some mirrors for distance measurement.


Tumbleweed-black-greenTumbleweed updated systemd from 224 to 228 in one of four snapshots this week and there were plenty of other exciting updates.

The change log for the updated systemd states a number of properties previously only settable in unit files are now also available as properties to set when creating transient units programmatically via the bus.

Screenshot from 2016-02-10 11-45-32

GCC 5 updated to 5.3.1 in the most recent snapshot, 20160208. The update of GCC 5 will raise more errors, yet creates more consistent behavior.

Mozilla Firefox updated to 44.0 in the same snapshot and has updates to assist with spoofing attacks, unsafe memory manipulation found through code inspect and allows for control characters to be set in cookie names.

The 20160207 snapshot had ambitious change for YaST, which resulted in a big changes for YaST and a blog on openSUSE Lizards about those changes.

boxThe YaST team did a three-week sprint where they changed the design and revamped dialog for creating local users. Updates were made to core, network and update. The new dialog looks like the screenshot on the right and the openSUSE community needs to decide the default behavior for Tumbleweed regarding password encryption methods. The YaST team is putting a lot of effort in rewriting the layer that access to disks, partitions and volumes. A milestone met was the rewrite ability to examine a hard disk with a complex partitioning schema (including MS Windows partitions, a Linux installation and so on) and propose the operations that need to be performed in order to install the Geeko distribution. Read more about developments in YaST on Lizards.

One last package to highlight from the four Tumbleweed snapshots this week is sysdig in the 20160208 snapshot. Sysdig updated from 0.7.1 to 0.8.0. Sysdig is an open-source system-level exploration and troubleshooting tool. It captures system state and activity from a running Linux instance, then save, filter and analyze, which allow sysadmins to see the containers that are running. Take a look if that sounds interesting.

Users of Tumbleweed and expect minor changes in the coming week as there are currently no big changes in the factory staging. Plasma 5.5.4 is expected soon.

09 February, 2016

Michael Meeks: 2016-02-09 Tuesday.

21:00 UTCmember

  • Up early; mail chew, more code reading, chasing down a vile GL crasher; sales team call - more work, apparently un-related to recent commits - always fun. Finally created a workaround, unfortunately GL drivers appear to mangle memory where valgrind cannot go - poked Julian. Out to help at Scouts with M. back, and up extremely late working with Emmanuel & Tomaz.


Yes, I did contribute to free software. Does it mean every person from university has to spam me, just because he's "researching" it? Jeffrey Carver <carver@cs.ua.edu> , I'm talking about you. And we are not talking one message, either.

08 February, 2016

Michael Meeks: 2016-02-08 Monday.

21:00 UTCmember

  • Up early; mail chew - call with Kendy, poked at a chunk of tangled code; quick lunch; chat with Tor. Back to the typing interspersed with some team calls. Worked rather late.


Reviewing patches for the OpenStack CI infrastructure, there's one piece that often confuse contributors: The question how Zuul and Jenkins configuration are working together.

While we have the Infra Manual with a whole page on how to create a project - and I advise everyone to read it - , let me try to tackle the specific topic of adding new jobs from a different angle.

What we're discussing here are job, or tests, that are run. Jenkins actually runs these jobs. Zuul watches for changes in gerrit (URL for OpenStack is review.openstack.org) to trigger the appropriate jobs so that Jenkins runs them.

To understand the relationship between these two systems, let's try as an analogy programming languages: As a developer, you create a library of functions that do a variety of actions. You also write a script that uses this library to execute them. Jenkins can be considered the library of test functions. But just defining these is not enough, you have to call them. Zuul takes care of calling them, so in the analogy is your script.

So, to actually get a job running for a repository, you first need to define it in the Jenkins "library", and then you trigger its invocation in Zuul. You can also add certain conditions to limit when the job runs or whether it is voting.

If you dig deeper into Jenkins and Zuul, keep in mind that these are two different programming languages, even if both use YAML as format. Jenkins runs jobs and these are defined as text files using the Jenkins job builder. To define them, you can write a job, or use a job-template and instantiate it, or group several job-template in a job-group and instantiate that job-group to create with a few lines many jobs. Zuul uses these jobs and has as syntactic sugar templates to reuse jobs and the queues they run in.

Let's look at a simple examples, adding a new docs job to your repository called amazing-repo:

  1. Check out the project-config repository and make it ready for patch submission like creating a branch where you work on.
  2. Since for the docs job already a template exists, you can reuse it. It is called'gate-{name}-docs', so add it to your repository in file jenkins/jobs/projects.yaml:
    - project:
      name: amazing-repo
      node: bare-trusty
          - gate-{name}-docs
  3. Now define how to trigger the job. Edit file zuul/layout.yaml and update your repository entry to add the job:

    - name: openstack/amazing-repo
        - name: merge-check
        - gate-amazing-repo-docs
        - gate-amazing-repo-docs

    This adds the job to both the check and gate queue. So, it will notonly be run when a patch is initially submitted for review in the check queue but also after a patch gets approved in the gate queue. Since your tree might be different when you submitted a change and when it merges, we run jobs in both situations so that the tree istested exactly as it merges.
  4. Let's go


This is a followup to my post  "Creating new test jobs in OpenStack CI". Last time I covered the basic setup of jobs by Jenkins and Zuul. Since many OpenStack projects run the same jobs, the Zuul developers have introduced templates to easily group and reuse these jobs.

Let's look at one common example, it's the python-jobs template. Like all examples in this article, it is defined in file zuul/layout.yaml in the openstack-infra/project-config repository and to use it, you need to edit the same file.

Defining your own templates

Since you now know how to use a template, let's explain how they really look like. A template consists of a name, definitions for which jobs should run in which queue and allows to substitute the name of the repository in the job, so {name} gets replaced by your repository, in the example by amazing-repo.

Let's look at the python-jobs template:

  - name: python-jobs
      - 'gate-{name}-pep8'
      - 'gate-{name}-docs'
      - 'gate-{name}-python27'
      - 'gate-{name}-docs'
      - 'gate-{name}-pep8'
      - 'gate-{name}-python27'
      - '{name}-branch-tarball'

The template has the name python-jobs, adds three jobs to the check queue and the same jobs also to the gate queue. An additional job is added to the post queue. Jobs in the check get queue get triggered when a change gets submitted, jobs in the gate queue get triggered when a change gets approved by a core reviewer and jobs in the post queue get triggered after a change has merged.
If you are adding the same class of jobs to several repositories, create a template for it. A template can contain of a single job that is associated with one queue, or contain several jobs in several queues like the example above.

Using a template

So, if your project amazing-project wants to reuse the python-jobs template as is, just add it as template:

  - name: openstack/amazing-repo
      - name: merge-check
      - name: python-jobs

You can also limit, on which branches those are jobs are triggered. For example, to run the docs job only on stable/liberty and newer branches, you can add a condition:

  - name: gate-amazing-project-docs
    branch: ^(?!stable/kilo).*$

So, instead of saying run on liberty and newer, we block it on older supported branches, in this case kilo is the only older supported branch.

If you're introducing jobs, best practice is to add them first to the experimental queue, and then add them as non-voting, and only finally as voting. In this case, the templates do not help you at all for the first two steps, you have to look at their definition and add them manually.

First step, using the jobs in the experimental queue:

  - name: openstack/amazing-repo
      - name: merge-check
      - name: noop-jobs
      - gate-amazing-repo-pep8
      - gate-amazing-repo-docs
      - gate-amazing-repo-python27

Note that we use noop-jobs as a template, so that both check and gate queue have at least one job. The noop jobs do nothing but are important since Zuul requires at least one job to run


Questions and preamble

As has become normal, the FOSS/Linux community is peppered with anxiety over yet another major change to the tech landscape issuing forth from Redmond. With the release of Windows 10 comes a great many questions for the thoughtful, and this is especially true for our very own Linux communities. With gratitude we can recall our own past relief upon discovering that UEFI and Secureboot are not the herald of the end-times we had feared them to be. That being so does not however relieve the question of safely upgrading our dual-booting computers to Windows 10 without losing our ability to run Linux in tandem.

Excitement for Windows 10 was largely absent in me. I had grown quickly comfortable to the Windows 8.1 work-flow as it shared some similarities in those key areas which I had already grown to love in the GNOME Shell. Further, Windows served a role limited to usage for proprietary software that I deemed not sensible to coax into service on a Linux OS. However it did make sense for me to upgrade for my employment as a repair technician. It seems incumbent on me to familiarize myself with the upgrade process and the general operation issues of Windows 10.

Can I perform the upgrade safely?

In short, yes. Performing an in-place upgrade of your present Windows operating system will not overwrite your Linux partitions. However, the necessary Boot Configuration Data settings directing the UEFI firmware to use GRUB for booting will be lost. The Windows Boot Manager will be reasserted. This can be changed from within Windows using bcdedit.

How about a fresh installation?

Some users prefer to make a clean installation of their operating systems instead of in-place upgrades. Unlike in older versions of Windows, you can direct Windows 8 and above to specific partitions. This means that whether you wish to install Windows first in sequence or not is inconsequential; you can now install Linux first without worrying about the Windows installer overwriting it. 

One minor caveat however is that if you are not using a computer with UEFI firmware instead of a BIOS, GRUB will need to be installed after the Windows installation. 

Can I still get the free Windows 10 upgrade even if I want to cleanly install it? 

Yes. However, you will need to initiate the in-place upgrade for Windows 10 in your already present qualifying Windows 7, or 8.1 installation. As +How-To Geek says in their article, "When you upgrade a Windows 7 or 8.1 system to Windows 10, the installer confirms that you have a “genuine Windows” system installed and activates your computer for use with Windows 10. Note that you don’t actually get a Windows 10 product key — instead, your computer’s hardware is registered with Microsoft’s servers. When you install Windows 10 on that PC again in the future, it will check in with Microsoft’s servers, confirm it’s installed on a registered PC, and automatically activate


The below is a response to a Facebook query on why we use openSUSE over Ubuntu. I was happy with how it turned out and thought it could prove helpful to a larger audience.

There are a great number of reasons why we use openSUSE. Ultimately, what one prefers boils down to personal taste. I'll tell you why I use openSUSE.

1) YaST:

YaST is our system administration tool. It can be used both in graphical environment and on the command line. YaST has modules for managing an enormous number of things, such as /etc/sysconfig configuration files and systemd processes to boot loader configuration and repository management. YaST provides comfortable, safe tools for working with important parts of the system that would otherwise be difficult, confusing, and potentially dangerous.

2) zypper:

Our package manager is called zypper. It has the most advanced dependency resolution available of any package manager whether it be Linux or another operating system. What this means is that it is trivial for us to perform complex installations and configurations that would be difficult or impossible elsewhere. In my experience with Ubuntu, I've had several instances where apt resolved a problem by removing X entirely, which broke the GUI system and was difficult to repair. In openSUSE, zypper prevents this sort of thing from happening.

3) Desktops; 

On openSUSE all Desktop Environments (such as Gnome, KDE, etc.) are treated equally, and can coexist on the same installation. Installing a new desktop environment is no more complex than installing any other package. Once they are installed, they can be selected from a dropdown on the login screen. Other distributions typically rely on 'spins' for delivering alternative desktop environments, such as Ubuntu Gnome. Part of why we can do this is that zypper has superior logic, and can handle this complexity better than other package managers.


The openSUSE community is famed for its responsive and competent forums. Rarely is a user left without a solution for more than a day. Competent professionals and developers answer user questions in the relevant forums. Our community is friendly and helpful.

5)KDE and Gnome; 

openSUSE is famed for having one of the most stable and well integrated KDE environments of any distribution. Less well known is our incredibly well done Gnome implementation as well, which is what I prefer and am always happy with the job our team does.

6) OBS; 

Our Open Build Service gives users and developers a common place to build and share their software with the entire community. OBS works in concert with our online software.opensuse.org portal to allow easy Direct Install (formerly One-Click) of any software built on OBS. Direct Install will automate the adding of repositories, resolution of dependencies, and installation of the software. This makes otherwise complex or time consuming tasks swift and trivial. It also allows for an ever expanding library of software, and the distribution of complex packaged solutions in the form of YaST meta-packages.


07 February, 2016

Michael Meeks: 2016-02-07 Sunday.

21:00 UTCmember

  • Up; read, NCC - did the teen work on the SOS bus with J. an interesting vehicle. With night-clubs dying left & right - will Newmarket still need it ?
  • Back for a fine roast lunch; slugged the afternoon away - quartet practice with small girls; Back to the Future II, stories & bed.

06 February, 2016

Michael Meeks: 2016-02-06 Saturday.

21:00 UTCmember

  • Up early; breakfast, poked at mail; did some project mgmt. pieces; pizza lunch - out for a walk; worked much of the afternoon in the lounge wit the family - worked late; prepared teen work for tomorrow.

Devices at our booth
After rocking SCALE, FOSDEM was next and a great event. Killing, too - two days with about 8000 people, it was insane. Lots of positive people again, loads of stuff we handed out so we ran out on Sunday morning - and cool devices at the ownCloud booth.


When we still had stickers and Jan still liked me
We had quite a team at the booth, with Frank Karlitschek, Philippe Hemmel, Jan-C Borghardt, Lukas Reschke and myself. Lukas visited his first FOSDEM and even though he started to complain a bit on Sunday about having had to many social interactions, he enjoyed it. Philippe was at his first ownCloud booth but has helped out at booths before so that went entirely smooth and Jan - well, he's so popular, people were nice to me a few times thinking I was Jan. I had to disappoint them, Jan was often to be found in the Design devroom where he gave a talk about how we do design at ownCloud (see also our earlier blog about 6 ownCloud User Interaction Design Principles).

Lukas and cameras don't go together well
My experience was the usual FOSDEM rush with so many people already there at 9:30 on Saturday (even though it is supposed to start at 10:00) that you barely have time to think, eat & drink or walk around and talk to old friends. I already had a long day on Friday as I went to a community statistics workshop by Bitergia but I'd even be tired after FOSDEM if I had a week to sleep in before...


Frank pushes press away ;-)
We had lots of stuff at the booth. Our usual stickers, flyers and some posters as well as my laptop where people could see ownCloud and sign up to our newsletter (80 new readers, yay). We also had some very cool devices, 2 prototypes from our friends at Western Digital and a spreed.me box, stay tuned as we have some cool news coming from there soon ;-)

Unfortunately, I hadn't brought enough stickers and flyers, we ran out in the morning of Sunday already, as Jan couldn't help but tell me over and over again. Yes, I brought over twice as much as last year but I guess I didn't factor in the growth in popularity of ownCloud... I'll double up again next year. Maybe triple.

It was great to talk to people about ownCloud, the devices, give them stickers and, in rare cases, explain what ownCloud is. Most people who walked by the booth already used ownCloud (yeah, techie crowd!) or are planning to, just one out of 10 has not heard of it. In general, my biggest regret at FOSDEM is that there are still people walking by whom we didn't manage to talk to. Perhaps more of those don't know the awesome that is ownCloud and are put off by the busyness at our booth

05 February, 2016

Michael Meeks: 2016-02-05 Friday.

21:00 UTCmember

  • Up earlyish, out for run with J. back, slugged and chatted. Sue arrived, then B&A, Anthony & Louise - out for a birthday celebration at Kings in town; picked up babes, home. Slept exhaustedly for a while on the sofa; tea, bed early etc.


Dear Tumbleweed users and hackers,

Last week I slacked and missed to post the review. I will cover both weeks now, covering the snapshots 0126, 0128, 0130 and the just to be released 0203. As you already see from the number of snapshots, we had a lower pace than we’re used to – it was 4 snapshots in 1 week, now it’s in 2 weeks. Reasons for that are mostly that OBS seems to have quite some trouble in churning packages. Despite there being a queue, a lot of workers were idle. On PPC64LE it even seems as if the queue is not getting any smaller at all.

So, what did those 4 snapshots bring us (are just about to bring us):

  • KDE Applications 15.12.1, as promised. It should be complete.
  • KDEPIM5 is now set as default in the patterns
  • Systemd 228 (in snapshot 0203). NOTE: we have seen some cases where the network intarfaces change between predictable and persistent names, notably when updating from 13.2 to TW. Be aware of this when updating.
  • The CD Images can be written to USB again and are bootable. The defective driver has been fixed.
  • PulseAudio 8.0

Quite some changes… and more currently living in stagings. The main points there being:

With all those exciting news I wish you happy hacking on the weekend!

04 February, 2016

Michael Meeks: 2016-02-04 Thursday.

21:00 UTCmember

  • Into Cambridge for quarterly mgmt meetings; good to meet everyone - interesting talks, filled out paperwork, etc. Out for dinner in the evening; bed late.


SUSE Linux Enterprise 12 Service Pack 1 was released today. It contains lots of software updates and features. For more information have a look at the release notes of our Server and Desktop version.

SUSE Linux Enterprise 12 SP1 templates

SUSE Studio supports the new SUSE Linux Enterprise release from day one. Just click on the Create appliance link after you log in and select the template you'd like to start with.

SUSE Linux Enterprise Desktop 12 SP1 GNOME

Testdriving SUSE Linux Enterprise 12 SP1 GNOME desktop

As always you can configure, build, testdrive and publish your appliance.

New Packages
SUSE Linux Enterprise 12 SP1 includes now OpenJDK 8. SLE12 was having only the version 7 of OpenJDK. The customers that needed higher version of Java did not have a solution. But don't worry if you still need the OpenJDK 7 packages! OpenJDK 8 was added as an alternative along with OpenJDK 7 so that customers that need it can still use it. They are still available handled by alternatives.

The latest version of SUSE Linux Enterprise 12 updates also PostegreSQL to Version 9.4 which introduces the new pg_update feature. The new pg_update feature simplifies and speeds up the migration to a new PostgreSQL version. For detailed information, please have look at our release notes.

Furthermore the Python script interpreter was updated to version 2.7.9. Main feature is a improved SSL module which has better security checking of X509 certificates used in SSL/TLS communication.

As usual you can upgrade previous SUSE Linux Enterprise versions to the new Service Pack 1. Just go to the start tab of your appliance and click the Upgrade button at the top bar.

Upgrade to SUSE Linux Enterprise 12 SP1 from SLES 12

Upgrade to SUSE Linux Enterprise 12 SP1

In case you are not satisfied with the upgrade you can also rollback to your old appliance version. Just click on Undo upgrade at the bottom of the appliance start tab.

Happy building :)

03 February, 2016

Michael Meeks: 2016-02-03 Wednesday.

21:00 UTCmember

  • Up lateish; mail chew, started on admin backlog - signed paperwork, poked at expenses etc. Built ESC stats.


I've been asked recently why ownCloud zipps its files instead of tarring them. .tar preserves file permissions, for one, and with tar.gz or tar.bz2 you have compression too.

Good question. Let me start by noting that we actually have both: zip and tar.bz2. But why zip?

A long time ago and far, far away

In the beginning, we used tar.bz2. As ownCloud gained Windows Server support, we added zip. Once we dropped Windows support, we could have killed the zip files. But we had reasons not to: tar is, sadly, not perfect.

Issues with Tar

You see, tar isn't a single format or a 'real' standard. If you have a platform other than plain, modern Linux, think BSD or Solaris, or the weird things you can find on NAS devices, tar files can get you in trouble. Unlike zip, tar files also can have issues with character format support or deep folders. We've had situations where upgrades went wrong and during debugging we found that moving to zip solved the problem miraculously... And, as ownCloud, we're squarely focused on the practical user experience so we keep zip, alongside tar.bz2.

See also the GNU tar manual if you want to know more about the various tar formats and limitations.

Sadly, sometimes it is impossible to find one thing that works for everyone and in every situation.

Tarred turtle pic from wikimedia, Creative Commons license. Yes, that's a different tar, I know. But - save the turtles!


The campaign is over; the votes are counted and three members of the openSUSE community will lead the overall project on the openSUSE Board.

Tomáš Chvátal, Gertjan Lettink, and Bryan Lunduke take the helm with the existing board members of Michal Hrušecký, Kostas Koudaras and chairman Richard Brown.

The new board members each bring different experiences and cultural backgrounds, which will no doubt provide for an exchange of ideas in fulfilling their role of representing the community and the project. The new members are from the Czech Republic, Netherlands and United States, respectively.

Manu Gupta and Efstathios Iosifidis, who ran in this year’s elections, received several votes. Both are great members of the community and will have a chance to run in next year’s elections.

Many thanks to the departing board members Andrew Wafaa, Robert Schweikert and Bruno Friedmann; your efforts and time on the board are valued.

The project can not exist without its members and board, which represent the community. The board helps to resolve conflicts, facilitates decision making processes when needed and communicates with the community and project stakeholders. And yes, like the picture above suggests, occasionally slap each other in the face.

Those who make the decision to volunteer their time and efforts toward representing the project are greatly appreciated. Thank you to all future, past and present board members. Congratulations.

Older blog entries ->