Ok so you guys were right on both parts, Linux Kernel did update (I thought just headers did, but i was wrong) And my Video card updated as well.[2013-04-09 09:24] [PACMAN] Running 'pacman -Syyu'
[2013-04-09 09:24] [PACMAN] synchronizing package lists
[2013-04-09 09:25] [PACMAN] starting full system upgrade
[2013-04-09 12:11] [PACMAN] upgraded 0ad (a13-1 -> a13-2)
[2013-04-09 12:11] [
I'd like to install a base arch linux in a non-root directory on a remote computer.I tried the instructions from: https://wiki.archlinux.org/index.php/In … get_systemI have my remote directory mounted and naively thought this should work as well.
farresito wrote:Thanks to both, guys. Really appreciate your answers.@tomk: Its not that I install outside of pacman. I never install outside of pacman, but in that case I thought, as gem its part of ruby, that pacman would delete gem and, consequently, gem would delete what he aparently installed, being recursively, if that can be said so.
So I haven't used my laptop in a while.
Both of those deps are in community. And the way Packer handles these things now is scary. It works, but is very fragile. I am still not entirely happy with everything, like packer adhoc parses the AUR's html.Expac and Jshon were made for shell scripts, to replace messy and fragile code. Expac links against alpm (as does package-query, causing no end of pain for yaourt
If this symbol isn't defined, then you compiled alpm from git. The patch that changes the name of this function is unreleased.http://projects.archlinux.org/pacman.gi … e9cc198f19
falconindy
https://bbs.archlinux.org/profile.php?id=30251
2012-09-29T01:59:06Z
@g_baker:pacman is not 'broken', as you claim.And to begin with, don't bother manually downloading a package from the packages page.Pacman will auto-download and install it for you.
Next update you'll probably have pacman stop with conflicting files for talloc. This was an old package, that has symlinks, which pacman does not recognize as belonging to talloc, so best procedure:sudo pacman -Syu > fail messagesudo pacman -S talloc --forcesudo pacman -Syu
Good you can chroot fine. Easiest to downgrade from the testing kernel is chroot and install the prior version with "pacman -U linux-version" from /var/cache/pacman/pkg/ When you later look at the output of image generation from your previous upgrade to 3.9.3-1 (e.g. "less /var/log/pacman.log |grep ALPM"), did that show an error?