Weird portupgrade error on current amd64

[Michael Butler]

On 04/26/16 12:53, Manfred Antar wrote:
> 
>> On Apr 26, 2016, at 9:42 AM, Michael Butler <imb at protected-networks.net> wrote:
>>
>> On 04/26/16 10:15, Manfred Antar wrote:
>>> When using portupgrade on current it fails when upgrading libraries.
>>> I can reproduce this on 3 different amd64 machines.
>>>
>>> Example:
>>>
>>> portupgrade -vf libnice ends like this:
>>>
>>> --->  Build of net-im/libnice ended at: Tue, 26 Apr 2016 07:01:15 -0700 (consumed 00:00:10)
>>> --->  Uninstallation of libnice-0.1.13 started at: Tue, 26 Apr 2016 07:01:15 -0700
>>> --->  Fixing up dependencies before creating a package
>>> /usr/local/lib/ruby/site_ruby/2.2/pkgtools/pkgtools.rb:1180: warning: Insecure world writable dir /tmp/. in PATH, mode 041777
>>> --->  Backing up the old version
>>> --->  Uninstalling the old version
>>> /usr/local/lib/ruby/site_ruby/2.2/pkgtools/pkgtools.rb:1180: warning: Insecure world writable dir /tmp/. in PATH, mode 041777
>>> [Reading data from pkg(8) ... - 1593 packages found - done]
>>> --->  Deinstalling 'libnice-0.1.13'
>>> [Reading data from pkg(8) ... - 1593 packages found - done]
>>> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
>>> 	! libnice-0.1.13	(Broken pipe)
>>
>> This appears to be related to kernels with SVN revisions between r298585
>> and r298597. I am testing with a version after that to see if it has an
>> impact on the problem,
>>
>> 	imb
>>
> On SVN r298651 which I’m running it’s still broken
> Weird error !!! why only on certain ports.
> Thanks
> Manfred

You're right - my test failed too - sorry :-(

	imb