Re: devel/mico failing due to failed assertion

2016-03-13 Thread Karel Gardas
Guys, I've installed 5.8 chroot on 5.9-beta as of January 2016. I've removed /etc/resolve.conf after installing few packages and give MICO build a try. I've duplicated issue of assert in address.cc:555 since hostname is not resolvable. I've been able to solve this assert by putting: -ORBIIOPAddr

Re: devel/mico failing due to failed assertion

2016-03-11 Thread Stuart Henderson
On 2016/03/11 11:22, Karel Gardas wrote: > On Thu, Mar 10, 2016 at 10:28 PM, Marc Espie wrote: > >> Indeed, it is, but I guess this was done for a good reason in the past > >> and I would rather keep it this way. What I can certainly do for > >> 2.3.14 release is to add some

Re: devel/mico failing due to failed assertion

2016-03-11 Thread Karel Gardas
On Thu, Mar 10, 2016 at 10:28 PM, Marc Espie wrote: >> Indeed, it is, but I guess this was done for a good reason in the past >> and I would rather keep it this way. What I can certainly do for >> 2.3.14 release is to add some clear error message pointing to the >> incorrect

Re: devel/mico failing due to failed assertion

2016-03-11 Thread Karel Gardas
On Thu, Mar 10, 2016 at 7:37 PM, Michael McConville wrote: > Karel Gardas wrote: >> This is a sign of not so correct network configuration. MICO is really >> picky about it so it should be able to resolve your host name/IP >> address. What's failing precisely in the assert

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Theo de Raadt
> On Thu, Mar 10, 2016 at 05:58:05PM +0100, Karel Gardas wrote: > > On Thu, Mar 10, 2016 at 3:13 PM, Marc Espie wrote: > > > On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: > > >> This is a sign of not so correct network configuration. MICO is really > > >> picky

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Marc Espie
On Thu, Mar 10, 2016 at 05:58:05PM +0100, Karel Gardas wrote: > On Thu, Mar 10, 2016 at 3:13 PM, Marc Espie wrote: > > On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: > >> This is a sign of not so correct network configuration. MICO is really > >> picky about it so

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Michael McConville
Karel Gardas wrote: > This is a sign of not so correct network configuration. MICO is really > picky about it so it should be able to resolve your host name/IP > address. What's failing precisely in the assert above is that it's not > able to get IP for your hostname. Can you confirm that this is

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Karel Gardas
On Thu, Mar 10, 2016 at 3:13 PM, Marc Espie wrote: > On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: >> This is a sign of not so correct network configuration. MICO is really >> picky about it so it should be able to resolve your host name/IP >> address. What's

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Stuart Henderson
On 2016/03/10 15:13, Marc Espie wrote: > On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: > > This is a sign of not so correct network configuration. MICO is really > > picky about it so it should be able to resolve your host name/IP > > address. What's failing precisely in the assert

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Marc Espie
On Thu, Mar 10, 2016 at 11:53:56AM +0100, Karel Gardas wrote: > This is a sign of not so correct network configuration. MICO is really > picky about it so it should be able to resolve your host name/IP > address. What's failing precisely in the assert above is that it's not > able to get IP for

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Peter Hessler
On 2016 Mar 10 (Thu) at 10:53:26 + (+), Stuart Henderson wrote: :On 2016/03/10 02:05, Michael McConville wrote: :> It's been failing reliably on my machine since I started bulk building a :> couple months ago. : :If your local hostname doesn't resolve this triggers an assertion in :mico. :

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Stuart Henderson
On 2016/03/10 02:05, Michael McConville wrote: > It's been failing reliably on my machine since I started bulk building a > couple months ago. If your local hostname doesn't resolve this triggers an assertion in mico.

Re: devel/mico failing due to failed assertion

2016-03-10 Thread Karel Gardas
This is a sign of not so correct network configuration. MICO is really picky about it so it should be able to resolve your host name/IP address. What's failing precisely in the assert above is that it's not able to get IP for your hostname. Can you confirm that this is the case? On Thu, Mar 10,