Hi Joao, At 12:50 06.09.00 +0200, Joao Luis Silva Damas wrote:

Hi,

there is nothing wrong with having your own mnt-lower on your allocation/assignment objects.

The warning was the product of a small internal misunderstanding that wasn't much of a hassle when the tool was only for internal use, so it went unnoticed.

asused public is being modified to only issue warnings when the mnt-lower has the RIPE NCC HM maintainer, not your own. You are encouraged to use mnt-lower in your own objects since that gives you better control over registrations in the address space allocated to you.

Ah - ok, I was wondering about the warning too, that´s clear now. Another problem on the Linux setup we use was that "make install" didn´t install @INC (delegations and other files) to the right places, so that asused is to be called from the installation directory. Is this known already or do you have any hint what might be wrong?

The new release should be coming out very soon.

Regards, Joao Damas RIPE NCC

Regards, Juergen