It seems any Werkzeug version 0.11 or higher breaks out test_comment_notification test, it seems the port number is dropped from the URL in the email body:

I've converted the "\n" to newlines to make it more readable.

Werkzeug 0.10.4 or below:

Hi otherperson, chris commented on your post (​http://localhost:80/u/otherperson/m/some-title/c/1/#comment) at GNU MediaGoblin

Test comment #42

GNU MediaGoblin

Werkzeug 0.11.0 and above:

Hi otherperson, chris commented on your post (​http://localhost/u/otherperson/m/some-title/c/1/#comment) at GNU MediaGoblin

Test comment #42

GNU MediaGoblin

We could just change it to have the port number in the test and it would pass however that means pinning werkzeug at 0.11 or higher, this may or may not be a problem I don't know, we already pin it at 0.7.0 or higher.

On latest master, I get the following error when trying to view the atom feed of a collection. Atom feed of a user still works fine.

Error - <type 'exceptions.TypeError'>: 'LocalUser' object is not callable
URL: https://goblinrefuge.com/mediagoblin/u/andrew/collection/concerts/atom/
File '/path/to/mediagoblin/lib/python2.7/site-packages/paste/exceptions/errormiddleware.py', line 144 in __call__
  app_iter = self.application(environ, sr_checker)
File '/path/to/mediagoblin/mediagoblin/app.py', line 342 in __call__
  return self.call_backend(environ, start_response)
File '/path/to/mediagoblin/lib/python2.7/site-packages/Werkzeug-0.10.1-py2.7.egg/werkzeug/wsgi.py', line 591 in __call__
  return self.app(environ, start_response)
File '/path/to/mediagoblin/mediagoblin/app.py', line 276 in call_backend
  return self._finish_call_backend(request, environ, start_response)
File '/path/to/mediagoblin/mediagoblin/app.py', line 318 in _finish_call_backend
  response = controller(request)
File '/path/to/mediagoblin/mediagoblin/user_pages/views.py', line 626 in collection_atom_feed
  'name': obj.get_actor().username,
TypeError: 'LocalUser' object is not callable

Per the conversion on the devel list, activities which have deleted media cause issues in migrations such as 29 and 42. These migrations expect activity objects or targets to be non-null, so they don't know how to handle activities with deleted objects.