monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Broken monotone 0.19 database


From: Glen Ditchfield
Subject: [Monotone-devel] Broken monotone 0.19 database
Date: Sun, 09 Oct 2005 22:48:19 -0500
User-agent: KMail/1.8.2

I have a monotone database, used with monotone 0.19, that now gives me 
invariant violation messages.  To complicate matters, I ran "monotone db 
update" with monotone 0.23 in my working directory, without saving the MT 
directory.  Fortunately nothing irreplacable is in the database, but if 
there's an easy way out of this mess, I'd like to hear about it...

If I copy the original 0.19 database back to the original location, monotone 
0.19 --full-version says 
----------------------------------
monotone 0.19 (base revision: 168adf9537ff136c9b7fe7faad5991f92859390d)
Running on: Linux 2.6.8-24.18-default #1 Fri Aug 19 11:56:28 UTC 2005 i686
Changes since base revision:

new_manifest [52a617d908ac6c4bb5b837ce5306f75155dc59ef]

old_revision [168adf9537ff136c9b7fe7faad5991f92859390d]
old_manifest [a9ee1d741b855fdcc0d038d64d913cef70da72f5]

patch "po/monotone.pot"
 from [10e6d7cbad87eaa0dbe35c803cafa371567f024b]
   to [0465f6ac8d09fac5938ac067747b179aca677b67]


  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.
---------------------------------------------

monotone 0.19 --debug status says
---------------------------------------------
monotone: started up on Linux 2.6.8-24.18-default #1 Fri Aug 19 11:56:28 UTC 
2005 i686
monotone: command line: 'monotone', '--debug', 'status'
monotone: set locale: LC_CTYPE=en_US.UTF-8, LC_MESSAGES=en_US.UTF-8
monotone: initial path is /home/gjditchf
monotone: searching for 'MT' directory with root '/'
monotone: search for 'MT' ended at '/home/gjditchf' with '' removed
monotone: initializing from directory /home/gjditchf
monotone: found working copy directory /home/gjditchf
monotone: options path is MT/options
monotone: branch name is 'ca.mb.ditchfield.home.gjditchf'
monotone: local dump path is MT/debug
monotone: setting dump path to MT/debug
monotone: skipping nonexistent rcfile '/home/gjditchf/.monotone/monotonerc'
monotone: opening rcfile 'MT/monotonerc' ...
monotone: 'MT/monotonerc' is ok
monotone: executing status command
monotone: options path is MT/options
monotone: revision path is MT/revision
monotone: loading revision id from MT/revision
monotone: db.fetch("SELECT id FROM 'revisions' WHERE id = 
'612353df0c7aadbb4b57d7abf938c2638a46cefc'")
monotone: db.fetch("SELECT data FROM revisions WHERE id = 
'612353df0c7aadbb4b57d7abf938c2638a46cefc'")
monotone: old manifest is 698ce66b947445bbd6b39206fcf61d03734176d3
monotone: db.fetch("SELECT id FROM 'manifest_deltas' WHERE id = 
'698ce66b947445bbd6b39206fcf61d03734176d3'")
monotone: db.fetch("SELECT id FROM 'manifests' WHERE id = 
'698ce66b947445bbd6b39206fcf61d03734176d3'")
monotone: db.fetch("SELECT id FROM 'manifests' WHERE id = 
'698ce66b947445bbd6b39206fcf61d03734176d3'")
monotone: db.fetch("SELECT data FROM 'manifests' WHERE id = 
'698ce66b947445bbd6b39206fcf61d03734176d3'")
monotone: old manifest has 3320 entries
monotone: work path is MT/work
monotone: checking for un-committed work file MT/work
monotone: read rearrangement from MT/work
monotone: restriction includes delete file .kde/share/config/konq_history
monotone: restriction includes delete file .kde/share/config/ksmserverrc
monotone: restriction includes delete file .kde/share/config/ksslpolicies
monotone: restriction includes delete file .kde/share/config/susewatcherrc
monotone: restriction includes delete file .qt/qt_plugins_3.3rc
monotone: restriction includes delete dir .kde/share/apps/kcookiejar
monotone: path_component.cc:53: invariant 'I(!null_name(*i))' violated
monotone: fatal: std::logic_error: path_component.cc:53: invariant 
'I(!null_name(*i))' violated
--------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]