During my Debian 10 install testing, I noticed that after I enabled audio, my uploaded images were marked as failed processing and return 404. Then after uploading some audio and enabling video, all my audio was similarly marked as failed. It's fine for new uploads from there on, but the failed items remain failed.

One of my coworkers is running into this issue while trying to add audio support to our GMG instance. I'm posting it for them because it's currently not possible to sign up for new accounts on this bug tracker. Thanks! : )

I am following these instructions for audio: ​https://mediagoblin.readthedocs.io/en/stable/siteadmin/media-types.html

We have video, image, and pdf media types enabled. I am trying to add audio. I have added the dependencies. I get an AssertionError when adding mediagoblin.media_types.audio under the [plugins] section of my mediagoblin_local.ini file.

"/srv/ccs-mediagoblin/mediagoblin/mediagoblin/db/migration_tools.py", line 132, in migrations_to_run

assert self.database_current_migration is not None

AssertionError

The full traceback is identical to this unanswered mailing list message: ​https://lists.mediagoblin.org/pipermail/devel/2019-March/003243.html

Version: gmg 0.9.0 stable

I think it is referencing the pdf version being 0 in the database.

psql mediagoblin psql (9.3.24) Type "help" for help.

mediagoblin=> SELECT * FROM coremigrations WHERE name='mediagoblin.media_types.pdf';

name | version

mediagoblin.media_types.pdf | 0

(1 row)

Changing 0 to 1 does not have an effect.

If I remove the mediagoblin.media_types.audio line from mediagoblin_local.ini, the ./bin/gmg dbupdate command completes.

I did some of my own research about this issue. I wonder if this is related to the following file being nearly empty:

mediagoblin.git/mediagoblin/media_types/audio/migrations.py

It contains only: "MIGRATIONS = {}", whereas the 'video' analog contains more.

Any insights into this issue are appreciated. Thanks! : )

I thought I'd fixed this, but clearly not. Investigate what I did last time and check it has been applied permanently. Was related to HAProxy.