In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
Emacs, Glibc, Malloc and i586
As the pressure to stick to the
Fedora 11 release schedule built up some glitches arising in part from the decision to support i586 instead of i686 (see FWN#162) led to tense words.
Reports trickled in of problems with
emacs in rawhide. Per Bothner reported both that
emacs-23.0.91 threw an "Invalid regex: Unmatched ( or \\(" and that
emacs-23-0.92 was responding excruciatingly slowly. Ulrich Drepper speculated to that the regexp problem was due to some changes to
glibc. A bugzilla report by Andy Wingo expanded on the problem and drew comments suggesting that
mysql were also failing to due
glibc changes. Jakub Jelinek thought they were different problems with the
emacs errors being due to
TomLane asked what was going on with
glibc reverting to an earlier version in rawhide. Jesse Keating responded that
glibc for the
i586 architecture was broken for all versions after beta. After Panu Matilainen commented that
glibc.i586 was so broken that
rpm could not even read its own configurations Ulrich Drepper said: "If you want to complain then to the idiots who made the decision to go with .i586 instead of .i686 for x86 binaries. This is exactly the kind of problem I've been warning about all along. Using the i586 target stresses code paths (in this case in gcc) which are hardly ever used since nobody cares for this target in general." Panu disavowed any intent to complain.
Wireless Regulatory Domain Automatically Determined
Moonlight Still Banned in Fedora
The 2009-04-08 "Rawhide Report" caused some excitement when it seemed that
moonlightCite error: Closing
</ref> missing for
<ref> tag of Microsoft's "Silverlight" which is a virtual machine and framework for creating Rich Internet Applications, roughly competing in the same space as Adobe's Flex and Mozilla's Prism. It is considered to risky to include in Fedora due to legal worries raised by the Microsoft-Novell covenant. </ref> might have been enabled. It turned out that this was simply due to a confusion between a
mono API named "moonlight" and the actual
All that had actually happened was that Fedora Legal okayed the use of the mono compiler switch "moonlight" in order to facilitate RPMFusion's request.
Mono Breakage on PPC May Cause Reversion
mono issue discussed with reference to the 2009-04-08 Rawhide Report suggests that due to breakage on the
ppc architecture it may be necessary to untag the latest mono package.
Objections that the disabling of PPC architecture support on the
mono package was happening too close to the
Fedora 11 final freeze prompted David Nielsen to make the rejoinder that no help had been given to the Mono SIG despite their reporting a problem. Jesse Keating announced that in the absence of a fix before the final freeze
mono would simply be downgraded: "[t]his kind of version change shouldn't really be made after beta anyway."
Mary Ellen Foster requested, as a mono-dependent maintainer, that concrete actions be recommended. Jesse Keating and Toshio Kuratomi asked that all such did _not_ set "ExcludeArch: ppc" and rebuild as this would cause massive churn on a large number of packages. Instead a process to track down the failures and fix them with a fallback plan to revert to a mono release-candidate was proposed by Toshio.
YUM Downgrade Feature Now in Rawhide
yum downgrade <packagename>
He suggested: "[...]this will be most useful for rawhide users when installing test packages from koji static repos. etc. ... because then an older version will still be available in rawhide. Whereas if you upgrade to what is in rawhide there is nothing older available to downgrade to."
Multiple Package Ownership of Directories
Michael Schwendt and Christoph Wickert were clear that the packages Rahul mentioned should not own the directory because they were part of a dependency chain which led up to their ancestor package
hicolor-icon-theme. Contrary advice led to some sarcasm from Christoph Wickert about Red Hat employees not being familiar with Fedora packaging guidelines and it worried Peter Lemenkov, who believed that Red Hat employees all had "provenpackager" status (see FWN#170). Jason L. Tibbitts III corrected this latter assertion.
Paul Wouters reported that he had needed to
ssh into his machine to fix an X session problem and would like to revert "[...] to the old behavior of having ctrl-alt-backspace kill the current X session." See FWN#169 for earlier discussion.
Anders Rayner-Karlsson explained that dual-head setup in
Fedora 10 was as simple as:
xrandr --output LVDS --auto --output VGA --auto --above LVDS
to which Michael Cronenworth responded that this would need to be done in a start-up script as there was also now no
xorg.conf by default. Jesse Keating suggested using the
system-config-display tool instead as this would obviate the need for an
xorg.conf. Adam Jackson cautioned that nVidia's proprietary drivers might not export RANDR-1.2 yet and thus the latter might not work. Further discussions about whether
xorg.conf was needed for side-by-side wide virtual desktops suggested that Intel chipsets while currently enforcing a 2048 pixel limit may be capable of supporting up to 4096 pixels on
Intel 915 or
Intel 945 in the near future.
Dissent and discussion about Fedora's decision to follow the upstream rumbled on. Kevin Kofler suggested that "mailing list consensus" was not a good process by which to make such decisions as that taken by Xorg. Dave Airlie seemed as though he had had enough of personal attacks on him, but was also able to joke about it.