From Fedora Project Wiki


Fedora Weekly News Issue 219

Welcome to Fedora Weekly News Issue 219[1] for the week ending March 30, 2010. What follows are some highlights from this issue.

As there were no announcements during the past week, we kick this issue off with news from the Fedora Planet, including news on a new virtualization tool for resizing VM disks, details on a new Fedora Mini, to discuss Fedora on platforms such as Sugar, Moblin and Maeon (MeeGo), and thoughts on how to use Wikipedia better in the classroom. Ambassadors news brings us an event report from Open Fest 2010 in Athens, Greece. In Quality Assurance, details on this past week's Test Day on printing, and this week's two test days on SSSD implementation and ABRT, the automated bug report tool, as well as the first test compose for Fedora 13 beta, as well as many other great tidbits! In Artwork/Design Team news, details on a Fedora 13 countdown banner, details on preparing beta artwork, and a new icon set submission for F13. This week's issue wraps up with security advisories for Fedora 11, 12 and 13 released over the past week. Enjoy FWN!

We're also pleased to note the availability of Fedora Audio Weekly News (FAWN), an audio version in Ogg Vorbis format for a few past FWN issues that one of our contributors has begun. Find it on the Internet Archive[2] and have a listen!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback:

FWN Editorial Team: Pascal Calarco, Adam Williamson

Planet Fedora

In this section, we cover the highlights of Planet Fedora[1] - an aggregation of blogs from Fedora contributors worldwide. This edition covers highlights from the past three weeks.

Contributing Writer: Adam Batkin


Jan Wildeboer pointed out[1] that "IBM has chosen KVM via Red Hat Enterprise Virtualization to run their IBM Cloud", though it supports both RHEL and SuSE as guests.

Richard W.M. Jones released[2] a new tool, virt-resize to resize virtual machine disks and asked[3] "what features would you like to see?" for version 2.0? Rich also explained[4] how some of libguestfs and guestfish works.

Sebastian Dziallas announced[5] that there is now a Fedora Mini mailing list[6] to discuss Fedora on platforms such as Sugar and MeeGo.

The Red Hat JBoss team posted[7] an update on the status of JBoss Enterprise Middleware releases.

Justin O'Brien mentioned[8] that Paul W. Frields will be stepping down as Fedora Project Leader and that the election process will be coming up soon.

Luis Villa stepped[9] in to the mess of software patents and and their applicability to h264 and Ogg. "Let this be a friendly public service announcement: patent law says that anyone who uses a patent, not just the manufacturer or licensor of the patent-infringing good, can potentially be dragged into court on a charge of patent infringement." Luis followed-up[10] with some clarifications. "More patent lessons- first on submarine patents (basics!) and then on how patent pools are licensed. I don’t really want to continue this series, but the past few days have been a good reminder that there is a lot of misinformation out there around patents."

Casey Dahlin suggested[11] that instead of using talloc (see FWN Issue 218), libnih might be an even better alternative.

Karsten Wade wrote[12] about better ways to use Wikipedia in the classroom. "Where Wikipedia is a useful information source and starting place for deeper exploration beyond it’s reference-focused world, there is so much more that can be done with it to help teach the open source way. In fact, you can teach all of the basics of joining a collaborative free and open source software community without ever getting more technical than how to get an account and edit a wiki page."


In this section, we cover Fedora Ambassadors Project[1].

Contributing Writer: Larry Cafiero

Fedora at Open Fest 2010

Pierros Papadeas reports that last weekend Fedora attended Open Fest 2010 in Athens with a great booth and many people in attendance.

Fedora attracted many newcomers, especially with the Translation Marathon for Fedora 13 during the event.

On the wiki page you can find some blogposts-reports on the event and this nice gallery of photos from Fedora's presence there.

"We had a dual-projector setup with many swag, mostly produced by us, and some nice little ideas, like 'Try me!' signs," Pierros reported.

Pierros thanks all the Greek fellows, that helped Fedora be its best one more time.

Campus Ambassadors up and running

The Fedora Project's Campus Ambassadors program is up and running, and is looking for participants. If you're a high school or college student who wants to help promote Fedora on your campus, this is the place for you.

For more information, visit

Fedora 12 is here

With Fedora 12 Constantine now here, this is a reminder that posting an announcement of your event on Fedora Weekly News can help get the word out. Contact FWN Ambassador correspondent Larry Cafiero at lcafiero-AT-fedoraproject-DOT-org with announcements of upcoming events -- and don't forget to e-mail reports after the events as well.


In this section, we cover the activities of the QA team[1]. This week, we are trying out a new topic-focused layout, without the topic-by-topic weekly meeting recaps. Please let me know if you particularly like or dislike the new layout!

Contributing Writer: Adam Williamson

Test Days

Last week's Test Day[1] was on printing, including the implementation of automatic print driver installation[2]in Fedora 13. There was a disappointingly low turnout, despite Tim Waugh's extensive efforts to organize and promote the event. We theorize that printing works so well for most people that they didn't think it was necessary to turn up! Nevertheless, thanks to those who did come out to test, and reported five bugs for Tim to work on.

This week sees two Test Days. The first[3], on Tuesday 2010-03-30, will have passed by the time you read this; it will have been on the implementation of SSSD by default[4]. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. We'll bring you a report on this event next week.

