Home Home > 2011 > 06
Sign up | Login

Archive for June, 2011

Facebook bans KDE’s photo uploader; all uploaded content inaccessible.

June 27th, 2011 by

So in my head there’s a little Walter Sobchak beating on my conscience and shouting “This is what you get when you trust Facebook with your data, Will”.
The reason is that I upload photos to Facebook using KDE’s shared uploader and this has fallen victim to the whims of FB’s purge of its app biosphere. Unless the original developer can convince them that the app is not spammy, offering a bad experience or having the wrong attitude, the app, my photos (all archived elsewhere of course), but most importantly, all the kind comments from my friends and contacts that represent FB’s only value, get sent to the farm.
This is what you get when you trust one company with stuff you care about. Will.

[gsoc] osc code cleanup – summary of week 5

June 26th, 2011 by

Hi,

here’s a small summary of the 5th (coding) week. I’ve spent most
of the time with the url-like argument parser (more information can be
found here and here). Additionally I cleaned up/reworked the
remote file classes (now we have: RORemoteFile and RWRemoteFile).
I also added an AbstractHTTPResponse and HTTPError class to the httprequest
module (the main purpose of the AbstractHTTPResponse is to encapsulate a
“concrete” http response (for instance it can be used as a wrapper around
urllib(2)’s addinfourl class)).
TODO for this week:

  • write a search module in order to find packages, projects, requests etc.
  • maybe we also need something like a source module (mainly to access the
    /source route)
  • think about working copy code cleanup/internal restructuring

Marcus

LibreOffice 3.3.3 bugfix release available for openSUSE

June 21st, 2011 by

I’m happy to announce LibreOffice 3.3.3 bugfix release for openSUSE. The packages are available in the Build Service LibreOffice:Stable project. They fix various crashers, usability and translation problems, see the libreoffice-3.3.3.1 release news for more details. See also some notes about openSUSE LibreOffice build.

The openSUSE LO team hopes that you will be happy with this release. Though, any software contains bugs and we kindly ask you to report bugs. It will help us to fix them in the future releases.

Other information and plans:

The bugfix release 3.3.4 is planed two months from now. Though, I would rather provide LO-3.4.2 packages instead.

I am already working on the LO-3.4 packages. They are more complicated because there were significant changes in the build stuff. You might expect something within the next few weeks in the LibreOffice:Unstable project.

1-2-3 Cloud

June 20th, 2011 by

Towards the end of last year there was an article in openSUSE news “announcing” the cloud efforts in the openSUSE project and on OBS. Well, cloud is still all the rage (see Jos’ contribution to openSUSE News issue 180) and people just cannot stop talking about cloud computing.

Using openSUSE as a host for your cloud infrastructure is also making great progress. We have 3 cloud projects in OBS and hopefully these cover your favorite cloud infrastructure code, Virtualization:Cloud:Eucalyptus, Virtualization:Cloud:OpenNebula, and Virtualization:Cloud:OpenStack. The projects provide repositories for Eucalyptus, OpenNebula, and OpenStack, respectively.

We attempt to make it relatively easy to get a cloud up and running. In this process OpenNebula and OpenStack have progressed the most. Eucalyptus is working, but due to an issue with Eucalyptus and openSSL 1.0 and later (the version in openSUSE) automation has to wait until these issues are resolved.

For OpenNebula we now have a KIWI example that shows how one can get a cloud setup from scratch in less than 2 hours, including the image build. The example contains a firstboot workflow for the head node, and self configuration of cloud nodes.

For OpenStack SUSE Gallery images are in the works and will be published in the near future.

All repositories provide packages you can install on running openSUSE systems. If you are interested in using openSUSE as the underlying OS for your cloud or if you want to contribute to the cloud projects, subscribe to the cloud mailing list opensuse-cloud@opensuse.org

[gsoc] osc code cleanup – summary of week 4

June 19th, 2011 by

Hi,

here’s a small summary of the 4th (coding) week. I spent most of the
time with writing the RemoteFile classes and the BuildResult class
(+ testcases of course:) ).

TODO for this week:

  • improve RemoteFile classes
  • add APIInfo class:
    - resolve url-like parameters (api://foo/bar repo/arch)
    - raise an exception if required parameters are missing
    - initialize optional parameters with the config default
    - encapsulate “context-sensitivity” logic (sometimes parameters
    should be read from the working copy (like apiurl, project or
    package))

Marcus

Aux armes citoyens! Et cetera

June 19th, 2011 by

This post is for the openSUSE Members!

Whatever your opinion, just vote

Freedom and Democracy

Well, I think I have to explain that french title…

Nah, let’s not bother and move on :D

Part of democracy is that if you don’t cast your ballot you have no influence! So don’t let others decide for you, when you can act!

Members, we need your vote!

We’re almost 500 members, and this message is for you.
Our freedom to choose our direction and control our project as we wish works only when we vote. As in real world democracies, not voting gets you nowhere.

So why this reminder?

Because : I want you to vote!

  • First you read the stategy document (it’s really quickly done)
  • Think about it (Well, you have 10 days left for that)
  • Take a decision : Can you support that strategy?

    1. If 50% of your neurons +1 agree : vote yes
    2. if not : vote no
    3. if you really don’t know : vote I don’t know/care.
  • Connect to connect.opensuse.org and cast your vote.

What we need here is to send a strong signal that 99% of our members are alive and care about our project.
Otherwise, why would we bothered to become members, and keep that status, if not to infuence?

Ideas

Why not add this signature to your mails you use on ML and/or forums?

The openSUSE Strategy, I've casted my vote! And you? http://bit.ly/iB2Dzh

When?

Oh come on, I really hope that you’ve acted before reading this line ;-)

