xinitrc 4.0.11-1 is available for testing, which fixes all known and unknown bugs

Mike A. Harris mharris at www.linux.org.uk
Wed Oct 6 13:39:55 UTC 2004


The xinitrc package has underwent a fair number of changes in the
last couple of weeks, as I've passed through all open bug reports
against it in bugzilla.

Downside:
- While fixing everything, and cleaning up the package,
   I introduced a couple of minor but fatal bugs, which pretty much
   everyone, their brother, their dog, and their insurance salesman
   will get hit by.

- People are reporting these 2 bugs without first querying bugzilla
   to discover they've both been reported about 10000 times already,
   and are fixed internally.  ;o)


Upside:
- I now know how many users we have, since it seems like every single
   one of them has filed a bug about this.  ;o)
- I've discovered that a single typo or bad line in one file can make
   the entire universe crumble.


While I haven't yet figured out how to harness the power of xinitrc
to take over the world, and haven't figured out how to turn a profit
from "Fedora Core X11 protection insurance", I have fixed these two
nasty glitches and built new rpms internally for FC3testX.  ;o)

The 2 bugs are present in xinitrc-4.0.6-1 through 4.0.10-1:

- xinitrc missing closing "fi" in if block
     https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134673

- Xsession can't find xinitrc-common
     https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134785

Both of these issues are fixed in xinitrc-4.0.11-1, which is not yet
in rawhide, however I have uploaded it to people.redhat.com, where you
can download it manually, and install with "rpm":

     ftp://people.redhat.com/mharris/xinitrc-4.0.11-1.noarch.rpm

Those who wish to use "yum" or similar to get the package, can just
wait a day or so until the package gets pushed into rawhide normally.

Please test the new package to try and find any other glaring bugs
or problems that might still be present.  If you discover anything,
please query bugzilla first to see if someone else has reported it,
and if not, please open a new report for the issue.

Thanks for testing Fedora Core development, and riding the edge!  ;o)




More information about the test mailing list