In a few hours, updates for Fedora 8 and Fedora 9 will start hitting
mirrors. These updates are designed to transition users from our old
repo locations to new locations that have all our updates re-signed with
a new set of keys.
Most users will simply need to apply the offered updates, and later
apply any further updates, and verify/import the new GPG key.
The process to getting new updates is two stage.
Stage 1) Users configured to get updates from existing repos will see a
small set of updates available in the next few hours/days. These
updates include fedora-release, PackageKit, gnome-packagekit, and unique
(for Fedora 8, only fedora-release is offered). These updates should be
applied as soon as possible.
Stage 2) Once the above updates have been applied, your update tools
(yum, PackageKit, pirut) will see a new repository and a larger set of
updates available. This is your new standard flow of updates, that will
continue to see new updates as the lifetime of Fedora 8 and 9 progress.
There will be further milestones in the future that involve redirection
of release package repos to match that of updates, and removing of old
gpg key from rpm trust.
For more details and an FAQ, please see
https://fedoraproject.org/w/index.php?title=Enabling_new_signing_key
--
Jesse Keating
Fedora -- FreedomĀ² is a feature!
identi.ca: http://identi.ca/jkeating
As you well know, we have been working hard to get updates for 8 and 9
flowing again, complete with new package signing keys. Discussion has
been somewhat quiet on this front as we've all had our heads down and
have been working hard toward a solution, one that involves little to no
manual effort on behalf of our users.
Today we've reached a major milestone in this progress. We have done a
successful compose of all the existing and as of yesterday pending
updates for Fedora 8 and Fedora 9, all signed with our new keys. These
updates will soon hit mirrors in a new set of directory locations. What
we don't have quite yet is the updated fedora-release package in the old
updates location that will get you the new keys and the new repo
locations. The last mile testing of this update requires that new
updates be live on the mirrors.
Due to the size of the resigned updates, it may take a good while for
our sync process. This may delay getting the new fedora-release out
until tomorrow, but we'll be working hard on it.
While we're working on this update, we'll also be drafting a FAQ page to
explain to users what it is that we're doing, and hopefully answer some
of the questions that will come up. This document will be living
though, and as you encounter questions yourself, or questions via one of
our many avenues of support (email, IRC, forums, LUGS, etc..) please
help us in growing that document. Announcements regarding the location
of said document and how to help with content will be coming shortly.
We deeply appreciate the enormous magnitude of patience you the greater
community has shown us the Fedora project as we work though these
serious issues. It is a great testament to how wonderful it is to work
in and with the Fedora community.
--
Jesse Keating
Fedora -- FreedomĀ² is a feature!
identi.ca: http://identi.ca/jkeating
Greetings.
In the past, interested parties could bring matters to the attention of
FESCo in several ways: Mailing the chair, following up to the schedule
posting on the devel list asking for a new topic to be added, or
attending meetings on irc and bringing up the topic at the end of the
meeting in the Open Discussion phase.
While these methods work well for issues that simply need a bit of
discussion and a decision, longer term issues that should be tracked
and discussed further sometimes are forgotten.
To help solve this issue, and to make it easier for folks to bring an
issue before FESCo, I have asked Fedora Infrastructure to setup a trac
instance for FESCo to track tasks and handle new issues.
New issues for FESCo can now be filed at:
https://fedorahosted.org/fesco/
Please feel free to file issues there.
Note that FESCo (Fedora Engineering Steering Committee) handles the
process of accepting new features, the acceptance of new packaging
sponsors, Special Interest Groups (SIGs) and SIG Oversight, the
packaging process, handling and enforcement of maintainer issues and
other technical matters related to the distribution and its construction
Thanks.
kevin
Greetings.
In the past, interested parties could bring matters to the attention of
FESCo in several ways: Mailing the chair, following up to the schedule
posting on the devel list asking for a new topic to be added, or
attending meetings on irc and bringing up the topic at the end of the
meeting in the Open Discussion phase.
While these methods work well for issues that simply need a bit of
discussion and a decision, longer term issues that should be tracked
and discussed further sometimes are forgotten.
To help solve this issue, and to make it easier for folks to bring an
issue before FESCo, I have asked Fedora Infrastructure to setup a trac
instance for FESCo to track tasks and handle new issues.
New issues for FESCo can now be filed at:
https://fedorahosted.org/fesco/
Please feel free to file issues there.
Note that FESCo (Fedora Engineering Steering Committee) handles the
process of accepting new features, the acceptance of new packaging
sponsors, Special Interest Groups (SIGs) and SIG Oversight, the
packaging process, handling and enforcement of maintainer issues and
other technical matters related to the distribution and its construction
Thanks.
kevin
There will be an outage starting at Y2008-09-05 01:00 UTC, which will
last approximately 2 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2008-09-05 01:00 UTC'
Affected Services:
Websites
Database
Unaffected Services:
CVS / Source Control
Buildsystem
DNS
Mail
Torrent
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/808
Reason for Outage:
Need to perform maintenance on the db2 database server
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email
to track
the status of this outage.
-Toshio
The Fedora 10 Beta freeze is scheduled for the 19th of Aug, one week and
one day away. I know it hasn't been very long since the Alpha release,
but that's how we roll here in the land of 6 month release cycles.
Beta freeze also marks the Feature freeze, so it is very important that
you get your features into working, testable shape by then, or be
prepared to try your feature again for Fedora 11.
We'd like to treat rawhide as a slushy freeze at this point, we'll be
doing full composes against rawhide to test for various things and be
ahead of the curve come actual freeze time, so we'd like you to not land
any really dangerous changes without extensive testing first, and
notification to the Fedora lists about your scary change. If we all
work together we can get through the beta freeze period quickly and be
on to the bugfixing mode after beta releases.
http://fedoraproject.org/wiki/Releases/10/Schedule is the current
schedule, although releng/Fesco/Board has the ability to change the
schedule as needed. This week's meetings of the various boards, sigs,
groups, etc.. should focus on Beta readiness. It would be good to take
a moment to see what state your area of interest is in, and how likely
it would be that said area of interest will be in a "testable" shape by
the Beta freeze. If more (reasonable) time is needed, now is the time
to let the project know so that we can effectively manage the remainder
of our release schedule.
Thanks for all your hard work in making Fedora 10 great!
--
Jesse Keating
Fedora -- FreedomĀ² is a feature!
identi.ca: http://identi.ca/jkeating