something messed up with latest pkg update?

Sergey V. Dyatko sergey.dyatko at gmail.com
Wed Nov 27 10:00:24 UTC 2013


On Wed, 27 Nov 2013 13:55:52 +0400
Ruslan Makhmatkhanov <cvs-src at yandex.ru> wrote:

> portsnap fetch update
> pkg version -vl "<"
> portmaster pkg-1.1.4_10
> 
> Got some warnings:
> pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a 
> repository configuration file
> pkg-static: Warning: expecting a boolean for the 'enabled' key of the 
> 'FreeBSD' repo,  the value has been correctly converted, please
> consider fixing
> pkg-static: unable to open vulnxml file, try running 'pkg audit -F'
> first
> 
> Fixed 1st and 3rd. What it is supposed to do with 2nd one?
> 

should be 'enabled: yes' instead 'enabled: "yes"'

> Then, trying to update some ports:
> 
> portmaster ruby19-gems-1.8.25 gnuchess-6.1.0 libssh-0.5.2_1 
> libunibreak-1.0,1 libxml2-2.8.0_2 nmap-6.40 pciids-20131119
> 
> """
> ===>>> Working on:
> 	ruby19-gems-1.8.25
> 	gnuchess-6.1.0
> 	libssh-0.5.2_1
> 	libunibreak-1.0,1
> 	libxml2-2.8.0_2
> 	nmap-6.40
> 	pciids-20131119
> 
> ===>>> Gathering distinfo list for installed ports
> 
> 	===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS
> 
> 
> ===>>> ruby19-gems-1.8.25 1/7
> 	===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS
> 
> 
> ===>>> Cannot continue
> ===>>> Aborting update
> 
> ===>>> Update for ruby19-gems-1.8.25 failed
> ===>>> Aborting update
> 
> ===>>> Killing background jobs
> Terminated
> ===>>> Exiting
> """
> 
> Got this "No ORIGIN"  messages for every port that I try to update.
> Is this known issue? How to handle that?
> 



-- 
wbr, tiger


More information about the freebsd-ports mailing list