Nabble - Fedora Announce

Fedora Weekly News #154

2008-12-02T07:50:06Z

= Fedora Weekly News Issue 154 =

Welcome to Fedora Weekly News Issue 153 for the week ending November
30th, 2008.

http://fedoraproject.org/wiki/FWN/Issue154

This week many of us enjoyed Thanksgiving turkey and we all enjoyed a
full helping of Fedora 10 and were left stunned and satisfied. In
Announcements the availability of third-party repositories and
end-of-life of Fedora 8 are detailed. Developments catches up with
"Power Management and Filesystem Parameters" and a promising initiative
to bring the man pages up-to-date. Artwork passes on some kudos for the
"Release Banner for the Website" and the demo of some awesome
"Stickers". Don't forget to peruse the SecurityAdvisories!

If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[1].

FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala

[1] http://fedoraproject.org/wiki/NewsProject/Join

CONTENTS #154
1.1 Announcements
1.1.1 Fedora 10
1.1.2 Other
1.2 Developments
1.2.1 Python Bump to 2.6 in Rawhide
1.2.2 Power Management and Filesystem Parameters
1.2.3 Strange Resolution Problems
1.2.4 Cron Confusion
1.2.5 Man Pages to be Mandatory and Upstreamed
1.3 Artwork
1.3.1 Stickers
1.3.2 Release Banner for the Website
1.3.3 The Download Page
1.4 Security Advisories
1.4.1 Fedora 10 Security Advisories
1.4.2 Fedora 9 Security Advisories
1.4.3 Fedora 8 Security Advisories

== Announcements ==

In this section, we cover announcements from the Fedora Project.

http://www.redhat.com/archives/fedora-announce-list/

http://www.redhat.com/archives/fedora-devel-announce/

Contributing Writer: Max Spevack

It was a pretty quiet week in Fedora-land. Nothing really happened, so I
guess we can just move ahead to the next section of Fedora Weekly News.

Wait, what? Oh, yeah... how silly of me! I guess there was that one
small announcement, like the general availability of Fedora 10 on
November 25.
Fedora 10

Keeping with tradition, the Fedora Project Leader Paul Frields wrote[1]
a thank you message to the Fedora community on the eve of the release.

Also keeping with tradition, on the morning of the release, a
"whimsical" announcement was sent[2] out on the morning of the release.

Naturally, some of the third-party packagers of Fedora (RPM Fusion and
ATrpms) made their repositories available for Fedora 10 on the release
day also [3,4].

Chitlesh Goorah reminded[5] the community that the Spins SIG has
released seven Fedora 10 respins, all of which can be downloaded from
spins.fedoraproject.org.

Finally, Red Hat's CEO Jim Whitehurst sent a congratulatory email to the
Fedora community [6].

[1]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00013.html

[2]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00015.html

[3]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00014.html

[4]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00016.html

[5]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00022.html

[6]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00019.html

=== Other ===

Fedora 8 will reach its end-of-life[7] on January 7th (07-01-2009),
according[8] to Jon Stanley.

[7] http://fedoraproject.org/wiki/LifeCycle

[8]
http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00021.html

== Developments ==

In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

=== Python Bump to 2.6 in Rawhide ===

