[pull] master from nix-community:master #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
The source uses `launcher` instead of `daemon`. Additionally we remove `Type` and add `RestartSec` as defined in the source: https://github.com/espanso/espanso/blob/b421bcf73fa13506938d62425459d6c16c6a8d0a/espanso/src/res/linux/systemd.service#L5-L7C1
When zoxide initializes after fzf it causes fzf " ** " trigger to not work. To fix the issue we needed to make zoxide initialize earlier than fzf but after bash-completion. PR #5955
Flake lock file updates:
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/a3c0b3b21515f74fd2665903d4ce6bc4dc81c77c?narHash=sha256-nsNdSldaAyu6PE3YUA%2BYQLqUDJh%2BgRbBooMMekZJwvI%3D' (2024-10-14)
→ 'github:NixOS/nixpkgs/4c2fcb090b1f3e5b47eaa7bd33913b574a11e0a0?narHash=sha256-/uilDXvCIEs3C9l73JTACm4quuHUsIHcns1c%2BcHUJwA%3D' (2024-10-18)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
The `.assume-wrapped` path is not available since the merge of
NixOS/nixpkgs#347816
Use assume directly instead.
PR #5994
Actions were added in the v0.19.1 release.
This module enables wrapping programs which require access to libGL with nixGL on non-NixOS systems.
Some desktop files will refer to the absolute path of the original derivation, which would bypass nixGL wrapping. So we need to replace the path with the path to the wrapper derivation to ensure the wrapped version is always launched.
makeWrapper is more consistent with the rest of nixpkgs & home-manager, so it should be a little more maintainable. It can also validate that the wrapper command is executable at build time.
Co-authored-by: V. <[email protected]>
Co-authored-by: V. <[email protected]>
Co-authored-by: V. <[email protected]>
Previously, - `programs.yazi.enableNushellIntegration`, - `programs.yazi.enableFishIntegration`, and - `programs.yazi.enableZshIntegration` were set to false by default. It seems more appropriate to enable these integrations by default.
There's no launchd equivalent to this option, so this is a no-op on Darwin.
This facilitates a legitimate use-case for browserless systems. From the README: > On systems without a web browser, set the -device flag to authenticate > on another device using [OAuth device flow]: > ```ini [credential] helper = cache --timeout 7200 # two hours helper = oauth -device ``` [OAuth device flow]: https://www.rfc-editor.org/rfc/rfc8628 Please note that, for the documentation about the man-page to be accurate, NixOS/nixpkgs#302922 must be merged.
Added `mkAfter` to `git.extraConfig` to ensure our oauth is last, as required to work with additional helpers.
Adds a new Podman module for creating user containers and networks as systemd services. These are installed to the user's `$XDG_CONFIG/systemd/user` directory.
Call to git-maintenance in the systemd user service was using a erroneous value for exec-path flag. Removing the flag is fine.
Flake lock file updates:
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/18536bf04cd71abd345f9579158841376fdd0c5a?narHash=sha256-RP%2BOQ6koQQLX5nw0NmcDrzvGL8HDLnyXt/jHhL1jwjM%3D' (2024-10-25)
→ 'github:NixOS/nixpkgs/807e9154dcb16384b1b765ebe9cd2bba2ac287fd?narHash=sha256-l253w0XMT8nWHGXuXqyiIC/bMvh1VRszGXgdpQlfhvU%3D' (2024-10-29)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This makes extraPackages the default, but they do not shadow the env so you can still have packages (e.g. LSPs) with a different version than the global one in you local env like nix's shells.
Flake lock file updates:
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/807e9154dcb16384b1b765ebe9cd2bba2ac287fd?narHash=sha256-l253w0XMT8nWHGXuXqyiIC/bMvh1VRszGXgdpQlfhvU%3D' (2024-10-29)
→ 'github:NixOS/nixpkgs/76612b17c0ce71689921ca12d9ffdc9c23ce40b2?narHash=sha256-IigrKK3vYRpUu%2BHEjPL/phrfh7Ox881er1UEsZvw9Q4%3D' (2024-11-09)
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Recent nixpkgs update made a small change to how TOML is generated, causing the test toml to be out of date.
Recent nixpkgs update made a small change to how TOML is generated, causing the test toml to be out of date.
Recent nixpkgs update made a small change how YAML is generated, causing the test YAML to be out of date. The replacement match is also an exact example from the espanso wiki https://espanso.org/docs/matches/basics/#multi-line-expansions.
systemd rejects the service unit due to whitespace in the environment variable assignment, pointing to the repo path, being invalid for systemd's unit format. See #6023 for details. The git-sync variable should also be escaped due to similar issues with e.g. local git urls.
- added themes option - added themes test - updated broken man page links
Currently, the home-manager systemd service will only get restarted when
the home-manager configuration changes. This can lead to issues in
users' home directories not getting corrected for a while.
$ rm ~/.zshrc
$ sudo nixos-rebuild switch
$ ls ~/.zshrc
ls: cannot access '/home/enzime/.zshrc': No such file or directory
By adding `key`, this allows users to disable this shared module or they can choose to not disable this shared module (by filtering by key before disabling)
This means users can disable all shared modules if all modules are paths or attrsets with a key:
`configuration.nix`:
```nix
{ config, ... }:
{
home-manager.users.enzime = { ... }: {
disabledModules = config.home-manager.sharedModules;
};
}
```
Or disabling just this module specifically:
```nix
{ ... }:
{
home-manager.users.enzime = { ... }: {
disabledModules = [ { key = "home-manager#nixos-shared-module"; } ];
};
}
```
Or disabling all modules when you have modules you can't disable (like lambdas):
```nix
{ ... }:
{
home-manager.users.enzime = { ... }: {
disabledModules = lib.filter (v: lib.isString v || lib.isPath v || (lib.isAttrs v && v ? key)) config.home-manager.sharedModules;
};
}
```
https://nixos.org/manual/nixos/unstable/#sec-replace-modules
…ita-icon-theme` in the examples (#5712) `adwaita-icon-theme` has been moved out of the `gnome` scope and into the top level with NixOS/nixpkgs#319659
This is something that is useful, we should not hide it from the docs.
Nixpkgs updated upstream: NixOS/nixpkgs@90fcf3a
Using a fixed application name in the salt for the search engine name hash can break with minor branding changes. For example, LibreWolf 127 used the application name "LibreWolf", but in version 128 it is "Firefox". The proper name can be found in about:support -> Application Basics. Because it doesn't have to be related to the product name visible in most of the browser (for example in the window title and help menus), we shouldn't rely on cfg.name for that. The application name can be read from lib/*/application.ini and we can use that if the browser was installed via Home Manager. If not, we can fall back to cfg.name.
Currently translated at 100.0% (37 of 37 strings) Co-authored-by: Lorenzo Bevilacqua <[email protected]> Translate-URL: https://hosted.weblate.org/projects/home-manager/cli/it/ Translation: Home Manager/Home Manager CLI
Currently translated at 100.0% (37 of 37 strings) Co-authored-by: wadsaek <[email protected]> Translate-URL: https://hosted.weblate.org/projects/home-manager/cli/uk/ Translation: Home Manager/Home Manager CLI
This expands the Syncthing configuration to allow declarative settings. Code mostly pulled from the Nixpkgs module. Changes compared to the NixOS module are: Removed the following options: - user, group, systemService: Unnecessary since Syncthing always runs as the user declaring the configuration. - dataDir configDir, databaseDir: Pointed to ~/.local/state/syncthing, the default Syncthing directory. - openDefaultPorts: We don't have access to the system firewall. Furthermore, multiple changes to systemd services were made to maintain consistency with other Home Manager modules, sandboxing options might need to be reviewed further. Fixes #4049
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )