Re: ELF binary type "3" not known.

2017-03-20 Thread Chris H
On Mon, 20 Mar 2017 22:32:53 -0700 (PDT) Don Lewis wrote > On 20 Mar, Chris H wrote: > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I received this message during a big > > build session. I

Re: ELF binary type "3" not known.

2017-03-20 Thread Don Lewis
On 20 Mar, Chris H wrote: > I'm not sure which of the two lists I'm directing > this to is the best/correct one. So I picked both. > > To the point; I received this message during a big > build session. I was only able to catch the one from > x11/nvidia-driver in such a way as to actually get >

Re: ELF binary type "3" not known.

2017-03-20 Thread Chris H
On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lo wrote > On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: > > > > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > > > > > I'm not sure which of the two lists I'm directing > > > this to is the

Re: ELF binary type "3" not known.

2017-03-20 Thread Kevin Lo
On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: > > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I received this message

Re: ELF binary type "3" not known.

2017-03-20 Thread O. Hartmann
On Mon, 20 Mar 2017 21:11:44 -0700 "Chris H" wrote: > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I

Re: ELF binary type "3" not known.

2017-03-20 Thread Chris H
On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > I'm not sure which of the two lists I'm directing > this to is the best/correct one. So I picked both. > > To the point; I received this message during a big > build session. I was only able to catch the one from >

ELF binary type "3" not known.

2017-03-20 Thread Chris H
I'm not sure which of the two lists I'm directing this to is the best/correct one. So I picked both. To the point; I received this message during a big build session. I was only able to catch the one from x11/nvidia-driver in such a way as to actually get the entire message: Installing

Re: net/rubygem-signet causing poudriere to be unhappy

2017-03-20 Thread Adam Weinberger
> On 20 Mar, 2017, at 11:53, Shawn Webb wrote: > > Hey All, > > It looks like the new net/rubygem-signet port is causing issues with > poudriere: > > Error: Duplicated origin for rubygem-signet-0.7.3: > security/rubygem-signet AND net/rubygem-signet. Rerun with -vv

net/rubygem-signet causing poudriere to be unhappy

2017-03-20 Thread Shawn Webb
Hey All, It looks like the new net/rubygem-signet port is causing issues with poudriere: Error: Duplicated origin for rubygem-signet-0.7.3: security/rubygem-signet AND net/rubygem-signet. Rerun with -vv to see which ports are depending on these. Thanks, -- Shawn Webb Cofounder and Security