The success of Fedora's dogged persistence in pursuing an "upstream all
possible patches" methodology was anecdotally highlighted during a
thread in which Ignacio Vazquez-Abrams warned that all Python packages
in rawhide would soon be affected. An apology was made[1] by Ignacio for
a dramatic subject-line ("It's all ASPLODY!), but he explained that
"[w]ithin the next few days Python 2.6 will be imported into Rawhide.
This means that EVERY single Python-based package in Rawhide will be
broken, and that we'll need to slog our way through rebuilding it
package by package." Ignacio suggested that the list of approximately
seven hundred packages could be examined with a:

repoquery --disablerepo=\* --enablerepo={development,rawhide} \
--whatrequires "python(abi)" | sort | less

Ignacio expressed[2] willingness to trigger the rebuilds for some of the
packages but "[...] there's no way I can get [700] done in a timely
fashion."

[1]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01809.html

[2]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01813.html

Ville Skyttä asked[3] "[i]f a package installs some *.py, *.pyc, *.pyo
somewhere else than in versioned python dirs, and the source *.py is
python 2.6 compatible, will the *.pyc and *.pyo compiled with 2.5 break
with 2.6?" Ignacio confirmed[4] that such packages should not need to be
recompiled as the API had not changed beween versions 2.5 and 2.6.

[3]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01826.html

[4]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01837.html

Tom 'spot' Callaway suggested[5] using a separate Koji tag so that
Ignacio could use a process similar to that which Tom had employed for
the transition from PERL-5.8 to PERL-5.10. Jeremy Katz remembered[6]
that such tagging had been used for past bumping of Python and suggested
"It's good to at least get the stack up through yum and friends building
and working before thrusting the new python upon everyone as otherwise
it's quite difficult for people to even try to fix things on their own."
A list of the essential packages was made[7] by Seth Vidal and
Konstantin Ryabitsev.

[5]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01823.html

[6]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01815.html

[7]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01820.html

On the foot of some skeptical questions from Les Mikesell Tom
reported[8] that the end result of following such a process for PERL was
that "[Fedora is] closer to perl upstream than we've ever been, and we
have most of the long-standing perl bugs resolved (and we fixed the
"RHEL slow perl" bug without even being aware of it as a byproduct of
the methodology). The fact that you just noticed it means that we must
have done some things properly, you're welcome. :)"

[8]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01839.html

On 28-11-2008 Ignacio reported[9] that "[...] we're going to go ahead
and commit 2.6 to Rawhide and start the rebuild of all Python packages
in Rawhide. So please keep your hands off any packages that require
python(abi) until we're done. Or if you like, you can help out by
bumping the release and building against the dist-f11-python tag." He
later explained[10] that python-2.6 would appear in rawhide "[...]
within 10 days if all goes well. Then releng will need to fold the tag
back into f11-dist" and confirmed[11] that the version in Fedora 11 will
be Python-2.6.

[9]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02126.html

[10]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02130.html

[11]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02136.html

On 30-11-2008 Ignacio posted[12] the results of the "first cycle of
rebuilds" and categorized the failures into several convenient classes.
On 01-12- 2008 Ignacio posted the results of round two which he
explained[13][14] were "a set of packages that a different net caught. I
used python(abi)=2.5 for the first set in order to get the low-level
packages, and this one uses libpython2.5.so.1.0." The latest follow-up,
on 01-12-2008 consisted[15] of the list of packages which "[...] contain
compiled Python code but do not have a Requires of python(abi). Please
note that this is a packaging bug as the bytecode is specific to the
version of the Python it was compiled with. Whether this is a problem
with rpm's macros or with the package itself must be dealt with on a
case-by-case basis."

[12]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02201.html

[13]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00014.html

[14]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00028.html

[15]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00041.html

=== Power Management and Filesystem Parameters ===

A series of three disk-power management proposals were published[1] as
an RFC by Matthew Garrett. They were generally well-received and
discussion was mostly focused on ways to instrument the kernel to
measure any resulting changes and to ensure that disk lifetimes are
monitored carefully.

[1]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02047.html

The first, least controversial, proposal is to get Ingo Molnar's
relatime patch upstream. An extensive discussion in LWN[2] explains that
this allows applications to keep track of when files have been read
without having to constantly update the last file access time, thus
reducing the number of writes to the disk.

[2] http://www.lwn.net/Articles/244829/

Matthew's second proposal was to "[...] increase the value of
dirty_writeback_centisecs. This will result in dirty data spending more
time in memory before being pushed out to disk. This is probably more
controversial. The effect of this is that a power interruption will
potentially result in more data being lost." The third proposal was to
enable laptop-mode[3] by default in order to mitigate the second change.

[3] cat
/usr/share/doc/kernel-doc-2.6.27.5/Documentation/laptops/laptop-mode.txt

EricSandeen was interested[4] in how Matthew would measure the effects
on power and performance, whether it was possible to identify individual
applications causing disk accesses, and whether disk spin-down should be
considered. When Matthew replied[5] that it would be difficult to
monitor disk access without causing further disk access David Woodhouse
suggested using blktrace and this was eagerly recognized[6] by Matthew
as exactly what he needed.

[4]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02048.html

[5]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02052.html

[6]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02093.html

Eric's spin-down suggestion was confirmed: "Yes, the long-term plan
involves allowing drive spindown. I'm hoping to do this adaptively to
let us avoid the spinup/down tendancies a static timeout provides, but
you're right that monitoring SMART information would be a pretty
important part of that. I lean towards offering it on desktops and
servers, but not enabled by default."

Phil Knirsch posted[7] that he was working on similar ideas currently
including "the idea if a combination of a monitoring backend and a
tuning engine could provide an automatic adoption of the system to the
current use. E.g. during daytime when a user works with his machine we
would typically see quite a few reads and write all the time. Drive
spindowns or other power saving features could during that time be
reduced so that the user will have the best performance. During the
night (in case he didn't turn of the machine) only very few read and
even fewer write operations should happen, at which time the disk could
then be powered down most of the time. And of course this can be
extended to not only disk drives but other tunable hardware components."

[7]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02089.html

Some of the pitfalls of choosing defaults for all users were exposed
when Ralf Ertzinger and Phil disagreed[8] on the ideal behavior of
logging mechanisms. Phil drew a distinction between system logging
mechanisms and user application logs and argued that losing data from
the latter was not as important. Dariusz Garbowski put[9] the point of
view of "Joe the User": "He cares a lot that he lost last hour of his
xchat (or whatever he uses) logs. He quite likely doesn't care about
last hour of syslog messages (he may not even be aware they exist in the
first place)..."

[8]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02099.html

[9]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02137.html

See FWN#88[10],FWN#100[11][12] for previous discussion of
power-management in Fedora.

[10]
https://fedoraproject.org/wiki/FWN/Issue88#PowerTOP_Release_Opens_Up_New_Directions_In_Power_Saving

[11] http://fedoraproject.org/wiki/FWN/Issue100#Disabling_Atime

[12]
http://fedoraproject.org/wiki/FWN/Issue100#Reducing_Power_Usage_Of_Fedora

=== Strange Resolution Problems ===

A report of a strange name resolution problem was made[1] by Mark
Bidewell. Yum failed to download the Adobe flash-plugin with an error:
[Errno 4] IOError: <urlopen error (-2, 'Name or service not known')>
Trying other mirror." , yet it was possible to download it directly over
HTTP using the browser.

[1]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02002.html

Christian Iseli added[2] that he had a similar "[...] issue which seems
to be due to some sort of DNS lookup problem. In my case I'd get the
'Name or service not known' for download1.rpmfusion.org." Christian's
troubleshooting revealed that specific sites (linuxdownload.adobe.com
and download1.rpmfusion.org) were consistently resolved with ping or
firefox but failed with wget and ssh. Moreover: "Putting the IP
addresses in /etc/hosts "works around" the problem[.]"

[2]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02071.html

Following some questions from Seth Vidal nothing seemed[3] obviously
wrong and the mystery remains.

[3]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02082.html

=== Cron Confusion ===

Pavel Alexeev asked[1] for guidance on how to correctly rpm package a
cron job. The specific requirement was a cronjob that ran every twenty
minutes and might thus use the /etc/cron.d directory provided by cronie
,the SELinux and PAM aware derivative of vixie cron. Pavel wondered how
he could make a package which would work for both variants of cron.

[1]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02179.html

When Martin Langhoff confirmed that /etc/cron.d was necessary Pavel
replied[2]: "[...] /etc/cron.d [is] provided only by cronie [and] now we
have several other crons in the repositories[.]" He listed several other
implementations of cron found by a

# repoquery '*cron*' | egrep -v '^(yum-cron|PackageKit-cron|cronolog)'

[2]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02182.html

Ignacio Vazquez-Abrams corrected[3] him: "The only replacement for
cronie in that list is fcron. Feel free to log a bug against it." Till
Maas and Pavel noted[4], however, that the /etc/cron.* directories were
also provided by the package named crontabs.

[3]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02183.html

[4]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02187.html

Patrice Dumas posted[5] the welcome news that he was "[...] currently
preparing a fcron sub-package that would be completly compatible with
cronie and would watch /etc/cron.d (using inotifywait). I'll keep the
list informed."

[5]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02187.html

=== Man Pages to be Mandatory and Upstreamed ===

A vigorous thread flowered from the promising seed planted[1] by Michael
Cronenworth in which he advocated getting rid of all current
documentation: "Yes, what I'm about to describe should obsolete man,
info, and all the other dozen "help" documentation found in all the
Fedora packages." Michael proposed that a new, lightweight standard of
some sort would solve the problem of missing documentation.

[1]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02015.html

During the course of the week there have been requests for
"NetworkManager cli docs"[2] and "PulseAudio info needed"[3] in which
the desired information has mostly been found on external web pages
instead of in documentation supplied with the OS.

[2]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg01757.html

[3]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02041.html

Richard W. M. Jones suggested[4] instead that the Debian model should be
followed: "Debian forces all programs to come with a man page. If one is
missing, this is considered a bug and packagers have to write one."
Patrice Dumas was[5] against compulsion and preferred leaving the choice
to the packager.

[4]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02023.html

[5]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02025.html

The idea of upstreaming the man pages was introduced[6] by Thorsten
Leemhuis: "One reason for that: If you add man pages from debian to a
fedora package then you have to recheck every now and then if the man
pages are still up2date. That afaics often tends to be forgotten (I'm
guilty myself here)." Richard agreed[7] and in the course of several
clarifications made the strong point that "[...] it's a really useful
feature of Debian that _any_ command, any many configuration files and
other files, are documented using 'man'. I find it a big negative
against Fedora that things aren't so consistently documented."

[6]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02024.html

[7]
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02050.html

There seemed to be little disagreement on the desirability of providing
more information but Michael was not impressed[8] with Trond Danielsen's
suggestion that yelp would fulfill his requirements: "[...] it lacks in
the lightweight department. It eats 40 megs of RAM upon startup and more
RAM once searching occurs or pages are opened. Sure, we're all getting
gigabytes of RAM these days, but it's a HELP tool with TEXT." Basil
Mohamed Gohar was inspired[9] to "[write] or two man pages, because I've
run into the missing-man-page problem too often." He suggested a very
reasonable sounding action plan for identifying missing man pages and
then filling them in with at least stubs in order to form a SIG which
would work on providing quality replacements. Gergely Buday also
seemed[10] interested.

[8]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00004.html

[9]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00023.html

[10]
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg00060.html

== Artwork ==

In this section, we cover the Fedora Artwork Project.

http://fedoraproject.org/wiki/Artwork

Contributing Writer: Nicu Buculei

=== Stickers ===

In a message posted[1] to both @fedora-art and @fedora-marketing, Máirín
Duffy showed the community a demo of a sticker sheet "I've been through
a few rounds with the printing company to correct various issues and I
just received a digital proof from them that I'm pretty happy with" and
asking for feedback "Does this look good? If you see any errors or
issues let me know and I'll have them fixed, otherwise I'd like to send
to send them myapproval ASAP."

[1]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00100.html

Gerold Kassube asked[2] about the empty stickers "with some I miss the
content to fedora and I ask myself: If somebody sees that freedom boble,
does he realize that it's fedora or is it only for insider?!" and
proposed an alternate slogan "In my head I have a big idea for a sticker
which could also be a good marketing which I want to share with you and
your outstanding ideas in the past (and I'm also sure in the future). I
like the phrase 'Fedora! Leaders not fellows'". In reply, Paul Frields
pointed[3] the possibility to combine the stickers "Well, the nice thing
about these stickers is they're *extremely* inexpensive. So we can hand
out a sheet or two per person, and people can paste *both* a freedom
bubble and the logo together!" and stressed the importance of a single,
consistent, marketing message "I think it's important for us not to
develop too many 'official' slogans, because it dilutes our message.
'What is Fedora? 4 Foundations? IFV? Leaders?'"

[2]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00101.html

[3]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00103.html

=== Release Banner for the Website ===

In a last check before the release day, Ricky Zhou from the website team
asked[1] about the status of the graphics to be used on the website
"Just to make sure everything will be ready for Tuesday, will we have a
final version ready for adding to the site by some time on Monday?" and
quickly Paolo Leoni replied[2] with an upload of the needed images and a
minor modification[3] from Nicu Buculei. Jaroslav Reznik added[4] a KDE
specific flavour it it (the banner contains screenshots of the desktop).

[1]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00107.html

[2]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00108.html

[3]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00116.html

[4]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00140.html

=== The Download Page ===

In a post to @fedora-art Seth Kenlon expressed[1] his delight with the
design of the download page[2] "I don't know who takes care of this
stuff, but I was really really impressed with the new/updated download
page for fedora 10. The buttons on the right side of the page are
brilliant -- "KDE Fans Click Here" and "Need PowerPC? Click here" -- now
sure, I'm biased, because those two versions of Fedora happen to be the
two that I use :^) but......objectively speaking, that is user friendly
and attractive. Great job, who ever did that!" The page was designed, as
Ricky Zhou pointed[3] by Máirín Duffy "Not surprisingly, this was the
work of Máirín - thanks a lot for making that page beautiful and easy to
use!"

[1]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00145.html

[2] http://fedoraproject.org/en/get-fedora

[3]
https://www.redhat.com/archives/fedora-art-list/2008-November/msg00147.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 ===

* nagios-3.0.5-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00881.html
* imlib2-1.4.2-2.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00906.html
* php-Smarty-2.6.20-2.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00940.html
* net-snmp-5.4.2.1-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg01002.html

=== Fedora 9 Security Advisories ===

* imlib2-1.4.2-2.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00856.html

=== Fedora 8 Security Advisories ===

* imlib2-1.4.2-2.fc8 -
https://www.redhat.com/archives/fedora-package-announce/2008-November/msg00858.html

==== Fedora 8 is nearing EOL ====

Per FESCo support for Fedora 8 will be discontinued on January 7th 2009
https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html

--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

F11 Naming: Sulphur -> Cambridge -> ?

2008-12-02T05:56:07Z

Hi All,

It's that time of year again. Time to start the naming process
for the next Fedora release.

To recap on the rules:

1) <NewName> must have some link to Cambridge

More specifically, the link should be
Cambridge is a <blank> and
<NewName> is a <blank>
Where <blank> is the same for both

2) The link between <NewName> and Cambridge cannot be the same as
between Sulphur and Cambridge. That link was "both are cities".

