~mediagoblin

Trackers

~mediagoblin/mediagoblin

Last active 2 months ago

#44 Mediagoblin webpage on Sourcehut is linked to wrong domain 3 months ago

Comment by ~mediagoblin on ~mediagoblin/mediagoblin

REPORTED RESOLVED FIXED

#12 Configure step fails on Arch Linux with syntax error near unexpected token `newline' 3 years ago

Comment by ~mediagoblin on ~mediagoblin/mediagoblin

Great, thanks Charlotte! Could you please tell me what version of autoconf you have by running autoconf --version?

#15 Copy contributing docs over from wiki to sphinx 3 years ago

Ticket created by ~mediagoblin on ~mediagoblin/mediagoblin

We need high-quality contributor docs and we don't have any.

#14 Are ./configure && make appropriate for MediaGoblin? 3 years ago

Ticket created by ~mediagoblin on ~mediagoblin/mediagoblin

(Updated to remove details about pyconfigure now this is gone.)

The autogen.sh/configure/make steps are pretty unusual for a Python application.

I suspect we may be able to add a lot of clarity and remove a significant barrier to contribution by looking at an alternative, but I'm not fully across the background here.

./autogen.sh && ./configure && make currently:

  • updates git submodules (bootstrap.sh)
  • looks for a python interpreter and venv module
  • makes a virtualenv
  • installs python dependencies into the virtualenv (./bin/python3 -m pip install --editable .)
  • runs devtools/update_extlib.sh to install Bower and then bower install jquery etc.
  • builds translations
  • builds texinfo docs (broken and we don't use anyway)

That's all pretty unusual for a Python application, and adds a lot of fairly dense build config/infrastructure.

The translation building makes sense, and it's nice that the system can find the python interpreter, but beyond that these tools aren't normally used to create virtualenvs and install Python/JS deps. That's a bit unusual.

Installing could be a compelling feature, if we're not installing as a Python package. But maybe a python package would be easier.

#13 View all users media link is hard to find 3 years ago

Ticket created by ~mediagoblin on ~mediagoblin/mediagoblin

The only way to get to the "view all a user's media" page is via a hard to spot link at the bottom of the profile page below the first page of media.

This link should be to below the profile text and collections link (if applicable).

It's not so clear what the difference between the profile and the "all media" pages are since they both show media. Maybe the profile should only show the most recent items?

#12 Configure step fails on Arch Linux with syntax error near unexpected token `newline' 3 years ago

Ticket created by ~mediagoblin on ~mediagoblin/mediagoblin

lilmike reported by IRC that:

So I've got a really strange issue. I'm trying to run mediagoblin on arch
linux, and running ./bootstrap.sh works fine, but upon running configure I
get
checking for python3... python3
./configure: line 1934: syntax error near unexpected token `newline'
./configure: line 1934: ` '''
This has been happening even before the new release, it's just so strange

Ben suspects this is related to the autoconf version as has seen the same in Guix. Specifying autoconf2.69 in Guix fixes the issue.

#5 --system-site-packages is hard-coded, so why do we specify it during deployment? 3 years ago

Comment by ~mediagoblin on ~mediagoblin/mediagoblin

Fixed in 0db9b5bb by removing the VIRTUALENV_FLAGS='--system-site-packages' from docs and CI builds.

REPORTED RESOLVED FIXED

#11 [PATCH] Testing. 3 years ago

on ~mediagoblin/mediagoblin

REPORTED RESOLVED INVALID

#5 --system-site-packages is hard-coded, so why do we specify it during deployment? 3 years ago

Comment by ~mediagoblin on ~mediagoblin/mediagoblin

I've just run:

make distclean
./bootstrap
./configure
make

and confirmed that make uses --system-site-packages. I think we're safe to remove it from our docs and CI builds.

#4 Replace werkzeug.contrib.atom.AtomFeed with something else 3 years ago

Comment by ~mediagoblin on ~mediagoblin/mediagoblin

Done! werkzeug.contrib.atom.AtomFeed has been replaced with FeedGenerator and we can now move beyond Werkzeug 1.0.

REPORTED RESOLVED FIXED