Florian Bruhin
Florian Bruhin
Today I cleared my keyboard's EEPROM to debug something, and was surprised that my macros were gone when restoring the backup. I'm (mostly) okay with the settings under "my keyboard"...
As outlined in [Troubleshooting — pytest-qt documentation](https://pytest-qt.readthedocs.io/en/latest/troubleshooting.html), when Qt calls abort, often the user doesn't have any useful information due to pytest's output capturing. I can see two ways around...
With a trivial `answer.ipynb` like this: ```json { "cells": [ { "cell_type": "code", "execution_count": null, "id": "2382e31c-1117-46df-b981-81100e7f68f3", "metadata": {}, "outputs": [], "source": [ "def answer():\n", " return 42" ] }...
Might make the packages smaller: https://bugreports.qt.io/browse/QTBUG-82681 https://fedoraproject.org/wiki/Features/DwarfCompressor
Rebuilding the docker image every time takes considerable time - we should cache a docker image with the deps installed (maybe even build that in a Travis cronjob) and then...
See https://hub.docker.com/r/archlinux/base/ and https://github.com/czka/archlinux-docker/issues/8#issuecomment-304961640
``` $ bash patch.sh qt5-{base,imageformats,virtualkeyboard,webkit} + (( 4 == 0 )) + packages='qt5-base qt5-imageformats qt5-virtualkeyboard qt5-webkit' + patch_qt 'qt5-base qt5-imageformats qt5-virtualkeyboard qt5-webkit' + for pkg in '"$@"' + [[ qt5-base...
There are some tools supposed to make editing PKGBUILDs automatically easier: - https://github.com/ava1ar/customizepkg - https://github.com/archlinuxfr/customizepkg - https://sourceforge.net/projects/customizepkg-ng/
When building with `--temp` we should have a way to mark them as "okay" and release