Due to an ongoing issue with booting many Dells (and some Toshiba)
systems via CD, we've had to delay the release of Test1. The good news
is that we've found a solution and a new kernel is building in koji as
I type this. The bad news is that there is not enough time to get the
output of that build and spin it into a set of trees for release on
Thursday. As such, we're slipping the release to Tuesday of next
week, August 7.
This gives us time to consume the kernel build and generate a release
candidate tree early tomorrow, and spend all day, and all of Thursday
beating on it for real blocker issues. Friday morning is our Go/No Go
point. If all things are Go, we'll be handing it off to mirrors and
giving them the weekend and Monday to sync up the release. If we're No
Go, we will determine then a new release date.
All the gory details can be found at
Release Engineer: Fedora
If you use enterprise-class Linux (EL) distributions derived from
Fedora, such as Red Hat Enterprise Linux or CentOS, we have something
very exciting for you.
Ever find yourself rebuilding one of the high-quality Fedora packages
for your EL version because it didn't ship with the EL distro?
Friends, there is a new way. May we introduce ...
Extra Packages for Enterprise Linux (EPEL)
EPEL is a community of package maintainers working from inside of
Fedora. Many are the same people who maintain the Fedora version. Yet,
there room for new packages and contributors. Currently, around 1000
packages are available, and we've been growing at the rate of several
dozen packages every week.
How to use EPEL:
You can look for packages here:
Looking for a package not in EPEL or other questions?
Re https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249435 , there
are a number of packages that need to be rebuilt (and subsequently
tagged for the test release). The list of packages is the intersection
of packages that were built with the combination of binutils >=
188.8.131.52.17-2 && binutils <= 184.108.40.206.17-4 && gcc >= 4.1.2-16 and not noarch. The list is at http://jkeating.fedorapeople.org/needrebuild While not every package will show errors, we're going to rebuild them just in case.
Fedora rel-eng will be working to rebuild these packages today. If you
were already rebuilding one of these, please drop a line to
rel-eng(a)fedoraproject.org so that we don't step on each other.
Release Engineer: Fedora
The Fedora Engineering Steering Committee would like to remind maintainers
that a license change in a package is a very serious event - it has as many,
if not more, implications for related packages as ABI changes do.
Therefore, if your package changes license, even if it just changes the
license version, it is required that you announce it, whether on this list
Note that any license change to a more restrictive license or license
version may affect the legality of portions of Fedora as a whole; ergo,
FESCo reserves the right to block upgrades of packages to versions with
new licenses to ensure the legal distribution of Fedora.
Please contact FESCo if you have any questions.
Tips for Fedora Package Maintainers when issuing updates.
1) Push or Revoke Updates-Testing
Please don't forget to deal with your packages sitting in
updates-testing. Some packages were sitting here for more than a month.
Your Updates Testing package may be marked as "Stable" if they are ready
to be pushed as an official update. If you want to cancel an update, or
if it was superseded by a newer package, you will want to "Unpush" it.
2) EVR Version Problems
Currently F7 uses Bodhi (the Fedora Updates System) while FE-6 uses the
legacy Extras buildsystem. This can sometimes create EVR promotion
problems between the distributions. Example:
2) foo-1.2.4-1.fc7 is pushed to F7 updates-testing
foo-1.2.4-1.fc6 is built for FE-6
3) FC6 version of foo is "newer" than foo in F7, because the FC6 package
went directly into the repository while the F7 package is only in testing.
Build for FE6 only *after* the F7 update has been officially pushed.
On Monday, perl-devel will be removed from the f8 buildroots. This
means that if you try to build a perl-* package that uses the perl build
tools, you will need to add those tools to the BuildRequires for the
package. The most common will be:
But you should also watch the build output to make sure tests aren't
being skipped due to other missing modules.
Red Hat, Inc.
"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching