Package Details: pharo-launcher 1:3.1.1-3

Git Clone URL: https://aur.archlinux.org/pharo-launcher.git (read-only, click to copy)
Package Base: pharo-launcher
Description: Pharo Launcher helps you manage your Pharo images
Upstream URL: http://www.pharo-project.org/
Keywords: pharo pharo-launcher
Licenses: MIT
Submitter: laurent.laffont
Maintainer: laurent.laffont (badetitou)
Last Packager: badetitou
Votes: 11
Popularity: 0.000029
First Submitted: 2015-09-05 08:29 (UTC)
Last Updated: 2024-05-18 11:17 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

macie commented on 2021-07-20 20:06 (UTC)

I've tested updating to version 2.3 - it only needs changing version number and hashes.

But when I tried to run image based on Pharo 9, I got error: PrimitiveFailed: primitive #primLoadSymbol:module: in TFFIBackend failed. It wass caused by missing dependencies to shared libraries in Pharo 9 VM libgit2 version. I used:

$ ldd ~/Pharo/vms/90-x64/lib/libgit2.1.0.0.so | cut -f1 -d' ' -s | cut -f1-2 -d'.' | xargs pacman -F

to find missing dependences. In case of pcre this libgit2 version depends on version 3, but it is versioning scheme from Debian. So after install I created links to Arch versions:

# ln -s /usr/lib/libpcre.so.1 /usr/lib/libpcre.so.3
# ln -s /usr/lib/libpcreposix.so.0 /usr/lib/libpcreposix.so

(I'm not sure, if that global links are good idea)

As Pharo 9 is current stable version, I think that pharo-launcher should deal with mentioned issues.

badetitou commented on 2020-08-24 19:38 (UTC) (edited on 2020-08-24 19:39 (UTC) by badetitou)

I have updated Pharo Launcher to version 2.2

Following the comment of @macie, it is indeed a problem of user right for basicFile is nil. Thus, I change the pkgbuild to autorize "Others" to write in the folder "/usr/share/pharo-launcher"...

I hope it will not create security problem...

macie commented on 2020-08-01 12:19 (UTC) (edited on 2020-08-01 12:19 (UTC) by macie)

Hi, I had the same problem (receiver of "basicFileID" is nil). I solved it by changing users group to my private group (in PKGBUILD file). Building script probably should check if user has required groups. And if I understanding correctly documentation, we shouldn't use users groups (see: https://wiki.archlinux.org/index.php/Users_and_groups#Unused_groups).

BTW there is newer version of pharo-launcher (2.2).

badetitou commented on 2020-04-27 20:29 (UTC)

I don't think it can be a version problem... I already saw your error on my laptop when I was trying to create a snap. And the error appeared for both 1.9.2 and 2.0 pharo launcher version.

The problem is that in OSSVMProcess>>initializeSessionID The program try to access PharoLauncher.image. But it cannot. And if its not a permission problem. I don't know what it can be... Maybe an external library missing or version... but I have not clue which one.

ElCep commented on 2020-04-27 13:28 (UTC)

I can upload an image but git errors appear. Whereas the executable to download on the site of pharo him does not have these errors. Is it a version problem?

badetitou commented on 2020-04-26 17:41 (UTC)

:/ It should not be something different than user permissions.. but i do not know which one. Can you "skip" the error? if so, run an image? download an image?

ElCep commented on 2020-04-24 17:09 (UTC)

ls -l /usr/share/pharo-launcher/PharoLauncher.image
-rwxrwxr-x 1 root users 72291168 23 avril 08:49 /usr/share/pharo-launcher/PharoLauncher.image

badetitou commented on 2020-04-24 16:13 (UTC) (edited on 2020-04-24 16:15 (UTC) by badetitou)

Could you show me the permission of the PL file?

ls -l /usr/share/pharo-launcher/PharoLauncher.image and are you sure we are not on a readonly disk? (try touch /usr/share/pharo-launcher/test if there is no error you can remove the created file).

If you ignore the error(if you can), can you download an image? launch it?

ElCep commented on 2020-04-24 14:20 (UTC)

No specific in installation. :-/

badetitou commented on 2020-04-24 14:05 (UTC)

It might be a problem with user permissions... I have no clue where can be the problem. Do you have a specific installation? (with some non-default permission in /usr/share/pharo-vm/).