You are not logged in.
Hello.
I'm using Archlinux and the system works flawessly. Sadly, there's a problem when trying to install AUR packages.
The following happens installing any AUR package I tried lately.
==> Continue installing wicked-git? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>y
loading package data...
error: './wicked-git-20090112-1-i686.pkg.tar.gz': cannot open package file
==> WARNING: Your package is saved in /tmp/yaourt-tmp-timofonic/wicked-git-20090112-1-i686.pkg.tar.gz
cp: cannot stat `./wicked-git-20090112-1-i686.pkg.tar.gz': No such file or directory
==> WARNING: Unable to copy wicked-git-1-i686.pkg.tar.gz to /tmp/yaourt-tmp-timofonic/ directory
Any idea about how to fix it? I tried using both an user with sudo and root, same problem.
Regards.
Last edited by timofonic (2009-07-14 19:52:53)
Offline
I did the following and still happens...
pacman -Sf $(pacman -Qq | grep -v "$(pacman -Qmq)")
Offline
Perhaps the method to use is given by the man pacman files.
pacman -U (.pkg.tar.gz package ID found in the directory generating the package)For example: ...pacman -U /var/local/kernel26-2.6.30-5-x86-64.pkg.tar.gz......since the pkg generated is in that directory for this theoretical case.
Any locally generated package is loaded with ...pacman -U....
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Perhaps the method to use is given by the man pacman files.
pacman -U (.pkg.tar.gz package ID found in the directory generating the package)For example: ...pacman -U /var/local/kernel26-2.6.30-5-x86-64.pkg.tar.gz......since the pkg generated is in that directory for this theoretical case.
Any locally generated package is loaded with ...pacman -U....
What do you mean? The package doesn't exist, I double checked it.
Maybe I need to check where yaourt writes it. Any suggestion about what util to use for that?
EDIT: I used "lsof" command and found the file is there, but yaourt can't locate it and deletes the directory after
$ ls /tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/w*
/tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/wicked-git-20090708-1-i686.pkg.tar.gz
/tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/wicked-git-20090709-1-i686.pkg.tar.gz
Please, could anyone help me to solve this problem?
Last edited by timofonic (2009-07-09 22:08:47)
Offline
EDIT: I used "lsof" command and found the file is there, but yaourt can't locate it and deletes the directory after
$ ls /tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/w*
/tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/wicked-git-20090708-1-i686.pkg.tar.gz
/tmp/yaourt-tmp-root/aur-wicked-git/wicked-git/wicked-git-20090709-1-i686.pkg.tar.gzPlease, could anyone help me to solve this problem?
yaourt has been bugged like this with vcs packages for a while. It's a result of makepkg automatically fetching the latest snapshot.
When you started installing that package, yaourt tracked the initial $pkgver as 20090112. After makepkg fetched the latest snapshot (and updated the $pkgver to reflect it) and finished building, the $pkgver became 20090708. yaourt doesn't take this into account and still tries to install wicked-git-20090112-1-i686.pkg.tar.gz, which can't be found because the correct file is supposed to be wicked-git-20090708-1-i686.pkg.tar.gz.
Offline
As tdy said, yaourt is not very good for svn/cvs/git/etc type packages. You are better using the primary tools, makepkg and pacman.
Offline
Timofonic, when you installing git package via yaourt you must edit PKGBUILD and change pkgver to current date.
Offline
Yeah, but the future will be aurbuild or other stuffs maybe.
Offline
Timofonic, when you installing git package via yaourt you must edit PKGBUILD and change pkgver to current date.
OK, you are right. Thanks.
Any way to automate that proccess?
Offline