Anyway, so I got base-devel installed and of course then Toilet built without issues, everything looks good.
Wow, if only configure scripts would say something like 'the tool im using to check if your files exist... doesnt exist!'. It's sort of an insane leap in logic to go from 'command not found' to saying 'library doesn't exist', haha.
Of course, some lessons learned; pacman -Sy and pacman -Syu once a month should keep the system in healthy standing, which should help to avoid issues like this. : )
Thanks again,
]]>The repos don't retain outdated packages (though you can possibly use the ARM to obtain them), so 'pacman -S package' will get you a 404 error.
Very true, but a 404 error will not damage one's system in any way. That's just a sign that one should do an 'Syu'. If one gets a 404 error trying to install 'package' for this reason, then they proceed with `pacman -Sy package`, it is quite possible they will have damage to their system.
I'd rather have a command fail at installing a package than suceed at breaking my system.
When should you sync? You'll get lots of opinions on how often, but I'd stand firm on my answer of "only as often as you update". In otherwords, only use -Sy as part of an -Syu.
If you need to sync your database to install a package, there is a high likelihood that'd you'd also need to update your system to install that package without breaking something.
]]>I went with Arch for a VPS which I use to host various services also for programming/scripting/etc.
Title updated as requested.
WorMzy, I'm curious to know when you'd think it's a good point to sync DB's? After each major update?
]]>You probably don't want to hear this, but I've had this arch system for over a year now, and the only time I ever did a pacman -Syu was when I first set it up, hah. I had one incident before that to do with pcre after an update, and a couple times had to update pacman, but never ran into anything like this before.
Does that mean the Arch Linux server you're working on is not a computer you use very often? And out of curiousity, why are you installing a video game on a server?
So I should be updating everything every month? Would it make sense to just run pacman -Syu in a crontab once a month at 3am or something?
Oh, no! Don't update in a cron job! As the user of your Arch Linux computer, it's your job (and not the Arch Linux developers') to make sure an update goes correctly and that nothing breaks. I'd say updating once a month is a dangerous bare minimum. I update at least once a day, but mostly just because it's fun.
I hope you don't take offense at this but, I think you're the most experienced unexperienced Arch Linux user I've ever met. It's fascinating!
]]>If you don't update for ages, then want to install something new, you run into the sort of problem you're experiencing now. I disagree with Trilby's statement about not updating pacman's databases and installing packages, for a lot of packages that simply won't work. The repos don't retain outdated packages (though you can possibly use the ARM to obtain them), so 'pacman -S package' will get you a 404 error.
Updating via cron is a Very Bad Idea™ too. Arch is a very hands-on distro. I think you may find something like debian better suited to your needs.
]]>theoddsarebad, please retitle your thread to reflect your glibc fubar so it accurately reflects your core issue.
Moving to NC...
]]>theoddsarebad wrote:and only do partial updated usually
I know it's been said, but to reiterate, this is a very bad idea, please break this habit.
Many may argue that it is important to upgrade regularly. While I agree, waiting between updates usually won't cause any real problems - at least not big ones. Partial upgrades, however, will almost always cause serious problems in arch.
You can, of course, add additional software at anytime without updating anything. If you fully update (pacman -Syu) in April, then in June you want a new package you can still add it (pacman -S package). Just don't sync your database in between (never pacman -Sy).
Hmm, so when exactly should the db's be sync'd?
You probably don't want to hear this, but I've had this arch system for over a year now, and the only time I ever did a pacman -Syu was when I first set it up, hah. I had one incident before that to do with pcre after an update, and a couple times had to update pacman, but never ran into anything like this before.
So I should be updating everything every month? Would it make sense to just run pacman -Syu in a crontab once a month at 3am or something?
]]>drcouzelis wrote:theoddsarebad wrote:bootstrap requires automake > 1.5.
pacman -S automake, returns automake 1.12.5.Version 1.12 is totally newer than version 1.5.
Tell that to this bootstrap file, it doesn't seem to believe it.
According to the PKGBUILD file, the bootstrap file isn't necessary. It's just configure, make, and make install.
By the way, I think you win an award for "Interesting Thread Title".
]]>and only do partial updated usually
I know it's been said, but to reiterate, this is a very bad idea, please break this habit.
Many may argue that it is important to upgrade regularly. While I agree, waiting between updates usually won't cause any real problems - at least not big ones. Partial upgrades, however, will almost always cause serious problems in arch.
You can, of course, add additional software at anytime without updating anything. If you fully update (pacman -Syu) in April, then in June you want a new package you can still add it (pacman -S package). Just don't sync your database in between (never pacman -Sy).
]]>You might be able to salvage the situation somewhat using the "online fix if --force'd" method described here: https://wiki.archlinux.org/index.php/Ta … ib_symlink
But honestly, if reinstalling is a viable option for you, it'll probably be a lot faster -- you have at least five months of changes and updates to catch up on, and you've fallen at the first hurdle as it were.
]]>This isn't a total loss at least, since it's a VPS I can download the image, extract all the files, and get the VPS back.
That'll probably take me a little while to get through, when I get the VPS back up I'll first do a full update then try the base-devel again and then finally have Toilet.
So I'll be gone a bit while I work on the restore, but I'll be back to post on if it did finally succeed or not.
It's going to be a long day... sigh.
Thanks again,
]]>So you should be able to follow the 'basic' instructions on the wiki page for the glibc update. I don't think you have broken anything in that attempted force - but you do still need to complete the update before you try to install anything new.
]]>