Re: something messed up with latest pkg update?

2013-11-27 Thread Ruslan Makhmatkhanov 

Johan Hendriks wrote on 27.11.2013 14:00:

Got this "No ORIGIN"  messages for every port that I try to update. Is
this known issue? How to handle that?


The second one in my case was the line  enabled in /etc/pkg/FreeBSD.conf

FreeBSD: {
   url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
   mirror_type: "srv",
   signature_type: "fingerprints",
   fingerprints: "/usr/share/keys/pkg",
   enabled: "yes"
}

I had to change enabled: "yes"  to enbled: yes
Remove the " .


Thank you, this worked to me.



I can not help you with the rest of the errors.. Sorry

regards
Johan


The rest of the problems were solved by copying 
/usr/local/etc/pkg.conf.sample to /usr/local/etc/pkg.conf


--
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: something messed up with latest pkg update?

2013-11-27 Thread Johan Hendriks 

Ruslan Makhmatkhanov schreef:

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?

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?



The second one in my case was the line  enabled in /etc/pkg/FreeBSD.conf

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: "yes"
}

I had to change enabled: "yes"  to enbled: yes
Remove the " .

I can not help you with the rest of the errors.. Sorry

regards
Johan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: something messed up with latest pkg update?

2013-11-27 Thread Sergey V. Dyatko 
On Wed, 27 Nov 2013 13:55:52 +0400
Ruslan Makhmatkhanov  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
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: something messed up with latest pkg update?

2013-11-27 Thread Łukasz Wąsikowski 
W dniu 2013-11-27 10:55, Ruslan Makhmatkhanov pisze:

> 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?

Try enabled: yes (without quotes) in pkg.conf.

-- 
best regards,
Lukasz Wasikowski
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"