We're doing the name collection differently this year than in
the past. Contributors wishing to make a suggestion are asked to
go to the F11 naming wiki page, and add an entry to the suggestion
table found there:

https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_11

The naming submissions are open starting now until Dec 8. The
rest of the schedule is outlined on the wiki page.

So, put on your thinking caps and come up with some really good
suggestions!

Happy naming.

josh

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

FUDCon F11 Boston

2008-12-01T09:19:10Z

FUDCon F11 Boston -- News Update!
=================================

* All of our location information is confirmed -- we will be holding
the conference as predicted, at MIT in the Sloan Building. There
will be plentiful space for hackfests and BarCamp sessions over the
course of the weekend.

* FUDPub will be held at Flat Top Johnny's on Saturday night (January
10) from 6:00-10:00pm.

* The wiki remains open for registration. Please remember to note
your shirt size, whether you prefer vegetarian fare for lunch on
Saturday, and any other important information (in the "Comments"
section).

* The hotel group rate is good until DECEMBER 19. After that, it will
be up to the hotel to decide whether or not to extend their offer of
$99/night. So sign up now!

And here's some further news to sweeten the pot -- the One Laptop Per
Child and SugarLabs communities will be joining us for FUDCon, to
address areas of common interest like packaging and building for these
unique projects, and to talk to Fedora community members about getting
involved. This should make FUDCon a very exciting event and I look
forward to seeing everyone there who can make it!

