Age | Commit message (Collapse) | Author | Files | Lines |
|
grocy: 4.0.0 -> 4.0.2
|
|
* auto-cpufreq: 1.7.1 -> 1.9.9
* fix test
* set `meta.buildDocsInSandbox = false`
required because description depends on restricted module argument pkgs
|
|
Relying on the built-in UEFI console here was already necessary, so we
are losing nothing by removing the needless `serial` call, which hung
some systems.
This also makes the implementation much easier to understand.
Also, no ugly-font menu anymore!
|
|
This helps keep logic simpler, as what we do is forcing text mode, which
means the non-default case is `truthy`, making things easier to digest
in the config file.
Also renaming this option is considered "internal", since it lives only
within the `iso-image` namespace, and also not a breaking change since
it was not part of a stable release.
|
|
This solves an issue where *some systems* (tested on Steam Deck) the EFI
GOP may be broken during stage-1.
|
|
It's not like the iso-image will be anything else than isohybrid
FAT+iso9660...
|
|
Which ***anyway*** was not disabled correctly. Following changes will
actually disable it.
What this did was disable the "themed" menu driver, but still continued
relying on the gfxterm infra, which in itself is why things were ugly
and weird.
|
|
|
|
Hey, look at that, grub is the correct way around on a Steam Deck!
|
|
The `serial` console hangs on some systems. Unknown why.
Anyway, the way this worked right now relied on it telling the user on
the UEFI console how to enable it. So if I understand it correctly, it
will not cause any regression there.
|
|
With a bash array.
This change is morally a no-op.
|
|
This patch packages mu4e as an Emacs lisp package based on the mu4e
output of the multiple-output package mu, which makes mu4e a good
citizen of Emacs lisp packages in two aspects.
First, mu4e now utilizes the Emacs lisp package infrastructure in
Nixpkgs. This allows users who want to do AOT native compilation for
non-default Emacs variants[0] to build only mu4e itself instead of the
whole mu package[1].
Second, mu4e now conforms to the Emacs builtin package manager[2].
Without this patch, mu4e autoloaded commands do not work
out-of-the-box[3] because its directory is added to load-path by
site-start.el after the initialization of package-directory-list,
which causes package-activate-all to not load mu4e-autoloads.el. This
patch fixes this issue when mu4e is installed to Emacs using the
withPackages wrapper[4].
[0]: such as emacs-pgtk
[1]: mu.override { emacs = emacs-pgtk; }
[2]: package.el
[3]: either (require 'mu4e) or (require 'mu4e-autoloads) is needed to
be called before an autoloaded command is called
[4]: emacs-pgtk.pkgs.withPackages (epkgs: [ epkgs.mu4e ])
|
|
akkoma: 3.9.3 → 3.10.4
|
|
It's broken for a lot of people.
|
|
boot.initrd.systemd: make TPM2 modules optional
|
|
Add `programs.ecryptfs` for mount wrappers
|
|
cawbird: remove due to being broken and abandoned
|
|
dae,nixos/dae: 0.2.4 -> 0.3.0
|
|
anbox: unbreak
|
|
|
|
kratos: 0.10.1 -> 1.0.0
|
|
-- dedicated to Larry the bird
|
|
The `ecryptfs` package refers to the setuid wrapper paths, but they do
not exist so far in NixOS.
|
|
|
|
|
|
|
|
GitLab instances created or updated between versions [15.11.0, 15.11.2]
have an incorrect database schema. [1] This will become a problem once
upgrading GitLab to >=16.2.0.
A workaround can be found in the GitLab docs: [2]
[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/408835
[2]: https://docs.gitlab.com/ee/update/versions/gitlab_16_changes.html#undefined-column-error-upgrading-to-162-or-later
|
|
GitLab instances created or updated between versions [15.11.0, 15.11.2]
have an incorrect database schema. [1] This will become a problem once
upgrading GitLab to >=16.2.0.
A workaround can be found in the GitLab docs: [2]
[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/408835
[2]: https://docs.gitlab.com/ee/update/versions/gitlab_16_changes.html#undefined-column-error-upgrading-to-162-or-later
|
|
https://gitlab.com/gitlab-org/gitlab/-/blob/v16.3.1-ee/CHANGELOG.md
Fixes CVE-2022-4343
Fixes CVE-2023-0120
Fixes CVE-2023-1279
Fixes CVE-2023-1555
Fixes CVE-2023-3205
Fixes CVE-2023-3915
Fixes CVE-2023-3950
Fixes CVE-2023-4018
Fixes CVE-2023-4378
Fixes CVE-2023-4630
Fixes CVE-2023-4638
Fixes CVE-2023-4647
Co-Authored-By: Yaya <github@uwu.is>
|
|
|
|
|
|
|
|
As noted in https://github.com/NixOS/nixpkgs/pull/102341 this is not
actually running as a forked process. It only tells the process that it
is running "as a daemon, so shut the warning up".
See `daemon_` here
- https://github.com/anbox/anbox/blob/9de4e87cdd05135e1c71e6eadb68bf82719cebdf/src/anbox/cmds/container_manager.cpp#L38-L79
It is **strictly** used to hide that message.
Co-authored-by: Matt Votava <mvnetbiz@gmail.com>
|
|
|
|
|
|
|
|
|
|
python310Packages.mautrix: 0.20.0 -> 0.20.1
|
|
This is not unlikely to happen, given the enthusiasm shown by some users,
but we are not there yet, and this will save them from breaking their system.
|
|
|
|
|
|
|
|
|
|
|
|
nixos/budgie: Use Network Manager Applet indicator, budgie.budgie-gsettings-overrides: Update defaults
|
|
nixos/mautrix-whatsapp: various fixes
|
|
nixosTests.custom-ca: resolve out of memory situations
|
|
They are easily observable on hydra. E.g. on the latest eval
https://hydra.nixos.org/build/233893887
https://hydra.nixos.org/build/233900101
|
|
|
|
lxd: Add VM image and server support for QEMU VMs
|