Jupyter-book: Problem with the migration of books to 0.6.3

[nozebacle]

Hello,

I just encountered a very weird problem with a book that I upgraded from 0.5.1 to 0.6.3

I always used deploy.sh to build the book and when I upgraded my local installation of jupyter-books it required me to migrate the book to the new version. I did it apparently without problems, but from then on it was impossible to me to see changes on my deployed github pages books.

I think I just discovered the root of the issue: inside my old _build folder I had old .md files. Thus, every time I changed my source in content, either the gh pages system or my local jekyll were ignoring the changes and using the outdated .md file.

I guess this can be fixed in the migration script if it deletes the .md files from the _build folder.

[choldgraf]

oh no! that's a good catch - so just to be clear, a fix here would be to ensure that old .md files in the _build folder are deleted upon upgrade...is that right?

[nozebacle]

That's what seems to me like the right fix. I deleted the old .md files in _build and now everything is updated when it should. I cannot say anything about old notebook files, but for markdown that seems to be the neccessary fix.

[choldgraf]

This should now be fixed in #449 - thanks for bringing it up!