scille / parsec-build Goto Github PK

At startup, some old files cause a crash:

C:\Program Files (x86)\Parsec\core>parsec.exe
Traceback (most recent call last):
  File "C:\Python36-x64\lib\site-packages\cx_Freeze\initscripts\__startup__.py", line 14, in run
  File "C:\Python36-x64\lib\site-packages\cx_Freeze\initscripts\Console.py", line 26, in run
  File "parsec/cli.py", line 6, in <module>
  File "C:\projects\parsec-build\parsec-cloud\parsec\cli_utils.py", line 3, in <module>
  File "C:\Python36-x64\lib\site-packages\trio\__init__.py", line 18, in <module>
  File "C:\Python36-x64\lib\site-packages\trio\_core\__init__.py", line 24, in <module>
  File "C:\Python36-x64\lib\site-packages\trio\_core\_ki.py", line 9, in <module>
  File "C:\Python36-x64\lib\site-packages\trio\_util.py", line 67, in <module>
  File "C:\Python36-x64\lib\site-packages\cffi\api.py", line 56, in __init__
Exception: Version mismatch: this is the 'cffi' package version 1.12.2, located in 'C:\\Program Files (x86)\\Parsec\\core\\lib\\cffi\\api.pyc'.  When we import the top-level '_cffi_backend' extension module, we get version 1.12.1, located in 'C:\\Program Files (x86)\\Parsec\\core\\lib\\_cffi_backend.cp36-win_amd64.pyd'.  The two versions should be equal; check your installation.

https://github.com/Scille/parsec-build/blob/master/win32/installer.nsi#L15

OK pour Norton Antivirus avec PARSEC 1.3.0 ("Parsec est sécurisé")

Problème persistant avec Windows Defender qu'il faut forcer.

Should use git describe --tags as release name (and in build files)

Système : Windows 10 Pro version 1809. Ecran +/- 22"
Version PARSEC déjà installée: 1.1.2
Objectif: répondre à une invitation de Thierry à rejoindre une organisation, puis partager un fichier

1. Le client parsec se lance (process en arrère-plan), mais pas de GUI (et donc pas de signalement de nouvelle version 1.2.1)
2. Je lance la désinstallation de PARSEC (=1.1.2). -> OK
3. Je telecharge 1.2.1 de Github 64b. Problèmes de signalement de logiciel dangereux par Windows Defender et Norton, pour mémoire. A l'install, erreur : ne peut écraser le fichier parsec.exe.
   En fait, le process 1.1.2 n'a pas été tué. Il empeche la suppression de son exécutable.
   Après assassinat manuel, ok pour le nouveau lancement install.

Keys and values that will have to be removed when uninstalling Parsec on Windows

HKEY_CURRENT_USER\Software\Classes\CLSID\{6C37F945-7EFC-480A-A444-A6D44A3D107F}
HKEY_CURRENT_USER\Software\Wow6432Node\CLSID\{6C37F945-7EFC-480A-A444-A6D44A3D107F}
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\{6C37F945-7EFC-480A-A444-A6D44A3D107F}
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\HideDesktopIcons\NewStartPanel\{6C37F945-7EFC-480A-A444-A6D44A3D107F}

Some "Role on workspace X has changed" notifications are displayed even though the role hasn't actually changed.

This has been observed on a workspace with a single owner and no other users. Upon opening a parsec session in a second device, those notifications have appeared for all such workspaces (3 of them).

Currently, the Windows build generates two .exe (one in the main Parsec folder, one in core/). At execution, the first one execs the second one by launching core/parsec.exe core gui.
This causes problems when trying to pin the app to the taskbar, as it's the second .exe that gets pinned, not the first one.
Ideally, we should only have one .exe with the correct Parsec icon that launches the GUI when no arguments are given.