fbs

Resolves #304.

This improvement is only included in fbs Pro.

This release makes fbs sign on Windows more robust with respect to flakiness in the underlying invocation of Microsoft's signtool. It also adds a new setting windows_sign_server that can be used to configure the timestamp server used for signing.

Specifically, this release makes errors of the following form less likely:

SignTool Error: The specified timestamp server either could not be reached or returned an invalid response.
SignTool Error: An error occurred while attempting to sign: C:\....

This improvement is only included in fbs Pro.

fbs Pro users had no easy way to install fbs Pro in buildvm virtual machines. This release fixes this: You can now add fbs_pro.tar.gz into requirements/ and add fbs_pro.tar.gz to requirements/base.txt to have it installed in the VM.

This improvement is only included in fbs Pro.

Commands such as fbs buildvm ubuntu were plagued by several problems due to outdated Python and OS versions. This release fixes this.

Specifially, building for Python 3.9.7 gave:

/root/.pyenv/plugins/python-build/bin/python-build: line 1730: patch: command not found
BUILD FAILED (Fedora 25 using python-build 20180424)

Thank you @meramsey for the PR!

This improvement is only included in fbs Pro.

The following warning was shown when installing fbs:

DEPRECATION: fbs is being installed using the legacy 'setup.py install'
method, because it does not have a 'pyproject.toml' and the 'wheel' package
is not installed. pip 23.1 will enforce this behaviour change. A possible
replacement is to enable the '--use-pep517' option. Discussion can be found
at https://github.com/pypa/pip/issues/8559".

This release fixes this.

This improvement is only included in fbs Pro.

The following error occurred when you had multiple Qt bindings (eg. PyQt5 and PySide6) installed, but not PyQt6:

ValueError: 'PyQt6 is not in list

This release fixes this.

This improvement is only included in fbs Pro.

fbs installer gave the following error:

Cannot find support/ directory.

This release fixes this.

This improvement is only included in fbs Pro.

fbs installer gave the following error on Apple Silicon machines:

bless: The 'openfolder' is not supported on Apple Silicon devices.

This release fixes this.

These improvements are only included in fbs Pro.

fbs Pro's error tracking via Sentry did not track exceptions that prevented the app from starting - see #283. This release fixes this. Thank you @apastel for the analysis and suggested fix!

Running fbs installer on Linux could give error:

fbs could not find executable 'fpm'. Please install fpm using the instructions at
https://fpm.readthedocs.io/en/latest/installing.html.

This link no longer works. It was fixed to be .../installation.html.

Thanks @meramsey for the fix!

These improvements are only included in fbs Pro.

fbs Pro now gives much more helpful error messages on Windows. This saves developers time when installing necessary dependencies, for example.

Previously, fbs freeze on Pop!_OS gave the error Your Linux distribution is not supported.

ApplicationContext.get_resource(...) loaded files in src/main/resources/base/ before .../windows during fbs run. This release fixes this. The same fix is available in fbs Pro 1.1.0.

Thank you @gentlegiantJGC for the report in #263.

As of Windows 10 build 20236 and later, signtool arguments /fd and /td are required. fbs sign now passes them in all cases. The change is backwards-compatible with earlier Windows versions.

Thank you @abood91 for the PR, which I adapted here.

On at least some Windows 10 machines, launching the application at the end of the installer produced error Windows cannot find 'C'. This release fixes this. See #255 and #249.

Otherwise, their results may depend on the user's operating system.

Thank you @weiyi0 for the PR (#250).

The problem was that version numbers need to consist of three numbers (eg. 1.2.3). Now, there is a meaningful error message when the user tries to enter just 1.0.

fbs's buildvm fedora and buildvm arch commands were broken. This releases fixes Fedora and gives a base implementation towards a fix for Arch. Similarly to the previous release (which was for Ubuntu), you can now specify the Python version (and Python OS-level build dependencies) via additional build_args settings called python_version and python_build_deps.

Motivated by PR #231. Thanks @meramsey!

You can now also specify the Python version you want in the VM by specifying the build_arg called python_version. See ubuntu/Dockerfile and base.json in _defaults/.