In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
Auto Upgrading YUM Not Worth It
A discussion over the possible ways to upgrade from Fedora 10 to Fedora 11 was started by Gerry Reno when he asked why
Fedora 10 only presented
Rawhide as an option and not
Fedora 11 Alpha.
A quick answer posted by GianlucaSforna mentioned the technical difficulties of tracking the versions of packages included in the alpha release. Paul W. Frields was concerned that anyone trying such an upgrade made sure to update
rpm before upgrading. This latter point spawned a longish thread in which the possibility of making
YUM take care of checking to see whether a newer version of itself or
rpm is available.
How to Update from Fedora 10 to Rawhide
yum update rpm
Fedora 10 repository enabled and then to enable the
Rawhide repository and do a general:
Unfortunately this seemed to not work for "nodata" and Michael A. Young's suggestion that a "[...] temporary issue with F10 having a more recent version of audit-libs than rawhide [...]" seemed like a promising lead. "Nodata" resolved problem by using the rescue CD to do a "
rpm -e --nodeps" and then "
Fedora 11 Beta Slips by One Week
Jesse Keating announced that Release Engineering, QA and maintainers had agreed that the beta release of
Fedora 11 would slip by seven days due to several issues mostly related to the rewrite of
Finding the Source
# yum install yum-utils # yumdownloader --source package_name
Eric Sandeen wondered if it might be better to use the upstream repositories and Joe explained that his objective was to build a new kernel from source and use KGDB to gain familiarity with the source. Todd Zullinger pointed to a goldmine of information on the topic on the wiki.
How to Open ACLs and Find Non-responsive Maintainers
A couple of related threads dealt with the need to deal with a package which lay dormant apparently due to maintainer inactivity.
Manuel Wolfshant had inquired earlier in the week about the allowing the provenpackagers to fix the
gdal package. Jon Stanley promised to re-add a ticket dealing with the issue to an upcoming FESCo meeting.
In a separate thread the latest Rawhide Report led Kevin Kofler to ask for an opening of the ACLs on
gdal so that it could be fixed for multiple dependent packages. When Jesse Keating asked Alex Lancaster if he started the non-responsive maintainer process the answer appeared to be that it was Jesse himself. In an aside MilosJakubicek provided links to the current process. Alex seemed to demonstrate clearly that the maintainer was inactive.
- GDAL is a library to handle Geographic Information Systems data