bundle - Pysolfc(solitaire) for Porteus 5.0rc1

Post#1 by **ncmprhnsbl** » 07 Jul 2019, 02:51

PySolFC is a collection of more than 1000 solitaire card games. There are games that use the 52 card International Pattern deck, games for the 78 card Tarock deck, eight and ten suite Ganjifa games, Hanafuda games, Matrix games, Mahjongg games, and games for an original hexadecimal-based deck. PySolFC features multiple cardsets and backgrounds, sound, unlimited undo, player statistics, and much more..

it is available for all desktops through the bundles application in the system menu.
bundle contains: pysolfc-2.6.3-x86_64-1_ncm python-six-1.12.0-x86_64-3 python-pillow-6.1.0-x86_64-1 tk-8.6.9.1-x86_64-1

Post#2 by **Ed_P** » 07 Jul 2019, 20:56

Very nice ncmp.

Post#3 by **Ed_P** » 16 Jul 2019, 16:42

Missing a file.

Code: Select all

guest@porteus:~$ pysol.py
Traceback (most recent call last):
  File "/usr/bin/pysol.py", line 27, in <module>
    from pysollib.init import init
ImportError: No module named pysollib.init

Post#4 by **raja** » 16 Jul 2019, 16:58

You will be able to add needed modules through PIP. Pl activate jss bundle pythonPIP.

Post#5 by **Ed_P** » 16 Jul 2019, 17:53

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# PIP
bash: PIP: command not found
root@porteus:/home/guest# pythonPIP
bash: pythonPIP: command not found
root@porteus:/home/guest#

I also don't know where I would find the missing file.

Post#6 by **jssouza** » 16 Jul 2019, 19:50

Ed_P, raja meant you can activate the pip bundle from bundles and install any python module - bundle - Python3 PIP for Porteus 5.0rc1

Anyway, pysolfc works perfectly fine on Cinnamon.

Post#7 by **Ed_P** » 16 Jul 2019, 20:08

jssouza wrote: ↑
16 Jul 2019, 19:50
Ed_P, raja meant you can activate the pip bundle from bundles and install any python module - bundle - Python3 PIP for Porteus 5.0rc1

But what python module has pysollib.init?

Anyway, pysolfc works perfectly fine on Cinnamon.

I'm running Cinnamon.

Code: Select all

System Memory: 3809M
Boot device:   /mnt/sda6
Boot device format: "ntfs" 
Boot folder:   /porteus5.0/
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso
OS:       Porteus-v5.0
ARCH:     x86_64
Desktop:  cinnamon_x86_64-20190531  Cinnamon 4.0.10                      <<<<<<<<<<<<< Note current version even
Kernel:   Linux porteus 5.1.5-porteus
Cmdline:  quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso volume=33 reboot=cold extramod=/porteus5.0/003Modules;/porteus5.0/Modules

Post#8 by **ncmprhnsbl** » 16 Jul 2019, 23:43

well .. suffice to say, there's no missing (python)module ..
i would guess that one of your other (porteus)modules could be interefering with python's ability to find it..

Post#9 by **Ed_P** » 17 Jul 2019, 00:10

You might have stumbled upon something ncmp.

Code: Select all

guest@porteus:~$ pysol.py
guest@porteus:~$ 
guest@porteus:~$ pysol.py
guest@porteus:~$ 
guest@porteus:~$ pysol.py
guest@porteus:~$

Always Fresh mode.

Code: Select all

System Memory: 3809M
Boot device:   /mnt/sda6
Boot device format: "ntfs" 
Boot folder:   /porteus5.0/
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso
OS:       Porteus-v5.0
ARCH:     x86_64
Desktop:  cinnamon  Cinnamon 4.0.10
Kernel:   Linux porteus 5.1.5-porteus
Cmdline:  quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso volume=33 reboot=cold #extramod=/porteus5.0/003Modules

Porteus-Livedbg log: 
# Recognized devices:
/dev/sda1: LABEL="ESP" UUID="CE3C-F23D" TYPE="vfat" 
/dev/sda3: LABEL="OS" UUID="A64AB3B24AB37D9D" TYPE="ntfs" 
/dev/sda4: UUID="1E426F58426F33A5" TYPE="ntfs" 
/dev/sda5: LABEL="Image" UUID="0010ED9410ED90C8" TYPE="ntfs" 
/dev/sda6: LABEL="Data" UUID="2628E9A628E974E9" TYPE="ntfs" 
/dev/sda7: LABEL="Backups" UUID="F8ACEAFCACEAB472" TYPE="ntfs" 
/dev/sda8: LABEL="Backup10.1" UUID="E842EC8742EC5C36" TYPE="ntfs" 

# Booting device:
/mnt/isoloop

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-cinnamon.xzm

ISO=/mnt/sda6//ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso

Post#10 by **ncmprhnsbl** » 17 Jul 2019, 05:14

now activate your modules one by one, and check if/ which one breaks pysol... something python related probably..

Post#11 by **Ed_P** » 18 Jul 2019, 17:49

Well I did that and can not replicate the error, even booting normally again.

Post#12 by **ncmprhnsbl** » 18 Jul 2019, 23:15

a glitch!.. ..in the matrix! .. the agents are here! get out! now!

Post#13 by **ncmprhnsbl** » 20 Jul 2019, 12:43

i just noticed that my bundle has python-pillow-6.1.0-x86_64-1.txz and cinnamon already has python-pillow-6.0.0-x86_64-1
by rights, i should make a pysolfc bundle for cinnamon without python-pillow
hard to say if this was the cause of the problem..

Post#14 by **Ed_P** » 20 Jul 2019, 13:39

I appreciate the follow up but I'd suggest waiting on a cinnamon build until the problem happens again.