Your command didn't work: $ echo -n ".headers on \n select * from migrate_version;"|sqlite3 state.sqlite Usage: .headers on|off
But doing it manually: $ sqlite3 state.sqlite sqlite> .headers on sqlite> select * from migrate_version; repository_id|repository_path|version Buildbot|/usr/lib/python2.7/dist-packages/buildbot/db/migrate|22 $ls -al rwxr-xr-x 1 USER USER 228 sie 27 14:24 . drwxr-xr-x. 1 USER USER 718 wrz 1 07:29 .. -rw-r--r-- 1 USER USER 1,1K maj 14 11:37 buildbot.tac drwx------ 1 USER USER 118 maj 15 08:34 gitpoller-workdir -rw------- 1 USER USER 888K sie 18 08:16 http.log -rw-r--r-- 1 USER USER 5,7K cze 3 12:34 master.cfg -rw------- 1 USER USER 4,4K maj 14 11:37 master.cfg.sample drwxr-xr-x 1 USER USER 94 maj 14 11:37 public_html drwx------ 1 USER USER 491K sie 18 08:24 runtests -rw-r--r-- 1 USER USER 136M sie 18 08:14 state.sqlite drwxr-xr-x 1 USER USER 20 maj 14 11:37 templates -rw-r--r-- 1 USER USER 65M sie 27 14:24 twistd.log If it's hard to reproduce then we can close this bug as incident because i'm can to drop all my history and start with fresh one. I submitted this bug not to restore builds history but to find a problem :) On Wed, 27 Aug 2014 18:38:49 +0300 Andriy Senkovych <jolly_ro...@itblog.org.ua> wrote: > Package: buildbot > Followup-For: Bug #758857 > > Hello fri.K, > > Thank you for your feedback, but I'm not able to reproduce the bug you > mentioned. I have tried to upgrade several different master instances and got > upgraded with no problem. > > Please specify more information on your setup. What is the contents of > migrate_version table. To get this info, run following: > > echo -n ".headers on \n select * from migrate_version;"|sqlite3 state.sqlite > > Example output: > > repository_id|repository_path|version > Buildbot|/usr/lib/python2.7/dist-packages/buildbot/db/migrate|24 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