--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

attachment0 (196 bytes) Download Attachment

Fedora 10 Cambridge Spins : Other Planetary Systems

2008-11-29T10:04:59Z

Hello there,

While astronomers took first ever pictures of other planetary systems
[1] last month, the fedora community was building its own planetary
systems. Some say one planet isn't enough, other strive to enlarge
their own planet. While F-10 Cambridge elevates the performance
barrier and much more, other planetary spins have been geared to
specific applications.

Ladies and Gentlemen, the following spins have also been released
together with Fedora 10 Cambridge release to ensure that you will be
the most productive in your specific work environment with opensource
software:
- Fedora Electronic Lab
- Fedora KDE
- Fedora Edu-Math
- Fedora XFCE
- Fedora AOS
- Fedora Developer
- Fedora BrOffice

For more details, please visit https://fedoraproject.org/wiki/SIGs/Spins/10

All these official spins can be downloaded at
http://spins.fedoraproject.org/ for both i386 and x86_64 architectures
as LiveCDs or LiveDVDs.

[1]: http://gizmodo.com/5086678/astronomers-take-first-ever-pics-of-other-planetary-systems

Kind regards,
Chitlesh GOORAH

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

Fedora Board IRC meeting 1900 UTC 2008-12-02

2008-11-27T10:39:11Z

