fossil reconstruct fails right after fossil deconstruct.
running fossil deconstruct ~/artifactdir from within a fossil source checkout and then fossil reconstruct clone.fossil ~/artifactdir fails.  Fossil does create clone.fossil but most of the tables contained within are empty.  fossil ui clone.fossil brings up an empty project with nothing in its timeline.
I've also tried fossil deconstruct -R fossil.fossil ~/artifactdir instead of being inside of a checkout as above.  After running deconstruct the artifact directory is populated with artifacts and a cursory check against fossil ui shows that they contain the right things.  So I'm only guessing that reconstruct is the problem...

i tested successfully a deconstruct(into a local directory of checkout) / reconstruct(into std-dir of my multi repo. server) of my clone of

the reconstructed repository worked. some things to mention:
  *  the number of artifacts files matches the number of artifacts displaed on the stat page
  *  the new repo-file was much bigger than the original; the stat page shows a big number of free pages in the sqlite db

so i think too, it should be a problem of reconstruct, but i don´t understand this part of the code :-(

i get the same error, if i use the standard deconstruct with subdirectories, named like the first 2 chars from the uuid.

if exporting with <b>-L 0</b> in a flat list of files, it works.

the current implemenation of reconstruct ignores subdirectories and reads files only in the given dir, not recursing into the subdirs:
<pre>
      if( file_isdir(pEntry->d_name)==1 ){
        continue;
      }
</pre>

with checkin [92f8cefcc8] i've extended the command help with notes about the flat import. i think, it´s not necessary to implement recursion in reconstruct.