perl-devel will be removed from the f8 buildroots
by Robin Norwood
Hi,
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:
BuildRequires: perl(ExtUtils::MakeMaker)
But you should also watch the build output to make sure tests aren't
being skipped due to other missing modules.
-RN
--
Robin Norwood
Red Hat, Inc.
"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching
16 years, 10 months
koji.fedoraproject.org Unplanned outage | 6/28/07 - 6:00PM EDT
by Jesse Keating
O U T A G E R E P O R T F O R M
===================================
Incident Date:
6/28/07
Incident Time:
6:00PM EDT
Elapsed Time of Incident:
Ongoing
People/Groups Impacted:
Package builders / update tool / koji web services
Site Affected:
koji.fedoraproject.org
Description:
The koji.fedoraproject.org server is experiencing very high load. Attempts to
login and address the load issue are under way.
Future Recommendations:
Continue investigating process issues with httpd (if that proves to be the
culprit once more).
--
Jesse Keating
Release Engineer: Fedora
16 years, 10 months
Fedora 8's FUDCon
by Max Spevack
Yesterday the Fedora Board made the decision not to hold an in-person
FUDCon for F8. Like you, I'm a disappointed, but I'm also excited for
us to try out an organized, weekend-long virtual hackfest (more below).
The Board also began planning for the F9 FUDCon, which would be held
around January or February 2008. This earlier planning should give us
time to resolve the kinds of problems we've faced with this short-notice
FUDCon.
There's a couple of reasons for the cancellation of the Fedora 8 FUDCon.
The first is the most obvious of all -- we have been unable to secure a
location that could offer us a place for both a FUDCon and a hackfest.
Additionally, the administrative overhead for putting on a FUDCon is
very high. Becoming a FUDCon event planner becomes a full time job for
a couple of people in order to make the event happen. Especially this
late, just getting the logistics for a FUDCon worked out would take up
lots of people's time that we can't really afford.
Also a factor is the financial cost of a FUDCon. With the comparatively
smaller scope of Fedora 8, it seems wise to save money now by not going
through the whole FUDCon process, and allowing the financial and budget
planners to have more opportunity to make a larger commitment to Fedora
9. Fedora 9 will be a bigger release, and I'd rather have one really
good FUDCon and hackfest then, than try to do two of them on the cheap.
The feature list for Fedora 8 is coming together very well, and we're
planning over the next few weeks how we can do a virtual hackfest for
F8. The idea is to pick some days, probably the same weekend (4, 5
August), and organize energy around people having an IRC-based hackfest
that weekend.
We can capture some of the energy that would come from a hackfest, but
in a way that has significantly less overhead and organizational costs.
Part of the danger of trying to plan and discuss things in public from
the very beginning is that when you're forced to pull the plug on
something, you have to send out emails like this. I'm willing to accept
that, because overall I think we get a bretter experience for everyone
by doing our planning in the open.
Sorry, folks, for the short notice coming and going! We really
appreciate your understanding, flexibility, good ideas, and patience.
--Max
--
Max Spevack
+ http://fedoraproject.org/wiki/MaxSpevack
+ gpg key -- http://spevack.org/max.asc
+ fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21
16 years, 10 months
Packaging guidelines: Directory ownership clarification
by Tom Callaway
Guidelines change:
http://fedoraproject.org/wiki/Packaging/Guidelines
The following addendum was made to the FileAndDirectoryOwnership
section:
Another exception for directory ownership in packages is when there is
no clear dependency hierarchy.
An example:
Foo-Animal-Emu puts files into /usr/share/Foo/Animal/Emu
Foo-Animal-Llama puts files into /usr/share/Foo/Animal/Llama
Neither package depends on the other one. Neither package depends on any
other package which owns the /usr/share/Foo/Animal/ directory. In this
case, each package must own the /usr/share/Foo/Animal/ directory.
~spot
16 years, 10 months
koji.fedoraproject.org Unplanned outage | 6/25/07 - 1:30PM EDT
by Jesse Keating
O U T A G E R E P O R T F O R M
===================================
Incident Date:
6/25/07
Incident Time:
1:30PM EDT
Elapsed Time of Incident:
Ongoing
People/Groups Impacted:
Package builders / update tool / koji web services
Site Affected:
koji.fedoraproject.org
Description:
The koji.fedoraproject.org server is experiencing very high load. Attempts to
login and address the load issue are under way.
Future Recommendations:
Continue investigating process issues with httpd (if that proves to be the
culprit once more).
--
Jesse Keating
Release Engineer: Fedora
16 years, 10 months
Bugzilla Products for Fedora Core and Fedora Extras merged
by Toshio Kuratomi
Greetings,
Until yesterday, bugzilla.redhat.com was living in the past,
holding onto the former glory memory of a separate Fedora Core and
Fedora
Extras. Thanks to the hard work of our bugzilla admins, bugzilla has
caught up to the present and those products have been united under one
simple name, Fedora. All old bugs targeting Fedora Extras or Fedora
Core now target Fedora instead. All packages which were once a part of
Fedora Core or Fedora Extras are now members of Fedora.
As part of this change, owners.list has been updated. This was largely
a trivial replacement of "Fedora Extras" or "Fedora Core" with "Fedora"
but in a few places the package had been present in both Core and
Extras. For these, the packages have been merged with the owners and
initialcc list for each being combined. This means that a few packagers
in Extras who gave up their packages to Core maintainers or vice versa
may now be listed as a co-owner.
You can check whether this is the case for any of your packages by
checking out the current owners.list from cvs:
CVSROOT=:ext:URSERNAME@cvs.fedora.redhat.com:/cvs/extras cvs co owners
and verifying that your name is associated with the packages you wish.
If everything is fine, nothing needs to be done. If you want to make a
change, please follow the procedure here:
http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure
to make your change requests.
Thanks,
Toshio
16 years, 10 months
OCaml Guidelines
by Toshio Kuratomi
The guidelines created by our hardworking OCaml SIG have been approved
by the Packaging Committee and FESCo. Everyone who has been wondering
about the difference between a cmi, cmx, and cma can visit::
http://fedoraproject.org/wiki/Packaging/OCaml
for the official word on what they mean and how to package them.
-Toshio
16 years, 10 months