Dead line is 29 June

Links related

[1] Aux armes citoyens : La Marseillaise
[2] etc the singing version by Serge Gainsbourg
[3] Cast your vote connect poll
[4] Article on news.o.o

ATI/AMD fglrx 8.861 Catalyst 11.6 available for openSUSE 11.2, 11.3, 11.4, Factory

June 17th, 2011 by

New version of catalyst 11.6 / fglrx 8.861 available

fglrx-8.861

Please refer to my previous article where all the installation procedure is explained.

  • Quick résumé :
  • There’s no full changelog about them, but Catalyst 11.6 installer (pdf)
  • Get the cheat-sheet 11.6 version
  • Kernel supported up to 3.0x version
  • Should be the latest version supporting 11.2
  • Wrong (to my point of view) create an xorg.conf file which is unneeded if you work with /etc/xorg.conf.d/50-device.conf and have driver "fglrx&quot inside

Warning

Some instabilities could happen. In case of crash like no keyboard, mouse, and blackscreen on reboot. Try to shutdown properly your computer with the shutdown poweroff button (or remote ssh). On reboot, just add 3 at the end of grub line to restart in console mode.
Then with yast or zypper you can always remove the actual version and try the previous version available in the repos.

All credits to Sebastian Siebert (freespacer) : 11.6 article (German)

What about tumbleweed, factory?

Users have reported that version 8.861 of catalyst 11.6 compile correctly under Tumbleweed with 2.6.39 kernel and the driver is ready for kernel 3.0x, so until xorg change too much and then AMD support for the new version, installing the 11.4 version should work

For factory, I’ve build a repository (see previous article) that can be used, and fglrx build.
The new package are called SUSE121 & no more SUSEFACTORY.

Stats Numbers ?

Month Unique IP Number of visits Pages Hits Bandwidth
Jan 2011 2355 6411 19688 35263 16.63 GB
Feb 2011 2906 7719 26383 41142 22.37 GB
Mar 2011 8055 21157 228494 258613 59.13 GB
Apr 2011 10592 29129 418281 437416 76.87 GB
May 2011 12511 36816 608350 626901 104.91 GB

All proudly served by openSUSE powered server! zypper dup from 11.2 to 11.4 in 45minutes last month

[gsoc] summary of week 3

June 10th, 2011 by

Hi,

here’s a small summary of the 3rd (coding) week. This week I spent
most of my time with developing the remote model classes. The goal
was to put most of the code into a base class from which all remote
models will be derived (if you’re interested how it works have a
look at it). So far we have classes for:

  • a remote project (RemoteProject – manages project metadata)
  • a remote package (RemotePackage – manages package metadata)
  • a request (Request)

TODO for this week:

  • add exception handling to the httprequest.py module
  • add a RemoteFile class which can be used to access a remote file
    like a buildlog, prjconf or a source file
  • add a BuildResult class:
    - get the build results for a project or package
    - get the buildlog of a package
    - get the binary/binaries from the api

Bee Keeping: Catch a Swarm

June 6th, 2011 by

Quite off topic, but for those of you who are interested in bee keeping as I am I for once like to share a video that we were able to create on a sunny sunday morning recently:

It shows the activity of catching a bee swarm that has been going out of the bee hive before. Swarming is natural behaviour of bees for reproduction. In early summer the bees create a new queen and as it is emerging, the old queen is swarming out of the hive looking for a new home. One form of the old and meaningful circle of reproduction.

A bee swarm is a very impressive event, the clip might give you an impression. And as our seven year old son was brave enough to take this movie, I thought it is worth sharing. Bee keeping is a family virus :-)

[gsoc] summary of week 2

June 3rd, 2011 by

Hi,

here’s a small summary of the 2nd (coding) week. This
week I spent most of my time with working on an OO-style class
for doing http requests:

  • it’s possible to switch the http(s) implementation without touching any
    library code
  • supports response validation (if a schema was specified for the request)

Currently I’m still working on the “remote models”:

  • decided to use lxml.objectify:
  • – goal is to encapsulate the xml logic solely into the object itself
  • – example workflow:
    prj = RemoteProject(‘some_name’)
    prj.title = ‘dummy’
    prj.description = ‘foo bar’
    repo = prj.add_repository(name=’openSUSE_Factory’)
    repo.add_path(project=’openSUSE:Factory’, repository=’standard’)
    repo.add_arch(‘i586′)
    # change arch to x86_64
    repo.arch[0] = ‘x86_64′
    repo.save()

Minor stuff:

  • decided to use the “logging” module:
    this way we can easily add “debug” and “info” etc. messages and it’s up to
    the “client” which messages it wants to display (I’m not talking about
    the messages which are displayed when “osc up” is called or something like
    that)