Mike Sullivan wrote: > Colin Ngam wrote: >> Mike.Sullivan at sun.com wrote: >> >> Hi Mike, >> >> Thanks Mike. You have been a great help. It is always nice to know >> what we can expect if builds get error. > > don't expect that I'll always answer - it depends on my mood, and > in this case I was indeed worried that the upgrades might have > affected things. You're kinda lucky I was peeking anyway on a > Sunday night after a lot of margaritas :) > >> >> Anyway, back to the good news part. I tried env -i and looks like >> the build has been successful but I get >> alot of of these type of errors: >> >> Inconsistencies between pkgdefs and proto area: >> >> Unit T File Name Reloc/Sym name perm >> owner group inode lnk maj min package(s) >> ------------------------------------------------------------------------------------------------------------ >> >> >> filea: f >> var/ruby/1.8/gem_home/doc/rubygems-0.9.4/ri/Gem/SourceInfoCache/cdesc-SourceInfoCache.yaml >> >> - 644 - - 0 1 - - SUNWruby18r >> fileb: f >> var/ruby/1.8/gem_home/doc/rubygems-0.9.4/ri/Gem/SourceInfoCache/cdesc-SourceInfoCache.yaml >> >> - 600 - - 0 1 - - proto > > that looks a lot like your umask might not be the default 022 - nightly > doesn't reset it and some things don't set the permissions correctly > still. > > Mike > Hi Mike,
Does env -i changes my umask? My umask is set by my .bashrc script to 022. I need to get a clean build and so far has not been successful on zod.sfbay. Thnaks. colin
