To use the local mirror for yum updates, edit /etc/yum.repos.d on the Rawhide system, commenting out the mirrorlist entry and adding a baseurl entry pointing to the local mirror:
[development]
name=Fedora Core - Development
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/
# This line is commented by the addition of # at the start
# of the line, which disables the use of repositories on the standard
# mirrorlist
#mirrorlist=http://fedora.redhat.com/Download/mirrors/fedora-core-rawhide
# This line directs yum to the local mirror
baseurl=http://
bluesky /fedora/os/
enabled=1
gpgcheck=0
9.4.1.5. Rawhide-related mailing lists
The fedora-devel-list and fedora-test-list discuss Rawhide-related developments and issues, and include automated reports describing changes that have been made to Rawhide packages.
Rawhide is a standard yum repository. Package maintainers submit package source to the Fedora build system, which builds the packages periodically and emails a report to the fedora-devel-list and fedora-test-list . The report looks like this:
Date: Fri, 14 Jul 2006 09:28:29 -0400
From: buildsys@redhat.com
Subject: rawhide report: 20060714 changes
To: fedora-devel-list@redhat.com, fedora-test-list@redhat.com
Message-ID: <200607141328.k6EDSTJ5031177@hs20-bc2-6.build.redhat.com>
New package xorg-x11-drv-amd
Xorg X11 AMD Geode video driver
Updated Packages:
ImageMagick-6.2.8.0-1.1
-----------------------
* Wed Jul 12 2006 Jesse Keating - 6.2.8.0-1.1
- rebuild
anaconda-11.1.0.57-1
--------------------
* Thu Jul 13 2006 David Cantrell - 11.1.0.57-1
- Fix unknown error on shadow file (#196705, clumens)
- Removed inet_calcGateway (clumens)
- Don't guess gateway address in text network UI (#197578, clumens)
- Change iutil.copyFile calls to shutil.copyfile (clumens)
- Removed DRI enable/disable code from xsetup (clumens)
- Removed copyFile, getArch, memInstalled, and rmrf from iutil (clumens)
- Don't pass command as first argument to subprocess calls (clumens)
- Added network debugging mode for readNetConfig( ) in loader
- Removed "BOOTP" string from loader network config UI
- Added new dialog for network device config in stage2 (katzj)
- Write gateway address to correct struct in manualNetConfig
- Removed IP_STRLEN macro since that's moved to libdhcp
- Link and compile libisys with libdhcp
- Added back 'confignetdevice' and 'pumpnetdevice' in iutil
- Removed isys_calcNetmask and isys_calcNS (clumens)
- Added xkeyboard-config to fix VT switching (katzj)
...(Lines snipped)...
Broken deps for i386
----------------------------------------------------------
anaconda-runtime - 11.1.0.57-1.i386 requires syslinux
gnucash - 2.0.0-2.1.i386 requires libgsf-gnome-1.so.114
mkbootdisk - 1.5.3-2.1.i386 requires syslinux
perl-suidperl - 4:5.8.8-6.1.i386 requires perl = 4:5.8.8-6
systemtap - 0.5.8-2.1.i386 requires libdw.so.1(ELFUTILS_0.120)
Broken deps for ia64
----------------------------------------------------------
gnucash - 2.0.0-2.1.ia64 requires libgsf-gnome-1.so.114( )(64bit)
perl-suidperl - 4:5.8.8-6.1.ia64 requires perl = 4:5.8.8-6
systemtap - 0.5.8-2.1.ia64 requires libdw.so.1(ELFUTILS_0.120)(64bit)
...(Lines snipped)...
The report lists new and removed packages, the latest changelog entries from updated packages, and a list of broken dependencies for each architecture. Developers, package maintainers, and testers review this report daily, discussing the results on the mailing lists.
The build system places the resulting RPMs on a master server, where they are periodically retrieved by the mirror servers and made accessible to the world. Individual systems use the standard yum client and transfer protocols (HTTP or FTP) to access files on the mirror servers.
The rsync tool works by comparing files and directories on the client and server systems and transferring only the files that have changed. This comparison can use combinations of file-modification timestamp, file size, and checksum, depending on the command-line options selected.
9.4.3.1. ...testing upcoming Fedora Core versions without performing a network installation or update?
The Fedora Core project produces at least three test releases before each Fedora Core release. These test releases are effectively clean snapshots of Rawhide released in ISO form; they can be installed from optical disc using the same method as Fedora Core releases (see Chapter 1 and Lab 10.3, "Preparing Alternate Installation Media ").
You will find announcements of test releases on the Fedora web site and the fedora-announce-list . The test releases may be downloaded from test directories in the Fedora mirror servers; the releases are numbered in increments of 0.01 starting with a version number that is 0.1 less than the upcoming Fedora Core version numberso Fedora Core 7 test 1 will be found in the directory test/6.90 , and FC7t2 will be in test/6.91 .
9.4.3.2. ...using other repositories with the Rawhide development repository?
That's not usually recommended. Repositories such as Livna (and even Fedora Extras) do not update their packages to work with new Fedora Core releases until just before the official release of a new Fedora Core version.
9.4.4. Where Can I Learn More?
The Fedora Testing Guide: http://www.fedoraproject.org/wiki/Testing
The manpages for yum and rsync
List of Fedora mirrors: http://fedora.redhat.com/Download/mirrors.html
Torrent trackers for Fedora Core, including test releases: http://torrent.fedoraproject.org/
The BitTorrent home page: http://bittorrent.com/
9.5. Participating in Fedora Projects
Within the Fedora Community, there are many different projects aimed at developing and improving various aspects of Fedora Linux. Regardless of your skill set, interests, or experience, there is probably a role that is perfect for you in one of the projects. Becoming directly involved in a Fedora project contributes back to the Fedora community and can build your skill and reputation.
A list of Fedora Projects is maintained at http://fedoraproject.org/wiki/Projects . Each project has separate standards and requirements for participation, so a good place to start is by reading the project outline to determine the participation requirements, then joining the relevant mailing lists to meet and get to know other project members.
Here are some projects to consider:
Читать дальше