Fedora 13 Software Translation
by Noriko Mizumoto
It is 16-Feb today, Software String Freeze.
All Fedora translators are expecting NO more String change in any
Fedora13 packages, and looking at to complete as many translation as
possible from now on till the translation deadline. Please make sure
that POT is up-to-date with latest strings.
noriko
Fedora Localization Project
14 years, 2 months
Fedora 13 Branching (and thus freezing) tomorrow
by Jesse Keating
Tomorrow (or well the day after tomorrow to some of you) we will be
branching off F-13 in CVS. This will start at 00:00 UTC on Feb 17.
After this point, when the outage ends, all builds for Fedora 13 will
happen from the F-13/ branch in CVS. All builds must go through bodhi
in order to make it into Fedora 13. When you submit your build to
bodhi, please push to testing first, as it will allow your peers to test
your update before it makes it into the Fedora 13 tree.
For those of you who maintain a critical-path package, net positive
karma from releng and/or QA plus at least one more net positive karma is
required before your package can move out of testing and into Fedora 13.
We're still working on the wiki documentation for all of this, but hope
to have a good chunk in place tomorrow.
Builds from devel/ will continue to be pushed to rawhide each night and
devel/ can be considered open for Fedora 14 development items.
https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan has some
info about the upcoming change and base information we'll use when
editing the other wiki pages.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
14 years, 2 months
Notice: dnssec-conf updates in Fedora 11 and 12
by Paul W. Frields
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Fedora Project recently issued an update to the dnssec-conf
package, to fix an issue that caused Fedora 11 and 12 systems using
BIND (named) to put an inordinately heavy load on RIPE nameservers.
However, this update has been found to break some BIND configurations
as seen in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=563232
The problem occurs in these packages:
dnssec-conf-1.21-3.fc11
dnssec-conf-1.21-7.fc12
To determine if your system is affected, run the following command:
rpm -q dnssec-conf
If one of the above package descriptors does not appear, your system
is not affected and you may safely ignore this message. If you are
affected, please continue reading.
== Workaround ==
If you have already accepted this update, you can downgrade the
package and start the failed BIND (named) daemon again using these
commands:
su -c 'yum downgrade dnssec-conf'
su -c 'service named start'
== Solution ==
System owners running BIND name servers on Fedora 11 or 12 systems are
advised not to accept the specific dnssec-conf pacakge updates listed
above. There are several ways to avoid these specific updates.
* If you use the PackageKit graphical client, or another graphical
client, deselect the dnssec-conf update in the dialog that lists
package updates.
* If you use the yum command-line client, use this command to exclude
dnssec-conf from the list of packages to be updated:
su -c 'yum --exclude=dnssec-conf update'
== Remediation ==
A new update is being prepared to address this problem for Fedora 11
and 12 users, and will be pushed to our mirrors as soon as possible.
Users who are not running BIND nameservers (named) on their Fedora 11
and 12 can safely disregard this notice. When the new updates are
pushed, a follow-up announcement will be made here. At that time,
affected system owners can safely accept the replacement updates.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLceHHrNvJN70RNxcRAoY1AKDGuYgvJvoRi6sYpBsl3vbYyiMy2QCg3Beh
KNbq55w4R2A4qtLCwQosJPg=
=zRrs
-----END PGP SIGNATURE-----
14 years, 2 months
Fedora 13 Alpha Freeze in one week (minus one day)!
by Jesse Keating
I forgot to send this out yesterday, but the Fedora 13 Alpha freeze is
this coming Tuesday.
https://fedoraproject.org/wiki/Alpha_Freeze_Policy
This time around things are going to be different and interesting.
We're in the middle of deploying No Frozen Rawhide¹ which will change
how freeze breaks are requested. The intention is to use bodhi to
submit update requests for Fedora 13. When requested for testing, these
will be published to the fedora 13 updates-testing repo where peers can
review and provide karma on your request. If marked stable, they will
go into pub/fedora/linux/development/13 and be included in the Alpha.
We're still working on the documentation for all of this.
More announcements to come!
¹) https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
14 years, 2 months
No Frozen Rawhide coming soon! New paths on mirrors!
by Jesse Keating
With a burst of testing last week, we confirmed that our infrastructure
should handle No Frozen Rawhide
http://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal . Feature
freeze is tomorrow, which is when we'd branch our source control, and
when we'd enact no frozen rawhide. The timing is a bit tight, so we may
have to delay a day or two in order to get this done, but the end result
would be two nightly trees being published.
/pub/fedora/linux/development/rawhide/ will become the new path of
Rawhide. It will continue to not have install images, and it will be
the place where builds from the devel branch in CVS go to. It'll be
Fedora 14 intended content.
/pub/fedora/linux/development/13/ will become the new path of the
branched Fedora 13 content. This is where builds from the F-13/ branch
in CVS will go, after they pass through bodhi as "stable".
/pub/fedora/linux/updates/testing/13/ will be where potential Fedora 13
builds go after passing through bodhi as "testing". This is where
you'll find the latest stuff proposed for freeze break and where testing
and peer review of these freeze breaks will happen. When a maintainer
feels enough testing has happened, or enough karma triggers the bodhi
auto request, the build will be marked "stable" and show up in the
development/13 tree at the next nightly compose.
Even though we've been talking about No Frozen Rawhide for quite a
while, this will indeed surprise some people, so we will be trying to be
extra verbose in what we are doing over the next few days, and always
available for questions. Unfortunately I have to step out for a few
hours and thus any responses to this email will not be seen by me for a
few hours.
You can find us at #fedora-devel on Freenode if you wish to discuss
live, or help us with documenting these changes and setting expectations
with our developers and users.
I will be updating
http://fedoraproject.org/wiki/No_Frozen_Rawhide_Implementation later
today with our current progress and plans.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
14 years, 2 months
qt-4.6/kde-4.4 updates
by Rex Dieter
the kde-sig is beginning work to prepare qt-4.6/kde-4.4 updates, which
will be landing in f11 and f12 koji buildroots shortly.
Maintainers of qt/kde packages, please be aware of this if doing builds
yourself. If you have any concerns or questions, please drop by
#fedora-kde on freenode/irc (or followup to this on -devel list).
-- Rex
14 years, 2 months
Outage Notification - 2010-02-04 23:00 UTC
by Mike McGrath
There will be an outage starting at 2010-02-04 23:00 UTC, which will last
approximately 1 hour.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-02-04 23:00 UTC'
Affected Services:
Bodhi
Buildsystem
CVS / Source Control
Database
Fedora Account System
Fedora Community
Fedora Hosted
Fedora Package Database
Mail
Mirror System
Translation Services
Websites
Unaffected Services:
DNS
Fedora People
Fedora Talk
Torrent
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/1964
Reason for Outage:
Network team is working on stuff in PHX2. This is a "there may be an
outage" type deal so it's quite possible this will have no impact on us.
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.
14 years, 2 months
