The latest version of Subsonic (6.1.6) does not suport Java SE 9 or later
because it depends on the JAXB APIs. Those are considered to be Java EE
APIs are no longer contained on the default classpath in Java SE 9 and
are completely removed in Java SE 11..
(cherry picked from commit 14c5fe8c1b61c957ad45d0df801c7928d9e4d134)
* teamviewer: fix issue #96633
Fix teamviewer's breakage post 15.5.3 -> 15.15.5.
Teamviewer client was no longer able to connect to its backing
server as it now uses dbus to do so. Following changes were
required:
- add missing dbus and polkit service/policy files to package.
- add missing dbus lib to `LD_LIBRARY_PATH`.
Changes to the nixos module as a separate changeset.
(cherry picked from commit 506966d15658d8a411f364f47bbc0f3f9366dba3)
* nixos/teamviewer: fix issue #96633
Add teamviewer package as a dbus package now that the
client / server communication depends on dbus.
(cherry picked from commit 200e959995fa8088b5722bc8255109c03f2a4f78)
* nixos/teamviewer: fix issue #44307
Move to a forefront launch of the daemon. Doing so allowed us
to move the service from forking to simple to avoid the
missing pid error log.
Also:
- Make the dbus dependency explicit.
(cherry picked from commit 953bbc0d7373102cf89625dc3bb7ab8e91134069)
* teamviewer: 15.15.5 -> 15.18.5
Upgrading to the last version still using qt5.14. Later version
will be using qt5.15 which is not in 21.05 stable branch.
This fixes us the crash observed in 15.15.5 when stopping
the service.
(cherry picked from commit db889eb9137a859eedfc5b402de84271c0659662)
* teamviewer: refactor executable wrapping
This centralizes `PATH` and `LD_LIBRARY_PATH`, avoid multiple
layers of wrappers.
Refactor as suggested by @Artturin in PR provided patch:
<https://github.com/NixOS/nixpkgs/pull/140076#issuecomment-934770391>.
(cherry picked from commit c55bc5bfd3377d54f5b6153d09c033cceadfcc05)
* teamviewer: fix 97148 (busybox installed issue)
Simply add `coreutils` as a runtime dependency which will
prevent teamviewer from using incomplete busybox implementation
of expected gnu binaries.
As suggested by @Artturin in PR comment:
<https://github.com/NixOS/nixpkgs/pull/140076#issuecomment-934770391>.
(cherry picked from commit 4fb188e1d190f2e08053dba3e2e95fff1e29183a)
* teamviewer: 15.18.5 -> 15.22.3
Required move from libsForQt514 -> libsForQt515.
Note that this changset won't be backportable to 21.05.
(cherry picked from commit 975ab7f3a02ac0232afe7920a8f7d78fc22d5ccb)
Co-authored-by: Raymond Gauthier <jraygauthier@gmail.com>
This fixes the fonts directory availability when not running an xserver,
such as headless machines.
(cherry picked from commit a27dc95e72b5671df59e04853aa48a50d65f2031)
This reverts commit f182b8d23b.
This doesn't need to be on 21.05, because 21.05 doesn't have MariaDB
10.6.
It shouldn't be on 21.05 because the package version warning mentions
21.11, which is confusing and misleading.
The `$(</path/to/file)`-expansion appears verbatim in the cmdline of
`nextcloud-occ` which means that an unprivileged user could find
sensitive values (i.e. admin password & database password) by monitoring
`/proc/<pid>/cmdline`.
Now, these values don't appear in a command line anymore, but will be
passed as environment variables to `nextcloud-occ`.
(cherry picked from commit 9f37d6aee028679b8a94be59d74984e708acaa85)
calibre-web no longer starts without proper calibre DB path configured,
so the default testcase (completely unconfigured) is removed.
(cherry picked from commit 80f7656229efee8817880250b2ca097a69898330)
The MariaDB version 10.6 doesn't seem supported with current Nextcloud
versions and the test fails with the following error[1]:
nextcloud # [ 14.950034] nextcloud-setup-start[1001]: Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 4047 InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.
According to a support-thread in upstream's Discourse[2] this is because
of a missing support so far.
Considering that we haven't received any bugreports so far - even though
the issue already exists on master - and the workaround[3] appears to
work fine, an evaluation warning for administrators should be
sufficient.
[1] https://hydra.nixos.org/build/155015223
[2] https://help.nextcloud.com/t/update-to-next-cloud-21-0-2-has-get-an-error/117028/15
[3] setting `innodb_read_only_compressed=0`
(cherry picked from commit 675e262f5a03eb9aa6b0500434ee30a9d6b882a0)
5.13.19 was the last 5.13 release and the version is now EOL[1].
[1] https://lwn.net/Articles/869747/
(cherry picked from commit 01eb8ec98a52c1e7317fd62f5bc58db30951e716)
When restoring a backup, discourse decompresses the backup archive in
the /share/discourse/tmp dir. Before this change, it is linked to /run
which is typically backed by memory, so the backup will fail to
restore if you do not have enough memory on your system to contain the
backup. This has already happened to me on two small forums.
This moves tmp to the StateDirectory /var/lib/discourse/tmp which is
typically backed by disk.
(cherry picked from commit f933c68374b9c6195dc74d26c95fc9bf240fead8)
The `services.mastodon` module currently hardcodes sidekiq's concurrency
to 25, but doesn't set a DB pool size, which defaults to 5 or the number
of configured web threads.
(This behaviour is very strange, and arguably a mastodon bug.)
This also makes sidekiq's concurrency configurable, because 25 is a tad
high for the hardware I'm running it on.
(cherry picked from commit e8fd7792d1eeb4ea4943cc34525da1159ab50bc9)
Having a disks object with a dictionary of all the disks and their
properties makes it easier to process multi-disk images.
Note the rename of `label` to `system_label` is because `$label`i
is something of a special token to jq.
(cherry picked from commit 71b3d18181974523ef7264106a4bf213a3103439)
Introduce an AWS EC2 AMI which supports aarch64 and x86_64 with a ZFS
root.
This uses `make-zfs-image` which implies two EBS volumes are needed
inside EC2, one for boot, one for root. It should not matter which
is identified `xvda` and which is `xvdb`, though I have always
uploaded `boot` as `xvda`.
(cherry picked from commit bd38b059eae05871579b2dfd51cd41d058b6a1ec)
This is a private interface for internal NixOS use. It is similar
to `make-disk-image` except it is much more opinionated about what
kind of disk image it'll make.
Specifically, it will always create *two* disks:
1. a `boot` disk formatted with FAT in a hybrid GPT mode.
2. a `root` disk which is completely owned by a single zpool.
The partitioning and FAT decisions should make the resulting images
bootable under EFI or BIOS, with systemd-boot or grub.
The root disk's zpools options are highly customizable, including
fully customizable datasets and their options.
Because the boot disk and partition are highly opinionated, it is
expected that the `boot` disk will be mounted at `/boot`. It is
always labeled ESP even on BIOS boot systems.
In order for the datasets to be mounted properly, the `datasets`
passed in to `make-zfs-image` are turned in to NixOS configuration
stored at /etc/nixos/configuration.nix inside the VM.
NOTE: The function accepts a system configuration in the `config`
argument. The *caller* must manually configure the system
in `config` to have each specified `dataset` be represented
by a corresponding `fileSystems` entry.
One way to test the resulting images is with qemu:
```sh
boot=$(find ./result/ -name '*.boot.*');
root=$(find ./result/ -name '*.root.*');
echo '`Ctrl-a h` to get help on the monitor';
echo '`Ctrl-a x` to exit';
qemu-kvm \
-nographic \
-cpu max \
-m 16G \
-drive file=$boot,snapshot=on,index=0,media=disk \
-drive file=$root,snapshot=on,index=1,media=disk \
-boot c \
-net user \
-net nic \
-msg timestamp=on
```
(cherry picked from commit 076f6e2d948259e18ddac8e562c62b5b53de9fe6)
Because of `ProtectSystem=strict`, Promtail cannot write to the positions
file if it's not in its `CacheDirectory` (the default value).
(cherry picked from commit b6ad701a2c6bf619fa9418a8e27c4940ce921456)
This error occurs if `nextcloud-occ maintenance:install` fails and the
`upgrade` command is attempted to be executed afterwards.
Due to the nature of the installer we can't do much about it, so I guess
it makes sense to add some notes about it. The other notes in the
`Pitfalls`-section are semantically a list of different topics, so I
changed that accordingly now.
Closes#111175
(cherry picked from commit 561418f996fc015f4db48b1c9b7c31338cb280d9)
This doesn't work anymore and thus breaks the installation leaving a
broken `/var/lib/nextcloud`.
It isn't a big deal since we set this value in the override config
before, so the correct table-prefix is still used. In order to confirm
that, I decided to add a custom prefix to the basic test.
(cherry picked from commit eaeb4fe04ee5a5ffae4f7dc03d3f072d59d80337)
Fixes nmcli being passed an empty string before the interface name,
which would stop captive-browser from starting up.
(cherry picked from commit 910f233fb7120c51cb8cbbaed4fab4caa6e5d751)
twisted is used in matrix-synapse for smtp handling.
Mostly this is used for password resets, but also notifications
are delivered that way.
older versions of twisted require the e-mail server to
have TLS1.0 enabled.
Obviously, quite a lot of servers have this disabled which means
synapse won't be able to deliver mails using such servers.
matrix-synapse issue:
https://github.com/matrix-org/synapse/issues/6211
Gitea now provides this functionality as an admin command.
Is significantly faster, especially on slow disks.
(cherry picked from commit c854b8570285ac4c14282a5efa0f8334a520ac8d)
The udev rules were updated upstream without an explanation as you can
see in [this comment][commit].
[commit]: 0bcf928ada
(cherry picked from commit eab36fabf6168f8fdbb2b835ce3ab689b9902ab1)
Pascal Wittmann
Maximilian Bosch
github-actions[bot]
rnhmjoj
Linus Heckemann
Pavel Borzenkov
figsoda
Timothy DeHerrera
Ryan Mulligan
embr
Jan Solanti
Your Name
Zhaofeng Li
Pamplemousse
Domen Kožar
Artturin
Ilan Joselevich
talyz
Florian Klink
Ankit Pandey
Victor Nawothnig
Maximilian Güntner
Zane van Iperen
Wael M. Nasreddine