Pulsar Edit
pulsar 1.105.0 x86-64 RPM Fedora - not in path, warning messages output #178
-
|
Hello, I have Fedora 36. I started using Pulsar a few weeks ago when an issue I raised was resolved pulsar-edit/pulsar#227 . There was a CI RPM offered there https://cirrus-ci.com/task/4875413076312064 that I was using. I have now updated the Pulsar to the generally available 1.105 version, RPM, x86-64. And I have two issues I did not have before. First, just starting "pulsar" from the command line no longer works. I can start it by typing "/opt/Pulsar/pulsar". Why woiyuld an RPM install put the installation under /opt ? Second, after starting it in that way, I get a stream of warning messages, which follows. Am I doing something wrong? Or is this expected? Or should I raise an issue for one or both of these? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
Not sure about the install issue I'm afraid, I just tried it on my own Fedora system and it installs to ~ $ sudo dnf remove pulsar
Dependencies resolved.
=====================================================================================================================================================================================================================
Package Architecture Version Repository Size
=====================================================================================================================================================================================================================
Removing:
pulsar x86_64 1.105.0-1 @@commandline 711 M
Transaction Summary
=====================================================================================================================================================================================================================
Remove 1 Package
Freed space: 711 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : pulsar-1.105.0-1.x86_64 1/1
Running scriptlet: pulsar-1.105.0-1.x86_64 1/1
Verifying : pulsar-1.105.0-1.x86_64 1/1
Removed:
pulsar-1.105.0-1.x86_64
Complete!
~ $ which pulsar
which: no pulsar in (/usr/local/go/bin:/home/dae/go/bin:/home/dae/.nimble/bin:/home/dae/.nvm/versions/node/v16.17.1/bin:/home/dae/.local/bin:/home/dae/bin:/home/dae/.cargo/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/dae/.local/share/JetBrains/Toolbox/scripts:/home/dae/.local/share/JetBrains/Toolbox/scripts)
~ $ sudo dnf install ./Downloads/Linux.pulsar-1.105.0.x86_64.rpm
Last metadata expiration check: 0:06:43 ago on Thu 18 May 2023 17:32:49 BST.
Dependencies resolved.
=====================================================================================================================================================================================================================
Package Architecture Version Repository Size
=====================================================================================================================================================================================================================
Installing:
pulsar x86_64 1.105.0-1 @commandline 139 M
Transaction Summary
=====================================================================================================================================================================================================================
Install 1 Package
Total size: 139 M
Installed size: 711 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : pulsar-1.105.0-1.x86_64 1/1
Running scriptlet: pulsar-1.105.0-1.x86_64 1/1
Verifying : pulsar-1.105.0-1.x86_64 1/1
Installed:
pulsar-1.105.0-1.x86_64
Complete!
~ $ which pulsar
/usr/bin/pulsarHowever I can also see that there is indeed a dir in As for if there should be a bug reported for those errors, I'm inclined to say not as we are going to be doing a huge update with Electron anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I have reinstalled the RPM and the issues went away. (The second one probably went away because the first one did; "pulsar" appears to start "detached", immediately returning the terminal to the prompt) |
Beta Was this translation helpful? Give feedback.
-
|
Ok there is definitely something going on here. It seems when pulsar is installed by However performing an upgrade i.e. I had 1.105.0 installed and then tried to install the upgrade to 1.105.2023051902 and now the binary in So I did a My assumption is that this script isn't running because the upgrade isn't an install: Not sure what is removing the contents of |
Beta Was this translation helpful? Give feedback.
-
|
I've now raised this as an issue here - pulsar-edit/pulsar#544 as it can be replicated and I suspect is what you originally saw. |
Beta Was this translation helpful? Give feedback.
Not sure about the install issue I'm afraid, I just tried it on my own Fedora system and it installs to
/usr/bin. See the below - I uninstalled it and reinstalled just to check. You can seewhich pulsarno longer returned anything then on reinstall it foundpulsarin/usr/bin/.~ $ sudo dnf remove pulsar Dependencies resolved. ===================================================================================================================================================================================================================== Pack…