From: Dan A. <da...@co...> - 2004-12-04 08:34:41
|
Hello, As the subject says, I've upgraded the monotone server to run 0.15. This version is incompatible with 0.14. Please follow instructions at: http://www.venge.net/monotone/README.changesets BTW, you may also need to recreate your working copies after migrating the database. -- Dan Aloni da...@co... |
From: Henry N. <Henry.Ne@Arcor.de> - 2004-12-09 09:22:49
|
Dan Aloni wrote: > Hello, > > As the subject says, I've upgraded the monotone server to run 0.15. > This version is incompatible with 0.14. Please follow instructions at: > > http://www.venge.net/monotone/README.changesets > > BTW, you may also need to recreate your working copies after migrating > the database. > Can only not automatic find your last certs. Database have created new, init and downloaded, followed by stepguide. http://www.colinux.org/?section=scs Can you repair this? Or must we add your public key? $ monotone --db=colinux.db heads --branch=stable monotone: branch 'stable' is empty Source can extract with this command line: # monotone --db=colinux.db checkout ea8c1a30ea72ca847c4593b1eb6a9bdf2597db28 yourdirout # monotone --db=colinux.db list certs ea8c1a30ea72ca847c4593b1eb6a9bdf2597db28 monotone: warning: no public key 'gbo...@pr...' found in database ----------------------------------------------------------------- Key : gbo...@pr... Sig : unknown Name : changelog Value : * add configre, drop patch/w32api-2.5.diff ----------------------------------------------------------------- Key : gbo...@pr... Sig : unknown Name : date Value : 2004-12-08T16:43:25 ----------------------------------------------------------------- Key : gbo...@pr... Sig : unknown Name : author Value : gbo...@pr... ----------------------------------------------------------------- Key : gbo...@pr... Sig : unknown Name : branch Value : stable -- Henry Nestler |
From: Dan A. <da...@co...> - 2004-12-10 12:33:42
|
On Thu, Dec 09, 2004 at 10:22:08AM +0100, Henry Nestler wrote: > Dan Aloni wrote: > >Hello, > > > >As the subject says, I've upgraded the monotone server to run 0.15. > >This version is incompatible with 0.14. Please follow instructions at: > > > > http://www.venge.net/monotone/README.changesets > > > >BTW, you may also need to recreate your working copies after migrating > >the database. > > > > Can only not automatic find your last certs. Database have created new, > init and downloaded, followed by stepguide. > http://www.colinux.org/?section=scs > > Can you repair this? Or must we add your public key? It turned out that I had to push some null revision in order to get it fixed, and then it insisted on a merge with gboutwel's revision. However, I now see the server printing this when I try to push the merge: monotone: discarding debug log monotone: fatal: std::logic_error: netsync.cc:565: invariant 'I(j != attach_map.end())' violated Doesn't look good. I'll send this to the monotone people. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-12-10 12:42:06
|
On Fri, Dec 10, 2004 at 02:35:34PM +0200, Dan Aloni wrote: > On Thu, Dec 09, 2004 at 10:22:08AM +0100, Henry Nestler wrote: > > Dan Aloni wrote: > > >Hello, > > > > > >As the subject says, I've upgraded the monotone server to run 0.15. > > >This version is incompatible with 0.14. Please follow instructions at: > > > > > > http://www.venge.net/monotone/README.changesets > > > > > >BTW, you may also need to recreate your working copies after migrating > > >the database. > > > > > > > Can only not automatic find your last certs. Database have created new, > > init and downloaded, followed by stepguide. > > http://www.colinux.org/?section=scs > > > > Can you repair this? Or must we add your public key? > > It turned out that I had to push some null revision in order > to get it fixed, and then it insisted on a merge with gboutwel's > revision. > > However, I now see the server printing this when I try > to push the merge: > > monotone: discarding debug log > monotone: fatal: std::logic_error: netsync.cc:565: invariant 'I(j != attach_map.end())' violated > > Doesn't look good. I'll send this to the monotone people. http://lists.gnu.org/archive/html/monotone-devel/2004-11/msg00059.html Seems to be fixed already, I'll try to upgrade. -- Dan Aloni da...@co... |
From: Henry N. <Henry.Ne@Arcor.de> - 2004-12-10 16:59:41
|
Dan Aloni wrote: > On Fri, Dec 10, 2004 at 02:35:34PM +0200, Dan Aloni wrote: > >>On Thu, Dec 09, 2004 at 10:22:08AM +0100, Henry Nestler wrote: >> >>>Dan Aloni wrote: >>> >>>>Hello, >>>> >>>>As the subject says, I've upgraded the monotone server to run 0.15. >>>>This version is incompatible with 0.14. Please follow instructions at: >>>> >>>> http://www.venge.net/monotone/README.changesets >>>> >>>>BTW, you may also need to recreate your working copies after migrating >>>>the database. >>>> >>> >>>Can only not automatic find your last certs. Database have created new, >>>init and downloaded, followed by stepguide. >>> http://www.colinux.org/?section=scs >>> >>>Can you repair this? Or must we add your public key? >> >>It turned out that I had to push some null revision in order >>to get it fixed, and then it insisted on a merge with gboutwel's >>revision. >> >>However, I now see the server printing this when I try >>to push the merge: >> >>monotone: discarding debug log >>monotone: fatal: std::logic_error: netsync.cc:565: invariant 'I(j != attach_map.end())' violated >> >>Doesn't look good. I'll send this to the monotone people. > > > http://lists.gnu.org/archive/html/monotone-devel/2004-11/msg00059.html > > Seems to be fixed already, I'll try to upgrade. > I pull your last trying from 2004-12-10T12:28:41. Get an error, if diff two versions. # monotone diff ea8c1a30ea72ca847c459 42e68775e8ff9fc8 monotone: fatal: std::logic_error: database.cc:769: invariant 'I(ident() != "")' violated My thing is, that gboutwel have no key in database (private or public). Can you or George add this key? If I download new database (init and so before), and use onmy monotone version 0.15, than have this error. # monotone --db=colinux.db list certs ea8c1a30ea72ca847c45 monotone: warning: no public key 'gbo...@pr...' found in database ----------------------------------------------------------------- Key : gbo...@pr... Sig : unknown Name : changelog Value : * add configre, drop patch/w32api-2.5.diff ...snip... Other idea. Perhaps you can do this steps on server? 0) use old DB from 0.14, call tstep 1 to 3 with new binary 1) monotone --db=co.db db migrate 2) monotone --db=co.db db changesetify 3) monotone --db=co.db pull monotone.colinux.org stable Created by Lucas. After this stepguide, my local database is correct, and have key for gboutwel. -- Henry Nestler |
From: Henry N. <Henry.Ne@Arcor.de> - 2004-12-11 16:39:37
|
Ok, Database on server is ok now. Have checked the standard client version for 0.15 on WinXP. Henry Nestler wrote: > Dan Aloni wrote: > >> On Fri, Dec 10, 2004 at 02:35:34PM +0200, Dan Aloni wrote: >> >>> On Thu, Dec 09, 2004 at 10:22:08AM +0100, Henry Nestler wrote: >>> >>>> Dan Aloni wrote: >>>> >>>>> Hello, >>>>> >>>>> As the subject says, I've upgraded the monotone server to run 0.15. >>>>> This version is incompatible with 0.14. Please follow instructions >>>>> at: >>>>> http://www.venge.net/monotone/README.changesets >>>>> >>>>> BTW, you may also need to recreate your working copies after migrating >>>>> the database. >>>>> >>>> >>>> Can only not automatic find your last certs. Database have created new, >>>> init and downloaded, followed by stepguide. >>>> http://www.colinux.org/?section=scs >>>> >>>> Can you repair this? Or must we add your public key? >>> >>> >>> It turned out that I had to push some null revision in order to get >>> it fixed, and then it insisted on a merge with gboutwel's revision. >>> >>> However, I now see the server printing this when I try to push the >>> merge: >>> >>> monotone: discarding debug log >>> monotone: fatal: std::logic_error: netsync.cc:565: invariant 'I(j != >>> attach_map.end())' violated >>> >>> Doesn't look good. I'll send this to the monotone people. >> >> >> >> http://lists.gnu.org/archive/html/monotone-devel/2004-11/msg00059.html >> >> Seems to be fixed already, I'll try to upgrade. >> > > I pull your last trying from 2004-12-10T12:28:41. > Get an error, if diff two versions. > > # monotone diff ea8c1a30ea72ca847c459 42e68775e8ff9fc8 > monotone: fatal: std::logic_error: database.cc:769: invariant 'I(ident() > != "")' violated > > My thing is, that gboutwel have no key in database (private or public). > Can you or George add this key? > > > If I download new database (init and so before), and use onmy monotone > version 0.15, than have this error. > > # monotone --db=colinux.db list certs ea8c1a30ea72ca847c45 > monotone: warning: no public key 'gbo...@pr...' found in database > ----------------------------------------------------------------- > Key : gbo...@pr... > Sig : unknown > Name : changelog > Value : * add configre, drop patch/w32api-2.5.diff > ...snip... If you have get some empty heads from buggy database on server, please use your backup database from version 0.14 and next steps! > 0) use old DB from 0.14, call tstep 1 to 3 with new binary > 1) monotone --db=colinux.db db migrate > 2) monotone --db=colinux.db db changesetify > 3) monotone --db=colinux.db pull monotone.colinux.org stable 4) monotone --db=colinux.db heads --branch=stable stdout> monotone: branch 'stable' is currently merged: stdout> fa6cb8eadb5496d12...2731 da...@co... 2004-12-11T10:17:27 -- Henry Nestler |
From: Nuno L. <li...@xp...> - 2004-12-09 16:41:23
|
Dan Aloni, dando pulos de alegria, escreveu : > Hello, > > As the subject says, I've upgraded the monotone server to run 0.15. > This version is incompatible with 0.14. Please follow instructions at: > > http://www.venge.net/monotone/README.changesets > > BTW, you may also need to recreate your working copies after migrating > the database. > For those that already have a monotone database for the old version, the steps to update it are the following (after you have a monotone binary of the right version - 0.15): 1) monotone db migrate 2) monotone db changesetify 3) monotone pull monotone.colinux.org stable 4) monotone update Do this in your source directory (where you have the MT/ subdirectory). If not, add a "--db=path/to/colinux.db" to the above (except in steps 3 and 4, as they need to be in the source directory). There is an optional step just to clean up obsolete old state: 5) monotone db execute "delete from manifest_certs" Regards, ~Nuno Lucas |