UpgradeValidationException when there is no "default" journal

[anoopd]

I have installed latest jrnl using pip and tried to run it ....... i had two journals work and fitness which the new one asked will be upgraded and i gave a yes but i got

 Upgrading plain text 'default' journal stored in /Users/anoopd/journal.txt...
  Created a backup at /Users/anoopd/journal.txt.backup

Upgrading plain text 'work' journal stored in ~/work.txt...
Created a backup at ~/work.txt.backup

 Upgrading plain text 'fitness' journal stored in ~/fitness.txt...
 Created a backup at ~/fitness.txt.backup

 The following journal failed to upgrade:
 default
  Aborting upgrade.`

[wren]

This sounds to me like you don't have a default journal. Which I hadn't considered before. If you copy one of your other journal to the default journal location (e.g. cp ~/work.txt ~/journal.txt), does that allow the migration to complete? I suspect that should get you unstuck.

If that does work, please report back. It would point to a bug in how we handle journals that exist in the config, but not on the file system.

[anoopd]

Sorry to mention , i have already tried that by doing touch ~/work.txt and touch ~/journal.txt even before i posted this issue .

[wren]

@anoopd touch ~/journal.txt is going to give you an empty file for a journal, which will likely have an error. Can you try cp ~/work.txt ~/journal.txt and see if that works? We do still need to fix the bug, but this command might get you going in the meantime.

[rinat715]

I got the same error.
`Following plain text journals will upgraded to jrnl 2.0.0:
default -> /home/archman/Documents/configs/journal.txt
Continue upgrading jrnl? [y/N]
y

Upgrading plain text 'default' journal stored in /home/archman/Documents/configs/journal.txt...
Created a backup at /home/archman/Documents/configs/journal.txt.backup
DEBUG jrnl.Journal opened LegacyJournal with 30 entries
DEBUG jrnl.Journal Imported 30 entries from LegacyJournal to PlainJournal

The following journal failed to upgrade:
default
Aborting upgrade.
Please tell us about this problem at the following URL:
https://github.com/jrnl-org/jrnl/issues/new?title=UpgradeValidationException
Exiting.`

[anoopd]

@wren Thank you , i deleted journal.txt and copied the work.txt as journal.txt and it is working now ! Thank you

[wren]

@anoopd I'm glad that worked for you! We still need to fix this bug to handle it better for other users, so I'm going to leave it open for now.

[pspeter]

Upgrading fails for me too. After some debugging I noticed that the new Journal class seems to completely ignore the config["dateformat"] and thus parses the old dates wrong. That's why upgrading seems to fail.

My dateformat was %d.%m.%Y %H:%M. 09.05.2019 gets interpreted as 2019-09-05, but it should be 2019-05-09.

I guess this makes this issue related to #630.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.