The Board is holding its monthly public meeting on Tuesday, 2 December
2008, at 1900 UTC on IRC Freenode. The Board has settled on a
schedule that puts these public IRC meetings on the first Tuesday of
each month. Therefore, the next following public meeting will be on 6
January 2008. For these meetings, the public is invited to do the
following:

* Join #fedora-board-meeting to see the Board's conversation. This
channel is read-only for non-Board members.
* Join #fedora-board-public to discuss topics and post questions.
This channel is read/write for everyone.

The moderator will direct questions from the #fedora-board-public
channel to the Board members at #fedora-board-meeting. This should
limit confusion and ensure our logs are useful to everyone.

We look forward to seeing you at the meeting.

Paul

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

Reminder of Fedora 8 end-of-life

2008-11-26T21:34:01Z

As a reminder, Fedora has a policy of ending maintenance for a release
one month after the release of Fedora N+2 (i.e. Fedora 8 maintenance
would end one month after Fedora 10 was released). In this instance,
that date would be December 25.

At today's FESCo meeting [1], it was decided to slightly deviate from
this policy. This decision was made in order to avoid having it
happen over the holidays, since according to policy, EOL would have
been on Christmas Day.

It was therefore decided to extend the end-of-life date of Fedora 8 to
Jan 7, 2009. After this time, there will be no more updates, including
security updates, issued for Fedora 8, and new builds will no longer
be allowed in koji, our buildsystem.

Also at or shortly after that time, all bugs open against Fedora 8
will be closed, since no more updates will be made.

Thanks!
-Jon

[1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg02014.html

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

From Jim Whitehurst: F10!

2008-11-26T21:26:20Z

Hello everyone,

Jim Whitehurst has sent us the following congratulatory message on
Fedora 10. I'm forwarding it myself, since the mailing list software
seems not to care that Jim could have it erased with the drop of his
big red hat, and keeps swallowing his email to us! ;-)

Paul Frields

* * * * *

FROM: Jim Whitehurst
RE: F10!

Yesterday marked the tenth release of Fedora, and I wanted to take the
opportunity to congratulate the Fedora community. We at Red Hat are
glad to be part of Fedora, and in fact I've already downloaded and
installed it myself. Ten releases in five years is an astonishing pace
of innovation, and the community has much to be proud of.

Over the last five years the Fedora Project has come far: creating a
publicly available packaging code base, establishing a completely free
and open source infrastructure for its engineering processes, unifying
the software repositories, and developing scalable, local grassroots
communities. As a result of those efforts, you've also created artwork,
marketing, project hosting, mirroring tools, and many other pieces of
free software that will benefit the entire Linux ecosystem.

One of the things that sets Fedora apart is its unwavering commitment to
working with upstream software projects. By working with upstream, you
can take advantage of the full power of the open source development
model. That helps create more value in Red Hat's product offerings, but
it also results in a more sustainable process for open source worldwide.

I want to thank each and every one of Fedora's thousands of
contributors, and again, congratulations on Fedora 10!

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

attachment0 (196 bytes) Download Attachment

Cooperative Bug Isolation for Fedora 10

2008-11-26T13:08:14Z

