Thanks for the tip but I know that. I have full access to the voyage code. Without knowing the reason and context an issue is useless. Norbert
Am 26.03.2017 um 19:35 schrieb Stephane Ducasse <stepharo.self@gmail.com>:
Add an issue in the Voyage github repo and do a pull request to push esteban releasing a new version.
On Sun, Mar 26, 2017 at 1:15 PM, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote: I get that same problem, too, every time I do "Software update". But never understood the rationale of dropping a database at this point. I think we should remove this line
Norbert
Am 25.03.2017 um 22:04 schrieb Hilaire <hilaire@drgeo.eu <mailto:hilaire@drgeo.eu>>:
ah yeah, I wrote an internal durty hack to get it rolling
cleanUp: aRepository (aRepository isKindOf: Boolean) ifFalse: [ aRepository dropDatabase]
Le 25/03/2017 à 21:46, Hilaire a écrit : It occurs in Pharo5, likely not in Pharo4, or may be I fixed in my image, I don't remember.
-- Dr. Geo http://drgeo.eu <http://drgeo.eu/>