Arch Linux User Repository

I assume it depends on openssl-1.1:

21:12:06.178 [error] Unable to load crypto library. Failed with error:
":load_failed, Failed to load NIF library /opt/pleroma/lib/crypto-4.6.5.4/priv/lib/crypto: 'libcrypto.so.1.1: cannot open shared object file: No such file or directory'"
OpenSSL might not be installed on this system.


21:12:06.191 [warn] The on_load function for module crypto returned:
{:error, {:load_failed, 'Failed to load NIF library /opt/pleroma/lib/crypto-4.6.5.4/priv/lib/crypto: \'libcrypto.so.1.1: cannot open shared object file: No such file or directory\''}}

Could you let the upstream compile a new release for OpenSSL upgrade?

thanks, it works

@malacology Your issue may be resolved by installing libxcrypt-compat from core repo. Here's a recent(about a few months ago) chat log at #pleroma irc channel on libera.chat: https://0x0.st/oP6Y.txt

and I fail in this package it will report similar report like this and always restart consider the systems config

2022-05-21 23:58:02.490306 supervisor_report   #{label=>{supervisor,start_error},report=>[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{on_load_function_failed,crypt}},{offender,[{pid,undefined},{id,kernel_safe_sup},{mfargs,{supervisor,start_link,[{local,kernel_safe_sup},kernel,safe]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
2022-05-21 23:58:02.490487 crash_report        #{label=>{proc_lib,crash},report=>[[{initial_call,{supervisor,kernel,['Argument__1']}},{pid,<0.3156.0>},{registered_name,[]},{error_info,{exit,{on_load_function_failed,crypt},[{init,run_on_load_handlers,0,[]},{kernel,init,1,[{file,"kernel.erl"},{line,189}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,295}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,374}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,342}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}},{ancestors,[kernel_sup,<0.3141.0>]},{message_queue_len,0},{messages,[]},{links,[<0.3143.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,27},{reductions,265}],[]]}
2022-05-21 23:58:03.493987 crash_report        #{label=>{proc_lib,crash},report=>[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.3140.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,138}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}},{ancestors,[<0.3139.0>]},{message_queue_len,1},{messages,[{'EXIT',<0.3141.0>,normal}]},{links,[<0.3139.0>,<0.3138.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,27},{reductions,193}],[]]}
2022-05-21 23:58:03.496012 std_info            #{label=>{application_controller,exit},report=>[{application,kernel},{exited,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}})

Crash dump is being written to: erl_crash.dump..

full journal is here https://log.malacology.net/pleroma.log

and install process seems okay https://log.malacology.net/pleroma_install.log

After installation, you should see a message like this:

If postgresql is installed locally, the user should run the following commands to initialize pleroma:
>>> sudo -Hu pleroma -s /bin/bash /opt/pleroma/bin/pleroma_ctl instance gen --output "/etc/pleroma/config.exs" --output-psql "/tmp/setup_otp_db.psql" --uploads-dir "/var/lib/pleroma/uploads" --static-dir "/var/lib/pleroma/static" --dbname "pleroma" --dbuser "pleroma"
>>> sudo -Hu postgres psql -f "/tmp/setup_otp_db.psql"
>>> sudo -Hu pleroma /opt/pleroma/bin/pleroma_ctl migrate

If the user is using a remote postgresql instance, they should ensure "/tmp/setup_otp_db.psql" be executed remotely after the first command:
>>> sudo -Hu pleroma -s /bin/bash /opt/pleroma/bin/pleroma_ctl instance gen --output "/etc/pleroma/config.exs" --output-psql "/tmp/setup_otp_db.psql" --uploads-dir "/var/lib/pleroma/uploads" --static-dir "/var/lib/pleroma/static" --dbname "pleroma" --dbuser "pleroma"
>>> # Now execute "/tmp/setup_otp_db.psql" remotely.
>>> sudo -Hu pleroma -s /bin/bash /opt/pleroma/bin/pleroma_ctl migrate

Have you executed these commands according to your postgresql installation? Normally the first command

sudo -Hu pleroma -s /bin/bash /opt/pleroma/bin/pleroma_ctl instance gen --output "/etc/pleroma/config.exs" --output-psql "/tmp/setup_otp_db.psql" --uploads-dir "/var/lib/pleroma/uploads" --static-dir "/var/lib/pleroma/static" --dbname "pleroma" --dbuser "pleroma"

should have initialized the config file.

After installation and starting, I am getting the following errors:

Sep 20 09:51:11 tiger systemd[1]: Started Pleroma social network.
Sep 20 09:51:11 tiger pleroma[119213]: /opt/pleroma/erts-10.7.2.1/bin/beam.smp: /usr/lib/libtinfo.so.6: no version information available (required by /opt/pleroma/erts-10.7.2.1/bin/beam.smp)
Sep 20 09:51:13 tiger pleroma[119213]: !!! Config path is not declared! Please ensure it exists and that PLEROMA_CONFIG_PATH is unset or points to an existing file

Am I missing a step?

As @peter.babic said, new version came out

Amd64=https://git.pleroma.social/pleroma/pleroma/-/jobs/174791/artifacts/download Arm=https://git.pleroma.social/pleroma/pleroma/-/jobs/174793/artifacts/download Arm64=https://git.pleroma.social/pleroma/pleroma/-/jobs/174795/artifacts/download

Hello, currently branch 2.2.2 is considered stable.

https://git.pleroma.social/pleroma/pleroma/-/commit/c2186a62d54043ea9638d33f80c7576aba9783e8

Hi @faye, thanks for your reply.

To rename a package:

1. Prepare the files in your local repo to match the new name
2. Push it to the new repo on the AUR
3. Verify it works correctly
4. Submit a merge request of pleroma into pleroma-bin via "Submit request"

Thanks for updating the package. Please also bump pkgrel each time you modify PKGBUILD when it doesn't change the software's actual version as per PKGBUILD pkgrel definition.

Good day to you too! :)