Same error. But if I comment the definition of
resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
The problem was that in some places there was a
toppath with double p (pp)
and in some places it was
topath with single p (p).
Will toppath be brought back?
On 11/6/2012 10:04 PM, Andre Caldas wrote:
Same error. But if I comment the definition of
resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
The problem was that in some places there was a
toppath with double p (pp)
and in some places it was
topath with
On 16-10-2012 00:14, Aditya Mahajan wrote:
Same error. But if I comment the definition of
resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
Hans
-
On Tue, Oct 16, 2012 at 11:37 AM, Hans Hagen pra...@wxs.nl wrote:
On 16-10-2012 00:14, Aditya Mahajan wrote:
Same error. But if I comment the definition of
resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
Hans
confirmed
--
luigi
On 2012-10-16, at 5:37 AM, Hans Hagen pra...@wxs.nl wrote:
On 16-10-2012 00:14, Aditya Mahajan wrote:
Same error. But if I comment the definition of
resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
Thanks. The format is made cleanly now.
Aditya