The second[5] will be on ABRT[6], the automated bug report tool which has been included with Fedora by default since the release of Fedora 12. We'll be testing Fedora 13 enhancements to ABRT and making sure the system is working correctly for the upcoming Fedora 13 release. ABRT is important to all Fedora users and developers, so if you have a few minutes, please come along and help test! As usual, you can test with an installed Fedora 13 or Rawhide system, or a live image which is available on the Test Day page. Zdenek Prikryl, Jiri Moskovc and Adam Williamson will be on hand during the event, which will run all day on Thursday 2010-04-01 in the #fedora-test-day IRC channel.

If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[7].

Fedora 13 testing

The first test compose for Fedora 13 Beta was announced[1] by Rui He on 2010-03-23. The group helped to fill out the planned installation[2] and desktop[3] test matrices. Rui He provided a summary[4] of the TC test results. Shortly after the test compose, the first release candidate build followed[5] on 2010-03-26. Andre Robatino provided delta ISOs between TC1 and RC1[6]. Again, the group quickly filled out the desktop[7] and install[8] matrices. The testers found several blocker issues.

The third blocker bug review meeting for Fedora 13 Beta was held on 2010-03-26[9]. All outstanding Beta blocker bugs were reviewed, and developers were consulted on the remaining open bugs to ensure fixes should be available in time for the release candidate process to begin the following week.

'John H' reported[10] that the test candidate build failed to install correctly to an Intel X25-M SSD. James Laska suggested[11] he file a bug report on the issue.

Kamil Paral, Joachim Backes[12] and others found a bug[13] which prevented the boot process from completing successfully with the Plymouth graphical boot system enabled. The bug was later tracked down and resolved in a build which will be brought into the second Beta release candidate.

Update acceptance testing

During the weekly QA meeting[1], the group discussed the status of the various proposed changes and policies regarding updates. Adam Williamson summarized that "we need: a policy/sop for the 'proventesters' group, and a guide to providing updates-testing feedback for a) branched and b) stable releases, explaining what actually should be tested and how feedback should be given". Adam Miller provided[2] a second draft of the proventesters SOP proposal, and Adam Williamson posted a discussion of testing procedure[3] which posited that a policy for testing updates was impossible within the current Bodhi system, and the best way forward would be to revise the way Bodhi works. Mathieu Bridon pointed out[4] that Williamson's proposal was very similar to Doug Ledford's earlier proposal[5], and explained that the infrastructure team was already working Doug's ideas into their plans for 'Bodhi 2', the next major revision of Bodhi.

Target bug trackers

Following on from discussion the previous week, Adam Williamson posted a proposal[1] on the use of the Target bug trackers, suggesting either discontinuing their use or repurposing them to track bugs which did not constitute release blockers, but for which fixes would be accepted through release freezes. The thread turned into quite a wide-ranging discussion about freeze procedures and update acceptance. Later, Adam summarized by suggesting the key issue to decide is 'whether we want to have a time-defined stage' where only fixes for blockers and certain specifically chosen bugs would be accepted, and if a tracker bug is the most sensible way to keep track of those bugs[2].

Bugzapping in the classroom

Vedran Miletić asked the group[1] for advice and support on teaching Bugzapping in a university environment. Christopher Beland applauded the idea, and suggested Firefox, Evolution, Nautilus and Rhythmbox as good components for a class group to work on. Adam Williamson offered[2] to provide support and assistance.

rsync for test builds

Andre Robatino asked[1] if it would be possible to set up rsync access for the server on which test builds are stored, to make it easier to convert a DVD build into a multi-CD build for testing purposes. He then suggested[2] that zsync would serve the purpose even better. Adam Williamson pointed out[3] that zsync was still not packaged in Fedora due to a problem with bundled libraries.


In this section, we cover the Fedora Design Team[1].

Contributing Writer: Nicu Buculei

Counting Down to Fedora 13

Alexander Smirnov created[1] a complex and elaborate count-down banner for the upcoming Fedora 13 release "I upload sample image to wiki and concept in the form of animation to my fedorapeople space" and Máirín Duffy offered[2] a number of improvements in the text "f you have the rocket launching, maybe you don't need to say 'launched in', you can just say 'X days' so translators only need to translate 'days' and you don't have to worry about running out of space for the translation as much."

Preparing Beta Artwork

As John Poelstra reminded[1] about the upcoming schedule and deadlines, Nicu Buculei noticed[2] the team is behind it, and proposed to use the Alpha artwork in the Beta release "Considering we are way pas the deadline for finalizing the Beta wallpaper and very close to its package deadline, I propose that if we nobody propose an improvement in the next 24 hours, we go for Beta (and most likely final version) with Rocket Trails 2 that was already used for Alpha". Martin Sourada agreed[3] "I should like to add that the Alpha wallpaper is awesome albeit rather lowish resolution and is missing dual screen versions" and offered to package it "I'm ready to do the packaging work as soon as I have the necessary sources" while Paul Frields talked[4] possible future enhancements "If we want to take another stab at the wallpaper for post-Beta/GA, I know that Mairin Duffy had collected some constructive critiques." Kris Thomsen showed availability[5] to work on splashes, which are derivatives of the wallpaper "I can try to do the firstboot/anaconda banners".

New Mist Icons

Máirín Duffy submitted[1] an addition to the default Fedora icon theme "Lapo has created some new Mist icons very recently and was wondering if we could get them into F13" and Matthias Clasen pointed[2] to a small packaging problem "Mairin, these look indeed great. But we'll need at least the folder icons in the same sizes that they are present in the gnome icon theme, or things will look bad at different zoom levels in nautilus" which was quickly corrected[3]

Security Advisories

In this section, we cover Security Advisories from fedora-package-announce.

Contributing Writer: Pascal Calarco

Fedora 13 Security Advisories

Fedora 12 Security Advisories

Fedora 11 Security Advisories