Hey there,

On Sat 12 Apr 2025 at 02:23:15 +0000, ~jahway603 wrote:

I then decided to try the latest commit acd9d04f, ran into errors & was still unable to build. I saw some type of error about mediagoblin/tests/test_ldap.py:32: could not import 'ldap': No module named 'ldap', so then installed the python3-ldap package, tried to build again, and then that ldap error went away but it was still not able to build.

This is odd: ldap should be detected as missing, and the tests skipped.

Do you have an optimal place to past error logs? Any ideas?

Looks like SourceHut has one: https://paste.sr.ht/. The output of your configure script, as well as config.log would be useful to see.

-- Olivier Mehani shtrom+mediagoblin@ssji.net PGP fingerprint: 4435 CF6A 7C8D DD9B E2DE F5F9 F012 A6E2 98C6 6655 Confidentiality cannot be guaranteed on emails sent or received unencrypted.

I believe the gstreamer1 package name may be the equivalent of that on AlmaLinux.

I tried to add commit c70e444c in there and it still would not build.

I then decided to try the latest commit acd9d04f, ran into errors & was still unable to build. I saw some type of error about mediagoblin/tests/test_ldap.py:32: could not import 'ldap': No module named 'ldap', so then installed the python3-ldap package, tried to build again, and then that ldap error went away but it was still not able to build.

Do you have an optimal place to past error logs? Any ideas?

"~jahway603" outgoing@sr.ht writes:

Since rabbitmq-server is not available by default on AlmaLinux 9.x, I was able to get it setup by following RabbitMQ's upstream instructions here.

If you'd prefer, you can also use Redis:

[celery] broker_url = "redis://"

I am stuck on the make step under "Install MediaGoblin".

Below is a PrivateBin link with the stdout/stderr shown when running through this step: https://bin.linux.pizza/?ff1480ed2fa7c694#CCt8FxTXFmut26Q6cc7UoWW7QGE5CrANQ3Zin5XHo8aW

We fixed a similar error "can't copy 'licenses/*'" seen in Debian 11 on the master branch back in October (c70e444c). Could you please try that branch and see if this is resolved for you?

The issue appears to be that slightly older versions of Python, Setuptools, Pip or similar don't support the wildcard syntax in setup.cfg's "options.data_files" config.

For what it's worth, we do have a Fedora CI build which might offer some clues as to what the appropriate OS packages are called:

https://git.sr.ht/~mediagoblin/mediagoblin/tree/master/item/.builds/fedora-39.yml

I am following the step-by-step guide to installing MediaGoblin here.

Since rabbitmq-server is not available by default on AlmaLinux 9.x, I was able to get it setup by following RabbitMQ's upstream instructions here.

I am stuck on the make step under "Install MediaGoblin".

Below is a PrivateBin link with the stdout/stderr shown when running through this step: https://bin.linux.pizza/?ff1480ed2fa7c694#CCt8FxTXFmut26Q6cc7UoWW7QGE5CrANQ3Zin5XHo8aW

• From the output above, I tried installing boost, which included boost-python3
• I believe I found the required audio & video packages to install within docs/source/siteadmin/media-types.rst - could not find an equiv AlmaLinux package for python3-gstreamer1.

I then tried make again, and here is the result:
https://bin.linux.pizza/?1fdf4a3e77d194a2#Ef1Xpkbd1yvVsBPTiewt52srFpJa9doLZ1Z1x3zERvur

Any ideas on what to try next to fix this?

I like this idea @sturm and the basic installer shell script you've written so far.

In https://docs.mediagoblin.org/en/master/siteadmin/deploying.html, there are only git commands pulling mediagoblin code from Savannah and no documentation on how to build from Sourcehut (SH).

When I type git status, I should not be getting "Not currently on any branch." when dealing with a Sourcehut repo. The git command options are totally different between SH and what is documented in https://docs.mediagoblin.org/en/master/siteadmin/deploying.html.

This issue was attempted to be reported in Issue #37 which was incorrectly resolved as "Documentation missing on how to build from sourcehut".

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.

Olivier: I'm just happy I was able to get anything to work as I ran into issue after issue to finally get this up and running today. I followed the instructions here, https://docs.mediagoblin.org/en/master/siteadmin/deploying.html, which mostly worked. I'd like to contribute documentation but I need to learn how to do that on here or Savannah.

I'm using v0.12.1rc1 branch and Python 3.9.2 on Debian 11. Is there anything I can run here to get better data for this issue?

Found this link to setup the audio plugin and pre-req, https://docs.mediagoblin.org/en/master/siteadmin/media-types.html, but it doesn't specify what is supported.