On Sunday 18 October 2009 10:15:25 pm David Rosenstrauch wrote:
On 10/18/2009 06:30 AM, David C. Rankin wrote:
......That's when the lightbulb winked on and when the feeling of SHAME begin to settle in on my consciousness. Further investigation revealed that on 10/8 when I had updated my box and the new pacman package was installed, I used the pacman.conf from an earlier update of my x86_64 Arch server as a "go-by". It would seem that there was one occasion with the community repository that an 'x86_64' did not get replaced by and 'i686', thus 'the loose nut behind the keyboard' had installed some:
Good Linux debugging clue: when you're having a bunch of major problems that no one else is, it usually means you did something stupid that no one else did! :-)
Seriously, though, I was reading all your messages going by, and kept thinking: there must be something weird he did to his box that's causing him all these problems, because Arch rarely gives me this much grief - especially with recent upgrades, as they've all gone very smoothly.
Anyway, all's well that ends well, and glad to hear you solved the problem!
DR
Yah.. I'm usually very good at problem solving, but in a decade with Linux, this is the first time I had ever seen an ELFCLASS64... Also, I'm still new enough with Arch and pacman that strange messages that I've never seen before don't register yet as to whether they are of the ID-10-T variety or if they have something to do with an Arch tool -- but I'll get there. P.S. The ID-10-T error? write it all together in lower-case and look at it again ;-) (id10t => idiot) I try to minimize the number of ID-10-T errors I create :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com