On Sep 10, 2009, at 2:17 PM, Tom Van Vleck wrote:

> Upgraded my Mini to 10.6, installed the dev tools,
> downloaded 0.29.9, did ./bootstrap.  (This machine
> had never had fink before.)
>
> after the usual questions and wallpaper, it ended with
>
>  pod2man –section=1 /sw/src/fink.build/dpkg-bootstrap-1.10.21-1218/
> dpkg-1.10.21/scripts/dpkg-architecture.pl > dpkg-architecture.1
>  /bin/sh: /usr/bin/pod2man: Permission denied
>  make[2]: *** [dpkg-architecture.1] Error 126
>  make[1]: *** [all-scripts] Error 2
>  make: *** [all-recursive] Error 2
>  ### execution of make failed, exit code 2
>  phase compiling: dpkg-bootstrap-1.10.21-1218 failed
>
> I tried several variants: running as myself, as su, under
> sudo; 32 bit and 64 bit.  all failed identically.
>
> the file
>  /sw/src/fink.build/dpkg-bootstrap-1.10.21-1218/dpkg-1.10.21/scripts/
> dpkg-architecture.1
> is mode 664 owned by user 1000, not me, not root.

Permissions on /usr/bin/pod2man looked OK.
-rw-rw-rw-  30 root  wheel  807 Jun 24 03:42 /usr/bin/pod2man

I noticed something that might be a difference.
On the target machine, which has never had fink:
$ which tar
/usr/bin/tar
$ tar --version
bsdtar 2.6.2 - libarchive 2.6.2

on a 10.5 machine that has fink:
$ which tar
/sw/bin/tar
$ tar --version
tar (GNU tar) 1.22

perhaps the -o flag should be specified when untar'ing archives?
What may have happened is that some files were extracted and
ownership was given to a nonexistent user ID.  Perhaps fink's tar
is smart enough not to do this, but bsdtar is not.




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fink-beginners mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.beginners

Reply via email to