Home Home
Sign up | Login

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

new osc feature to edit a request

January 30th, 2011 by

Hi,

I just pushed a new osc feature to git master which allows you to edit a submit action. Use case: suppose you review a request (which has at least one submit action) and you find a small typo (for instance in the spec file) but except the typo everything is fine. So instead of declining the request you can fix the typo, create a new request (which contains the fix + the original changes), accept the newly created request and supersede the original request (that’s basically what osc does behind the scenes).

Example:

# request with id 80 needs a small fix
marcus@linux:~> osc rq show 80 –edit
Request: #80

submit:       home:Admin/foo  -> home:foobar/dest
delete:       home:foobar/xxx

Message:
deletes package xxx and fixes dest.

State:   new        2011-01-30T15:04:03 Admin
Comment: <no comment>
A    /tmp/osc_editsrr2iDcI/test.spec
A    /tmp/osc_editsrr2iDcI/src.tar.bz2
At revision 1.
Checked out package ‘foo.home_Admin’ to /tmp/osc_editsrr2iDcI. Started a new shell (/bin/bash).
Please fix the package and close the shell afterwards.
marcus@linux:/tmp/osc_editsrr2iDcI> # fix it and commit changes
marcus@linux:/tmp/osc_editsrr2iDcI> exit
exit
Request: #None

submit:       home:Admin:branches:REQUEST_80/foo.home_Admin(cleanup) -> home:foobar/dest
delete:        home:foobar/xxx

Message:
<no message>
d(i)ff/(a)ccept/(b)uildstatus/(e)dit/(s)kip/(c)ancel > a -m “accepted request and applied small fix”
Supersede original request? (y|N) y
marcus@linux:~>

By the way you can also do it manually (osc rq clone <id>; osc co <clone project>; fix package(s) and commit changes; create a new request, accept it and supersede original request).

Tags:
Posted in Build Service | Comments Off on new osc feature to edit a request

Boo

January 28th, 2011 by

Arts, buffer, check, clutter, cobbler, colorblind, concurrent, convert, cook, crash, dialog, dump, expect, file, folks, fortune, genius, global, hello, indent, less, links, meanwhile, mirror, screen, sparse, suck, tree, units, words. What do these ordinary English words have in common? They are also names of software projects, which becomes a problem if you want to recognize package names in text. I understand that in the old days, the name of a command or application was only relevant in the context of the computer it ran on, and file names had to be short. Some of these names have allowed for a variety of jokes. But why, in the age of portable programs, WWW and search engines, can’t people come up with less ambiguous names? I mean, it’s not hard to join two words, or, at a minimum, prefix a word with a vowel, like, uhm, a round fruit does. 🙂

Oh, and did I mention that we have over 160 packages with a 2-3 letter name? The one mentioned in the title is a programming language, btw.

Tags: , ,
Posted in Hackweek | 2 Comments »

A heartly ‘Thank You’

January 27th, 2011 by

I would like to leave a very fond ‘Thank You’ to everyone who has placed their trust in me on the recent elections. The number of votes on me was a true surprise.

This election was probably one of the most important in openSUSE history, mainly to the fact that it’s the Board that is going to push the Foundation forward. I find the results very pleasing and I’m happy to see Henne and Peter moving up to help on those efforts.

Thank you all for an inspiring source of motivation.

Nelson

Posted in Uncategorized | Comments Off on A heartly ‘Thank You’

openSUSE KDE Team activity, Jan 2011

January 27th, 2011 by

What’s been going on in the openSUSE KDE team this week?  The news on everybody’s lips is that the KDE project released 4.6.0 yesterday.  Naturally, we’ve got it available for download for all current openSUSE releases as we prepare 4.6 for openSUSE 11.4.  4.6 brings better performance and improved power management control to the Plasma workspaces.  The KDE 4.6 application releases include features such as navigation capabilities in the Marble map app, more ways to search your files in Dolphin, and photo sharing via social networks.  KDE 4.6.0 is currently available in the KDE:Distro:Factory repositories.  A KDE:Release:46 repository will shortly be made available, providing the point releases in the KDE 4.6 series.

