#37 Documentation missing on how to build from sourcehut a month ago

Comment by ~sturm on ~mediagoblin/mediagoblin

I forgot to mention, the SourceHut and Savannah repositories are kept in sync, so there's no issues with sticking with whatever you have.

#37 Documentation missing on how to build from sourcehut a month ago

Comment by ~sturm on ~mediagoblin/mediagoblin

From speaking with ~jahway603 on IRC, we've confirmed that the newly released version 0.12.1 fixes the Jinja2 issue. Please see the documentation on upgrading for how to switch to this version:

https://docs.mediagoblin.org/en/stable/siteadmin/upgrading.html\

I appreciate that this approach of checking out a git tag is confusing. We'll take this on board and consider how to make the process simpler. Ideally I'd like to avoid people running MediaGoblin from having to use git at all.

REPORTED RESOLVED CLOSED

#38 SyntaxWarning when running ./bin/gmg a month ago

Comment by ~sturm on ~mediagoblin/mediagoblin

This warning is originating from the PyLD library and not MediaGoblin itself. These sorts of warnings are relevant to developers, but not to users of MediaGoblin, so I think we probably should disable them. Does that sound reasonable to you Olivier?

#34 Jinja2 error during make 3 months ago

on ~mediagoblin/mediagoblin

~sturm, thanks, I will try the new changes you pushed, and also try using a different python version, I vaguely remember how to do that, or in any case google will know. Thanks for your hard work and for letting us know!

#32 Choose Favicon in HTML Title 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

Thanks ~bxbrenden, I've updated the ticket title so that it now only mentions the favicon.

#16 cannot process audio files 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

"~lilmike" outgoing@sr.ht writes:

TLDR: It's an arch issue, nothing you can do with the manifest to work around it.

Thanks Mike! I'll leave this ticket open for a while to see if anything changes in a few months with an updated image.

#16 cannot process audio files 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

Hi Michael,

Sorry for the delayed reply. I've just tried your Arch CI build for SourceHut, but doesn't seem to run as expected. Here's the build:

https://builds.sr.ht/~mediagoblin/job/952039

and here's the branch "arch":

https://git.sr.ht/~mediagoblin/mediagoblin/commit/8fbb8f01f2e458591859230ead29228c45db5619

If you had a chance to investigate, that would be very useful. I've never used Arch myself.

#35 Suggested minor gitignore updates 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

Hmm, removing install-sh seems to have broken our SourceHut CI builds, so I've rolled back that change. I don't know enough about install-sh to see what the issue is. It appears to be regenerated locally for me when ./bootstrap.sh runs, but not in CI.

https://builds.sr.ht/~mediagoblin/job/952036 (Debian 11) https://builds.sr.ht/~mediagoblin/job/952037 (Ubuntu 20.04)

RESOLVED IMPLEMENTED REPORTED

#35 Suggested minor gitignore updates 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

Thanks ~peter_horvath. I've merged this change. The challenge with package-lock.json and package.json is that they're a symptom of us needing to move to npm install and possibly adding a JS build step as opposed to using the legacy Bower tool.

REPORTED RESOLVED IMPLEMENTED

#34 Jinja2 error during make 3 months ago

Comment by ~sturm on ~mediagoblin/mediagoblin

Hi ~blagovest, ~iptrip, I've just pushed up some changes to the master branch that installs a recent Pip and uses pip install rather than python setup.py develop to install dependencies. I suspect this, in combination with the pinned maximum version on Jinja2, should now fix your issues. Apologies for the slow response. Please re-open this if you're still experiencing issues.

~komali2, unfortunately we have some version of dependencies that don't yet work on Python 3.10 (which Ubuntu 22.04 runs). The main culprit is Celery I believe. For now I've specified a maximum Python version to help avoid confusion. Fixing this situation iscertainly on my mind though. Feel free to open a separate ticket to help us track it.

REPORTED RESOLVED FIXED