Arch Linux User Repository

Not you, personally. Those trying to build it and it failing on building the ruby-stud dependency. Don't be so touchy to those trying to help.

I don't need to do anything, I don't maintain ruby-stud, report the issue there.

Here's the fix. You need to download an manually patch ruby-stud package, build and install it.

https://github.com/jordansissel/ruby-stud/pull/33/commits/f0b8e6feb44fdeefbb936fee37d5ecb798d3b177

Then everything else can build just fine. Why are we depending on 13 year old broken code to do a build?

Again, not related to this package. makepkg does use bash by default, so that's not an issue. The issue with a specific ruby package that's broken, which is a dependency of a package required on aarch64: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=signal-desktop-beta#n56

That's not related to this package, report the issue to ruby-stud.

I'm on aarch64 / arm64. Last version I was able to build successfully was 7.41.0beta1-1. Since then it's constantly failing to build fpm due to being unable to build it's ruby-stud dependency.

==> Making package: ruby-stud 0.0.23-1 (Tue 25 Feb 2025 01:03:01 PM PST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
WARNING:  licenses is empty, but is recommended. Use an license identifier from
https://spdx.org/licenses or 'Nonstandard' for a nonstandard license,
or set it to nil if you don't want to specify a license.
WARNING:  open-ended dependency on rspec (>= 0, development) is not recommended
  use a bounded requirement, such as "~> x.y"
WARNING:  open-ended dependency on insist (>= 0, development) is not recommended
  use a bounded requirement, such as "~> x.y"
WARNING:  make sure you specify the oldest ruby version constraint (like ">= 3.0") that you want your gem to support by setting the `required_ruby_version` gemspec attribute
WARNING:  See https://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: stud
  Version: 0.0.23
  File: stud-0.0.23.gem
==> Starting check()...
.................Failed (Expected ["item!"], but got nil). Sleeping for 0.02
Failed (Expected ["item!"], but got nil). Sleeping for 0.04
Failed (Expected ["item!"], but got nil). Sleeping for 0.08
Failed (Expected ["item!"], but got nil). Sleeping for 0.16
Failed (Expected ["item!"], but got nil). Sleeping for 0.32
Failed (Expected ["item!"], but got nil). Sleeping for 0.64
............................F............

Failures:

  1) Stud::Temporary#file with a block should clean up after the block closes
     Failure/Error: reject { File }.exists?(path)

     Insist::Failure:
       Class does not respond to the 'exists?' method
     # ./spec/stud/temporary_spec.rb:44:in `block (4 levels) in <top (required)>'

Finished in 30.1 seconds (files took 0.04851 seconds to load)

It has something to do with fpm as it seems. Seems like the USE_SYSTEM_FPM env var is ignored or something similar. To be honest I have no idea.

Thanks for changing it back!

mkurz, it should build without that (and it works for x64), no idea why it's not working on ARM, but I will change to the old behavior then.

Even with

npm run generate

it does not work:

[build:release     ]   ⨯ cannot execute  cause=exit status 1
[build:release     ]                     errorOut=/usr/lib/ruby/3.3.0/rubygems.rb:259:in `find_spec_for_exe': can't find gem fpm (>= 0.a) with executable fpm (Gem::GemNotFoundException)
[build:release     ]            from /usr/lib/ruby/3.3.0/rubygems.rb:278:in `activate_bin_path'
[build:release     ]            from /usr/bin/fpm:25:in `<main>'
[build:release     ]     
[build:release     ]                     command=fpm -s dir --force -t deb -d libnotify4 -d libxtst6 -d libnss3 -d libasound2 -d libpulse0 -d libxss1 -d 'libc6 (>= 2.31)' -d libgtk-3-0 -d libgbm1 -d libx11-xcb1 --deb-recommends libappindicator3-1 --deb-compression xz --architecture arm64 --after-install /tmp/t-KI3JLY/0-after-install --after-remove /tmp/t-KI3JLY/1-after-remove --description '
[build:release     ]      Private messaging from your desktop' --version '7.36.0~beta.1' --package /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/release/signal-desktop-beta_7.36.0-beta.1_arm64.deb --name signal-desktop-beta --maintainer 'Signal Messenger, LLC <support@signal.org>' --url 'https://github.com/signalapp/Signal-Desktop#readme' --vendor 'Signal Messenger, LLC <support@signal.org>' --deb-priority optional --license AGPL-3.0-only '/home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/release/linux-arm64-unpacked/=/opt/Signal Beta' /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/16x16.png=/usr/share/icons/hicolor/16x16/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/24x24.png=/usr/share/icons/hicolor/24x24/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/32x32.png=/usr/share/icons/hicolor/32x32/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/48x48.png=/usr/share/icons/hicolor/48x48/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/64x64.png=/usr/share/icons/hicolor/64x64/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/128x128.png=/usr/share/icons/hicolor/128x128/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/256x256.png=/usr/share/icons/hicolor/256x256/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/512x512.png=/usr/share/icons/hicolor/512x512/apps/signal-desktop-beta.png /home/mkurz/.cache/yay/signal-desktop-beta/src/Signal-Desktop-7.36.0-beta.1/build/icons/png/1024x1024.png=/usr/share/icons/hicolor/1024x1024/apps/signal-desktop-beta.png '/tmp/t-KI3JLY/2-Signal Beta.desktop=/usr/share/applications/signal-desktop-beta.desktop'
[build:release     ]                     workingDir=
ERROR: "build:release" exited with 1.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: signal-desktop-beta-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
signal-desktop-beta - exit status 4

However, when in addition changing back to

-  USE_SYSTEM_FPM=$([ $(uname -m) == "aarch64" ] && echo true || echo false) bash -c 'npm run build'
+  USE_SYSTEM_FPM=$([ $(uname -m) == "aarch64" ] && echo true || echo false) bash -c 'npm run build:esbuild:prod && npm run build:release -- --linux dir'

like it was before, it works again...

@Edu4rdSHL Why did you drop '...:esbuild:prod && npm run build:release -- --linux dir'? Thanks!