announcements beat is done
by Max Spevack
Sorry i missed last week -- w/ memorial day, i simply forgot. My
apologies.
14 years, 10 months
- 2
- 3
Stepping down from FWN for at least 6 months
by Oisin Feeley
Hi all,
I'm afraid that due to other pressures I'm not going to be able to
continue to reliably edit FWN or write the Development beat for FWN so
following next week (FWN 178) I'm going to call it quits for the
immediate future. I'd love to continue but it's just not possible in
terms of spare time.
I'll post to @fedora-devel to try and get someone to take on the beat.
Best wishes and thanks for the pleasure of working with you all,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
14 years, 10 months
- 6
- 7
qa beat done for 178
by Adam Williamson
qa beat is in for this week's issue. yaaaay, weekend!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 10 months
- 2
- 1
can't do virt beat this week
by Dale Bewley
This is a very busy week for me. I'm pretty certain I won't have time to
do the Virt FWN beat this weekend. I'll be back next week.
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
14 years, 10 months
- 2
- 1
Fedora Weekly News #177
by Oisin Feeley
Fedora Weekly News Issue 177
Welcome to Fedora Weekly News Issue 177[1] for the week ending May 24th,
2009.
This week we offer a special collector's edition with the last ever
Fedora Webcomic. PlanetFedora links Jeff Shelten's thoughts on "Why
Students Should Get Involved in Open Source", Ambassadors reports on
"Fedora en Mexico", Developments is getting "In a Flap Over Flags",
QualityAssurance takes a look at a "Mozilla/Beagle Blocker Bug
Proposal", Artwork says goodbye to itself but welcomes Design.
SecurityWeek examines the problems of "Cloudy Trust". Translations notes
that "Sections of the Fedora User Guide Cannot be Translated".
SecurityAdvisories includes an ipsec-tools update. Virtualization shares
details on the "Rawhide Virtualization Repository".
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[2]. We welcome reader feedback:
fedora-news-list(a)redhat.com
FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala
1. http://fedoraproject.org/wiki/FWN/Issue177
2. http://fedoraproject.org/wiki/NewsProject/Join
Table of Contents
1.1 Planet Fedora
+ 1.1.1 General
1.2 Ambassadors
+ 1.2.1 Fedora en Mexico
+ 1.2.2 Tips on Fedora 11 release events
+ 1.2.3 Announce your Fedora 11 events
1.3 QualityAssurance
+ 1.3.1 Test Days
+ 1.3.2 Weekly meetings
+ 1.3.3 Blocker bug review meeting
+ 1.3.4 Adobe Flash installation instructions
+ 1.3.5 Fedora 11 Common Bugs page
+ 1.3.6 Mozilla / Beagle blocker bug proposal
+ 1.3.7 New Bugzappers
1.4 Developments
+ 1.4.1 In a Flap Over Flags
+ 1.4.2 FESCo Election Questions
+ 1.4.3 Anaconda vs YUM Upgrades
+ 1.4.4 Broken Dependencies in Fedora 12 Development
+ 1.4.5 Too Many Conflicts
1.5 Artwork
+ 1.5.1 Goodbye Fedora-art, Welcome Fedora-design
+ 1.5.2 Statistics Poster
1.6 Fedora Weekly Webcomic
1.7 Security Week
+ 1.7.1 Cloudy Trust?
1.8 Translation
+ 1.8.1 New Translations for Fedora Websites
+ 1.8.2 Zero-day Changes Made to the Release Notes
+ 1.8.3 system-config-kdump Not Enabled for Submission
+ 1.8.4 Sections of the Fedora Users-Guide Cannot be
Translated
+ 1.8.5 SELinux User Guide Now Available for Translation
1.9 Security Advisories
+ 1.9.1 Fedora 10 Security Advisories
+ 1.9.2 Fedora 9 Security Advisories
1.10 Virtualization
+ 1.10.1 Fedora Virtualization List
# 1.10.1.1 Rawhide Virtualization Repository
# 1.10.1.2 No libguestfs on Fedora 10
# 1.10.1.3 New Release virt-inspector
+ 1.10.2 Fedora Xen List
# 1.10.2.1 Xen 3.4.0 Released
+ 1.10.3 Libvirt List
# 1.10.3.1 Libvirt VMWare ESX Driver In Development
== Planet Fedora ==
In this section, we cover the highlights of Planet Fedora[1] - an
aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
1. http://planet.fedoraproject.org
=== General ===
Michael DeHaan wrote[1] an essay "Recognizing and Avoiding Common Open
Source Community Pitfalls" such as that "contributors appear overnight
out of the woodwork, that users grow on trees, and that its possible to
direct community members as if they were employees."
Thorsten Leemhuis asked[2]: "What questions would you like to ask the
Fedora Board or FESCo Candidates?" for the upcoming Fedora Board and
FESCo elections. "Hence we need to prepare a few good questions that we
can send to the candidates once the nomination period ends. And that's
where I need *your help*"
Richard W.M. Jones announced[3] the first proper version of
virt-inspector, "a command line tool that tells you whats in a virtual
machine. You just point it at a disk image or a libvirt domain" and it
can discover a number of pieces of information about the installed VM.
Thomas Canniot posted[4] a How-To about running a successful release
event. "Fedora 11 is going to be released at the end of the month and
very soon, our massive army of ambassadors will want to spread how proud
they are of their Fedora 11 release to the masses."
Jef Spaleta calculated[5] new Fedora usage statistics that combined the
Smolt and MirrorManager logs to come up with some very interesting new
numbers.
Paul W. Frields responded[6] to the recent discussions about the new
fedora-devel moderation policy. "Theres simply no place in free
software, and certainly not in Fedora, for that kind of abuse. Of course
harsh words arent the end of the world. When we let them become the
noise that drowns out the signal, though, were putting the project at
risk. If contributors feel their time in community discussions are
wasted, they will either hold them elsewhere, or simply go away."
Jack Aboutboul interviewed[7] Lennart Poettering ("Red Hat Desktop Team
Engineer and resident audio guru") about Pulse Audio and audio in
Fedora.
Susan Lauber wrote[8] about "how can you - a Fedora contributor - assist
in making the wiki more useful for everyone?" For anyone wondering how
they can start contributing to Fedora, this is a great way to start,
without any long-term commitments.
Nicu Buceli reported[9] from eLiberatica 2009[10] in Bucharest, Romania.
Jeff Sheltren discussed[11] "Why Students should get Involved in Open
Source". Jeff says that "from my experience, open source experience has
given our student employees an enormous boost when looking for their
first jobs out of college."
Adam Williamson mentioned[12] the Common F11 bugs wiki page, and how you
can help: "Its really easy - everything you need to know to add an
issue to the Common Bugs page is right there in the page source, as a
comment. If you edit the page youll see a few chunks of comments which
explain how to add an issue (including a template entry), and what else
to do when adding one..." James Laska also suggested[13] that there are
still some high priority defects that could use some extra testing in
preparation for the imminent Fedora 11 release.
Thorsten Leemhuis explained[14] that "There is one small change in
Fedora 11 that I guess will confuse Fedora and RPM Fusion users with
x86-32 (aka i386/ix86) systems quite a lot, but afaics did not get
enough attention yet: By default, the PAE kernel will be used on 32-bit
hardware, where appropriate."
1. http://michaeldehaan.net/2009/05/17/oss-pitfalls/
2.
http://thorstenl.blogspot.com/2009/05/what-questions-would-you-like-to-as...
3. http://rwmj.wordpress.com/2009/05/19/virt-inspector/
4.
http://blog.mrtomlinux.org/index.php?post/HowTo-run-a-successful-IP
5. http://jspaleta.livejournal.com/42464.html
6. http://marilyn.frields.org:8080/~paul/wordpress/?p=1653
7. http://jaboutboul.blogspot.com/2009/05/sound-of-fedora-11.html
8.
http://travelingtrainer.laubersolutions.com/2009/05/revisiting-wiki-searc...
9. http://nicubunu.blogspot.com/2009/05/preamble-to-eliberatica.html
10. http://www.eliberatica.ro/2009/
11. http://sheltren.com/students_in_oss
12.
http://www.happyassassin.net/2009/05/22/fedora-11-common-bugs-page/
13. http://jlaska.livejournal.com/5561.html
14.
http://thorstenl.blogspot.com/2009/05/fedora-11-kernel-pae-and-what-it-me...
== Ambassadors ==
In this section, we cover Fedora Ambassadors Project[1].
Contributing Writer: Larry Cafiero
1. http://fedoraproject.org/wiki/Ambassadors
=== Fedora en Mexico ===
Alejandro Acosta recently presented the remixes workshop at the May
session of the local Linux User Group know as Gluch in Chihuahua,
Mexico. The reason is that many of the members of the Gluch could not
attend the workshop at Flisol since they where helping out in other
tasks.
Alejandro created a customized distro based on Fedora AKA Remix and then
tested it on a LiveUSB.
A report on the activities can be found here [1] and at the Fedora
Mexico Facebook page here [2].
In addition, Alejandro also gave a talk about Fedora to COPI (an
organization of college IT professionals) at their May 2009 meeting. A
report on the talk at COPI can be found here [3].
1.
http://alexacosta.wordpress.com/eventos/fedora-workshop-gluch-may-09/
2. http://www.facebook.com/pages/Fedora-Mexico/71816678729?ref=ts
3. http://alexacosta.wordpress.com/eventos/fedora-talk-copi-may-09/
=== Tips on Fedora 11 release events ===
Thomas Canniot posted a very helpful guide in his blog for those who are
holding events around the upcoming Fedora 11 release.
Thomas' blog can be found here [1].
1.
http://blog.mrtomlinux.org/index.php?post/HowTo-run-a-successful-IP
=== Announce your Fedora 11 events ===
With the upcoming release of Fedora 11, posting 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).
== QualityAssurance ==
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
1. http://fedoraproject.org/wiki/QA
=== Test Days ===
There was no Test Day last week, as we are deep in the Fedora 11 final
release run-up.
Currently, no Test Day is scheduled for next week - it is too close to
the scheduled release of Fedora 11 for any testing to produce results
directly in Fedora 11 final release, but if you would like to propose a
test day which could result in changes for post-release updates, or an
early test day for Fedora 12, please contact the QA team via email or
IRC.
=== Weekly meetings ===
The QA group weekly meeting[1] was held on 2009-05-20. The full log is
available[2]. Adam Williamson reported that he had filed a ticket to
have Bodhi use the appropriate resolution for bugs fixed with stable
release updates. Luke Macken said he would take care of the ticket. Adam
also reported that he had not yet remembered to ask the Bugzilla team to
add a link to the Fedora bug workflow page.
James Laska reported that he had not yet sent out a Test Day feedback
survey to previous participants, but had a draft ready and would
continue to work on it.
John Poelstra said that he had not yet finalized a schedule for blocker
bug reviews during the Fedora 12 cycle, as the overall Fedora 12 cycle
was still not finalized. He will revisit the issue next week.
Will Woods reported there had been little work on the autoqa project or
adding upgrade test cases to the Wiki during the week, as testing for
Fedora 11 release had taken priority.
The group discussed the Fedora 11 release situation, and noted that the
release had been pushed back one week. They examined the blocker bug
list, and found it was generally manageable. Francois Cami noted that
major fixes to X.org's core or the ATI driver were unlikely as Dave
Airlie is on vacation. The group noted that most remaining X.org
blockers were in the Intel driver, and assigned to
The group then discussed the Fedora 11 Common Bugs page[3]. Adam
Williamson volunteered to revise the existing page to match the format
used for previous releases, initiate a few other changes based on his
previous work on Mandriva Linux Errata pages, and talk to other groups
about the use of the page, including the Documentation group, and the
IRC, mailing list and forum support teams. Francois Cami volunteered to
help ensure all appropriate X.org issues are tracked on the page.
In open discussion, Francois Cami noted that for Fedora 11, users of
several generations of ATI Radeon cards would now only have the free
drivers as a viable choice, whereas previously they would be able to use
the ATI proprietary driver from third-party repositories. It was also
noted that, at release time, the commonly-used RPMFusion repository
would have no packages available for the proprietary driver even for
cards for which it is still available, due to the lack of a reliable
patch for kernel 2.6.29. The group discussed whether this could be
explained in the release notes (with no definite resolution, but advice
to check with the Documentation team), and how to note the requirements
for a full and useful bug report for problems with the free driver from
such users. Adam Williamson noted that the appropriate venue for such
information would be the Bugs and Feature Requests Wiki page[4].
The Bugzappers group weekly meeting[5] was held on 2009-05-19. The full
log is available[6]. John Poelstra reported on progress of the
housekeeping changes for Fedora 11's release, and the group agreed that
he was doing a fine job and should keep it up.
Adam Williamson reported on the progress of the triage metric system.
Brennan Ashton has again been busy (and without access to a regular
internet connection), so progress has been slow. Adam clarified that the
main choke point now was the lack of a set of test data for the scripts,
to ensure that they were working correctly, and explained he was doing
his best to get this data made available. Once it is available, work on
the system is no longer solely dependent on Brennan being available.
Adam Williamson also reported on the progress of the proposal to include
setting the priority / severity fields as part of triage. He had sent
out the mail asking for feedback on how to proceed, but had received
none yet. The group agreed that he should send out another mail as a new
thread, and set a deadline of the end of the week; if no significant
feedback to the contrary was received by that point, the group agreed
they should proceed using the method proposed by Matej Cepl.
The next QA weekly meeting will be held on 2009-05-27 at 1600 UTC in
#fedora-meeting, and the next Bugzappers weekly meeting on 2009-05-26 at
1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2. http://fedoraproject.org/wiki/QA/Meetings/20090520
3. http://fedoraproject.org/wiki/Common_F11_bugs
4. http://fedoraproject.org/wiki/BugsAndFeatureRequests
5. http://fedoraproject.org/wiki/BugZappers/Meetings
6.
http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-May-19
=== Blocker bug review meeting ===
John Poelstra announced[1] a joint QA / Release Engineering Fedora 11
blocker bug review meeting on Friday 2009-05-22. The meeting was not
logged, but all outstanding release blockers were reviewed, some were
closed or downgraded, and action plans were decided for several.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg00946.html
=== Adobe Flash installation instructions ===
Christopher Beland explained[1] that he had updated the Wiki page on
Flash[2] with the latest instructions on installing it on x86-64
systems. Adam Williamson noted[3] that the page should emphasize free
software alternatives as well as the proprietary Adobe Flash system.
Paul Frields announced[4] that he had made such a change.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01004.html
2. http://fedoraproject.org/wiki/Flash
3.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01006.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01027.html
=== Fedora 11 Common Bugs page ===
Adam Williamson announced[1] his revisions to the Fedora 11 Common Bugs
page, and asked the group to contribute to expanding and maintaining the
page and consistently refer to it when explaining problems. He also
explained some of the planned improvements to the content of the page
and its interaction with Bugzilla.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01026.html
=== Mozilla / Beagle blocker bug proposal ===
Jonathan Kamens asked[1] whether a bug preventing Beagle from searching
Mozilla Firefox and Thunderbird data should be a release blocker, on the
basis that desktop search is a key function for some users and web
browser and email data are important sets which someone may wish to
search. Brian Pepple pointed out[2] that it did not meet the official
release blocker criteria[3], but Jonathan responded that the page admits
this is a subjective judgment, and many bugs that do not strictly meet
those criteria are in fact considered blockers. In the end, it was
mostly agreed that, because Beagle is not installed by default and so is
not considered core functionality, the issue should not be considered a
blocker.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01041.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01042.html
3. http://fedoraproject.org/wiki/QA/ReleaseCriteria
=== New Bugzappers ===
Two new Bugzappers volunteers introduced themselves this week: Xia Shing
Zee[1] and Alex Turner[2].
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg00734.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01028.html
== Developments ==
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
=== In a Flap Over Flags ===
This week's "frank and open exchange of views" took the (non)inclusion
of country flags as its subject. A reminder was posted[1] by Kevin Fenzi
of a previous FESCo decision to split flags representing geopolitical or
ethnocultural concepts into separate subpackages. Tom Callaway posted[2]
the history of how he had come to draft the proposal and noted that the
inclusion of the Taiwan/Republic of China flag and possible consequences
to the distributability of Fedora in the P.R.C. were the initial
impetus. Upon request Josh Boyer provided[3] the relevant IRC log of the
2009-03-27 FESCo meeting.
Lots of discussion was had in several separate threads. FESCo was
criticized repeatedly for taking the decision.
When Project Leader Paul W. Frields was pressed to comment he replied[4]
that it was not his job to interfere with FESCo decisions of this sort
and that he agreed with David Woodhouse's take: namely, that while
disapproving of censorship, there was precedent for removing material
deemed likely to offend the sensibilities of some users.
Although Bill Nottingham thought that it was absurd Toshio Kuratomi and
Seth Vidal explored[5] some ideas about how YUM plugins and a new entry
in the Provides namespace might enable a technical solution.
Jesse Keating outlined[6] the advantages of a "no flags" policy in
gaining possible contributors from the PRC and also getting wider
exposure for software in RHEL.
Denis Leroy was a persistent critic of the decision and called[7] for
most of FESCo to resign.
Patrice Dumas kicked off[8] a fresh instance of the thread which recast
the discussion in terms of two separate issues: legality and giving
offense.
Christoph Wickert started[9] a fresh instance of the thread because:
"[t]he `Package Maintainers Flags policy" thread already counts more
than 225 mails, but nobody bothered to answer 7 simple (?) questions I
asked in my mail, although it was one of the very first three mails on
the topic. So what did I do wrong? Was it that I mentioned the missing
FESCo meeting minutes? If 8 out of 21 summaries are missing, IMHO this
is a fact worth mentioning. I'm one of the few maintainers who directly
is affected by the policy. Would somebody - preferably a FESCo member,
who voted for the flags proposal - please be so kind to answer my
questions. TIA!" Josh Boyer answered[10] pretty thoroughly. He included
the information that the policy would be revisited in the next meeting
and an explanation that the FESCo meeting summaries were incomplete due
to the failure of an attempt to rotate the onerous minute taking duties.
Bill Nottingham added[11] that the missing items should now be
available.
Yet a further thread was started[12] by Martin Sourada as a proposal to
create icon-themes as a long-term support solution.
The policy, as currently formulated is[13] posted on the wiki.
The 2009-05-22 FESCo meeting voted[14] to overturn the flag policy and
to start gathering information on the actual scope of the problem. Kevin
Kofler started[15] a thread to this end.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01403.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01427.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01670.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01480.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01550.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01582.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01661.html
8.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01557.html
9.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01740.html
10.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01743.html
11.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01892.html
12.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01910.html
13. http://fedoraproject.org/wiki/Package_Maintainers_Flags_Policy
14.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01869.html
15.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01895.html
=== FESCo Election Questions ===
John Stanley reminded[1] everyone that nominations for five FESCo seats
are open until 2009-05-29 for "[a]ny interested Fedora packager [...]
the only requirement is membership in the 'packager' group in FAS."
Given the rumblings over the geopolitical flags issue (and other signs
of discontent) it may be that this will be an interesting election.
The requirement to be a packager was a new one and raised[2] questions
from John Poelstra and Rahul Sundaram. Jesse Keating argued[3] that
FESCo was "[...] primarily concerned with the packages and distribution
release side of the house." This was disputed by several commenters who
referenced decisions made by FESCo which affected documentation, artwork
and internationalization.
John Rose wanted to know why the voting-pool was not the same as the
candidate-pool and Josh Boyer responded[4] that the issue should be
raised by filing a ticket with FESCo. Andreas Thiemann and John Rose
agreed[5] that there was a culture of meritocracy in the Fedora Project
and John Rose observed that: "The Fedora Board and FESCo and others
think of themselves as being part of a meritocracy (at least that is my
perception of what they think) but at the same time are trying to
encourage more widespread democratic participation which naturally runs
counter to perpetuating the meritocracy."
A subsequent 2009-05-22 FESCo meeting addressed the issue of restricting
its membership to packagers and ratified the current practice while
leaving open the door for further discussion if need be. The meeting
summary (posted[6] by Bill Nottingham) noted that no one who lacked
packager status had actually expressed interest in running.
Thorsten Leemhuis asked[7] for participation in preparing questions to
pose to the candidates once the nominations are closed.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01735.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01756.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01768.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01796.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01879.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01869.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01507.html
=== Anaconda vs YUM Upgrades ===
A brief thread initiated by David Timms explored[1] why it has been
easier to upgrade a system with anaconda rather than YUM. David
referenced a suggestion that: "anaconda is cheating (ie running --nodeps
installs). This would allow it to complete an upgrade where dependencies
lead to unavailable packages that are not on the dvd, but are in the
complete Fedora, and or non- fedora repositories, that are not available
at upgrade time."
Seth Vidal replied[2] that as anaconda was running outside of the system
experiencing the update it was free to use "--nodeps [without] a concern
for not being able to complete the transaction." Anaconda's ability to
use blacklists to exclude particular items from such transactions is now
available to preupgrade as a YUM plugin.
Jeremy Katz added[3] that: "It also means that we can do things like use
a newer version of rpm or a new kernel with ext4 support to (eventually)
allow for migrating from ext3->ext4[.]"
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01353.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01360.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01386.html
=== Broken Dependencies in Fedora 12 Development ===
Michael Schwendt posted three lists of broken dependencies in Fedora 12
development[1][2][3].
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01866.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01867.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01868.html
=== Too Many Conflicts ===
Michael Schwendt reminded[1] the list that packagers were ignoring
conflicts too readily.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01917.html
== Artwork ==
In this section, we cover the Fedora Artwork Project[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
=== Goodbye Fedora-art, Welcome Fedora-design ===
Máirín Duffy announced[1] a major rebranding: "we are going to rebrand
ourselves as the Fedora Design team rather than the Fedora Art team,
both in hopes of attracting more UX designers, and also since it's a
more accurate representation of the team so folks needing help with UI
design will know where to go." The change involves modification in the
mailing list, IRC channel, the Fedora Account System and awesome new
functionality, shared file storage "This means rather than painfully
uploading your work file-by-file to the wiki, you can just drag and drop
files in batches to the shared directory and link to the top level or
individual files from the wiki [...] This way, other folks on the design
team can collaborate and upload their improvements and remixes to the
same place so we don't have files for the same project all over the
place."
1.
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00171.html
=== Statistics Poster ===
Steven Moix asked[1] of @fedora-design about an updated statistic
poster[2] "Could someone have a look at the Statistics Poster to update
it to 4F standards and update it with recent statistics?", request
quickly accomplished[3]Paul Frields "It was very easy to do, thanks to
the way it was created -- whoever you are, thank you very much!" (as
discovered later[4], it was developed by Dimitris Glezos and Máirín
Duffy)
1.
http://lists.fedoraproject.org/pipermail/design-team/2009-May/000044.html
2. http://fedoraproject.org/wiki/Marketing_statistics_poster
3.
http://lists.fedoraproject.org/pipermail/design-team/2009-May/000048.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2009-May/000049.html
== Fedora Weekly Webcomic ==
Nicu's latest and last webcomic[1]
1. http://nicubunu.blogspot.com/search/label/webcomic
== Security Week ==
In this section, we highlight the security stories from the week in
Fedora.
Contributing Writer: JoshBressers
=== Cloudy Trust? ===
CIO.com has a nice article that points out some of the probably flaws in
cloud computing: Cloud Security: Danger (and Opportunity) Ahead. [1] In
theory, cloud computing is a fine idea that has the potential to lower
the cost of a CPU cycle dramatically. The thing nobody is really talking
about yet is keeping your data secure. Right now, it would be rather
unwise to presume that anything you send to the cloud won't be
compromised in some way. Securing a highly multi-user environment such
as this is going to pose a huge challenge. Problems nobody has even
though of are going to emerge, and will take a great deal of cooperation
and understanding to solve them. This is one of the places that Open
Source style collaboration will prove to be highly useful.
1.
http://www.cio.com/article/492999/Cloud_Security_Danger_and_Opportunity_A...
== Translation ==
This section covers the news surrounding the Fedora Translation (L10n)
Project[1].
Contributing Writer: Runa Bhattacharjee
1. http://fedoraproject.org/wiki/L10N
=== New Translations for Fedora Websites ===
Translations in Korean, Traditional Chinese, French, Japanese, and
Russian were added for the various Fedora-website pages for the first
time in Fedora 11[1].
1.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00104.html
=== Zero-day Changes Made to the Release Notes ===
Ruediger Landmann announced[1] the zero day updates to the F11 Release
Notes which in include all the issues reported by the Translation and
Documentation team.
Earlier, DomingoBecker reported[2] the lack of references about the
'5.2.1. Fingerprint Readers' section in the Fedora 11 Release Notes.
PaulFrields suggested[3] the addition of a link to a wiki page as the
reference with a mention of note for 'further information' and the note
could be easily translated by reusing translations from existing
sections.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00121.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00112.html
3.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00114.html
=== system-config-kdump Not Enabled for Submission ===
Kris Thomsen brought forward a problem[1] with the submission of the
system-config-kdump package via translate.fedoraproject.org. It was
later found[2] that the user account 'transif' used to submit
translations via translate.fedoraproject.org had not been granted
submission privileges for this module. This problem is currently in
process of being resolved.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00118.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00133.html
=== Sections of the Fedora Users-Guide Cannot be Translated ===
Daniel Cabrera reported[1] that some lines from the Fedora User Guide
are missing from the .pot file and as a result these lines remain
untranslated in the final document. This was caused while merging the
many disparate files generated by publican[2].
1.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00125.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00130.html
=== SELinux User Guide Now Available for Translation ===
Scott Radvan, writer of the Fedora SELinux User Guide, announced[1] the
availability of the document for translation. The disparate files have
been merged together into a single .pot file, which can be downloaded.
The translations for this document can be submitted via
translate.fedoraproject.org[2].
1.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00142.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-May/msg00148.html
== Security Advisories ==
In this section, we cover Security Advisories from
fedora-package-announce.
http://www.redhat.com/mailman/listinfo/fedora-package-announce
Contributing Writer: David Nalley
=== Fedora 10 Security Advisories ===
* ipsec-tools-0.7.2-1.fc10 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00746....
* nsd-3.2.2-2.fc10 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00847....
* memcached-1.2.8-1.fc10 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00851....
* quagga-0.99.12-1.fc10 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg01037....
=== Fedora 9 Security Advisories ===
* ipsec-tools-0.7.2-1.fc9 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00725....
* giflib-4.1.3-10.fc9 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00771....
* nsd-3.2.2-1.fc9 -
http://www.redhat.com/archives/fedora-package-announce/2009-May/msg00844....
== Virtualization ==
In this section, we cover discussion of Fedora virtualization
technologies on the @et-mgmnt-tools-list, @fedora-xen-list, and
@libvirt-list and lists.
Contributing Writer: Dale Bewley
=== Fedora Virtualization List ===
This section contains the discussion happening on the fedora-virt list.
==== Rawhide Virtualization Repository ====
Mark McLoughlin announced[1] the launce of the virt preview
repo(FWN#171[2]). "We've set up a repository for people running Fedora
11 who would like to test the rawhide/F12 virt packages. To use it, do
e.g."
$> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
[rawvirt]
name=Virtualization Rawhide for Fedora 11
baseurl=http://markmc.fedorapeople.org/virt-preview/f11/$basearch/
enabled=1
gpgcheck=0
EOF
$> yum update
Adding "this is very much a work-in-progress."
Mark McLoughlin decribed[3] the different types of users consuming these
packages:
* 1) Users who want things to stay stable and who aren't necessarily
expecting new features until they update to F-12 - these are people
with just the updates repo enabled
* 2) Same as (1) but who are willing to help out testing updates for
the whole distro in order to catch things before they hit the people
in category (1) - these people have the updates and updates-testing
repos enabled
* 3) Mostly the same as (1) or (2), but have a specific interest in
testing new virt features and are willing to deal with virt
regressions - these people enable the updates, updates-testing and
preview repos
* 4) People who are interested in helping with helping with F-12
development in general, not just virt - these people run rawhide
Daniel Berrange added[4] "The virt-preview repo is intended primarily as
an aid to testing / early experimentation. It is not intended for
'production' deployment."
1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00074.html
2.
http://fedoraproject.org/wiki/FWN/Issue171#Virtualization_Technology_Prev...
3. http://www.redhat.com/archives/fedora-virt/2009-May/msg00086.html
4. http://www.redhat.com/archives/fedora-virt/2009-May/msg00081.html
==== No libguestfs on Fedora 10 ====
Ján ONDREJ referenced[1] FWN[2] when asking if Richard Jones would
consider including qemu-0.10 into image:Echo-package-16px.pnglibguestfs
package to satisfy dependencies for Fedora 10.
Richard "had a go at backporting the changes to qemu that we ship in
F-10. qemu in F-10 is based on qemu 0.9, and doesn't include the
vmchannel patch." But "ended up with a qemu which compiled, but kept
segfaulting, and it was tricky to diagnose exactly why."
"Is it really a problem to use the libguestfs[3] and/or qemu[4] packages
from Fedora 11 builds? You can grab the latest builds out of Koji."
"This worked OK for me, although I have now moved to using Fedora
11-Preview, and have mostly abandoned Fedora 10."
Daniel B and Mark Mc concurred, Fedora 11 is the place to get libguestfs
.
1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00064.html
2.
http://fedoraproject.org/wiki/FWN/Issue175#libguestfs_on_non-Fedora_Platf...
3.
http://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=l...
4.
http://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=qemu
==== New Release virt-inspector ====
Richard Jones announced[1] "the first 'really working' version of
virt-inspector[2]."
"This is a tool based around libguestfs which can inspect a virtual
machine disk image and tell you some interesting things about what's
inside it."
Some of the things virt-inspector can tell you:
* What operating system(s) are installed, and what distros and
versions. It currently covers RHEL releases, Fedora releases, Debian
releases, and has limited support for Windows.
* How disk partitions are expected to be mounted (eg. /dev/sda1 ->
/boot)
* What applications are installed.
* What kernel(s) are installed.
* What kernel modules are installed.
1. http://www.redhat.com/archives/fedora-virt/2009-May/msg00073.html
2. http://git.et.redhat.com/?p=libguestfs.git;a=summary
=== Fedora Xen List ===
This section contains the discussion happening on the fedora-xen list.
==== Xen 3.4.0 Released ====
Pasi Kärkkäinen forwarded[1] an announcement from the Xen list.
"This release contains a number of important new features and updates
including:
* Device passthrough improvements, with particular emphasis on
support for client devices (further support is available as part of
the XCI project[2])
* RAS[3] features: cpu and memory offlining
* Power management - improved frequency/voltage controls and
deep-sleep support. Scheduler and timers optimised for peak power
savings.
* Support for the Viridian (Hyper-V) enlightenment interface
* Many other x86 and ia64 enhancements and fixes
Fedora 11 includes Xen version 3.3.1.
1. http://www.redhat.com/archives/fedora-xen/2009-May/msg00014.html
2. http://xenbits.xensource.com/xenclient/
3.
http://en.wikipedia.org/wiki/Reliability,_Availability_and_Serviceability
=== Libvirt List ===
This section contains the discussion happening on the libvir-list.
==== Libvirt VMWare ESX Driver In Development ====
Matthias Bolte announced[1] "a project of the Paderborn Center for
Parallel Computing"[2] having "a subgoal is to extend the driver base of
libvirt. We've started an VMware ESX driver and are investigating
Hyper-V support."
"The ESX driver isn't complete yet, currently it supports:"
* domain lookup by ID, UUID and name
* domain listing
* domain suspend and resume
* domain reboot, if the VMware tools are installed inside the domain
* domain start and shutdown
* domain migration
"We think this code might be useful for others and would be glad if the
driver could be merged into libvirt in medium term." Matthias was met
with enthusiasm from the core libvirt developers.
1. http://www.redhat.com/archives/libvir-list/2009-May/msg00431.html
2. http://pc2.uni-paderborn.de
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
14 years, 11 months
- 1
- 0
FWN 177 status
by Oisin Feeley
Hi all,
I've created the wikipage for #177 and added the following beats which
were marked complete:
Planet
QA
Developments
Artwork
Comic
SecurityWeek
I uploaded the Weekly Webcomic and stubbed-out the blurb for the
Welcome.
I see that Dale is hard at work on Virtualization ;-)
I am going to be out of the loop until late Monday again. I may be able
to snatch 20 minutes here and there throughout the day but nothing is
guaranteed.
Thanks everyone for this week's great content. Sorry to read that it's
the last comic Nicu :-(
Best,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
14 years, 11 months
- 3
- 3
Fwd: Re: Non English Podcast?
by Oisin Feeley
The message below is interesting. It turns out that Henrik is
translating FWN into German each week and podcasting it. I'd like to
link to his RadioTux show somewhere relatively prominent. Also does
anyone else know if there are other translations?
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
----- Original message -----
From: "wonderer" <wonderer4711(a)gmx.de>
To: "For discussions about marketing and expanding the Fedora user base"
<fedora-marketing-list(a)redhat.com>
Date: Thu, 21 May 2009 15:42:38 +0200
Subject: Re: Non English Podcast?
Hy,
>> I do the FWN in german, because I was asked to and nobody else stepped
>> in (maybe they know that it is a time-eating job if you are not an
>> Translation Expert and you work under a littel bit of pressure, because
>> the FWN come out monday and the RadioTux show is in thursday).
>>
>
> Hi Henrik,
>
> I had no idea you were doing this until I saw this post. Would you mind
> if we put a link to your work on the FWN wikipage?
>
I do this since the last 3-4 FWNs and have postet this on the german
list.
At this moment I "parked" those at http://wonderer.fedorapeople.org/ and
try to put them on the wiki (time will tell when I'm done with that ...
:-) ).
Feel free to link to it.
mit freundlichen Grüßen / best regards
Henrik Heigl - wonderer(a)fedoraproject.org
14 years, 11 months
- 1
- 0
QA beat done
by Adam Williamson
QA beat is in for FWN 177. weekend!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
14 years, 11 months
- 1
- 0
Fedora Weekly News 176
by Pascal Calarco
Welcome to Fedora Weekly News Issue 176[1] for the week ending May 17th,
2009.
In this week's content-rich issue, announcements brings us Fedora
Activity Day (FAD) updates from Maylasia and the upcoming Berlin and
Porto Alegre FUDCons, and several upcoming Fedora related eventsin
Romania and Brazil. A sampling of the Fedora Planet reveals changes in
IcedTea, Eclipse Linux Tools, detail on transitioning from rawhide to
Fedora 11, amongst other jewels. In QA news, details from the recent
iBus test days and many weekly meeting updates. In Developments, a
broken dependency brouhaha flavored the fedora-devel list this week
along with discussion of emacs add-ons for the Fedora Electronic Lab
spin, and details on being excellent to one another on the list. In
translation news, updates to Fedora 11 and news of inclusion of the
specspo package in the upcoming release. The artwork team muses about
wallpaper gallery developments and needs and final media art prep for
F11. Nicu's Fedora webcomic postulates on the F11 pre-release queue, and
we complete this week's melange with much news on the virtualization
front from the lib-virt list.
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[2]. We welcome reader feedback: fedora-news-list(a)redhat.com
FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala
1. ↑ http://fedoraproject.org/wiki/FWN/Issue176
2. ↑ http://fedoraproject.org/wiki/NewsProject/Join
-- Announcements --
In this section, we cover announcements from the Fedora Project[1] [2] [3].
Contributing Writer: Max Spevack
1. ↑ http://www.redhat.com/archives/fedora-announce-list/
2. ↑ http://www.redhat.com/archives/fedora-devel-announce/
3. ↑ https://fedoraproject.org/wiki/Events
--- Fedora 11 (Leonidas) ---
Oddly enough, there weren't any Fedora 11 announcements this week. The
schedule[1] continues to list Tuesday, May 26 as the release date.
1. ↑ https://fedoraproject.org/wiki/Releases/11/Schedule
--- Fedora 12 (Rawhide) ---
The KDE Special Interest Group[1] has begun the process of bringing KDE
4.3-beta1 into Fedora 12's Rawhide[2].
1. ↑ https://fedoraproject.org/wiki/SIGs/KDE
2. ↑
http://www.redhat.com/archives/fedora-devel-announce/2009-May/msg00008.html
--- Bugzilla ---
Some housekeeping in Bugzilla will take place[1] following the Fedora 11
release. All Rawhide bugs will automatically be changed to Fedora 11 --
because the Rawhide under which those bugs will followed will have also
changed into Fedora 11. Secondly, all Fedora 9 bugs will automatically
receive a notice stating that there is only one month of support
remaining for that release.
1. ↑
http://www.redhat.com/archives/fedora-devel-announce/2009-May/msg00007.html
--- FUDCons and FADs ---
This section previews upcoming Fedora Users & Developers Conferences, as
well as upcoming Fedora Activity Days.
-- Fedora Activity Day Malaysia
Planning is underway for a Fedora Activity Day[1] in Malaysia at the end
of May, contingent upon gathering together sufficient Fedora
contributors to make such an event worthwhile. If you are in the area
and are interested in attending or have some ideas on projects that
could be worked on, see the wiki page[2] for more information.
1. ↑ https://fedoraproject.org/wiki/FAD
2. ↑ https://fedoraproject.org/wiki/FAD_Malaysia_May_2009
--- FUDCon Porto Alegre 2009 ---
FUDCon Porto Alegre[1] will take place June 24-27 in Brazil. About 30
people have signed up so far, and we're hopeful for an attendance of
over 100.
If you would like more information, and to sign up, please visit the
wiki page.
1. ↑ https://fedoraproject.org/wiki/FUDCon:LATAM_2009
--- FUDCon Berlin 2009 ---
FUDCon Berlin[1] will be held from June 26-28, and we're getting close
to crossing the 100-person-preregistered mark.
Don't forget to pre-register[2] for the event, and also to sign up for
lodging[3] if you need it.
1. ↑ https://fedoraproject.org/wiki/FUDCon:Berlin_2009
2. ↑ https://fedoraproject.org/wiki/FUDCon:Berlin_2009_attendees
3. ↑ https://fedoraproject.org/wiki/FUDCon:Berlin_2009_lodging
--- Upcoming Events ---
Consider attending or volunteering at an event near you!
May 22-23: eLiberatica[1] in Bucharest, Romania.
May 29-30: III ENSL e IV FSLBA[2] in Salvador, Brazil.
1. ↑ http://www.eliberatica.ro/2009/
2. ↑ https://wiki.softwarelivre.org/Festival4
-- Planet Fedora --
In this section, we cover the highlights of Planet Fedora[1] - an
aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
1. ↑ http://planet.fedoraproject.org
--- General ---
Deepak Bhole joined the blogging world (welcome!) by explaining[1]
changes that the IcedTea Java web browser Plugin will be undergoing in
order to continue functioning after some ancient APIs (LiveConnect and
OJI) are removed from Gecko (Mozilla-based projects) in the coming months.
Eclipse Linux Tools has released version 0.2 of their Eclipse plugin,
and Andrew Overholt described[2] some of the new features along with the
requisite eye candy.
Dracut is a new tool, designed to generate an initramfs and replace all
of the different methods currently employed by various distros. Harald
Hoyer appealed[3] for anyone interested in helping contribute, noting
that it is one of the Features slated for Fedora 12.
Paul W. Frields linked[4] to a fedora-devel post by Jesse Keating
explaining how to configure a system to ensure that a Fedora 11
pre-release properly transitions onto the stable Fedora 11 repositories
once it has been released (or how to stay on rawhide if that is your plan).
Jesse Keating was interviewed[5] for a podcast, about the upcoming
Fedora 11 release. Jesse also announced[6] some discussions that the
Fedora Advisory Board has had about the hostility that sometimes
surfaces on the fedora-devel list and ways that it might be dealt with.
"This is the "warning shot". Our hopes is that folks will start to
figure out what is and is not allowed to happen on the list and things
will tone down a bit".
Adam Williamson noted[7] a number of reasons that there can never be a
common Linux Package format, but suggested that "what others want is
something that would actually be achievable, which is a unified system
to make it easier for third parties to independently provide
self-contained software packages for various distributions...If you want
to do it really snazzily, though, what you want to do is design the App
Store for Linux, or Steam for Linux, or something like that." Jesse
Keating responded[8] that a potential complication might be "that user
buy in is going to be hard when you take a software platform (such as
RHEL or Fedora) that uses one tool to manage updates for the entirety of
your software set (yum, PackageKit, whatever frontend) and suddenly add
one or more tools to specifically manage one or two software bundles".
1. ↑
http://dbhole.wordpress.com/2009/05/11/the-future-of-icedtea-plugin/
2. ↑ http://overholt.ca/wp/?p=130
3. ↑ http://www.harald-hoyer.de/personal/blog/dracut
4. ↑ http://marilyn.frields.org:8080/~paul/wordpress/?p=1631
5. ↑ http://jkeating.livejournal.com/69319.html
6. ↑ http://jkeating.livejournal.com/69477.html
7. ↑ http://www.happyassassin.net/2009/05/15/packaging-standards-again/
8. ↑ http://jkeating.livejournal.com/69726.html
--- Events ---
Event reports and photos of FOSSComm in Greece by Dimitris Glezos[1] and
Pierros Papadeas[2].
Anirudh Singh Shekhawat posted[3] photos[4] and descriptions of the
setup for FOSJAM in India (which included the setup of Fedora 10 on 80
machines!).
Máirín Duffy attended an ACM SIGCHI panel on "User Experience in Open
Source" and posted[5] detailed notes on the topic.
1. ↑ http://dimitris.glezos.com/weblog/2009/05/12/fosscomm-recap-2
2. ↑ http://pierros.papadeas.gr/?p=24
3. ↑ http://acedip.blogspot.com/2009/05/countdown-to-fosjam-day-0.html
4. ↑ http://acedip.blogspot.com/2009/05/preparing-for-fosjam.html
5. ↑
http://mairin.wordpress.com/2009/05/14/notes-on-the-user-experience-in-op...
-- QualityAssurance --
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
1. ↑ http://fedoraproject.org/wiki/QA
--- Test Days ---
This week's Test Day[1] was on iBus[2], the new default input method
framework for Asian languages in Fedora 11. Over 15 people came out to
test and report their results, and overall the new system seemed to be
working solidly, but testing revealed several issues for the developers
to work on. Thanks to all who came out for the Test Day.
Currently, no Test Day is scheduled for next week - it is too close to
the scheduled release of Fedora 11 for any testing to produce results
directly in Fedora 11 final release, but if you would like to propose a
test day which could result in changes for post-release updates, or an
early test day for Fedora 12, please contact the QA team via email or IRC.
1. ↑ https://fedoraproject.org/wiki/Test_Day:2009-05-14_iBus
2. ↑ https://fedoraproject.org/wiki/Features/IBus
--- Weekly Meetings ---
The QA group weekly meeting[1] was held on 2009-05-13. The full log is
available[2]. Will Woods reported that he had been doing a lot of
upgrade tests, but had not had time to write them up formally as test
cases as was planned at the previous meeting.
Adam Williamson reported that he had completed the revision of the
Fedora bug workflow page[3] to include the alternative processes agreed
for closing bugs in Rawhide at the previous meeting, and had made
further changes. He directed the group to his announcement email[4] for
further details.
Will Woods reported there had been little work on the autoqa project
during the week, as testing for Fedora 11 release had taken priority.
The group discussed how to get feedback on the conduct of Test Days
themselves, rather than on the software being tested. Adam Williamson
suggested adding a 'suggestion box' to the normal layout for Test Day
wiki pages. Jóhann Guðmundsson suggested an email to the
fedora-test-list mailing list. James Laska wanted to get in touch with
the maintainers who had been involved with Fedora 11 Test Days for their
suggestions; Adam Williamson thought it better to simply contact them
via email then attempt to set up some kind of survey system.
The group then discussed the Fedora 11 release situation. James Laska
explained that Jesse Keating had already led a complete review of all
outstanding blocker bugs for the release, trimming the list from over 70
to under 40 by downgrading the priority of some issues, and closing some
which had already been addressed, after testing. Jesse thought the
planned schedule for a second round of reviews was too late, and decided
that it should happen on 2009-05-18. The group agreed that the handling
of the final stages of release had not been optimal for F11, and for F12
the group should endeavour to get the blocker bug review done earlier in
order to be ready for the release candidate phase, and that it would be
useful to hold more blocker review meetings earlier in the cycle overall.
The group then discussed the release candidate phase (note that release
candidate builds are generally not widely distributed beyond the QA
group, for reasons of timing and available resources). James Laska
explained that he planned to create an installation test matrix, with
'how to test' documentation. Will Woods and Jesse Keating were already
working on smoke testing early pre-RC builds. Adam Williamson suggested
sending an email to fedora-test-list to remind members that now is an
ideal time to be testing installation from Rawhide.
Jóhann Guðmundsson raised the issue of the lack of clarity regarding
Fedora's target user base, which Adam Williamson had mentioned in
discussions on fedora-devel-list. Jesse Keating mentioned that the issue
was already under active discussion by the board. After a long
discussion, the group all agreed that the QA group did not need to have
an opinion on what type of user Fedora should be targetting, but should
make it clear to the board that the lack of a clear definition of this
issue was actively affecting the ability of the QA group to work
effectively, and QA work would benefit immediately from a clear
resolution of this issue, whatever the resolution may be.
Jóhann Guðmundsson asked about progress on Jesse Keating's proposal to
drop the Alpha milestone for the Fedora 12 release cycle. Jesse reported
the proposal had been approved by the Release Engineering group and then
by FESCo.
The Bugzappers group weekly meeting[5] was held on 2009-05-12. The full
log is available[6]. John Poelstra reported that the planned email to
fedora-devel-announce about the housekeeping changes in Bugzilla for
Fedora 11 release was ready, and asked for feedback. The group agreed
the email looked fine except for talking about Fedora 12 instead of
Fedora 11. John promised to fix this and then send out the email.
The group briefly discussed the query used to find bugs filed on Rawhide
to be changed to Fedora 11, and mostly agreed that it looked fine.
Adam Williamson reported on the progress of the triage metric system.
Brennan Ashton had been very busy during the week and hence difficult to
get hold of. He reported that the Python development group was waiting
for Brennan to provide test data for them to confirm their proposed
fixes to the code were correct, and he was trying to get Brennan to
provide this data.
Adam Williamson also reported on the progress of the proposal to include
setting the priority / severity fields as part of triage. The request
for feedback on fedora-devel-list had produced little response; Adam
suggested this wasn't a problem, as the main point was to make sure no
developers were actively opposed to the proposal for good reasons. The
group agreed that Adam would send a mail to the list to move the process
along with a view to starting work on priority / severity as part of the
initial triage process soon.
Edward Kirk revived the proposal to create a
000-Not-Sure-What-Component-To-File-Against component to catch bug
reports when the reporter was not sure what the component should be.
Adam Williamson pointed out the potential drawback to the proposal was
that it would encourage reporters not to bother selecting the correct
component for their report, thus needlessly increasing the load on the
triagers. The group agreed that the current small number of bugs filed
against the 0xFFFF component which currently occupies the first spot in
the components list indicated this was not a problem worth making an
active effort to address, and further agreed to work on correctly
assigning all bugs currently filed against 0xFFFF.
The next QA weekly meeting will be held on 2009-05-20 at 1600 UTC in
#fedora-meeting, and the next Bugzappers weekly meeting on 2009-05-19 at
1500 UTC in #fedora-meeting.
1. ↑ http://fedoraproject.org/wiki/QA/Meetings
2. ↑ http://fedoraproject.org/wiki/QA/Meetings/20090513
3. ↑ http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
4. ↑
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg01034.html
5. ↑ http://fedoraproject.org/wiki/BugZappers/Meetings
6. ↑
http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-May-12
--- Upcoming Bugzilla Changes ---
John Poelstra announced[1] that the regular housekeeping changes to
Bugzilla for a new release would be happening on 2009-05-26, with all
bugs filed on Rawhide being changed to Fedora 11, and a comment left on
bugs filed on Fedora 9 that they must be moved to a later release if
confirmed still to be valid, or else they will be closed as WONTFIX.
1. ↑
http://www.redhat.com/archives/fedora-test-list/2009-May/msg00560.html
--- Bugzappers New Member SOP ---
Adam Williamson reported[1] that he had revised the new members SOP[2]
to be clearer and more explicit, and the page explaining how to join the
Bugzappers group[3] to fully explain the revised process, including the
self-introduction email.
1. ↑
http://www.redhat.com/archives/fedora-test-list/2009-May/msg00673.html
2. ↑ http://fedoraproject.org/wiki/BugZappers/sop_new_member
3. ↑ http://fedoraproject.org/wiki/BugZappers/Joining
--- Priority / Severity Process ---
Adam Williamson followed up[1] on the priority / severity proposal,
explaining that no significant negative feedback had been received from
the development group, and asking for votes on which method for setting
these fields the group should proceed with.
1. ↑
http://www.redhat.com/archives/fedora-test-list/2009-May/msg00674.html
-- Developments --
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
--- Broken Dependency Brouhaha ---
The deliberate introduction of a broken dependency by Richard W.M. Jones
resulted prolonged discussion and two FESCo discussion items tabled for
the 2009-05-15 meeting. One of those items was the possible removal of
"provenpackager" status from Richard.
Michael Schwendt noticed[1] that an update for libguestfs[2][3] had been
pushed by developer Richard W.M. Jones in the full knowledge that Fedora
10 users would need to import a Fedora 11 qemu package. An anonymous
comment on Bodhi situated the decision to release the update as an
example of Richard not respecting the release process. Richard argued[4]
that as the libguestfs package was completely new only those aware of
what they were doing would install it (and consequently would be aware
that they needed the qemu from Rawhide or Fedora 11.)
A strong reaction against "[c]reating broken deps when you know they
won't be corrected[...]" ensued[5] and led[6] to Seth Vidal deciding to
question Richard's suitability as a "provenpackager" on the basis that
he lacked common sense.
A sidethread on the advantages of introducing dependency-checking was
started by drago01. While Josh Boyer agreed[7] that it would be useful
he asked for help in solving the difficult problems which he listed.
The first of the 2009-05-15 FESCo meeting items resolved[8] that Toshio
Kuratomi and Richard W.M. Jones should draft a Packaging Guideline which
prohibited introducing broken dependencies and submit it for approval by
the Fedora Packaging Committee. For the second related meeting item it
was decided that as Richard's introduction of a broken dependency was
made in the absence of a clear prohibition against such actions, and as
he was clear that it would not recur, then no sanction should be taken.
The handling of similar requests to remove "provenpackager" status in
the future were agreed to be best handled on a case-by-case basis.
Richard added[9] that the necessary back-porting of changes to qemu in
Fedora 10 were going to happen. Currently the update has been revoked.
1. ↑ https://admin.fedoraproject.org/updates/F10/FEDORA-2009-4696
2. ↑ This exciting library's ability to perform modifications within
virtual machine images without the need to actually run those images has
been covered previously in the FWN virtualization beat
3. ↑
http://fedoraproject.org/wiki/FWN/Issue175#libguestfs_on_non-Fedora_Platf...
4. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01084.html
5. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01094.html
6. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01130.html
7. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01111.html
8. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01320.html
9. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01087.html
--- Verilog Emacs Add-Ons ---
The prime mover behind the Fedora Electronic Lab Spin, Chitlesh Goorah,
asked[1] for feedback on splitting-out "verilog-mode" into a separate
package so that upstream changes could be tracked more rapidly. This
would also have the benefit of laying the groundwork to support OVM and
VMM (see FWN#161[2]).
Jonathan Underwood made[3] some good points concerning the danger of
missing out on emacs trunk integration of such packages if they were
split out. He suggested instead: "[...] a packaging strategy whereby we
don't rip out verilog-mode from the core emacs packages, but we can also
have an add-on package which contains the latest and greatest
verilog-mode which, if installed, is loaded in preference to the one
from the core emacs packages[.]" This seemed to be accepted as a
positive direction by Chitlesh and a review of the emacs-verilog-mode
package was started[4] by Jonathan.
Jerry James raised[5] the issue of XEmacs also having its own version of
the package, due to byte-code divergence between Emacs and XEmacs, and
also some GPLv2 versus GPLv3 compatibility issues.
1. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01290.html
2. ↑
https://fedoraproject.org/wiki/FWN/Issue161#Electronic_Design_Automation_...
3. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01303.html
4. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01305.html
5. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01316.html
--- Open JDK7 Experimental Package ---
Lillian Angel asked[1] where the OpenJDK[2] team should post their
unstable java-1.7.0-openjdk package: 1)to RPMFusion; 2) to a personal
FedoraPeople page; 3) to the main Fedora repositories.
Lillian disliked the last option: "I am not keen on getting this package
pushed into Fedora since java-1.6.0-openjdk already exists, and jdk7
will not be stable until sometime after Feb 2010[3]."
Following several suggestions it was decided[4] that a personal
FedoraPeople repository was the best solution as there would be six or
seven packages with no interdependencies.
1. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01251.html
2. ↑ http://openjdk.java.net/
3. ↑ http://openjdk.java.net/projects/jdk7/milestones/
4. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01264.html
--- Making Noise About Moksha ---
When Dimi Paun continued[1] to report problems using PulseAudio (see
FWN#174[2]) responses suggested[3] that his use of non-Free Flash or
tweaking of GStreamer settings was responsible. Debugging using
gstreamer-properties to ensure that "pulsesink" or "autoaudiosink" was
the default sink was recommended[4].
Lennart Poettering wanted a bug filed instead of posts to @fedora-devel
and when Dimi explained that Bugzilla was too slow and he had already
spent a lot of time on the problem Rahul Sundaram suggested[5] using
Bugz instead.
Criticism of the display of possibly thousands of "CLOSED" bugs by Bugz
led Tom Callaway to offer[6] the hope that Fedora Community will allow
developers to "[...] show new/open packages only on a per package
basis[.]" This occasioned[7] some apparent criticism from Rahul Sundaram
of a lack of openness "[...] it is a giant silo [...]" around the
development of Fedora Community[8]. Tom Callaway offered[9] a list of
resources to contradict this. When Rahul returned[10] with the criticism
that there "[...]is definitely a big lack of communication on this
development with the rest of the Fedora community. There was a very
brief mail to fedora-announce list but how much input are you getting
input from Fedora maintainers whose job this is supposed to make
easier?" there was a distinct lack of enthusiasm for more aggressive
marketing. Josh Boyer reaffirmed the involvement of several developers
with large package lists and expressed[11] a fear that bike-shedding
would result from any more exposure. Paul W. Frields pointed[12] to a
useful interview[13] with Luke Macken about the Moksha web-application
framework upon which Fedora Community is being built.
Moksha is built on a collection of python-based web-frameworks and uses
Orbited instead of AJAX to connect rich web applications to servers.
Reportedly this is more responsive than AJAX techniques.
A test instance of Fedora Community and AJAX was reported[14] by Tom
Callaway to be up. He emphasized that it was a test instance, currently
not to be relied upon at all and a disinclination "[...] to spend time
wading through the `OMG THIS IS SLOWER THAN BUGZLILLA!!!1!'" reports.
1. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01003.html
2. ↑
http://fedoraproject.org/wiki/FWN/Issue174#PulseAudio_Flamewar_Continues
3. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01005.html
4. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01010.html
5. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01018.html
6. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01021.html
7. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01022.html
8. ↑ https://fedorahosted.org/fedoracommunity/
9. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01029.html
10. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01030.html
11. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01051.html
12. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01059.html
13. ↑ https://fedoraproject.org/wiki/Moksha_in_Fedora_11
14. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01132.html
--- Be Excellent to Each Other ---
Regular readers are no doubt aware that flamewars have become more
common on @fedora-devel. Project Leader Paul W. Frields posted[1] to the
@fedora-advisory-board that the FAB[2] had decided to deal with the
"[...] degradation in tone and signal [...]" by appointing moderators.
Mike McGrath worried[3] that this would constitute an extra burden for
board members and also objected to any censorship on principal. As a
related problem Mark McLoughlin wondered how posters warned privately by
moderators that their behavior was problematic could defend themselves.
Seth Vidal replied[4] that this was not a court of law and that problems
with moderators could be reported to the board. Later posts along these
lines drew[5] a response from Luis Villa which argued strongly that
over-valuing one's own liberty to the detriment of others' was a
problem: "Or to put it another way: The Fedora community exists to work
together towards some common goals. Sometimes, in the name of reaching
those goals, you have to be polite and adult towards others so that you
can work efficiently and constructively with those other people even
when you disagree with them, and work with them in the future after you
have stopped disagreeing. This use of words like 'freedom' and
'oppression' suggests to me that some people think their highest reason
for being here is about them. It's not about you, it's about working
together to build something bigger and better than you. And if you can't
play nicely with others in the name of those bigger and better things,
or don't understand why sometimes you have to play nice in order to get
to those bigger and better things, then maybe this isn't the right place
for you."
Paul W. Frields reported[6] that a good deal of work led by Kevin Fenzi
was going on to moderate the IRC channels. A later post made[7] by Max
Spevack referenced IRC bans in the #cobbler channel and suggested that
Red Hat employees needed to be tough-minded and hold themselves to
higher standards than other contributors.
1. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00026.html
2. ↑ http://fedoraproject.org/wiki/Board
3. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00031.html
4. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00059.html
5. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00072.html
6. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00043.html
7. ↑
https://www.redhat.com/archives/fedora-advisory-board/2009-May/msg00052.html
--- Best Way to Store Information Across Desktops ---
Kushal Das requested[1] tips on making a truly cross-desktop application.
Adam Williamson noticed that many applications were storing information
in ~/.config files and Mathieu Bridon provided[2] the information that
this was an XDG[3] spec from freedesktop.org which resulted in replacing
a plethora of .app directories with only two: .config to store
configuration and .local/share/ to store data.
Jaroslav Řezník pointed[4] to work by the KWallet and gnome-keyring
developers to develop[5] a single-sign-on solution on top of a
DBUS-based protocol.
1. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00901.html
2. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01009.html
3. ↑ http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html
4. ↑
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg00966.html
5. ↑ https://bugs.freedesktop.org/show_bug.cgi?id=16581
-- Translation --
This section covers the news surrounding the Fedora Translation (L10n)
Project[1].
Contributing Writer: Runa Bhattacharjee
1. ↑ http://fedoraproject.org/wiki/L10N
--- Fedora 11 Website Strings Frozen ---
RickyZhou announced the availability[1] of the string frozen content for
Fedora 11 websites. The translations can be submitted via
translate.fedoraproject.org.
1. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00075.html
--- Confirmation Process for Translation Commits ---
A wrong commit for the system-config-printer package[1] initiated a
discussion about introducing a pre-commit check on
translate.fedoraproject.org. The suggestions list included the inclusion
of a 'Revert Commit' button[2], 'diff display'[3], and 'confirmation
screen'[4].
1. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00069.html
2. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00073.html
3. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00072.html
4. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00074.html
--- Decision Regarding Inclusion of Specspo ---
As part of decision making process related to the size of images for
Live CD/DVD, Bill Nottingham requested review[1] of a decision to
exclude the specspo package due to a lack of updated translations since
October 2007 and the uncertainty about the process to submit
translations at present. The current maintainer Stepan Kasal apologised
for the inactivity and offered to rebuild the package for Fedora 11 with
any available translations. Suggestions favoured the retention of the
translations but removal of the package from the Live media if space was
a constraint[2][3][4]. At present, Bill Nottingham announced[5] its
return to comps and requested Stepan Kasal to rebuild it with the
available translations.
1. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00088.html
2. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00089.html
3. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00098.html
4. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00099.html
5. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00101.html
--- Zero-day Changes to Fedora 11 Release Notes ---
Due to a last minute decision from the QA team, KarstenWade intimated[1]
about zero-day changes to the Release Candidate version of the Fedora 11
Release Notes. Additionally, these changes along with the updated
translations would also be displayed in the version of the notes
available on docs.fedoraproject.org.
1. ↑
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00095.html
-- Artwork --
In this section, we cover the Fedora Artwork Project[1].
Contributing Writer: Nicu Buculei
1. ↑ http://fedoraproject.org/wiki/Artwork
--- Easily Customizing the Wallpaper ---
William Jon McCann forwarded[1] a MSDN blog post[2] about wallpaper
customization in Windows 7 and Nicu Buculei observed[3] the similarities
with "Wallpapers Extras"[4], a project of the Art Team which lately had
little activity. "[T]he plan there is to gather as many as possible
images from the larger community and figure out a way to select some
which we think are both good and diverse." Nicu was also reminded of an
old idea by former Fedora contributor Bryan W Clark: 'background
channels'[5].
From here the discussion went to discuss Máirín Duffy's question[6]
about the need for gallery software: "Would some gallery software help
us out? E.g. we could maybe talk to Fedora Infrastructure about having a
gallery install for our usage" and debates about the way to set the
wallpapers from inside desktop applications, which Jóhann B. Guðmundsson
identified[7] as important and Matthias Clasen as already solved by
Firefox[8].
1. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00135.html
2. ↑
http://blogs.msdn.com/e7/archive/2009/05/02/a-little-bit-of-personality.aspx
3. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00138.html
4. ↑ http://fedoraproject.org/wiki/Artwork/Wallpaper_Extras
5. ↑
http://www.gnome.org/~clarkbw/designs/background-channels/background%20ch...
6. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00141.html
7. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00142.html
8. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00145.html
--- Media Art for Fedora 11 ---
Clint Savage asked[1] on @fedora-art about one of the last design pieces
needed for the Fedora 11 release, CC/DVD labels and sleeves and he
quickly followed[2] with an initial design "I've created some initial
artwork for the sleeves, but I think it needs some help" which was
further improved[3] by Máirín Duffy: "I've moved much of the lion off
the design. I also removed a lot of the styles that were there to get
this effect" until a final design[4]. In parallel Susmit Shannigrahi
tried[5] a version in richer colors, suitable for printing on a smaller
scale.
1. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00096.html
2. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00129.html
3. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00131.html
4. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00134.html
5. ↑
http://www.redhat.com/archives/fedora-art-list/2009-May/msg00154.html
-- Fedora Weekly Webcomic --
Tracking Rawhide you should be running F11 already... are you?
File:FWN176Queue.png
Nicu's latest webcomic[1]
1. ↑ http://nicubunu.blogspot.com/search/label/webcomic
-- Virtualization --
In this section, we cover discussion of Fedora virtualization
technologies on the @et-mgmnt-tools-list, @fedora-xen-list,
@libvirt-list and @ovirt-devel-list lists.
Contributing Writer: Dale Bewley
--- Libvirt List ---
This section contains the discussion happening on the libvir-list.
---- Status and Plans for Next Release ----
Daniel Veillard recapped[1] the plans for the next release. A "feature
freeze on the 22nd" and a "target for next release is Friday 29th".
Work will continue on "reviewing and adding OpenNebula[2]/Power[3]
drivers and try to get the NPIV[4], netcf[5] and secure migration
patches in. It's likely not everything will make the release cut but we
can try !"
"So far we have mostly a lot of bug fixes and VirtualBox[6] driver
updates commited since 0.6.3."
1. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00220.html
2. ↑ http://www.opennebula.org/
3. ↑ http://www-03.ibm.com/systems/power/software/virtualization/
4. ↑ http://en.wikipedia.org/wiki/NPIV
5. ↑ https://fedorahosted.org/netcf/
6. ↑ http://www.virtualbox.org/
---- PCI Passthrough Support ----
Aaron Clausen had[1] trouble using PCI passthrough[2].
Daniel Berrange noted[3] "there aren't any docs on the [libvirt] website
yet, but Mark McLoughlin just wrote up some notes[4] for the Fedora 11
virt test" day.
Daniel also noted "you need a machine supporting VT-D[5]" (or IOMMU[6]
in general) "for this work - the vast majority of hosts with fullvirt
support do *not* yet support VT-D passthrough, but perhaps you're lucky ..."
1. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00122.html
2. ↑ http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
3. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00126.html
4. ↑
http://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization_KVM_PCI_...
5. ↑ http://www.intel.com/technology/itj/2006/v10i3/2-io/1-abstract.htm
6. ↑ http://en.wikipedia.org/wiki/IOMMU
---- Converting Between Domain XML and Native Configurations ----
Daniel Berrange updated[1] patches for an idea posted in April. Daniel
added a public API for converting back and forth between the native
hypervisor configurations and image:Echo-package-16px.pnglibvirt XML
representations[2].
Daniel's changes enable Xen guest conversion "to/from both XM config
format (/etc/xen files), and the SEXPR format used by XenD". "For QEMU,
it implemnets export of domain XML into the QEMU argv format" and
conversion from QEMU argv into domain XML.
"With this available, it makes it very easy for people using QEMU to
switch over to using libvirt for management."
1. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00321.html
2. ↑ http://libvirt.org/formatdomain.html
---- Virtual Box Support Increases ----
Pritesh Kothari contributed patches improving the VirtualBox[1] driver
submitted[2] just last month.
* "support for vrdp/sdl/gui"[3]
* "support for "Host only" and "Internal" networks"[4]
1. ↑ http://www.virtualbox.org/
2. ↑ http://www.redhat.com/archives/libvir-list/2009-April/msg00232.html
3. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00157.html
4. ↑ http://www.redhat.com/archives/libvir-list/2009-May/msg00115.html
--- end FWN 176 ---
Pascal Calarco, Fedora Ambassador
https://fedoraproject.org/wiki/User:Pcalarco
14 years, 11 months
- 3
- 3
Fedora Weekly News #175 status
by Oisin Feeley
Hi all,
So far I've edited the following and added them to the 176 wikipage:
Announcements
PlanetFedora
Developments
QualityAssurance
Translations
Artwork
Comics
The weekly webcomic (thanks Nicu!) is uploaded. Thanks everyone for your
hardwork and great contributions
I'm out of the loop until late Monday afternoon. Pascal or Huzaifa, are
you available to shepherd 176 out the door a bit earlier?
Best,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
14 years, 11 months
- 3
- 3