Somebody reported using a similar method (actually, they replaced the real /sw/bin/tar with a symbolic link to /usr/bin/gnutar, but that should be the same net result) and it worked for them.
Unfortunately, since apparently nobody who is familiar with the guts of the fink code has been able to reproduce this issue, I don't have another real fix to try. There's a workaround to try, though, which is to add the "--no-build-as-nobody" flag and retry your operation, i.e. fink --no-build-as-nobody selfupdate Also, here's a thought: You're using 'su -' to become root, but what is the value of the RootMethod field in /sw/etc/fink.conf ? On 3/21/13 10:44 AM, Pete Pardoe wrote: > Alexander > > That did not fix the problem. Every time I try to execute it (after su > - to become root) the tar command fails wherever it appears, however > using sudo to execute the command works. I prefer su - to sudo so if > there is an easy solution I would love to have it. > > Thanks, > > Pete > > On 21/03/2013 11:59 AM, Alexander Hansen wrote: >> On 3/21/13 7:07 AM, Pete Pardoe wrote: >>> It appears to just sit there when it hits the tar command, it does not >>> die it just sits there and when I control C it, it reports the >>> following. I am able to execute the tar command manually so I am at a >>> complete loss as to why this will not complete. >>> >>> Setting up fink-buildlock-base-files-1.9.14-1 (2013.03.21-05.42.22) ... >>> >>> sudo -u fink-bld [ENV] sh -c /tmp/fink.j6JZW >>> /sw/bin/tar --no-same-owner --no-same-permissions -xvf >>> /sw/src/base-files-1.9.14.tar.gz >>> ^C### execution of /sw/bin/tar failed, exit code 2 >>> ### execution of /tmp/fink.j6JZW failed, exit code 2 >>> Removing runtime build-lock... >>> Removing build-lock package... >>> /sw/bin/dpkg-lockwait -r fink-buildlock-base-files-1.9.14-1 >>> (Reading database ... 4560 files and directories currently installed.) >>> Removing fink-buildlock-base-files-1.9.14-1 ... >>> Failed: phase unpacking 'base-files-1.9.14.tar.gz': base-files-1.9.14-1 >>> failed >>> >>> >>> Also include the following system information: >>> Package manager version: 0.34.6 >>> Distribution version: selfupdate-cvs Thu Mar 21 05:42:17 2013, 10.8, >>> x86_64 >>> Trees: local/main stable/main >>> Xcode.app: 4.6.1 >>> Xcode command-line tools: 4.6.0.0.1.1358221012 >>> Max. Fink build jobs: 4 >>> >>> >>> Pete Pardoe >>> >> What method are you using to get administrative access for Fink? A root >> account? su? sudo with some special flags? >> >> We've had reports of similar issues when people have used a root >> account, but I haven't been able to reproduce the issue, which has made >> testing fixes a bit difficult. >> >> If you wouldn't mind trying out a potential solution, that'd be great. >> To do that, edit /sw/lib/perl5/Fink/PkgVersion.pm as a superuser and >> change the line which says >> >> $tarcommand = "$basepath/bin/tar $permissionflags $tarflags"; # Use >> Fink's GNU Tar if available >> >> to >> >> $tarcommand = "/usr/bin/gnutar $permissionflags $tarflags"; >> >> Then try your selfupdate again and let us know what happens. > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
