eeva/home-manager
1
0
Fork 0
mirror of https://github.com/nix-community/home-manager synced 2024-11-01 00:39:45 +01:00
Code Issues Releases Wiki Activity
home-manager/modules/po/hm-modules.pot

115 lines
2.8 KiB
Text
Raw Permalink Normal View History

home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR Home Manager contributors
# This file is distributed under the same license as the Home Manager Modules package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Home Manager Modules\n"
"Report-Msgid-Bugs-To: https://github.com/nix-community/home-manager/issues\n"
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
"POT-Creation-Date: 2023-05-27 09:08+0200\n"
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
home-manager: handle missing per-user profiles directory Specifically, if the global per-user profiles path do not exist and we cannot create it during the activation, then place our profile in the Home Manager data directory. We prefer to use the global location, though, since it makes it visible to `nix-collect-garbage`. This is intended to improve compatibility with Nix version 2.14 and later, which no longer creates the per-user directories. Also, use the Home Manager data directory to manage the gcroot for the current generation. It does not have to sit in the global per-user gcroots directory since it should never be eligible for GC.
2023-03-04 10:39:02 +01:00
#: modules/files.nix:234
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "Creating home file links in %s"
msgstr ""
home-manager: handle missing per-user profiles directory Specifically, if the global per-user profiles path do not exist and we cannot create it during the activation, then place our profile in the Home Manager data directory. We prefer to use the global location, though, since it makes it visible to `nix-collect-garbage`. This is intended to improve compatibility with Nix version 2.14 and later, which no longer creates the per-user directories. Also, use the Home Manager data directory to manage the gcroot for the current generation. It does not have to sit in the global per-user gcroots directory since it should never be eligible for GC.
2023-03-04 10:39:02 +01:00
#: modules/files.nix:247
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "Cleaning up orphan links from %s"
msgstr ""
home-manager: handle missing per-user profiles directory Specifically, if the global per-user profiles path do not exist and we cannot create it during the activation, then place our profile in the Home Manager data directory. We prefer to use the global location, though, since it makes it visible to `nix-collect-garbage`. This is intended to improve compatibility with Nix version 2.14 and later, which no longer creates the per-user directories. Also, use the Home Manager data directory to manage the gcroot for the current generation. It does not have to sit in the global per-user gcroots directory since it should never be eligible for GC.
2023-03-04 10:39:02 +01:00
#: modules/files.nix:263
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "Creating profile generation %s"
msgstr ""
home-manager: handle missing per-user profiles directory Specifically, if the global per-user profiles path do not exist and we cannot create it during the activation, then place our profile in the Home Manager data directory. We prefer to use the global location, though, since it makes it visible to `nix-collect-garbage`. This is intended to improve compatibility with Nix version 2.14 and later, which no longer creates the per-user directories. Also, use the Home Manager data directory to manage the gcroot for the current generation. It does not have to sit in the global per-user gcroots directory since it should never be eligible for GC.
2023-03-04 10:39:02 +01:00
#: modules/files.nix:280
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "No change so reusing latest profile generation %s"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/home-environment.nix:627
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid ""
nix: add support for `nix profile` PR #2833 Co-authored-by: David Arnold <dar@xoe.solutions> Co-authored-by: Florian Franzen <Florian.Franzen@gmail.com>
2021-11-10 19:23:33 +01:00
"Oops, Nix failed to install your new Home Manager profile!\n"
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
"\n"
"Perhaps there is a conflict with a package that was installed using\n"
nix: add support for `nix profile` PR #2833 Co-authored-by: David Arnold <dar@xoe.solutions> Co-authored-by: Florian Franzen <Florian.Franzen@gmail.com>
2021-11-10 19:23:33 +01:00
"\"%s\"? Try running\n"
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
"\n"
nix: add support for `nix profile` PR #2833 Co-authored-by: David Arnold <dar@xoe.solutions> Co-authored-by: Florian Franzen <Florian.Franzen@gmail.com>
2021-11-10 19:23:33 +01:00
" %s\n"
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
"\n"
"and if there is a conflicting package you can remove it with\n"
"\n"
nix: add support for `nix profile` PR #2833 Co-authored-by: David Arnold <dar@xoe.solutions> Co-authored-by: Florian Franzen <Florian.Franzen@gmail.com>
2021-11-10 19:23:33 +01:00
" %s\n"
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
"\n"
"Then try activating your Home Manager configuration again."
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/home-environment.nix:660
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "Activating %s"
msgstr ""
home-manager: migrate profiles to nix state directory If the user runs a recent Nix version that places per-user profiles in `$XDG_STATE_DIR/nix/profiles`, then migrate the home-manager profile there. Also clean up `setupVars` a bit.
2023-04-07 14:01:45 +02:00
#: modules/lib-bash/activation-init.sh:22
msgid "Migrating profile from %s to %s"
home-manager: handle missing per-user profiles directory Specifically, if the global per-user profiles path do not exist and we cannot create it during the activation, then place our profile in the Home Manager data directory. We prefer to use the global location, though, since it makes it visible to `nix-collect-garbage`. This is intended to improve compatibility with Nix version 2.14 and later, which no longer creates the per-user directories. Also, use the Home Manager data directory to manage the gcroot for the current generation. It does not have to sit in the global per-user gcroots directory since it should never be eligible for GC.
2023-03-04 10:39:02 +01:00
msgstr ""
home-manager: migrate profiles to nix state directory If the user runs a recent Nix version that places per-user profiles in `$XDG_STATE_DIR/nix/profiles`, then migrate the home-manager profile there. Also clean up `setupVars` a bit.
2023-04-07 14:01:45 +02:00
#: modules/lib-bash/activation-init.sh:53
msgid "Could not find suitable profile directory, tried %s and %s"
msgstr ""
#: modules/lib-bash/activation-init.sh:81
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "Sanity checking oldGenNum and oldGenPath"
msgstr ""
home-manager: migrate profiles to nix state directory If the user runs a recent Nix version that places per-user profiles in `$XDG_STATE_DIR/nix/profiles`, then migrate the home-manager profile there. Also clean up `setupVars` a bit.
2023-04-07 14:01:45 +02:00
#: modules/lib-bash/activation-init.sh:84
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid ""
"The previous generation number and path are in conflict! These\n"
"must be either both empty or both set but are now set to\n"
"\n"
" '%s' and '%s'\n"
"\n"
"If you don't mind losing previous profile generations then\n"
"the easiest solution is probably to run\n"
"\n"
" rm %s/home-manager*\n"
" rm %s/current-home\n"
"\n"
"and trying home-manager switch again. Good luck!"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:95
msgid "Error: USER is set to \"%s\" but we expect \"%s\""
msgstr ""
#: modules/lib-bash/activation-init.sh:104
msgid "Error: HOME is set to \"%s\" but we expect \"%s\""
msgstr ""
#: modules/lib-bash/activation-init.sh:119
home-manager: add basic i18n support The support for translated strings is, for now, limited to strings generated in Bash code.
2021-04-30 01:29:39 +02:00
msgid "Starting Home Manager activation"
msgstr ""
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:123
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "Sanity checking Nix"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:133
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "This is a dry run"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:137
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "This is a live run"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:143
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "Using Nix version: %s"
msgstr ""
home-manager: verify username and home directory The generation activation script should be run by the user specified in `home.username` and `home.homeDirectory`. If some other user runs the activation script, then files may end up in the wrong place or with the wrong owner. This commits adds a check early in the activation script that verifies that the running user match the user in the configuration. Fixes #4019
2023-05-26 15:11:22 +02:00
#: modules/lib-bash/activation-init.sh:146
treewide: make a few more strings translatable
2022-01-02 11:44:53 +01:00
msgid "Activation variables:"
msgstr ""
Reference in a new issue Copy permalink