Cortito pero informativo. Se está por realizar el primer BarCampNEA este 25 de junio de 2011, en la UTN FRRe. ¿Qué es una Barcamp? ¿Quienes la organizan? RegistrateMás

Escritorio Junio 2011, a photo by muadib.ar on Flickr. Por ahora, paso a dejar una captura de escritorio. La disposición de las cosas está basada según esta captura, y por si a alguien le interesa dejo algunas características. SO: Archlinux – KDE SC 4.6 Plasma theme: Redo Fondo: EKUA Iconos: Faenza-jetpack Estilo de ventanas: N.7Más

Me gustaría anunciar el lanzamiento de openSUSE 11.4 Medical

La nueva distribución está disponible en:

*http://susegallery.com/a/UbPYJM/opensuse-medical-114

Sólo tienes que disfrutarla!

Muchas Gracias!

Saludos!

—

Rousinopoulos Athanasios-Ilias

— About Me–
https://zoumpis.wordpress.com
http://www.zoumpis.eu
http://en.opensuse.org/User:Zoumpis

This week was a good week for coding, and the best part about it: most of my changes are now in s-c’s upstream trunk.

I started out trying to populate s-c database with only a few applications; this meant updating the update-software-center tool, and also changing some bits on the database update module. I was glad to discover that some functionality I have planned to develop in week 6 (parsing AppStream app-data xmls) was already there, thus making my job easier

After that, work continued by abstracting backend parts, such as InstallBackend and TransactionsWatcher, and also isolating as much as posible apt and apt_pkg usage. I have then expanded the PackageInfo abstraction to implement a dictionary like interface, containing _Package objects (before that, apt.Package were returned). It took some small steps, and sometimes mistakes from my side, but in the end, I guess I have got it done right. Work still needs to be done regarding usage of candidate and installed properties (which currently are apt.Version objects), and also on AptCache try_install_and_*depends methods (this should be either abstracted, either made apt-backend specific.

At the end of the week, preparing the next point of focus, I have managed to get a developing environment with PackageKit with Python gobject introspection data. Here comes the bad news: the py GI for packagekit is not ready for prime time. Reasons for that: GI is relatively new, there are no other users of PK from Python (only C and Vala). With help from ximion, hughsie, dantti and tomeu (and many other kind souls on #PackageKit, #introspection or #python), we isolated the problem inside pygobject, apparently an incomplete implementation of GPtrArray. I hope to get it fixed next week , so that I can continue work with PK.

Although I am a bit worried seeing segfaults in Python, it’s a sunny day out here (so I can finish my report on a non-technical note) so I’m sure that with help from these awesome people on IRC,  problem will be solved, and my project will continue according to the plan.

Next week: gi ninja and more PK!

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.

This is my second report about my gsoc project, well what is new: This week I occupied my self with augeas, it is the first time I try to use and expand an already existing library and utility. Even thought Augeas is very well documented and the people in their community are very helpful, i had some problems combining my thoughts and ideas with the existing code, because i was trying to find out the best way to avoid code duplication etc. That was at least at the start, now at the end of the week I can say that I am more familiar with the Augeas API and this will certainly help me in the coming weeks.

As long as it concerns the actual merging procedure, i began coding an implementation i have thought. Unfortunately, the approach i used was not sufficient generalized to work with all the configuration files. Therefor i had, to erase most of the coding i did these days. However, from every negative thing comes a positive, in this case, I was able to find a better solution that rise some new problems, however i hope I will be able to find out an answer for them in the following days and implement the right code.

Finally, a merge tool command was added in augtool that is able to use the aug_merge command i added in the library, the particular command will accept a source and a dest tree/path and will then try to combine them according to the flags that i will add as enumeration. The final conclusion I must speed up things a bit cause there are unexpected problems that may occur at the implementation at any time.

Best Regards,
Christos

While starting to implement error resilience (not erasure resilience, which is already working nicely) in my RAID-lookalike multi-disk block device RAnsrID, I finally had to notice that I didn't understand one aspect of Galois Field mathematics - the Reed-Solomon representation type has heavy influence on how to deal with errors (read: corrupted data).

So far, I only understood the canonical matrix style representation (basically a linear combination over the data disks for each redundancy disk). Turns out that with polynomial representation you can create way better (read: faster) algorithms for error correction - according to my analysis, erasure and error recovery is O(N²), compared to O(N³) for erasure correction in the linear combination case, and unknown (presumably O(N³⋅M²)) in the error case (N: total number of disks, M: number of redundancy disks).

Thus I will rewrite the redundancy routines based on Phil Karn's Reed-Solomon implementation - the best implementation with an open license I could find. Most implementations (like in par2) don't bother with error correction, and use block-level checksums to detect errors. That done, erasure recovery can be used. Needless to say, this is no option for my block device (where and why should I store the checksums).

No need to say that this delays delivery timeframe of RAnsrID further; especially as I'd like to incorporate the change in an at least data preserving backwards compatible way.

Also Hackweek 6 wasn't as productive as I hoped; I only managed to get the test suite up and running. Oh well.

Hello out there,

I am very pleased to announce the new issue (177) of openSUSE Weekly
News in Greek. In this one you will read about:

* openSUSE renames OBS
* Bryen Yunashko: Ready…Set…Code!
* Andreas Jaeger: Factory Progress
* Matt Barringer: SUSE Gallery Desktop Client
* Christos Bountalis: A utility for merging configuration / sysconfig files – Week 1
Report

And of course many many interesting news about openSUSE, plus usefull
advice for making our lives easier.

Enough… read more at: own.opensuse.gr or at
http://el.opensuse.org/Weekly_news.

Looking forward to hearing your comments, advice and anything you would
like to read about at the next issue.

The openSUSE Weekly News is translated in the Greek language from issue #150. You can read older translated issues here: http://el.opensuse.org/Κατηγορία:Weekly_news_issues

Enjoy it!
Efstathios Agrapidis (efagra)

Hello out there,

I am very pleased to announce the new issue (176) of openSUSE Weekly
News in Greek. In this one you will read a lot about free (as in freedom) software conferences, either they have already been done, or they will be done in the direct future.
A little sample from the subjects:

* openSUSE Conference 2011 to be creative and open!
* Manu Gupta: My GSoC Project – SaX3
* Michal Hrušecký: LinuxTag 2011
* Will Stephenson: Have you BURPed yet today?
* Anastasios Ksouzafeiris: How to install Enlightenment (E17) in openSUSE 11.4

And of course many many interesting news about openSUSE, plus usefull
advice for making our lives easier.

Enough… read more at: own.opensuse.gr or at
http://el.opensuse.org/Weekly_news.

Looking forward to hearing your comments, advice and anything you would
like to read about at the next issue.

Enjoy it!
Efstathios Agrapidis (efagra)