Re: [fossil-users] Is fossil export known to be broken?

On 2015-12-12T16:06:20 -0800 jungle Boogie wrote: > > Great news! > > Did you happen to change your git version at all during either test? Nope, same version all along (2.6.2). M ___ fossil-users mailing list

Re: [fossil-users] Is fossil export known to be broken?

On Sun, Dec 13, 2015 at 02:12:01PM +0100, Piotr Orzechowski wrote: > I've just looked at release notes for 1.34 and 1.33 and there was no > straightforward note about need to rebuild repositories. Maybe it would > be better to add such information to requiring release notes, or maybe > even fossil

Re: [fossil-users] Is fossil export known to be broken?

I've just looked at release notes for 1.34 and 1.33 and there was no straightforward note about need to rebuild repositories. Maybe it would be better to add such information to requiring release notes, or maybe even fossil would be able to suggest repo rebuilding itself? Pozdrawiam / With best

Re: [fossil-users] Is fossil export known to be broken?

On 13 December 2015 at 05:12, Piotr Orzechowski wrote: > I've just looked at release notes for 1.34 and 1.33 and there was no > straightforward note about need to rebuild repositories. Admittedly I don't do it every time, but I thought that was something to be done for every

Re: [fossil-users] Is fossil export known to be broken?

I guess it would be better to change help message about rebuild then. As of now, it says "Run this command after updating the fossil executable in a way that changes the database schema." So I would expect to see some information about such need in release notes. Perhaps it would be better to add

Re: [fossil-users] Is fossil export known to be broken?

On Sun, Dec 13, 2015 at 09:57:44PM +0100, Piotr Orzechowski wrote: > I guess it would be better to change help message about rebuild then. > As of now, it says "Run this command after updating the fossil > executable in a way that changes the database schema." So I would > expect to see some

Re: [fossil-users] Is fossil export known to be broken?

Thanks for clarifying that. So I guess it would be either release note advise or schema change notification when running maybe even any command, if it was up to me. ;) Pozdrawiam / With best regards, Orzech W dniu 13.12.2015 o 22:58, Joerg Sonnenberger pisze: > I wouldn't advise to run it after

Re: [fossil-users] Migrating github issues to fossil

Thanks a lot for the help. I ended up building myself something in python to do the following: 1) Pull down the github issues from their API with curl (based on http://www.fullo.net/blog/2012/06/25/export-github-issues-as-csv-with-v3-api/ ). 2) Make 'fossil ticket add' comments (like your Perl)