But that’s not all that we’ve been up to. Amarok 2.4.0 continues to help you rediscover your music, with better automatic playlists and removable device support.  We’ve packaged KOffice 2.3.1 including the realistic natural medium paint app, Krita.  KDevelop 4.2, also released today, is already on our mirrors.  C++ and PHP coders should check it out for its powerful code completion and refactoring support, augmented with better search and replace, improved Kate text editor, and QtHelp documentation support.  digiKam 1.8.0 leads the way in professional Free Software photo management.

The team continues to work to prepare openSUSE 11.4.  The openSUSE updater applet is being replaced by the more polished KPackageKit from KDE.  Our beta testers have already resolved several critical bugs before 4.6.0 was released, and is assessing PulseAudio and the range of Phonon sound system options for the best audio experience when 11.4 is released.  All dependencies on the old HAL system for hardware in KDE have now been replaced with udev, and have received a lot of testing.  KSynaptiks has been configured by default to allow touchpad taps, but disable the touchpad when typing.  And the team has been assiduously packaging new dependencies in KDE’s 4.6 releases so they are fully featured, including the Okteta hex editor plugin for KDevelop, the R backend for the Cantor math app, and the new speaker setup config module.

Artwork and branding for 11.4 is nearly complete, featuring the Celadon Stripes wallpaper by KDE’s Ivan Čukić .  The mysterious-looking upstream default wallpaper ‘Horos’ is also available – just install the package kdebase4-workspace-branding-upstream.  KDE’s Oxygen look and feel becomes possible in GTK apps by installing the new Oxygen GTK theme.  And a number of minor tweaks to the default KDE in a new installation of 11.4 add up to improved performance, for example by deferring starting services until they are needed.

If you want to join the fun or just need a helping hand, the expert and fanatical openSUSE KDE team can be found in #opensuse-kde on IRC, at opensuse-kde@opensuse.org or at http://en.opensuse.org/Portal:KDE.

Posted in Boosters, Distribution, Factory, KDE | 8 Comments »

Share your Kraft

January 25th, 2011 by

Its Hackweek number six at SUSE as you might have heard. Hackweek is great as employees are encouraged to work on a free software project they want. I work on my project Kraft and really appreciate the time that I can spend on it.

What I intend to do can be summarized with Share your Kraft. Up to now, Kraft is working fine for a single user. But what if a team wants to use Kraft and share number cycles (which are base for the document numbering like invoice number), documents and template catalogs? Well, as long as they share the same database, it might work (I didn’t test deeply) but if they happen to be on different locations it becomes difficult. I try to make that possible.

My development target for Kraft is simplicity. For the user of course, but also for the setup. The server to share data, which is obviously needed, must work on a cheap hosting offer, and it must work with a weak internet line. So a database connect via internet is not possible.

I decided to investigate in ownCloud and enhance it with a plug-in called KitoC. ownCloud is a project started by Frank Karlitschek and implements a handy but scalable WebDAV Server beside more. Seems to fit my needs perfectly. Yesterday I implemented the number server function in KitoC after good conversation with Cornelius at breakfast in the office. Not very much achieved yet, but had to learn a bit of ownCloud first. I keep you posted.

Tags: , ,
Posted in Boosters, Desktop, Hackweek, KDE | Comments Off on Share your Kraft

Oxygenise your Apache

January 24th, 2011 by

I have updated apache2-icons-oxygen with icons from KDE 4.6 RC2. Thanks Nuno & Co! Now Apache’s directory listings look a bit better 😉

See it in action here. If you want to download the tarball/rpm, go to the Build Service.

Posted in Apache, Artwork, KDE | 1 Comment »

Unity, Compiz and ATI…

January 22nd, 2011 by

I’ve finally added the Compiz packages to my development repository and unity itself alongside with some tools.

There are several bug reports on launchpad concerning ATI users, involving RADEON DRM driver and FireGL (fglrx) drivers. Unfortunately for me, I’m also a very happy ATI customer.

I’ve struggled yesterday with some ABI problems on compiz, this was mainly because I had git snapshots from different days, and updating and rebuilding it, really solved the issue.

