Package Details: mastodon 2.8.0-1

Git Clone URL: https://aur.archlinux.org/mastodon.git (read-only)
Package Base: mastodon
Description: Self-hosted social media and network server based on ActivityPub and OStatus
Upstream URL: https://joinmastodon.org
Licenses: AGPL3
Conflicts: mastodon-git
Submitter: flacks
Maintainer: None
Last Packager: flacks
Votes: 5
Popularity: 0.005860
First Submitted: 2018-06-19 19:35
Last Updated: 2019-04-13 17:31

Latest Comments

Llaurence commented on 2019-03-04 22:17

Gemfile.lock should not be removed: https://github.com/tootsuite/mastodon/issues/8983#issuecomment-437533243

diff --git a/PKGBUILD b/PKGBUILD
index 8eb9f76..f47195d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -38,10 +38,9 @@ sha512sums=('1829f16a5f98d1815168c8ecfd80b75bb3489e7b3e5eb06a858b0d35bdecc5a4542

 build() {
   cd mastodon-$pkgver
-  rm Gemfile.lock
-  bundle lock --update
-  bundle install --deployment --without development test
+  sed -i "s/1.17.3/$(bundle --version | cut -d' ' -f3)/g" Gemfile.lock
+  bundle install -j$(getconf _NPROCESSORS_ONLN) --deployment --without development test
   yarn config set ignore-engines true
   yarn install --pure-lockfile
 }

fbrennan commented on 2018-12-20 00:41

I'm not interested in fixing the namcap errors. Most of them are wrong anyway - namcap can't tell, but yes ffmpeg and magick are both used. Others would require that each Node module and Ruby gem be itself individually packaged and required instead of downloaded and built. Just by the nature of Node versioning that would be a nightmare to deal with.

buzo commented on 2018-12-19 16:28

Did you run namcap on the resulting package? It produces a huge amount of warnings and errors, see this paste.

Also, please rename the source tarball, preferably like this:

source=("$pkgname-$pkgver.tar.gz::<https://github.com/tootsuite/mastodon/archive/v>$pkgver.tar.gz"

fbrennan commented on 2018-12-11 04:43

Thank you @luka-devnull :-)

And for your previous comments as well. Helped me update the package after your first flag.

luka-devnull commented on 2018-12-08 09:31

v2.6.5 is out, which fixes a bug with yarn yanking packages in the pre v2.6.4 releases (including v2.6.2)

It's as easy as just updating the version number and the sha512sum though.

luka-devnull commented on 2018-11-09 03:45

You should also include libidn as a dependency. It doesn't build without it.

count0 commented on 2018-09-07 14:50

I'm getting the following build error when trying to upgrade to 2.5.0:

[1/6] Validating package.json... error mastodon@: The engine "node" is incompatible with this module. Expected version ">=8". error Found incompatible module info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ==> ERROR: A failure occurred in build(). Aborting... :: failed to build mastodon package(s)

flacks commented on 2018-08-29 21:03

Celti, thanks for the feedback. Updated.

Celti commented on 2018-08-29 09:34

git is a required makedepend. This fails to build in a container without it.

EDIT: Apparently npm is also a required makedepend to prevent yarn from arbitrarily changing the working directory and causing build failures for being unable to find .yarnclean (peripherally described as a docker issue in #6809 but also valid here).

EDIT 2: It also appears that yarn is a full dependency, not a makedepend — precompiling assets when running bundle exec rails mastodon:setup fails entirely without it.