You are not logged in.
Hi,
I tried to install awesome-git und wicked-git using yaourt:
I get:
loading package data...
error: './wicked-git-20090112-1-x86_64.pkg.tar.gz': cannot open package file
==> WARNING: Your package is saved in /tmp/yaourt-tmp-root/wicked-git-20090112-1-x86_64.pkg.tar.gz
cp: cannot stat `./wicked-git-20090112-1-x86_64.pkg.tar.gz': No such file or directory
==> WARNING: Unable to copy wicked-git-1-x86_64.pkg.tar.gz to /tmp/yaourt-tmp-root/ directory
(this is from wicked-git, but I get the same for wicked-git.
What is wrong?
Thanks!
Nathan
Offline
This is a yaourt issue, not a PKGBUILD/ABS issue. Moved to Community Contributions.
Offline
got the same issue with yaourt... or i guess i have it... haven´t tested it the last days..^^
Last edited by kanim (2009-01-20 23:48:09)
Offline
Hi,
I tested it with some other git packages, always the same.
Is this a bug?
Or maybe something wrong with my config?
Can anyone confirm?
Offline
i can confirm that it's a problem with yaourt and git
a few minitues ago, i installed a non git package through yaourt and it worked fine.
However a minute later i tried a git one and get exactly the same error
Offline
When you get a git/svn/cvs PKGBUILD the version is set to the date of the upload, but in the package creation process the latest snapshot is downloaded and version is changed on-the-fly accordingly (I have yet to see one that checks out a specific snapshot). I guess you need to take that into account when running yaourt, either to checkout a specific snapshot or to recognise the pkgver change.
You need to install an RTFM interface.
Offline
When you get a git/svn/cvs PKGBUILD the version is set to the date of the upload, but in the package creation process the latest snapshot is downloaded and version is changed on-the-fly accordingly (I have yet to see one that checks out a specific snapshot). I guess you need to take that into account when running yaourt, either to checkout a specific snapshot or to recognise the pkgver change.
i do not realy understand in what way this helps me...
couse there is nothing i can do against it and it worked great some weeks ago
Offline
for others with the same error
just change the version in the pkgbuild to the one you're downloading
e.g.
packver=12062008
to
packver=01262009
Offline