Today I’ll be implementing the required patches for compiz by Ubuntu,, and hopefully this will enable me to test Unity, this time on a spare laptop with Intel Graphics chipset. I was hoping to pop some screenshots today, unfortunately, I’m having a couple of problems with Compiz that hopefully a couple of missing patches will solve.

I’ve left behind the ‘clutk’ package, as it’s currently broken and I need to take closer look into ‘glew’ and work it out. Something for monday/tuesday spare time.

For the time being, the only screenshot I have to show is the one of CCSM (compizconfig-settings-manager) with the Unity plugin.

Posted in Uncategorized | Comments Off on Unity, Compiz and ATI…

LibreOffice 3.3 rc4 available for openSUSE

January 21st, 2011 by

I’m happy to announce that LibreOffice 3.3 rc4 packages are available for openSUSE in the Build Service LibreOffice:Unstable project. They are based on the libreoffice-3.3.0.4 release. Please, look for more details about the openSUSE LibreOffice build on the wiki page.

The packages are based on LibreOffice release candidate sources. Though, they include some addons from the old Go-oo project.  They have not passed full QA round yet and might include even serious bugs. Therefore they are not intended for data-critical usage. A good practice is to archive any important data before an use, …

As usual, we kindly ask any interested beta testers to try the package and report bugs against the product LibreOffice .

Known bugs

  • some packages were not renamed, .e.g. OpenOffice_org-thesaurus, …; they are not built from the main LibO sources; I will do soon.
  • SLED10 build is not available; need more love

More known bugs

Other information and plans:

First, I am sorry that I did not announce two older builds. I published rc2 build just before Christmas and the announce was forgot in the hurry. There were problems with building rc3. It was ready only one day before rc4, so it did not make sense to announce it.

There still might be some openSUSE-specific bugs that would need to be fixed. I hope that they do not break the base function but… I will continue with producing newer builds with more fixes from the stable libreoffice-3-3 branch. I will move the packages to a stable project once we finish testing of all the SUSE-specific addons. It should happen within the next few weeks.

Please be patient and thanks for understanding.

Posted in Desktop, OpenOffice.org | Comments Off on LibreOffice 3.3 rc4 available for openSUSE

openQA is testing for you

January 20th, 2011 by

You might have read the announcement of the factory-tested repo (or not, because it did not go on planet.o.o). There have been many additions to the testing during the last eight weeks.

openQA.o.o is a machine running automated software tests all the time to decide if factory-tested can be updated. If you think, this was boring, you might find out that it is not, since every testrun generates a video of approx 4 minutes that can be conveniently viewed in firefox.

You can view those test results on the openQA page.

And those are the updates:

  • I have added testing of development repos, so that it is now possible to detect bugs before they even get into Factory (most of those tests have “devel” at the end of their name). In fact, this has already found two such bugs.
  • The test system’s hardware was upgraded with a sponsored SSD and the software adapted to allow running multiple tests in parallel (using make -j3)
  • I have updated the web-interface to use the nice Bento theme
  • And I found yet another cool use-case for automated testing: it allows to bisect bugs. I did a binary search in old results for a live-installer bug which made it really easy to find the causing commit. However, seeing how long such a bug went unnoticed, made me think, that it would be nice if more people would check the results for anomalies, since not all of those can easily be auto-detected. As this just needs a firefox and little time, this is pretty easy to do. Much easier than to actually setup a test-system in any case.
  • An IRC notification bot was added, keeping #opensuse-openqa updated with new test results
  • Then, I am looking for additional automatic test-scripts, that also work standalone on an openSUSE install. It is especially important to test high-impact things. Things that break often or block many users if they break. And it would be nice to have a small result range such as OK|fail|unknown or it should at least be mappable to such.
  • Jürgen Weigert has packaged sikuli, so it is easy to create GUI tests with it, that could then be included in the test-suite.

Then there are still some things on the ToDo list…

  • Hermes integration to get email alerts and RDF feeds for newsreaders
  • Have more test variants auto-scheduled (-live and -dup)
  • Find a way to have Add-On-Repos with custom priority (otherwise Factory packages might be used, as happened for kernel-default-2.6.37-rc7) – using linuxrc’s driverupdate feature could be one way.

