Hello Kevin,
On Wednesday, October 13, 2010, 5:30:52 PM, you wrote:
Well, normally it's the s390 arch team's job to fix the build
on s390, and
they should have commit access to all packages, even Firefox. If that's not
the case, talk to the infrastructure team to get the required access.
But I agree that closing it as fixed in a more recent Fedora release
is
completely unacceptable for a build fix which prevents shipping the package
at all on that architecture. This MUST be fixed in the F12 branch.
Kevin Kofler
Kevin,
Reality checks:
1) Do you _really_ think that there is much use of desktops (let alone
desktop applications such as Firefox) on zSeries?
Most folks doing it are likely using emulation (Hercules), for
the usual educational and developmental purposes. These folks
will use the native browser, not the slower emulated system one.
Unless you have a dedicated LPAR or VM, running desktop apps is
quite rare on real zSeries hardware. It is mostly for bragging
rights. Every now and then folks with z10 or later hardware (which
finally is leading edge CPU performance) will experiment with
bringing up a desktop environment like Gnome. Older hardware
requires significant patience.
It isn't something that one would do on a production server, where
you pay for CPU consumed. In reality those servers would be almost
exclusively RHEL.
2) For several releases, s390x secondary architecture was not very
active. That has changed with F14, which is causing significant
excitement on mailing lists such as LINUX-390(a)VM.MARIST.EDU.
The s390x team decides where they invest their limited resources.
F14 is where they made the wise decision to focus - that equine is
not deceased, but chomping at the bit.
F14 on zSeries is a very viable release for application porting and
development, whether on real hardware or emulation. Mostly using
non-GUI means. I would expect nearly all downstream production
systems would be RHEL systems.
3) If there is anything that fits in the "do not touch" category, it
would be a core package on a secondary architecture on a release
no one is using that is nearing EOL.
It might be best to find a better target to rant and rave on both
Firefox and the stable release vision. Or just let it go.
Al