Fedora Weekly News Issue 178
Welcome to Fedora Weekly News Issue 178[1] for the week ending May 31st,
2009.
We have a couple changes of note this week. Oisin Feeley, who has been
on the editorial team for FWN and writer for the Development section, is
leaving FWN for an extended time period due to other commitments. We
will miss him and hope to have him back at some time. Adam Williamson,
who currently also writes the wonderful QA beat, joins the editorial
team at FWN -- welcome Adam!
This week's issue starts off with some poetry on next week's expected
Fedora 11 release, and much activity on upcoming Fedora activity days,
dev cons, and events. In news from the Fedora Planet, we learn about
SELinux sandbox, an overview on virtualization features in F11, several
musings on aspects of open source projects/communities, and a feature
interview with Fedora Project leader Paul W. Frields. The Quality
Assurance beat details the QA weekly meeting leading up to F11 next
week, F11 FAQ work, and release candidate testing detail. Development
asks whether gNaughty is indeed a Hot Babe, detail on getting graphics
support working for the Fedora Live USB with the Chrome9 Vx800 GPU, and
suggestions on upgrading to F11 via yum. In Translation news, upcoming
F11 website translation details and a new member of the Romanian
translation team. This issue is rounded out with an overview of the
security advisories for Fedora 9 and 10 this past week. Enjoy this issue
and get ready for Fedora 11 a week from tomorrow!
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[2]. We welcome reader feedback: fedora-news-list@xxxxxxxxxx
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue178
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) ---
This week's Fedora 11 announcements come with apologies to William
Butler Yeats[1].
Somewhere in the build systems of Fedora,
A shape with lion body and the name of a Greek king,
Is moving its slow thighs, while all about it
Reel shadows of the impatient downloaders.
The schedule slips again[2]; but now I know
That 6 months of stony sleep
Were vexed to release by Jesse Keating,
And what rough beast, its hour come round at last,
Slouches towards June 9th to be born?
1. http://en.wikisource.org/wiki/The_Second_Coming
2.
http://www.redhat.com/archives/fedora-announce-list/2009-May/msg00011.html
--- Fedora Board ---
The Fedora Board's next public IRC meeting will be held on Thursday June
4th, at 1700 UTC[1].
Join[2] #fedora-board-meeting to see the Board's conversation, and join
#fedora-board-questions to discuss topics and post questions.
1.
http://www.redhat.com/archives/fedora-announce-list/2009-May/msg00010.html
2. https://fedoraproject.org/wiki/Communicate#IRC
--- FUDCons and FADs ---
This section previews upcoming Fedora Users & Developers Conferences, as
well as upcoming Fedora Activity Days.
-- Fedora Activity Days: Malaysia and Rheinfelden
At press time, two Fedora Activity Days[1] were wrapping up, one in
Malaysia[2] and one in Germany[3] for more information. See Max
Spevack's blog[4] for more information.
1. https://fedoraproject.org/wiki/FAD
2. https://fedoraproject.org/wiki/FAD_Malaysia_May_2009
3. https://fedoraproject.org/wiki/FAD_Rheinfelden
4. http://spevack.livejournal.com/81179.html
--- Fedora Activity Day: Development Cycle ---
In North America, Jesse Keating announced[1] an upcoming Fedora Activity
Day[2] "for maintainers, QA, and release engineering folks to meet and
discuss ongoing issues with the Fedora Development Cycle and to create a
proposal on how to fix many of the issues. Note, this is not an event to
decide on a solution, it is an event to decide on a proposal, which will
then be shared with the whole community for more input and work."
1.
http://www.redhat.com/archives/fedora-announce-list/2009-May/msg00012.html
2.
https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle_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, 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 got almost 120
people pre-registered for the event.
If you would like more information, please visit the wiki page.
1. https://fedoraproject.org/wiki/FUDCon:Berlin_2009
--- Upcoming Events ---
Consider attending or volunteering at an event near you!
June 8-10: FAD Fedora Development Cycle[1] in Raleigh, North Carolina.
June 9: Fedora 11 Release Party[2] in Managua, Nicaragua.
June 13: Fedora 11 Release Party[3] in Wageningen, The Netherlands.
June 12-13: VCNSL[4] in Maracay/Aragua, Venezuela.
June 13: Southeast Linuxfest[5] in Clemson, South Carolina.
June 14: Docs FAD @ Southeast Linuxfest[6] in Clemson, South Carolina
June 17-19: Open Source Bridge[7] in Portland, Oregon.
June 24-27: FUDCon Porto Alegre[8] in Porto Alegre, Brazil.
June 24-27: LinuxTag[9] in Berlin, Germany.
June 26-28: FUDCon Berlin[10] in Berlin, Germany.
1.
https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle_2009
2. https://fedoraproject.org/wiki/User:Yn1v/Fedora_UCA_jun09
3. https://fedoraproject.org/wiki/Fedora11Wau
4. https://cnsl.org.ve/
5. http://southeastlinuxfest.org/
6. https://fedoraproject.org/wiki/FAD_SELF
7. https://fedoraproject.org/wiki/OSBRIDGE_2009
8. https://fedoraproject.org/wiki/FUDConLATAM2009
9. https://fedoraproject.org/wiki/LinuxTag2009
10. https://fedoraproject.org/wiki/FUDConBerlin2009
-- 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 responded[1] respond to an article[2] by Matt Assay on
cnet (which in turn cited one of Michael's previous posts[3] on the
topic of "Recognizing and Avoiding Common Open Source Community Pitfalls"):
"Sure — building any sort of collaborative infrastructure is hard.
Yet there are those that want to sell open source as that (another
bullet point on a slidedeck), and then there are those that believe
software is open, that information should be free, everyone can work
together with everyone, we are all equals, and that we will keep no
secrets."
Daniel Walsh introduced[4] the SELinux Sandbox,a "policy that allows
users to build scripts to process untrusted content into some output
that they could safely use." James Morris elaborated[5] with further
points on the SELinux Sandbox and the problems with Ambient Authority.
Jack Aboutboul interviewed[6] Daniel Berrange, Red Hat Virtualization
Team Engineer "about the many key upgrades to virt technology in F11
focusing on areas of usability, performance and security."
Dan Williams showed off[7] the new NetworkManager network selector user
interface, to replace the old GtkMenu-based interface.
Susan Lauber continued[8] with Part 2 of a series on improving the
Fedora Wiki: "Using Special pages to assist with wiki cleanup."
Gary Benson published[9] an excellent introductory article on the
history and reasoning behind Zero and Shark at java.net. Gary also
wrote[10] a tutorial on Instrumenting Zero and Shark.
Jeroen van Meeuwen posted[11] an opinion piece on "Why the Open Source
Channel Alliance is bad for Free Software". Jeroen also mentioned[12]
that "Starting in July...I'll be mentoring a workshop on Office and
Infrastructure IT entirely based on Free Software and Open Source
technology..."
Martin Sourada chronicled[13] his preferred desktop applications
(including background information on why each program is used) to ensure
that he can run a FLOSS desktop using Fedora.
Paul W. Frields was interviewed[14] about Fedora and RHEL by Randal
Schwartz and Leo Laporte at Twit.tv.
1. http://michaeldehaan.net/2009/05/24/earth-to-matt/
2.
http://news.cnet.com/8301-13505_3-10244853-16.html?part=rss&subj=TheOpenRoad
3. http://michaeldehaan.net/2009/05/17/oss-pitfalls/
4. http://danwalsh.livejournal.com/28545.html
5. http://james-morris.livejournal.com/41591.html
6.
http://jaboutboul.blogspot.com/2009/05/fedora-11-virtualization-reality.html
7.
http://blogs.gnome.org/dcbw/2009/05/26/face-transplants-are-the-new-botox/
8.
http://travelingtrainer.laubersolutions.com/2009/05/using-special-pages-to-assist-with-wiki.html
9. http://gbenson.net/?p=137
10. http://gbenson.net/?p=138
11. http://kanarip.livejournal.com/14584.html
12. http://kanarip.livejournal.com/14756.html
13. http://mso-chronicles.blogspot.com/2009/05/my-desktop.html
14. http://marilyn.frields.org:8080/~paul/wordpress/?p=2481
-- 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-27. The full log is
available[2]. Adam Williamson reported that he had again not yet
remembered to ask the Bugzilla team to add a link to the Fedora bug
workflow page.
James Laska reported that he was still not yet ready to send out a Test
Day feedback survey to previous participants, but continued to work on it.
John Poelstra reported that he had updated the current Fedora 12
schedule[3].
Will Woods reported that he had added a test case for upgrading from one
Fedora release to the next with an encrypted root partition[4].
The group discussed how to handle the installation test result matrix
wiki page[5] between release candidate revisions. James Laska committed
to work out his best solution and send it to the mailing list.
Adam Williamson reported that the cleaning and revising of the Fedora 11
Common Bugs page[6] was complete. James Laska added that he had as
promised been adding significant installation issues to the page. Adam
said that he had added the X.org issues of which he was aware, and
sound-related issues. He noted that François Cami had created an initial
draft of a list of ATI-related issues, but had not yet completed it.
Will Woods clarified that his preferred title in relation to autoqa
issues is Cap'n Autoqa. The minutes do not relate whether or not there
is a parrot.
The group reviewed the current status of Fedora 11 GA (final release)
from its perspective. (Note that this meeting took place before the
latest delay in the final ship date). They went over the list of
currently open release blocker bugs, and agreed it seemed possible to
make the final deadline for initial RC generation with all of the bugs
at least tentatively resolved. There was detailed discussion of two bugs
(502077 and 498553). Action plans were developed for both issues to have
them addressed within the one-day deadline the team was at this point
working with.
The Bugzappers group weekly meeting[7] was held on 2009-05-26. The full
log is available[8]. 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.
Significant progress had been made during the week by the author,
Brennan Ashton. The system is now fully working on the official Fedora
infrastructure hosting server[9]. It is currently working with a test
snapshot of data rather than with the live Bugzilla data, but it should
already be theoretically capable of working with the live data. The
project will now enter a tidying-up and beta testing phase during which
it will be brought up to a state where it can be declared fully usable.
This should take two weeks or so. The group noted that the list of
triagers was based on the FAS 'triagers' group, which leads back to the
existing question of how to rationalize the 'fedorabugs' and 'triagers'
groups. Brennan will work with Jon Stanley to address this issue.
Adam Williamson also reported on the progress of the proposal to include
setting the priority / severity fields as part of triage. As no feedback
opposing the Cepl Method[10] had been received on the mailing list, the
group agreed that it could now go ahead and adopt this as the official
method of setting severity at the triage stage. Adam said he would work
with the Bugzilla team to restrict access to the priority and severity
fields as had been agreed as part of the proposal, and then adjust all
the relevant documentation on the Wiki to put the severity policy into
place.
The next QA weekly meeting will be held on 2009-06-03 at 1600 UTC in
#fedora-meeting, and the next Bugzappers weekly meeting on 2009-06-02 at
1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2. http://fedoraproject.org/wiki/QA/Meetings/20090527
3.
http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html
4.
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Encrypted_Root
5. https://fedoraproject.org/wiki/QA:Fedora_11_RC2_Install_Test_Results
6. https://fedoraproject.org/wiki/Common_F11_bugs
7. http://fedoraproject.org/wiki/BugZappers/Meetings
8. http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-May-26
9. http://publictest14.fedoraproject.org/triageweb/
10. http://fedoraproject.org/wiki/User:Beland/Bugzilla_Legend#Proposal_B:
--- Unified Greasemonkey triage script ---
Matej Cepl announced[1] that he had released a new revised and unified
Greasemonkey script for triagers incorporating all features of all
previously released scripts. Edward Kirk thanked him for his work[2].
Steven Parrish noted[3] that GreaseMonkey did not yet work unmodified
with the current Firefox 3.5 pre-release as found in Fedora 11. Matej
suggested[4] the Nightly Tester Tools extension as an easy way to work
around this limitation.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01131.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01132.html
3.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01163.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01174.html
--- Merging Fedora 11 FAQ into other pages ---
Christopher Beland revived[1] the idea of merging the Fedora 11 FAQ[2],
maintained by Rahul Sundaram, into other pages, as most of its content
could more appropriately be located in various other places, including
the Release Notes, Installation Guide, Common Bugs page and other
places. Rahul explained[3] that he was happy for any content that could
be moved to a more appropriate place to be removed from the FAQ page.
The documentation team's Susan Lauber contributed some suggestions[4] on
other appropriate places the content could be moved to, and in a later
thread she provided[5] some more useful information on adding
information to the Release Notes post-freeze.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01226.html
2. http://fedoraproject.org/wiki/Fedora_11_FAQ
3.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01228.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01246.html
5.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01328.html
--- Release Candidate testing ---
James Laska announced[1] testing for the first release candidate build
for Fedora 11 (and, later, for the second[2]). He asked for
installation-related issues to be reported to the Wiki test matrix
page[3]. This led indirectly to questions about where to find the
release candidate images (their location is buried within the matrix
page in order to try and limit demand for the images) and why release
candidate images are not more widely promoted and distributed[4]. Jesse
Keating explained [5] that the amounts of data were too great, the
available storage and bandwidth resources too small, and the timeframes
too tight for release candidate images to be meaningfully distributed
for public testing. He did emphasize[6], however, that the community
could contribute useful testing through use of the Rawhide repositories
and installer images, which currently are synchronized with the release
candidate builds.
1.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01272.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01333.html
3. https://fedoraproject.org/wiki/QA:Fedora_11_RC2_Install_Test_Results
4.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01308.html
5.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01309.html
6.
http://www.redhat.com/archives/fedora-test-list/2009-May/msg01286.html
-- Developments --
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
-- Would You Like to Write This Beat ?
Following this issue (FWN#178) I will, with regret, no longer be
covering the @fedora-devel list. If you are interested in writing this
weekly summary of the deeds and doings on the list then please contact
fedora-news-list@xxxxxxxxxx or Pascal Calarco. A short overview of what
you may need to do can be obtained by reading the workflow[1] section of
the wiki. The @fedora-news list is also extremely open and helpful.
Joining[2] the News Project is quite straightforward.
1. http://fedoraproject.org/wiki/FWN/WorkFlow
2. http://fedoraproject.org/wiki/FWN/NewsProject/Join
--- Is gNaughty a Hot Babe ? ---
Rahul Sundaram posted[1] the results of a survey conducted, primarily on
@fedora-list and on the forums, to discover which
non-repository-packaged software Fedora consumers were using.
One interesting point is that CMUCL[2] was revealed[3] to be only
available for 32-bit systems. However what got people really excited
was[4] Rahul's question about what to do concerning the gNaughty
package. Its sole purpose seemed[5] to be downloading pornography. Rahul
referenced the hot-babe CPU monitor which enjoyed controversy in Debian
packaging circles due to its use of female nudity. Rahul wanted to find
out "[...] is this allowed in Fedora?"
Amusingly a good deal of the controversy focused on whether the content
was freely redistributable, but a predictable moral angle was raised[6]
by Muayyad AlSadi who asked for help in producing a spin which removed
content deemed objectionable. Muayyad is a Jordanian developer who has
been producing an Arabic-localized Fedora spin named "Ojuba" for some
time. Muayyad sought a way to make identifying and tagging packages
easier to facilitate this spin. Bill Nottingham was[7] skeptical about
the chances of tags keeping meaning unless there was some sort of review
board. Equally predictable was[8] the reaction typified by Seth Vidal
which resisted any attempt to restrict packages according to standards
which had nothing to do with licensing or patent issues. Mathieu Bridon
thought[9] that the creation of a wiki-page by Muayyad would allow
anyone interested in co-ordinating work on "Inappropriate Content" to
just go ahead and do it without dragging in bureaucracy.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02071.html
2. One of the Common Lisp implementations: http://www.cons.org/cmucl/
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02088.html
4.
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg02136.html
5.
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg02203.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02242.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02312.html
8.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02295.html
9.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02355.html
--- Chrome9 Vx800 Graphics Support on LiveUSB ---
Kristaps Viesalgs asked[1] for help in getting the Fedora Live USB to
boot correctly on a machine using a Via Vx800 "Chrome9" GPU. Kristaps
had some success with the latest upstream version (from their subversion
repository) and asked: "Is there any brutal option how to properly boot
X with vesa driver, install Fedora, then make openchrome svn
installation? Is Fedora planning to make for VIA graphic chipset
autoconfiguration utility?"
Adam Jackson asked[2] for a more specific bug report because the chip
should be supported. He preferred not to ship an autoconfiguration
utility instead of just getting the driver correct. Similar points were
made by Adam Williamson and [[User:|Xavier Bachelot]]. The latter
asked[3] any interested developers to help out the openchrome project in
both the 2D and 3D(Gallium) sides.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02146.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02154.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02163.html
--- Who Wants a Pony? ---
Kushal Das promised[1] a pony to anyone that would take the trouble to
review[2] one of his packages.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02139.html
2. http://bugzilla.redhat.com/show_bug.cgi?id=503021
--- Firestarter Retired as Unportable to PolicyKit ---
Adam Miller asked[1] whether he should just retire the Firestarter[2]
package for which he had recently become the maintainer. His query was
based on the recent filing of RFEs to integrate Firestarter with
PolicyKit. These suggested to Adam that a large amount of work would be
needed due to the lack of any upstream activity for four years and the
need to grok PolicyKit.
Following confirmation from Rahul Sundaram and Seth Vidal a decision was
made[3] by Adam: "I would honestly rather retire the package than do a
WONTFIX, if the project as a whole is going the direction of PolicyKit
and upstream is dead then I don't want to keep old and busted cruft
around the repositories as Fedora continues to look towards the future."
A further suggestion from "Cry" prompted[4] Adam to start filing RFEs
against system-config-firewall for any features present in Firestarter
but missing in system-config-firewall.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02089.html
2. Firestarter is a firewall configuration GUI
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02094.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02122.html
--- Russian Fedora ? ---
When Peter Lemenkov asked[1] about the idea of creating a Fedora
Foundation outside of the U.S.A. the usual arguments from the past few
years were rehashed. Kevin Kofler gave[2] an able summary why this would
still present Red Hat with a problem.
An assertion by [[User:|Alexey Torkhov]] that there existed[3] a Red
Hat-sanctioned "RussianFedora" spin which contained mp3 codecs and other
material excluded from the actual Fedora Project repositories drew
demands for proof from Rahul Sundaram.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02013.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02025.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02390.html
--- Will FESCo Revisit Kmods ? ---
A discussion of why VirtualBox will not be a feature due to its code not
yet heading upstream and consequently remaining as kmods drew a
statement of support from Kevin Kofler for reverting the current banning
of kmods should he become a FESCo member. Upon request from Richard W.M.
Jones for a dispassionate summary of the reasons to avoid kmods drew[1]
a concise response from Seth Vidal.
Adam Williamson and Matt Domsch (Dell's DKMS mastermind) kicked[2] some
ideas back and forth over the advantages of akmods versus kmods.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02254.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02368.html
--- Upgrade from Fedora 10 to Rawhide (Fedora 11) ---
Following a report from Uwe Kiewel that a yum upgrade had spewed all
sorts of errors the supported methods for upgrades were re-stated[1] by
Adam Williamson: "[I]f you talk to the people most involved in
implementing it (Seth) and testing it (Will) they will tell you that
doing live upgrades via yum can't really ever be 100% safe for various
reasons, but preupgrade can get very close and is useful in all the same
cases. So their position is, we support preupgrade, we don't support
yum. If yum works, great, if it doesn't, you can bug people to fix
whatever it stopping it working, but it's not 'required' by any policy
or guideline."
1.
http://www.redhat.com/archives/fedora-devel-list/2009-May/msg02041.html
-- Translation --
This section covers the news surrounding the Fedora Translation (L10n)
Project[1].
Contributing Writer: Runa Bhattacharjee
1. http://fedoraproject.org/wiki/L10N
--- Fedora Websites test instance ---
Ricky Zhou set up a preview test instance[1] with the translations for
the Fedora web pages, updated for Fedora 11[2]. At present, the Leonidas
image banner is not functional and an alternate text in english is
displayed. Some configuration related errors caused the translated
versions of the pages in a few languages to not preview correctly. These
were later fixed by Ricky. Any updates to the translations automatically
show up on the test site within one hour.
1. http://publictest1.fedoraproject.org/
2.
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00152.html
--- New members in FLP ---
Claudia Pascu joined the Romanian translation team this week[1].
1.
https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00188.html
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce.
https://www.redhat.com/mailman/listinfo/fedora-package-announce
Contributing Writer: David Nalley
--- Fedora 10 Security Advisories ---
* kernel-2.6.27.24-170.2.68.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01126.html
* squirrelmail-1.4.19-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01202.html
* wireshark-1.0.8-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01213.html
* jetty-5.1.15-3.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01262.html
* libwmf-0.2.8.4-18.1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01266.html
* php-Smarty-2.6.25-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01274.html
* freetype1-1.4-0.8.pre.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01316.html
* eggdrop-1.6.19-4.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01337.html
* acpid-1.0.6-11.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01342.html
* ntp-4.2.4p7-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01414.html
* opensc-0.11.8-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01420.html
* maniadrive-1.2-13.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01451.html
* php-5.2.9-2.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01452.html
--- Fedora 9 Security Advisories ---
* wireshark-1.0.8-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01167.html
* squirrelmail-1.4.19-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01195.html
* jetty-5.1.15-3.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01257.html
* libwmf-0.2.8.4-18.1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01269.html
* kernel-2.6.27.24-78.2.53.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01271.html
* php-Smarty-2.6.25-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01283.html
* eggdrop-1.6.19-4.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-May/msg01333.html
-+- end FWN #178 -+-
--
fedora-announce-list mailing list
fedora-announce-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-announce-list
