Package Details: pleroma-bin 2.4.1-1

Git Clone URL: https://aur.archlinux.org/pleroma-bin.git (read-only, click to copy)
Package Base: pleroma-bin
Description: A microblogging server software that can federate (= exchange messages with) other servers that support ActivityPub.
Upstream URL: https://pleroma.social/
Licenses: AGPL, CCPL:cc-by-4.0, CCPL:cc-by-sa-4.0
Conflicts: pleroma
Provides: pleroma
Submitter: gudzpoz
Maintainer: gudzpoz
Last Packager: gudzpoz
Votes: 1
Popularity: 0.000515
First Submitted: 2021-08-16 05:56
Last Updated: 2021-09-03 15:14

Latest Comments

1 2 Next › Last »

gudzpoz commented on 2021-09-21 03:24

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.

xeruf commented on 2021-09-20 09:52

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?

Vvyibaba commented on 2021-02-11 09:39

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

peter.babic commented on 2021-01-19 09:31

Hello, currently branch 2.2.2 is considered stable.

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

ashpie commented on 2020-11-09 08:54

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! :)

faye commented on 2020-11-08 22:14

Hi @Thulinma @Cciby and @Arisu ! Sorry for not fixing the issues earlier.

I've updated the package to use a fixed version and I will be updating it over time. I'm not sure how to change the name of the package without deleting this one and making a whole new package--so if you know a better way of doing it then I'll do that as well :)

I haven't been able to get compile from source to work well on arch with pleroma in a PKGBUILD due to the wide use of system administrator privileges in the build process.

Have a nice day!

Thulinma commented on 2020-11-08 15:37

Yes, the package should either be renamed to "pleroma-bin" or be built from source. Since the binaries are not directly compatible with the libraries in Arch, compiling from source would be best.

ashpie commented on 2020-11-08 15:27

Thanks @Thulinma, I would also add that, if I'm not mistaken, this package uses prebuilt artifacts, which means it should be named pleroma-bin as per submission guidelines: "Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix.".

Thulinma commented on 2020-11-08 14:46

Just to be clear: the correct solution here is not to only update the checksum, but to also change the download URL to be a specific version, as I mentioned in my earlier comment on 2020-07-20 (almost 4 months ago). I'm not sure why this hasn't happened yet.

ashpie commented on 2020-11-08 14:25

@faye cf previous comment by Cciby: pleroma.zip ... FAILED

Please update checksums.