You are not logged in.
I'm trying to install teamviewer from the AUR. I've grabbed the tarball. Extracted it. cd'ed into the "teamviewer" folder. And now ...
-- snip --
%makepkg -s
==> Making package: teamviewer 6.0.9224-2 (Tue Jan 11 19:36:09 EST 2011)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading teamviewer_linux.deb...
--2011-01-11 19:36:09-- http://www.teamviewer.com/download/teamviewer_linux.deb
Resolving www.teamviewer.com... 87.230.73.24
Connecting to www.teamviewer.com|87.230.73.24|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 19093632 (18M) [application/x-deb]
Saving to: "teamviewer_linux.deb.part"
100%[=================================================================================>] 19,093,632 178K/s in 3m 12s
2011-01-11 19:39:25 (96.9 KB/s) - "teamviewer_linux.deb.part" saved [19093632/19093632]
ln: failed to create symbolic link `/mnt/dl/teamviewer/teamviewer/src/teamviewer_linux.deb': Operation not permitted
==> ERROR: An unknown error has occurred. Exiting...
-- snip --
I'm fairly new to PKGBUILDs though the one or two others I have done succeeded.
I can't figure out where the symbolic links are coming into play. I see no explicit attempts to create a symbolic link in the PKGBUILD file.
I'm running makepkg as a normal user.
Thanks.
Last edited by whatshisname (2011-01-12 02:22:04)
Offline
What type of filesystem is this operation being done on? Ivsaw similar errors when trying to build a package on a vfat filesytem, which can't handle symbolic links. Makepkg creates the links as part of the build process...you wont see them in the PKGBUILD. Also you need to have write permissions in the directory you're working in.
Scott
Last edited by firecat53 (2011-01-12 01:39:13)
Offline
Firecat. Youdaman!
That was it!
Less than an hour after the post and problem solved.
I love this place!
Offline