On 12/12/12 10:28 AM, Stefan Bruda wrote:
> Hello,
> 
> At 08:55 -0700 on 2012-12-12 Alexander Hansen wrote:
>  >
>  > On 12/12/12 8:43 AM, Stefan Bruda wrote:
>  > > 
>  > > I am getting a strange problem when I try to upgrade anything that
>  > > involves expanding tar archives.  Updating readline6 for example gets
>  > > stuck at the following:
>  > > 
>  > > Unpacking fink-buildlock-readline6-6.2.4-1 (from 
> .../fink-buildlock-readline6-6.2.4-1_2012.12.12-10.30.33_darwin-x86_64.deb) 
> ...
>  > > Setting up fink-buildlock-readline6-6.2.4-1 (2012.12.12-10.30.33) ...
>  > > 
>  > > sudo -u fink-bld [ENV] sh -c /tmp/fink.pcn9E
>  > > /opt/sw/bin/tar  --no-same-owner --no-same-permissions -xvf 
> /opt/sw/src/readline-6.2.tar.gz
>  > > 
>  > > I have been waiting for awhile and stopped the process at this point.
>  > > Needless to say, the same command (/opt/sw/bin/tar ...) completes
>  > > quickly if issued outside the build process.  the target directory
>  > > (/opt/sw/src/fink.build/readline6-6.2.4-1) is empty.
>  > > 
>  > > The same thing happens with autoconf2.6.  These are the only two
>  > > packages that need updating, but I also tried with some others (e.g.,
>  > > fink rebuild enlightenment) and I get the same result.
>  > > 
>  > > Any suggestion is appreciated, as I have no idea what to try next.
>  > > Here is the system info:
>  > > 
>  > > Package manager version: 0.34.4
>  > > Distribution version: selfupdate-rsync Wed Dec 12 10:27:10 2012, 10.8, 
> x86_64
>  > > Trees: local/main stable/main
>  > > Xcode.app: 4.5.2
>  > > Xcode command-line tools: 4.5.0.0.1.1249367152
>  > > Max. Fink build jobs:  2
>  > > 
>  > "stuck tar" errors are typically associated with permissions.  What
>  > method do you have fink use to get super-user access?
> 
> Ah, thank you.  I am not sure what actually causes the issue but I
> your comment allowed me to find a workaround.
> 
> The method of obtaining root on the machine was to log in directly as
> root via ssh ( I kind of prefer this as I have set up my keys so I am
> more secure than using passwords).  In such a circumstance tar gets
> stuck.  On the other hand if I ssh into the machine as a normal user
> and *then* sudo bash to become root, then tar is happy and works as
> advertised.
> 
> So thank you so much for the suggestion.  As I said I don't know what
> particular thing causes the issue, but as long as there is a
> workaround everything is well.
> 
> Cheers,
> Stefan
> 

Ah.  That clarifies things a bit.  The issue appears to be in how the
environment gets set up when transferring control from root to the
unprivileged "fink-bld" user.  Another workaround is to use "fink
--no-build-as-nobody ..."


-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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

Reply via email to