The Cooperative Bug Isolation Project (CBI) is now available for Fedora
10. CBI (http://www.cs.wisc.edu/cbi/) is an ongoing research effort to
find and fix bugs in the real world. We distribute specially modified
versions of popular open source software packages. These special
versions monitor their own behavior while they run, and report back how
they work (or how they fail to work) in the hands of real users like
you. Even if you've never written a line of code in your life, you can
help make things better for everyone simply by using our special
bug-hunting packages.

We currently offer instrumented versions of Evolution, The GIMP, GNOME
Panel, Gnumeric, Nautilus, Pidgin, Rhythmbox, and SPIM. Download at
<http://www.cs.wisc.edu/cbi/downloads/>. We support PackageManager,
yum, apt, and many other RPM updater tools; see
<http://www.cs.wisc.edu/cbi/downloads/repo-config.html> for customized
configuration help for any of our supported distributions and updater
tools. Or just download and install
<http://www.cs.wisc.edu/cbi/downloads/rpm/fedora-10-i386/RPMS.tools/cbi-package-config-10-10.i386.rpm>
to automatically configure most popular RPM updaters to use the CBI
repository.

It's that easy! Tell your friends! Tell your neighbors! The more of
you there are, the more bugs we can find.

We still offer CBI packages for Fedora 1/2/4/5/6/7/8/9 as well. When
and if you decide to upgrade to Fedora 10, we'll be ready for you.
Until then, your participation remains valuable even on older distributions.

-- Dr. Ben, the CBI guy

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

Outage Notification - Fedorapeople.org 2008-11-30 06:00 UTC -> 2008-11-30 18:00 UTC

2008-11-26T11:02:01Z

Outage Notification - 2008-11-30 06:00 UTC

There will be an outage starting at 2008-11-30 06:00 UTC, which will last
approximately 12 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:

date -d '2008-11-30 06:00 UTC'

Affected Services:

fedorapeople.org
planet.fedoraproject.org

Reason for Outage:
The building where the system is housed is losing power for 12 hours for
renovation work

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.

-sv

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

ATrpms for Fedora 10; upcoming EOL for Fedora 8

2008-11-25T11:21:14Z

ATrpms is officially launching Fedora 9 support.

http://ATrpms.net/dist/f10/

o The actual download location is http://dl.atrpms.net/. Mirrors are
listed at http://atrpms.net/mirrors/

o "stable", "testing" and "bleeding", the three subrepos per
distribution are not cumulative inclusive on the server
side.
E.g. you need to add "stable" for "testing", and both "stable"
and "testing" for "bleeding".

ATrpms is a 3rd party general purpose package repository. It currently
supports

o F10/i386, F10/x86_64, F9/i386, F9/x86_64, F8/i386,
F8/x86_64
o RHEL5/i386, RHEL5/x86_64, RHEL4/i386, RHEL4/x86_64, RHEL3/i386,
RHEL3/x86_64

F10 support will be EOL'd once the Fedora Project drops support for it
(e.g. in about a month's time).

Configuration for package resolvers (replace i386 with x86_64 or ppc
as needed)

o yum
[atrpms]
name=Fedora 10 - i386 - ATrpms
baseurl=http://dl.atrpms.net/f10-i386/atrpms/stable

o smart
[atrpms]
name=Fedora 10 - i386 - ATrpms
baseurl=http://dl.atrpms.net/f10-i386/atrpms/stable
type=rpm-md

o apt
repomd http://dl.atrpms.net f10-i386/atrpms/stable

you can provide feedback or request support on the ATrpms lists
(http://lists.atrpms.net/), or the common bug tracker
(http://bugzilla.atrpms.net/).

Enjoy!
--
Axel.Thimm at ATrpms.net

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

attachment0 (204 bytes) Download Attachment

Cambridge Launched to Explore Solar System (Fedora 10)

2008-11-25T06:45:18Z

DATELINE: 2008-11-25

KEY FINGERPRINT: 61A8 ABE0 91FF 9FBB F4B0 7709 BF22 6FCC 4EBF C273

LOCATION: GEOSYNC ORBIT, FEDORA SPACE STATION VIA GLOBAL IRC NETWORK

BROADCASTING: FREEDOM FRIENDS FEATURES FIRST

(Cue J. Strauss' "Blue Danube.")

THIS IS FEDORA SPACE OPERATIONS ANNOUNCING with great pleasure the
successful launch of the new ship, Fedora 10: "Cambridge."

Strapped into the pilot seats are the latest GNOME (2.24) and KDE (4.1),
accompanied on their amazing journey by an all star crew of glitch free
audio, better printing and webcam support, and a new faster graphical
startup.

Also on this ride are wireless connection sharing and the next evolution
in PackageKit, hooking through your multimedia applications to help
install supporting software (codecs).

For developers and system administrators on this mission, we have built
in appliance tools, Eclipse 3.4, NetBeans IDE, improved virtualization
management with remote installation and storage capabilities, RPM 4.6,
and new security auditing toolsets.

Please remember to polarize viewports to properly enjoy Cambridge's
brand new graphics theme, "Solar," shining on the desktop. Also on this
flight is a new lightweight desktop environment, LXDE, joining the more
recent desktop envionment crew member, Sugar (from the starship OLPC
XO), and the venerable GNOME, KDE, and XFCE.

We are now leaving drydock for a 13-month mission of innovation and
exploration. Crew members and guests are invited to the forward lounge
to use, study, modify, and redistribute.

Get your copy of Fedora 10 today:

http://get.fedoraproject.org/

Join the many thousands of Fedora particpants and contributors:

http://join.fedoraproject.org/

If you missed the official launch, attend a Fedora 10 Launch Party near
you:

http://fedoraproject.org/wiki/FedoraEvents/ReleaseParty

[ This message was created by the Fedora Documentation Project ]

--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

signature.asc (204 bytes) Download Attachment

RPM Fusion free and nonfree repositories for Fedora 10 (Cambridge) now available

2008-11-25T06:18:14Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The RPM Fusion team is proud to announce the public availability of our
''free'' and ''nonfree'' package repositories for Fedora 10 (Cambridge).
The repositories contain multimedia applications, kernel drivers, games
and other software the Fedora Project doesn't want to ship for various
reasons.

RPM Fusion repositories give Fedora 10 the ability to play all kinds of
audio and video -- including, but not limited to MP3s or video files in
MPEG or Xvid formats.

You can browse the repository contents for the i386 architecture via
these URLs (x86-64, ppc and ppc64 are supported as well):

http://download1.rpmfusion.org/free/fedora/releases/10/Everything/i386/os/repoview/index.html
http://download1.rpmfusion.org/nonfree/fedora/releases/10/Everything/i386/os/repoview/index.html

To make RPM Fusion repositories available on a freshly installed Fedora
10 system run the following command:

{{{
| $ su -c 'rpm -ivh
http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'
}}}

More details about how to configure and use RPM Fusion can be found in
our wiki: http://rpmfusion.org/Configuration

You can also enable RPM Fusion while installing Fedora 10 -- details and
some screenshots that should give you an idea how everything works can
be found at http://rpmfusion.org/EnablingRpmFusionDuringFedoraInstall

Please note that the graphics drivers from AMD are not yet available in
the repositories as it seems they don't work with F10 right now. If you
know how to make them work let us know, then we'll try to ship them as
an update as soon as possible.

There is still a lot of room for a whole lot of improvements in RPM
Fusion. If you are a packager (or want to become one) then join us! Our
mailing lists can be found at
http://lists.rpmfusion.org/mailman/listinfo

Thanks for you interest in RPM Fusion.

~ The RPM Fusion Team (http://rpmfusion.org)

== More details ==

=== Reminder for the folks that plan to yum-update to Fedora 10 ===

If you have rpmfusion packages installed on your system already and plan
to live-update to Fedora 10 using yum then please leave the rpmfusion
repositories enabled for the big "yum update" run. Thus you'll get all
the updated packages from RPM Fusion as well, which is important, as
their dependencies get fulfilled by the Fedora 10 packages. That's not
the case for the old packages that are on your system right now -- those
in fact have dependencies on the older Fedora bits you are about to
update, which will lead to a lot of trouble.

=== Examples to get the most important bits from RPM Fusion ===

Once you installed the release rpm you can install software using the
graphical software installation tools which are part of Fedora. As
root-user you can also use yum on a command line to install packages;
for example:

~ * if you'd like to install Xine (a video player), run
{{{
# yum install xine-lib-extras-freeworld xine
}}}
That will also improve Totem capabilities, as the Totem from F10 can use
xine as backend as well.

~ * if you prefer MPlayer, run
{{{
# yum install mplayer-gui
}}}

~ * if you prefer VLC, run
{{{
# yum install vlc
}}}

~ * do you want to get enhanced audio and video support in applications
that rely on GStreamer? Then run this:
{{{
# yum install gstreamer-plugins-ugly gstreamer-plugins-bad gstreamer-ffmpeg
}}}

~ * do you want to get the latest Nvidia drivers? Then run this:
{{{
# yum install kmod-nvidia
}}}

~ Note that there are also "kmod-nvidia-173xx" and "kmod-nvidia-96xx" --
those are the legacy drivers that support older GeForce cards that are
not supported by the latest drivers.

=== Problems? ===

Let us know via http://bugzilla.rpmfusion.org/

=== Need support? ===

Many people in #rpmfusion on freenode and on
rpmfusion-users@... know how to help.

=== Developer contact ===

Meet us in #rpmfusion on freenode or join the mailing list at
http://lists.rpmfusion.org/mailman/listinfo

=== EOF ===

End of file
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkksCSYACgkQUjQh93TopkG1JgCfdXbO7+EBLtJ808FT9P4CHXL6
k4cAoIdiJdzsZRI2FcSlpc16WtQj0GOB
=cS2P
-----END PGP SIGNATURE-----

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

Fedora 10 around the corner!

2008-11-24T17:10:34Z

As we all get ready for tomorrow's release, I wanted to congratulate
everyone in the community on Fedora 10, and say a few words of thanks
as well.

For Fedora 9, I wrote an enormous congratulatory email tome. I'm
pretty sure that if printed and left somewhere without anyone keeping
an eye on it, it would actually collapse into a singularity and devour
the entire planet. So I'll try to keep it more brief this time, even
though it's tough for me to pack all my gratitude and pride in this
community into a tiny space.

First, I'd like to thank Brian Pepple and FESCo, Francesco Ugolini and
the FAMSCo, Dimitris Glezos and the FLSCo, Karsten Wade and the FDSCo,
and all the other steering committees and groups that kept up a steady
presence of open, public meetings throughout the release to ensure
that work was progressing well and transparently. These folks step up
not just to do productive work on their own, but to make sure that
other community members can do the same, with just as much
organization as is required, but no more than is needed. You folks
represent the best of what free software communities can achieve in
executing the best-laid plans.

A big thank-you to "Marvelous" Mike McGrath and our intrepid
Infrastructure team, without whom Fedora would have been in a shambles
following the intrusion this past August. These folks rebuilt our
entire community platform, spending many sleepless nights so our
nights would be restful and secure. And they did it all with the same
software we make available for everyone worldwide -- proving beyond a
shadow of a doubt that free software is truly the best way to achieve
stability, scalability, and availability. There are not enough gold
medals in the Olympics for you guys, as far as I'm concerned.

A huge shout goes out to our Ambassador teams worldwide -- over 600
Ambassadors already, and more every month. Just as they have been for
years, they're out there bringing local communities together around
free software. Every day they are cultivating a grassroots effort
that brings an increasing number of contributors into the world of
free software, and at the same time brings the four foundations of
Fedora to the people -- "Freedom, Friends, Features, First."

Speaking of which, another big burst of gratitude goes to Máirín
Duffy, Nicu Buculei, and the rest of our awesome Artwork team. Their
work spans the length of every release, because it's not just a
desktop background theme -- even though they produce another
miraculously beautiful one of those every time, like Fedora 10's
"Solar" theme. They also produce designs for every part of our
community, like software project sites, banners, stickers, fliers,
press contact letters, and posters. If you haven't seen them already,
you're going to love the new Four Foundations media; it's spectacular.

Thank you(*) also to the hundreds of translators work on the projects
where Fedora provides the upstream. Because of them, free software
will be even more useful in the hands of millions more people around
the world. I sometimes switch my computer to a different locale just
so I can see Fedora, in a sense, through someone else's eyes, and I'm
always surprised and gratified to see how thorough that experience is.

Kudos to our Websites team, now led by wunderkind Ricky Zhou, and
their dedicated work to make sure that our redesigns and content make
it out in one piece, on time and smoothly.

Thanks to Will Woods, James Laska, Jon Stanley, and the rest of our QA
team and the vital Bug Zappers for taking on some of the hardest
problems out there: The elusive search for quality and robustness in
our releases and our processes, and ensuring that our users and
developers have a positive experience using the Fedora distribution.
I spent a month or so helping triage bugs earlier this cycle, and I
hope everyone will pitch in a bit for Fedora 11 to do the same.

Packagers, where would be without you? You help keep the software
available for everyone 24/7, always making sure that whether someone's
a wee-hours developer or a day-job professional, he or she gets the
software needed to do the work. Thank you for providing over 10,000
reasons (and counting) why Fedora is for anyone and everyone.

Thanks to our Documentation team, particularly some of our new folks,
for spinning up brand-new, easy ways for people to get involved in
projects like wiki gardening, the release notes, and our various
end-user guides. I am very much looking forward to your good work
continuing into the next release.

Thank you to Jesse Keating, Josh Boyer, and our whole Release
Engineering team for keeping a close eye on our schedule and actually
getting our releases out the door, from Alpha to Beta to Preview to
"Cambridge" itself, and everything in between. I still don't know how
you guys get all this done and still have time for email, family, and
the occasional frosty beverage, but my hat's off to you guys.

I want to personally thank three very special individuals who work
incredibly hard behind the scenes at least as hard as they do in front
of them -- the indomitable Fedora Program Manager John Poelstra, who
has not only shepherded innumerable Fedora meetings successfully, but
who maintains a great attitude and is such a joy to work with on a
personal level; the amazing Tom 'spot' Callaway, who not only juggles
Perl in his sleep and maintains an encyclopedic knowledge of all
things Anuran, but also manages Fedora Engineering inside Red Hat with
a sure and steady hand; and Max Spevack, my predecessor and now
manager of the Community Architecture team, who's always ready to lend
an effort wherever it's required that day.

Last, but certainly not least, I want to thank you, the reader, if I
haven't already. You're part of our community too, and without you we
would be diminished. Free software isn't just about bits and bytes,
it's about people, about doing something real, something tangible,
something lasting for your fellow human beings. And with your help,
the Fedora Project has been able to lead in free software innovation
for over five years and ten releases now. Each and every one of you
-- pat yourself on the back for a job well done.

OK, I failed miserably at making it short, and I am certain that I
left someone out in my desire to thank everyone. If it was you, Dear
Reader, please accept my humble apologies and know that Fedora would
not be where it is today without your hard work and perseverance.
Thank you from the bottom of my heart on behalf of your fellow
community members and the millions of users whom you've helped.

Now, let's all look forward to Fedora 10, and beyond!

= = =
(*) 謝謝, merci, אַ דאַנק, ευχαριστώ, धन्यवाद, muchas gracias, நன்றி, tak,
kia ora, terima kasih, شكرًا, ขอบคุณ, ありがとう!

--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

--
fedora-announce-list mailing list
fedora-announce-list@...
https://www.redhat.com/mailman/listinfo/fedora-announce-list

attachment0 (196 bytes) Download Attachment