Read the error, it says too many levels of symbolic links. That's the problem.

Jeronimo Pellegrini wrote:
Hello.

I just got this error while trying to do a "monotone ls unknown":

monotone: fatal: std::exception: boost::filesystem::is_directory:
"/home/jeronimo/work/mono/info.randomnode.phd.llpomdp/trunk/code/multi-states/mylibs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs/.libs":
 Too many levels of symbolic links
monotone: monotone: this is almost certainly a bug in monotone.
monotone: please send this error message, the output of 'monotone 
--full-version',
monotone: and a description of what you were doing to [EMAIL PROTECTED]
monotone: wrote debugging log to 
/home/jeronimo/work/mono/info.randomnode.phd.llpomdp/MT/debugif reporting a 
bug, please include this file


And there certainly were unknown files t list.

Well, here is the output of monotone --full-version :

monotone 0.25 (base revision: 4f4cb0aa339ad70c5b2624db22073d9e9a36c115)
Running on: Linux 2.6.15.1 #1 PREEMPT Sun Jan 22 10:10:10 BRST 2006 i686
Changes since base revision: new_manifest [76b5ea65324372db9886d2c0a8cee8e759841c8c]

old_revision [4f4cb0aa339ad70c5b2624db22073d9e9a36c115]
old_manifest [76b5ea65324372db9886d2c0a8cee8e759841c8c]


  Generated from data cached in the distribution;
  further changes may have been made.

  Generated from data cached in the distribution;
  further changes may have been made.

  Generated from data cached in the distribution;
  further changes may have been made.

Thanks,
J.


_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel

--
Matthew A. Nicholson
Matt-Land.com


_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel

Reply via email to