It was a croxis problem after all! Had another process eating too much memory.
Search Criteria
Package Details: mastodon 4.6.3-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mastodon.git (read-only, click to copy) |
|---|---|
| Package Base: | mastodon |
| Description: | Your self-hosted, globally interconnected microblogging community |
| Upstream URL: | https://github.com/mastodon/mastodon |
| Keywords: | activitypub fediverse mastodon server |
| Licenses: | AGPL3 |
| Submitter: | flacks |
| Maintainer: | zoltix |
| Last Packager: | zoltix |
| Votes: | 27 |
| Popularity: | 0.151756 |
| First Submitted: | 2018-06-19 19:35 (UTC) |
| Last Updated: | 2026-07-03 16:55 (UTC) |
Dependencies (18)
- corepack
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-ffplayoutAUR, ffmpeg-cudaAUR, ffmpeg-whisper-gitAUR, ffmpeg-decklinkAUR, ffmpeg-whisperAUR, ffmpeg-cuda-fullAUR, ffmpeg-amd-full-gitAUR, librempeg-gitAUR, ffmpeg-full-llvmAUR, ffmpeg-fullAUR, ffmpeg-libfdk_aacAUR, ffmpeg-amd-fullAUR, ffmpeg-headlessAUR, ffmpeg-obsAUR, ffmpeg-gitAUR, ffmpeg-full-gitAUR)
- git (git-gitAUR, git-glAUR, git-wd40AUR)
- libheif (libheif-highmemAUR, libheif-noglycinAUR, libheif-gitAUR)
- libidn (libidn-gitAUR)
- libpqxx (libpqxx-gitAUR)
- libvips (libvips-gitAUR, libvips-notiffAUR)
- libxml2 (libxml2-gitAUR, libxml2-meson-gitAUR)
- libxslt (libxslt-gitAUR)
- libyaml (libyaml-gitAUR)
- nodejs (nodejs-gitAUR, nodejs-lts-hydrogenAUR, python-nodejs-wheelAUR, nodejs-lts-iron, nodejs-lts-jod, nodejs-lts-krypton)
- postgresql (postgresql-12AUR, postgresql13AUR, postgresql-gitAUR, postgresql15-docsAUR, postgresql15AUR, postgresql16-docsAUR, postgresql16AUR, postgresql17-docsAUR, postgresql17AUR, postgresql18-docsAUR, postgresql18AUR)
- protobuf (protobuf-gitAUR)
- ruby-bundler
- sudo (sudo-gitAUR, fudo-gitAUR, sudo-selinuxAUR, doas-sudo-shim-gitAUR, run0-sudoAUR, run0-sudo-shim-selinuxAUR, run0-sudo-shimAUR, run0-sudo-shim-gitAUR, doas-sudo-shimAUR, voixAUR, sudo-rs-system-names-gitAUR)
- valkey (valkey-gitAUR)
- yarn-berryAUR
- zlib (zlib-gitAUR, zlib-ng-compat-gitAUR, zlib-ng-compat)
Required by (0)
Sources (5)
croxis commented on 2026-06-29 17:27 (UTC)
zoltix commented on 2026-06-25 14:03 (UTC)
I ran a test on my local test machine and I didn’t have any issue. Please send me the log you sent earlier again, and I’ll have a look.
zoltix commented on 2026-06-25 13:39 (UTC)
It may sound obvious, but please also check that you have enough free disk space and inodes available during the build.
df -h df -i free -h
zoltix commented on 2026-06-25 13:37 (UTC)
Thanks for the report.
Unfortunately, the pasted output does not show the real error yet. The "YN0000" lines are only Yarn progress/status messages, so I would need the full build log to understand what actually failed.
Could you please retry with logging enabled and share the generated build log?
git clone https://aur.archlinux.org/mastodon.git cd mastodon makepkg -CsfL
Also, please include your Node/Corepack/Yarn versions if possible:
node --version corepack --version yarn --version
With the full log, I should be able to see whether this is a packaging issue, a dependency issue, or a temporary network/cache problem during the Yarn fetch step.
croxis commented on 2026-06-25 13:18 (UTC)
Thank you for updating the AUR! I'm getting the following error when doing a clean build on 4.6.1-2
➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0000: ⠸ ===========================================================================----- ==> ERROR: A failure occurred in build(). Aborting... -> error making: mastodon-exit status 4
Unfortunately there are no additional details.
zoltix commented on 2026-06-25 10:37 (UTC) (edited on 2026-06-25 10:40 (UTC) by zoltix)
Info for 4.6.2, we are using a non-Docker installation, this release does not apply directly to us.
This release was only made to update FFmpeg inside the Docker container images. Since we are not using Docker images, we can skip this Mastodon version.
The important point is to make sure that the system FFmpeg package is updated to a fixed version through the OS packages.
zoltix commented on 2026-06-18 12:01 (UTC)
I noticed an issue with avatars on my Mastodon instance: some accounts were showing the default icon instead of the custom avatar set by the user.
It looks like the database still referenced the avatars, but the physical files were missing or no longer correctly linked. I did a lot of tests, reinstalls and package changes, so it may be my own mistake.
But if anyone has the same issue with this installation, I have a small procedure to scan and restore the missing avatars. Let me know if you need it.
zoltix commented on 2026-06-17 21:47 (UTC)
Warning: this is not a simple package update.
Please carefully read the instructions displayed by "mastodon.install" during the installation/upgrade. Mastodon 4.6.0 requires a specific upgrade procedure, including database migrations, and the steps must be executed in the correct order.
This is more complex than I initially expected. I may try to improve and automate this process later, but for now, please follow the displayed procedure carefully.
zoltix commented on 2026-06-04 18:27 (UTC)
Thanks. Apparently this has been needed for quite a while. I’ll add libheif as a mandatory dependency in the PKGBUILD, since libvips only has it as optional on Arch and HEIC/HEIF uploads should just work.
nachtjasmin commented on 2026-06-04 15:10 (UTC)
I just realised that Mastodon also needs the libheif package. Otherwise, the upload of .heif/.heic pictures isn't possible. Semi-related issue: https://github.com/mastodon/mastodon/issues/31570
Pinned Comments
zoltix commented on 2026-06-25 10:37 (UTC) (edited on 2026-06-25 10:40 (UTC) by zoltix)
Info for 4.6.2, we are using a non-Docker installation, this release does not apply directly to us.
This release was only made to update FFmpeg inside the Docker container images. Since we are not using Docker images, we can skip this Mastodon version.
The important point is to make sure that the system FFmpeg package is updated to a fixed version through the OS packages.