On Tue, Mar 21, 2017 at 07:50:32AM +0100, Antoine Brodin wrote:
A> > This change is known to break a ton of ports. More than 100 if
A> > counting depends. I'm sorry for that and I already started to fix
A> > them.
A> >
A> > Please send all new breakages to me.
A>
A> Hi,
A>
A> Exp-runs should ha
On Tue, Mar 21, 2017 at 7:41 AM, Gleb Smirnoff wrote:
> Hi!
>
> This change is known to break a ton of ports. More than 100 if
> counting depends. I'm sorry for that and I already started to fix
> them.
>
> Please send all new breakages to me.
Hi,
Exp-runs should happen before breakage happe
Hi!
This change is known to break a ton of ports. More than 100 if
counting depends. I'm sorry for that and I already started to fix
them.
Please send all new breakages to me.
On Tue, Mar 21, 2017 at 06:39:49AM +, Gleb Smirnoff wrote:
T> Author: glebius
T> Date: Tue Mar 21 06:39:49 2017
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 was only able to catch
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
> th
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 best/correct one. So I picked both.
> > >
>
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 during a big
> > build ses
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 received this message during a big
> > build session.
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
> x11/nvidia-driver in such a
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 nvidia-dri
> 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 to see
> which ports are depe
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 Eng
12 matches
Mail list logo