your input is highly appreciated

Tags:
Posted in Factory, Quality Assurance | Comments Off on openQA is testing for you

Massive update on Ubuntu software…

January 20th, 2011 by

Screenshot using Radiance Light Theme and default Ubuntu indicator layout.

Some brief updates about the ongoing work towards bringing Ayatana Project software into openSUSE:

1. Software Updates

Canonical recently released a batch of updates which bring new functionality (Indicators seem to respond faster now) and very nice improvements, some of them contributed by down-streamers. From my humble experience I would risk to claim that Canonical is doing an excellent job as an upstreamer. I’ve updated all packages to the latest versions. This allowed to remove some patches.

2. Unity

Unity is now one step closer. For Unity I’ve started to package Compiz git snapshots from the correct branches pointed by Unity documentation. This brought something new to me, cmake. I’ve done this very slowly, reading some docs meanwhile about cmake. My packaging around Compiz is mainly based on OBS X11:Compiz repository, so pretty much all the credits should be for the original project Packagers which done an awesome job. Currently I’m missing only 3 packages to test Unity. Recently with kernel and mesa updates some issues around ATI hardware seem to have fixed for openSUSE Factory users, which enabled in my case FireGL, therefore I can test properly Unity now and check for the integration into openSUSE.

Unity by default uses the Ayatana’s Indicators, and if they are not present, it will fallback to GNOME’s applets. This is very nice and I’m thankful Canonical made it this way. This brings non-Ubuntu users the Unity experience at almost no trouble, since there isn’t actually much patching required to implement Unity.

3. GNOME:Ayatana Repository

GNOME:Ayatana Repository will be populated during the next two weeks with the latest changes and will provide for the time being the Ayatana’s Indicators and Unity. I am currently working around libappindicator stack and it’s Indicators. Currently I’m testing the patches required on the GTK+ stack and this is pretty much the last barrier before going into #STAGE2, polishing and populating GNOME:Ayatana.

It’s not decided yet what packages are going to present on Factory. My wish is to push only Unity into Factory and it’s dependencies, this might not happen for 11.4 as I’m not sure about the freeze schedules and it might be too late already, but since we’re depending on Compiz upstream, we’ll see what happens. Even if Unity isn’t going to be available on Factory, I’m sure we can use KIWI or SUSE Studio to release a small openSUSE Unity Spin.

I’ve also decided that I (typo: previously would) wouldn’t like to see Unity available by openSUSE before the official release from Ubuntu, for which I wish all the success.

Since the very early start that I’ve been using pkg-config as much as I can. According to some information that I collected previously, this would be great for cross-distribution build. Depending on the time and work done, I might make the necessary modifications and enable cross-distribution building on this project, thus, making it available for other RPM distributions supported by OBS. This will require a bit of testing before, so it will be work to be done after 11.4 is released and during it’s lifecycle. Maybe by the time of openSUSE 12 gets released, we will have this project also available for other RPM based distributions. I have no knowledge on Debian packaging, but Ubuntu ships this software and Debian probably has it also available so… that won’t be a problem.

4. Artwork

I am providing on GNOME:Ayatana Ubuntu’s Light Themes (Ambiance and Radiance) and offering a patched version of Metacity that renders those themes perfectly. I’m not changing the original colors from the themes or modifying them in any way. So they might be a bit more of orange and not green.

I’ve contacted some people to ask if they would be willing to donate some artwork to make a small package with Wallpapers, some have answered yes, so I will make a small package with a couple of wallpapers for the traditional resolutions and distribute it alongside with this software as optional as always.

5. GTK2, GTK3 and QT

Implementation of GTK3 will be done within the next days, as I am also considering enabling QT support for KDE users (Indicators only for now).

That’s pretty much the result of the last days of work… more news to come in the nearby future.

Tags: , , , , , , , , , , , , ,
Posted in Desktop, GNOME | 1 Comment »

« Older Entries
Newer Entries »