AppArmor 2.13.3 now has updated abstractions, and that means we no
longer need manual backports in qTox profile.
Remove redundant rules from qTox profile that are already available in
AppArmor 2.13.3.
(cherry picked from commit a01d31445f)
powerjungle (3):
feat(logging): check if current code is tagged
fix(logging): check if version is stable before other checks
refactor(logging): change VERSION_REGEX_STRING to a const
This commit adds a new define called "GIT_DESCRIBE_EXACT" through cmake.
It is checked with a regex in "updatecheck.cpp" for a version number after the
check for new updates. If there is no version number,
a warning is output to log.
The reason for the new define is to avoid doing too much regex on
"GET_DESCRIBE", since "GIT_DESCRIBE_EXACT" will not contain a version number if
the code is not tagged.
Maxim Biro (10):
chore(windows): update OpenSSL to 1.1.1h
chore(windows): update Qt to 5.12.9
chore(windows): update FFmpeg to 4.3.1
chore(windows): update QREncode to 4.1.1
chore(windows): update VPX to 1.9.0
chore(windows): update Expat to 2.2.10
refactor(windows): Snorenotify build script
fix(windows): libsnore-qt5 not being installed
refactor(Windows): unify whitespaces in NSIS scripts
fix(windows): iconengines not being installed
TriKriSta (5):
fix(ui): implement and connect reloadTheme in leaf classes
refactor: delete classes that were used to reload theme
refactor: save friendScroll as a class member
refactor: reorder of includes
fix: clear custom style before update style
This allows leaf classes to update independently when the GUI has changed themes, without
their parent having to call updateTheme() manually.
Fix#5924Fix#5592
When a setting is set it locks the Settings mutex and emits a signal for that
setting. If a slot is connected to that signal and lives on the same thread as
Settings, it is executed immediately with the Settings mutex still locked. That
slot can then lock a series of other mutexes. During this time another thread
can lock a mutex and then try to read settings, which will cause a deadlock due
to the opposite order of multiple mutex locking. By always emitting signals
after unlocking the Settings mutex, we avoid holding the Settings mutex while
executing slots.
Fix#6218
https://github.com/qTox/qTox/pull/5866 both updated our travis xcode version,
and also added the dots in 8e597ed736. When macOS
was updated by Apple, older versions aged out of support, and brew also stopped
supporting them. Our travis xcode9.2 at the time stopped getting binary
packages (kegs) from brew because of that, and started having to compile
packages which is what was causing the timeouts.
Updating our xcode version allowed us to get binary packages from brew again,
so the workaround of constant output to avoid timing out while compiling large
packages is no longer needed.
