DietPi-Software | Gogs: Install latest pre-compiled binaries from GitHub for ARMv7 + x86_64

[MichaIng]

Status: Testing

• DietPi-Patch | Remove /etc/__MACOSX if present, coming from our archives
• Changelog
• Testing on non-RPi ARMv7 to be failsafe
• Test reinstall from pre-v6.26 instance to assure InnoDB 4byte support does not break existing database
• Compile and use ARMv6 binaries

Fixes #2999

Commit list/description:

• DietPi-Software | Gogs: Install latest pre-compiled binaries from GitHub for ARMv7 + x86_64. For ARMv6 (RPi1/Zero) no binaries are available yet
• DietPi-Software | Gogs: Download to /tmp first to avoid moving the "__MACOSX" dir to /etc that comes with our ARMv6 archive
• DietPi-Software | Gogs: C_CHECK_URL receives 403 on GitHub download, thus skip it
• DietPi-Software | Gogs: On reinstall, remove old install dir, but preserve existing configs
• DietPi-Software | Gogs: Import pre-defined SQL file on fresh install to pre-create database. On current version otherwise an error occurs on access attempt
• DietPi-Software | Gogs: InnoDB large table prefix with Barracuda file format is required
• DietPi-Software | MariaDB: Assure/Enable 4-byte support (default since Stretch) and modern Barracuda file format + large table prefix (default since Buster) on all MariaDB installs. This has no effect on existing tables, setting this with ownCloud and Nextcloud installs never caused issues for other MariaDB databases and software using them, and, every Stretch to backports/Buster upgrade would break it the same way if so. However a special eye on this during Beta phase makes sense.

[MichaIng]

Strange, doing fresh install, entering credentials in web UI and attempt to go on results in:

Error 1071: Specified key was too long; max key length is 767 bytes

First I though this was due to our manual database creation, so I used /etc/gogs/scripts/mysql.sql instead, which then worked.

Now even exactly this is in installer, it fails with the same error. Manually dropping the database and re-importing with exactly the same commands again resolves it.

Pre-created database is empty, collation as it should be:

MariaDB [gogs]> show tables;
+----------------+
| Tables_in_gogs |
+----------------+
| user           |
+----------------+
1 row in set (0.00 sec)

MariaDB [gogs]> select * from user;
Empty set (0.00 sec)

MariaDB [gogs]> SELECT @@character_set_database, @@collation_database;
+--------------------------+----------------------+
| @@character_set_database | @@collation_database |
+--------------------------+----------------------+
| utf8mb4                  | utf8mb4_general_ci   |
+--------------------------+----------------------+
1 row in set (0.00 sec)

mysqlcheck -o gogs does not help as well, so there is no corruption or something.

Okay: https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes

• Only strange why this is no issue when running the exact same commands manually from console...

Okay well InnoDB 4byte support (incl. Barracuda file + large prefix) solves the issue reliably. We should add this by default to MariaDB installs, after tested with all software titles.
🈯️ Added as we do for ownCloud and Nextcloud