Thanks in advance for your bug report!

• Have you reproduced issue in safe mode?
• Have you used the debugging guide to try to resolve the issue?
• Have you checked our FAQs to make sure your question isn't answered there?
• Have you checked to make sure your issue does not already exist?
• Have you checked you are on the latest release of Pulsar?

What happened?

See: https://github.com/orgs/pulsar-edit/discussions/178

On upgrading the .rpm binary the pulsar binary in /usr/bin is lost meaning it can no longer be run from the command line. The .desktop is unaffected as it runs from /opt/pulsar.

See the steps below, shows that the binary itself does work normally as on install it works, just not on upgrade.

I have attempted to fix this in #543 but so far this is failing. I suspect it is because the script can't be found when added to the fpm options? This is only a guess as I noticed (I unfortunately no longer have the logs) that during the actual build process the post-install script is actually in a tmp/ dir.

It doesn't appear this issue is affecting the .deb.

Could possibly be related to the fpm option to remove the buildid? Not sure.

Pulsar version

1.150.0

Which OS does this happen on?

🐧 Red Hat based (Fedora, Alma, RockyLinux, CentOS Stream, etc.)

OS details

Fedora 36

Which CPU architecture are you running this on?

64-bit(x86_64)

What steps are needed to reproduce this?

• Download and install Pulsar 1.105.0 e.g (dnf install Linux.pulsar-1.105.0.x86_64)

• Run which pulsar - should return /usr/bin/pulsar

• Download and install Pulsar 1.105.2023051902 (dnf install pulsar-1.105.2023052013.x86_64.rpm)

  • dnf output will show that Pulsar has been upgraded.

• Run which pulsar - should return which: no pulsar in ...

• Remove pulsar with dnf remove pulsar

• Reinstall 1.105.2023051902 (dnf install pulsar-1.105.2023052013.x86_64.rpm)

• Run which pulsar - should return /usr/bin/pulsar

Additional Information:

No response