Package Details: signal-desktop-beta 7.37.0beta1-3

Git Clone URL: https://aur.archlinux.org/signal-desktop-beta.git (read-only, click to copy)
Package Base: signal-desktop-beta
Description: Signal Private Messenger for Linux - Beta version.
Upstream URL: https://signal.org
Keywords: secure-messenger signal signal-desktop
Licenses: GPL3
Conflicts: signal-desktop-beta-bin
Submitter: Edu4rdSHL
Maintainer: Edu4rdSHL
Last Packager: Edu4rdSHL
Votes: 16
Popularity: 0.34
First Submitted: 2020-08-17 19:09 (UTC)
Last Updated: 2024-12-12 17:09 (UTC)

Dependencies (33)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »

Edu4rdSHL commented on 2024-03-05 16:52 (UTC)

Stop spamming the package with unrelated comments. Thanks.

Lubo99 commented on 2024-03-05 16:48 (UTC)

none of this is working as said this is not bau archlinux instalation. its virtual machine running on android

anything related to makepkg or arch repository ends up => ERROR: Running makepkg as root is not allowed as it can cause permanent, catastrophic damage to your system.

Edu4rdSHL commented on 2024-03-04 15:19 (UTC)

Please learn how to use makepkg and the AUR, read the ArchWiki.

Lubo99 commented on 2024-03-04 08:58 (UTC)

[root@localhost ~]# ls Desktop Downloads signal-desktop-beta yaourt

root@localhost ~]# pacman -U signal-desktop-beta loading packages... error: could not open file signal-desktop-beta: Error reading fd 7 error: 'signal-desktop-beta': cannot open package file

maybe stupid question but any idea what to do? i can't commit any commands like this root@localhost ~]# makepkg -si ==> ERROR: Running makepkg as root is not allowed as it can cause permanent, catastrophic damage to your system.

this is vnc machine running on android 14 device

acheronfail commented on 2023-12-29 11:03 (UTC)

@Edu4rdSHL it's still an issue for me, I just tried to install it today on a freshly installed system, and got the same ruby fpm error that @initnull reported.

Edu4rdSHL commented on 2023-12-07 02:33 (UTC)

Is this still an issue? @initnull

initnull commented on 2023-08-24 16:57 (UTC) (edited on 2023-08-24 16:57 (UTC) by initnull)

This package has stopped building on aarch64 since beta 6.28 due to an error with ruby fpm.

cannot execute  cause=exit status 1
                errorOut=/usr/lib/ruby/gems/3.0.0/gems/fpm-1.15.1/lib/fpm/command.rb:413:in `block in execute': undefined method `default_architecture' for #<FPM::Command:0x0000aaaae7b816a8 @invocation_path="fpm", @context={}, @conflicts=[], @replaces=[], @provides=[], @dependencies=["libnotify4", "libxtst6", "libnss3", "libasound2", "libxss1", "libc6 (>= 2.31)"], @config_files=[], @directories=[], @logger=#<Cabin::Channel:0x0000aaaae7b81108 @subscribers={1160=>#<Cabin::Subscriber:0x0000aaaae7b808c0 @output=#<Cabin::Outputs::IO:0x0000aaaae7b80b18 @io=#<IO:<STDOUT>>,

Edu4rdSHL commented on 2023-05-20 00:41 (UTC)

@randomscumbag, it's an upstream issue, see https://github.com/signalapp/Signal-Desktop/issues/6417 and https://github.com/signalapp/Signal-Desktop/issues/6419.

Please always check upstream repo before reporting here.

<deleted-account> commented on 2023-05-20 00:34 (UTC)

Recent issue after last update.... Can't copy and paste images or from my computer screen into the messenger. Tried several different ways, Currently using FlameShot as my main screen shot grabber, when I paste ctl-v or right click paste, doesn't add anything. If I run Signal not the Beta, it copies things in correctly. I haven't changed anything on my system, this was after the last update which I did today 5/19/23

my apologeeze @Edu4rdSHL

mkurz commented on 2023-01-21 20:00 (UTC) (edited on 2023-01-21 20:04 (UTC) by mkurz)

@Edu4rdSHL Thanks!

Just to let you know, it is not just a common issue across AUR helpers, putting the export into the prepare function is violating the PKGBUILD specification. prepare() is for preparing the source code, not doing something that is needed to build the package. Not just yay or paru fail, even a common use case for makepkg will fail when putting the export into the prepare() function like you did. Have a look at the makepkg manpage:

$ man makepkg
...
       -e, --noextract
           Do not extract source files or run the prepare() function (if present); use whatever source already exists in the $srcdir/ directory. This is
           handy if you want to go into $srcdir/ and manually patch or tweak code, then make a package out of the result. Keep in mind that creating a
           patch may be a better solution to allow others to use your PKGBUILD.
...
       -o, --nobuild
           Download and extract files, run the prepare() function, but do not build them. Useful with the --noextract option if you wish to tweak the
           files in $srcdir/ before building.

Now, let's do what the man page says. First just let's download and prepare the source:

$ makepkg -o
==> Making package: signal-desktop-beta 6.3.0beta1-4 (Sa 21 Jän 2023 20:44:22)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
...
==> Validating source files with sha512sums...
...
==> Extracting sources...
...
==> Starting prepare()...
...
==> Sources are ready.

Nice, sources are downloaded and prepared. Now, lets imagine we modify the source ourselves, we are finished doing that and now we want to actually build the package:

$ makepkg -e
==> Making package: signal-desktop-beta 6.3.0beta1-4 (Sa 21 Jän 2023 20:49:43)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
...
[build:webpack   ] Error: error:0308010C:digital envelope routines::unsupported
[build:webpack   ]     at new Hash (node:internal/crypto/hash:71:19)
[build:webpack   ]     at Object.createHash (node:crypto:130:10)
...
[build:webpack   ] error Command failed with exit code 1.
[build:webpack   ] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[build:webpack   ] ERROR: "build:webpack:sticker-creator" exited with 1.
[build:webpack   ] error Command failed with exit code 1.
[build:webpack   ] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build:webpack" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...

BOOOM! Same error when just using makepkg! The npm variable was not set anymore, because in the second command the prepare function did not run anymore. You can also read more about that in this discussion: https://github.com/Jguer/yay/issues/1006 where people write things like "DO NOT USE PREPARE JUST TO SET VARIABLES. You are violating the PKGBUILD specification, and as a result your PKGBUILD sucks."

Thanks for fixing! Highly appreciated!

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 14 Next › Last »