"Trevor Daniels" <t.dani...@treda.co.uk> writes: > Further to this, I had a very helpful interchange today with one of > the other users at SourceForge who responded to my ticket. He > suggested exporting the text part of the DB as a JSON file, changing > all the occurrences of "author": "*anonymous" to "author": > "tdanielsmusic", and re-importing the file. I tried this. It works > and fixes the exposure problem. I've now created a new account > "googleimporter" and am in the process of changing the author to that > in all the imported tickets so my account remains separate. > > However, this has exposed another difficulty. Importing DBs is a > bottleneck. I managed to import part of the first file I modified, > enough to check it fixes the problem, but importing the main DB with > 4000-odd issues has so far failed due to congestion. The file uploads > but is then rejected with "Too many pending imports. Please try > later." This suggests we should aim to start the migration proper > early rather than later.
Should I ask at Savannah how they view the prospect of running Allura? Are there obvious selling points over Savane? Like that there is an API for manipulating issues? -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
