If you are updating on a machine please follow these steps
*BEFORE* updating your code to this commit.

If you are installing on a fresh database and do not need to think
about existing data, ignore the following and proceed as usual.

1. Run the following migrations:
```
python manage.py migrate --fake scipost zero
python manage.py migrate --fake notifications zero
python manage.py migrate --fake partners zero
python manage.py migrate --fake affiliations zero
python manage.py migrate --fake commentaries zero
python manage.py migrate --fake comments zero
python manage.py migrate --fake finances zero
```

2. *** NOW UPDATE/PULL GIT ***
3. Run: `python manage.py migrate --fake-initial`

This commit fixes the migration bug which made postgresql
think there still was a relation to a non-exisition table
called scipost_feedback, scipost_motion and scipost_nomination.

CAUTION! This will however reset all existing relations
with the Remark model to VGM models.

Migrations are ready to be run without dataloss.
 If asked during `migrate` to alter stale FK field,
 run with anwser `no`! This is not stale, Django just
 thinks it is due to state migration of the new apps.