Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... the Yum cache?

    ll /var/cache/yum/development/packages/libX11*

    What about the Java bug thread [sun.com] which is marked "Release Fixed 7(b22), 6u10(b09) (Bug ID:2155962) , 6-open(b03) (Bug ID:2156535)"? You might have some luck with the comment about using sed to fix the problem (search for "Submitted On 01-JUN-2007").

    • Thanks! That's the kind of information I was hoping someone could clue me in to. Unfortunately the package isn't in the cache on either of my machines. :)

      I finally found where whoever released 1.0-4 in Fedora mentioned a patch that was included and a bug number that was fixed. Unfortunately they left a digit out of the bug number. The bug they listed was completely unrelated, consisting of about five messages about a problem in 2001 ... and finally a message in 2007-12 saying "Here's libxcb-1.0-4 and it fixes this problem; closing." Oops. :) But continued searching led me to the real bug in Fedora's bugzilla (which has seen massive repeated reporting ... every other report is just "marked #XXXXXX as a dup of this bug"), and there I found out that in version 1.1 onward (at least on Fedora) there is an environment variable I can use, "LIBXCB_ALLOW_SLOPPY_LOCK", which will basically turn on the behavior from the patch in 1.0-4. So that's good enough for me, I think.

      Although really there's an enormous number of people here who need to get their act together:

      • First of all, my organization needs to get our act together and get our software fixed to run on versions of Java later than 1.5! And on later versions of Linux, for that matter ... I'm a major exception around here running on Fedora 8; everybody else is on ancient stuff.
      • Second of all I need to hang on to critical rpms to fix critical issues. :) And I probably need to find a more intelligent way to go about updating my system. Overall I like the approach of always grabbing updates when they are there and then dealing with the consequences. It's just that when there's consequences, then I don't like it. :) Thankfully my box is not "production." It just feels like it is sometimes. :)
      • Fedora could make it easier to back out recently-applied updates, because sometimes updates break things. They could save off rpms immediately before they are replaced. They could make it possible to reconstitute an rpm from a system that has it installed (this is probably possible). Most of all they could keep something like BackPAN: there's no reason why there shouldn't be a repository of all the rpms that have gone into Updates, for people who might need them.
      • The XCB folks need to quit saying it's not their problem. The bug is reported all over the net. :) [Disclaimer: I remember reading about this before and concluding it was XCB's problem. But I don't remember the details or the logic involved. They may very well be right that it's not their problem, in which case I retract this and don't blame them. :)]
      • I was going to say the Java folks need to get their act together, but they have. They've reported the bug to XCB, and they've provided a workaround in their latest version even though they don't think it's their fault. I'm not sure what more I was expecting from them: it's not their fault my organization is running old Java. :)
      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers