On Wed, Sep 2, 2015 at 1:37 PM, Jaap Akkerhuis wrote:
>
> > On Sep 2, 2015, at 21:54, Kevin Oberman wrote:
> >
> >
> > The information I just sent is correct. It is the vulnerability database
> > that is preventing the installation and not the port, so the problem will
> > remain until go14 is u
On 9/2/2015 9:49 PM, Kevin Oberman wrote:
On Wed, Sep 2, 2015 at 9:31 AM, Rob Belics wrote:
The date for vuln.xml, on the server which it won't build on, is September
1 while the date on the other is July 25.
OK. So the July 25 system seems to not be updating the vuln.xml file and
that file
> On Sep 2, 2015, at 21:54, Kevin Oberman wrote:
>
>
> The information I just sent is correct. It is the vulnerability database
> that is preventing the installation and not the port, so the problem will
> remain until go14 is updated to 1.4.3.
I didn't wait for that but blew away go14 and ju
On Wed, Sep 2, 2015 at 11:30 AM, Rob Belics wrote:
> On Wed, Sep 2, 2015 at 1:12 PM, Kimmo Paasiala wrote:
>
> > On Wed, Sep 2, 2015 at 8:13 PM, Rob Belics wrote:
> > > I found an updated vuln.xml in /usr/ports/security/vuxml/ dated today.
> I
> > > will copy that over to /var/db/pkg/ but still
On Wed, Sep 2, 2015 at 9:53 AM, Rob Belics wrote:
> I must have replied incorrectly. The dates on the two systems are
> different. The one that it does NOT build on shows vuln.xml as September 1
> while the other system builds and the date is June 25.
>
> I'm confused because I would think the ne
On Wed, Sep 2, 2015 at 9:31 AM, Rob Belics wrote:
> The date for vuln.xml, on the server which it won't build on, is September
> 1 while the date on the other is July 25.
>
OK. So the July 25 system seems to not be updating the vuln.xml file and
that file is from prior to the discovery of the vu
On Wed, Sep 2, 2015 at 1:12 PM, Kimmo Paasiala wrote:
> On Wed, Sep 2, 2015 at 8:13 PM, Rob Belics wrote:
> > I found an updated vuln.xml in /usr/ports/security/vuxml/ dated today. I
> > will copy that over to /var/db/pkg/ but still question why that file was
> > not updated.
> >
>
> It's not up
On Wed, Sep 2, 2015 at 8:13 PM, Rob Belics wrote:
> I found an updated vuln.xml in /usr/ports/security/vuxml/ dated today. I
> will copy that over to /var/db/pkg/ but still question why that file was
> not updated.
>
It's not updated by portsnap(8) but pkg-updating(8). Portmaster won't
update it
I found an updated vuln.xml in /usr/ports/security/vuxml/ dated today. I
will copy that over to /var/db/pkg/ but still question why that file was
not updated.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-po
I must have replied incorrectly. The dates on the two systems are
different. The one that it does NOT build on shows vuln.xml as September 1
while the other system builds and the date is June 25.
I'm confused because I would think the newer date would have built. How do
I get this sync'ed properly
The date for vuln.xml, on the server which it won't build on, is September
1 while the date on the other is July 25.
Here is the output when I try this:
===>>> The following actions will be taken if you choose to proceed:
Install lang/go
Install lang/go14
===>>> Proceed? y/n [y]
===>>> Startin
On Wed, Sep 2, 2015 at 8:36 AM, Rob Belics wrote:
> I have a server and my workstation. Both run FreeBSD 10.2-RELEASE. Both had
> lang/go version 1.4 on them. lang/go version 1.5 was released in ports and
> it builds on my local workstation, including reinstalling version 1.4.2
> but, on the serv
On Wed, Sep 2, 2015, at 10:36, Rob Belics wrote:
> I have a server and my workstation. Both run FreeBSD 10.2-RELEASE. Both
> had
> lang/go version 1.4 on them. lang/go version 1.5 was released in ports
> and
> it builds on my local workstation, including reinstalling version 1.4.2
> but, on the s
I should add that I'm doing this with portmaster
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
I have a server and my workstation. Both run FreeBSD 10.2-RELEASE. Both had
lang/go version 1.4 on them. lang/go version 1.5 was released in ports and
it builds on my local workstation, including reinstalling version 1.4.2
but, on the server, it complains about the previous security
vulnerabilities
15 matches
Mail list logo
