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

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Wednesday July 30, 2008
03:42 PM

Need to find a lost rpm

[ #37058 ]

It's the end of the world.

I mentioned in this post that I was dependent upon libxcb-1.0-4.fc8.i386.rpm, because of a bug that exists in libxcb-1.0-3.fc8.i386.rpm, which the XCB developers apparently do not feel is a bug. I am a moron for not having a copy of this rpm, upon which I am dependent.

Some time very recently, semi-automatic updates upgraded me to libxcb-1.1-1.fc8.i386.rpm. Like I said, the XCB people don't think this issue is a problem, so 1.1 doesn't include the fix. I assume the difference between 1.0-3 and 1.0-4 is some local Fedora patch.

It wasn't very smart of me not to keep this important rpm. It wasn't very smart of me to update my machine (although it ought not to be such a big deal, and it is nice to know when things break sooner rather than later). But what's really not smart is that once libxcb-1.1-1.fc8.i386.rpm, version 1.0-4 disappeared off the face of the map!! There's only one Fedora Updates directory per version, and there's only the latest rpm in there. As near as I can tell, this has been deleted, and nobody connected to the net seems to keep old versions.

So I have zero recourse, as far as I can tell. I have one system that has 1.0-4 installed. Does anyone know a way to reconstitute an rpm you do not have from a system that has that rpm installed? Or does anyone know a way to get old rpms that were issued in an update but are not in the latest update? Is there a version control repository somewhere that can get me back to this intermediate state? (If not, why not? How do they survive without it?) Is there a way to find out what changed between 1.0-3 and 1.0-4?

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 search results included rpm.pbone.net, rpmfind.net and a slew of others. The first two are usually helpful but not this time. I also ran across: http://orion.lcg.ufrj.br/RPMS/myrpms-f8-x86_64/repoview/repoview/libxcb-0-1.0-4. fc8.html [lcg.ufrj.br]
    • Awesome! Thank you! My searching only took me to sites with stale results for that package; every download link they provided went to an Updates directory that no longer had that version of the package.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • ... 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

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • export LIBXCB_ALLOW_SLOPPY_LOCK=true
  • I know that Mandriva keeps its packages versioned in a version control system. Red Hat probably does the same and you should be able to see what has changed by using the logs and the diffs.

    • Haven't found it as of yet. I'm sure it's there, though.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers