diff options
Diffstat (limited to 'docs/_locale/uk/contributing.pot')
| -rw-r--r-- | docs/_locale/uk/contributing.pot | 1727 |
1 files changed, 1727 insertions, 0 deletions
diff --git a/docs/_locale/uk/contributing.pot b/docs/_locale/uk/contributing.pot new file mode 100644 index 00000000..781d3731 --- /dev/null +++ b/docs/_locale/uk/contributing.pot @@ -0,0 +1,1727 @@ +msgid "" +msgstr "" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Localazy (https://localazy.com)\n" +"Project-Id-Version: VyOS Documentation\n" +"Language: uk\n" +"Plural-Forms: nplurals=3; plural=((n%10==1) && (n%100!=11)) ? 0 : ((n%10>=2 && n%10<=4) && ((n%100<12 || n%100>14))) ? 1 : 2;\n" + +#: ../../contributing/development.rst:653 +msgid "\"${vyos_libexecdir}/validators/foo bar $VAR(@)\" will be executed, <constraintErrorMessage> will be displayed on failure" +msgstr "\"${vyos_libexecdir}/validators/foo bar $VAR(@)\" will be executed, <constraintErrorMessage> will be displayed on failure" + +#: ../../contributing/development.rst:647 +msgid "<constraintErrorMessage> will be displayed on failure" +msgstr "<constraintErrorMessage> will be displayed on failure" + +#: ../../contributing/development.rst:632 +msgid "<node name=\"mynode\"> </node>" +msgstr "<node name=\"mynode\"> </node>" + +#: ../../contributing/development.rst:667 +msgid "<properties> <completionHelp> <list> foo bar </list>" +msgstr "<properties> <completionHelp> <list> foo bar </list>" + +#: ../../contributing/development.rst:670 +msgid "<properties> <completionHelp> <path> vpn ipsec esp-group </path> ..." +msgstr "<properties> <completionHelp> <path> vpn ipsec esp-group </path> ..." + +#: ../../contributing/development.rst:673 +msgid "<properties> <completionHelp> <script> /path/to/script </script> ..." +msgstr "<properties> <completionHelp> <script> /path/to/script </script> ..." + +#: ../../contributing/development.rst:646 +msgid "<properties> <constraint> <regex> ..." +msgstr "<properties> <constraint> <regex> ..." + +#: ../../contributing/development.rst:652 +msgid "<properties> <constraint> <validator> <name =\"foo\" argument=\"bar\">" +msgstr "<properties> <constraint> <validator> <name =\"foo\" argument=\"bar\">" + +#: ../../contributing/development.rst:638 +msgid "<properties> <help>My node</help>" +msgstr "<properties> <help>My node</help>" + +#: ../../contributing/development.rst:664 +msgid "<properties> <multi/>" +msgstr "<properties> <multi/>" + +#: ../../contributing/development.rst:660 +msgid "<properties> <priority>999</priority>" +msgstr "<properties> <priority>999</priority>" + +#: ../../contributing/development.rst:641 +msgid "<properties> <valueHelp> <format> format </format> <description> some string </description>" +msgstr "<properties> <valueHelp> <format> format </format> <description> some string </description>" + +#: ../../contributing/development.rst:635 +msgid "<tagNode name=\"mynode> </node>" +msgstr "<tagNode name=\"mynode> </node>" + +#: ../../contributing/upstream-packages.rst:81 +msgid "A fork with packaging changes for VyOS is kept at https://github.com/vyos/hvinfo" +msgstr "A fork with packaging changes for VyOS is kept at https://github.com/vyos/hvinfo" + +#: ../../contributing/development.rst:31 +msgid "A good approach for writing commit messages is actually to have a look at the file(s) history by invoking ``git log path/to/file.txt``." +msgstr "A good approach for writing commit messages is actually to have a look at the file(s) history by invoking ``git log path/to/file.txt``." + +#: ../../contributing/debugging.rst:44 +msgid "A number of flags can be set up to change the behaviour of VyOS at runtime. These flags can be toggled using either environment variables or creating files." +msgstr "A number of flags can be set up to change the behaviour of VyOS at runtime. These flags can be toggled using either environment variables or creating files." + +#: ../../contributing/development.rst:74 +msgid "A single, short, summary of the commit (recommended 50 characters or less, not exceeding 80 characters) containing a prefix of the changed component and the corresponding Phabricator_ reference e.g. ``snmp: T1111:`` or ``ethernet: T2222:`` - multiple components could be concatenated as in ``snmp: ethernet: T3333``" +msgstr "A single, short, summary of the commit (recommended 50 characters or less, not exceeding 80 characters) containing a prefix of the changed component and the corresponding Phabricator_ reference e.g. ``snmp: T1111:`` or ``ethernet: T2222:`` - multiple components could be concatenated as in ``snmp: ethernet: T3333``" + +#: ../../contributing/development.rst:569 +msgid "Abbreviations and acronyms **must** be capitalized." +msgstr "Abbreviations and acronyms **must** be capitalized." + +#: ../../contributing/build-vyos.rst:403 +#: ../../contributing/build-vyos.rst:591 +msgid "Accel-PPP" +msgstr "Accel-PPP" + +#: ../../contributing/development.rst:577 +msgid "Acronyms also **must** be capitalized to visually distinguish them from normal words:" +msgstr "Acronyms also **must** be capitalized to visually distinguish them from normal words:" + +#: ../../contributing/development.rst:165 +msgid "Add file to Git index using ``git add myfile``, or for a whole directory: ``git add somedir/*``" +msgstr "Add file to Git index using ``git add myfile``, or for a whole directory: ``git add somedir/*``" + +#: ../../contributing/testing.rst:99 +msgid "Add one or more IP addresses" +msgstr "Add one or more IP addresses" + +#: ../../contributing/development.rst:502 +msgid "Address" +msgstr "Address" + +#: ../../contributing/build-vyos.rst:800 +msgid "After a minute or two you will find the generated DEB packages next to the vyos-1x source directory:" +msgstr "After a minute or two you will find the generated DEB packages next to the vyos-1x source directory:" + +#: ../../contributing/build-vyos.rst:627 +#: ../../contributing/build-vyos.rst:656 +#: ../../contributing/build-vyos.rst:691 +msgid "After compiling the packages you will find yourself the newly generated `*.deb` binaries in ``vyos-build/packages/linux-kernel`` from which you can copy them to the ``vyos-build/packages`` folder for inclusion during the ISO build." +msgstr "After compiling the packages you will find yourself the newly generated `*.deb` binaries in ``vyos-build/packages/linux-kernel`` from which you can copy them to the ``vyos-build/packages`` folder for inclusion during the ISO build." + +#: ../../contributing/testing.rst:50 +msgid "After its first boot into the newly installed system the main Smoketest script is executed, it can be found here: `/usr/bin/vyos-smoketest`" +msgstr "After its first boot into the newly installed system the main Smoketest script is executed, it can be found here: `/usr/bin/vyos-smoketest`" + +#: ../../contributing/development.rst:7 +msgid "All VyOS source code is hosted on GitHub under the VyOS organization which can be found here: https://github.com/vyos" +msgstr "All VyOS source code is hosted on GitHub under the VyOS organization which can be found here: https://github.com/vyos" + +#: ../../contributing/development.rst:680 +msgid "All commit time checks should be in the verify() function of the script" +msgstr "All commit time checks should be in the verify() function of the script" + +#: ../../contributing/development.rst:514 +msgid "All interface definition XML input files (.in suffix) will be sent to the GCC preprocess and the output is stored in the `build/interface-definitions` folder. The previously mentioned `scripts/build-command-templates` script operates on the `build/interface-definitions` folder to generate all required CLI nodes." +msgstr "All interface definition XML input files (.in suffix) will be sent to the GCC preprocess and the output is stored in the `build/interface-definitions` folder. The previously mentioned `scripts/build-command-templates` script operates on the `build/interface-definitions` folder to generate all required CLI nodes." + +#: ../../contributing/issues-features.rst:14 +msgid "All issues should be reported to the developers. This lets the developers know what is not working properly. Without this sort of feedback every developer will believe that everything is working correctly." +msgstr "All issues should be reported to the developers. This lets the developers know what is not working properly. Without this sort of feedback every developer will believe that everything is working correctly." + +#: ../../contributing/development.rst:683 +msgid "All logic should be in the scripts" +msgstr "All logic should be in the scripts" + +#: ../../contributing/development.rst:90 +msgid "All text of the commit message should be wrapped at 72 characters if possible which makes reading commit logs easier with ``git log`` on a standard terminal (which happens to be 80x25)" +msgstr "All text of the commit message should be wrapped at 72 characters if possible which makes reading commit logs easier with ``git log`` on a standard terminal (which happens to be 80x25)" + +#: ../../contributing/development.rst:99 +msgid "Always use the ``-x`` option to the ``git cherry-pick`` command when back or forward porting an individual commit. This automatically appends the line: ``(cherry picked from commit <ID>)`` to the original authors commit message making it easier when bisecting problems." +msgstr "Always use the ``-x`` option to the ``git cherry-pick`` command when back or forward porting an individual commit. This automatically appends the line: ``(cherry picked from commit <ID>)`` to the original authors commit message making it easier when bisecting problems." + +#: ../../contributing/development.rst:336 +msgid "Another advantage is testability of the code. Mocking the entire config subsystem is hard, while constructing an internal representation by hand is way simpler." +msgstr "Another advantage is testability of the code. Mocking the entire config subsystem is hard, while constructing an internal representation by hand is way simpler." + +#: ../../contributing/build-vyos.rst:702 +msgid "Any \"modified\" package may refer to an altered version of e.g. vyos-1x package that you would like to test before filing a pull request on GitHub." +msgstr "Any \"modified\" package may refer to an altered version of e.g. vyos-1x package that you would like to test before filing a pull request on GitHub." + +#: ../../contributing/build-vyos.rst:831 +msgid "Any packages in the packages directory will be added to the iso during build, replacing the upstream ones. Make sure you delete them (both the source directories and built deb packages) if you want to build an iso from purely upstream packages." +msgstr "Any packages in the packages directory will be added to the iso during build, replacing the upstream ones. Make sure you delete them (both the source directories and built deb packages) if you want to build an iso from purely upstream packages." + +#: ../../contributing/testing.rst:56 +msgid "As Smoketests will alter the system configuration and you are logged in remote you may loose your connection to the system." +msgstr "As Smoketests will alter the system configuration and you are logged in remote you may loose your connection to the system." + +#: ../../contributing/testing.rst:12 +msgid "As the VyOS documentation is not only for users but also for the developers - and we keep no secret documentation - this section describes how the automated testing works." +msgstr "As the VyOS documentation is not only for users but also for the developers - and we keep no secret documentation - this section describes how the automated testing works." + +#: ../../contributing/build-vyos.rst:777 +msgid "Assume we want to build the vyos-1x package on our own and modify it to our needs. We first need to clone the repository from GitHub." +msgstr "Assume we want to build the vyos-1x package on our own and modify it to our needs. We first need to clone the repository from GitHub." + +#: ../../contributing/development.rst:175 +msgid "Attach patch to Phabricator task" +msgstr "Attach patch to Phabricator task" + +#: ../../contributing/development.rst:619 +msgid "Bad: \"Disables IPv6 forwarding\"" +msgstr "Bad: \"Disables IPv6 forwarding\"" + +#: ../../contributing/development.rst:563 +msgid "Bad: \"Frobnication algorithm.\"" +msgstr "Bad: \"Frobnication algorithm.\"" + +#: ../../contributing/development.rst:605 +msgid "Bad: \"Set TCP connection timeout\"" +msgstr "Bad: \"Set TCP connection timeout\"" + +#: ../../contributing/development.rst:562 +msgid "Bad: \"frobnication algorithm\"" +msgstr "Bad: \"frobnication algorithm\"" + +#: ../../contributing/development.rst:574 +msgid "Bad: \"tcp connection timeout\"" +msgstr "Bad: \"tcp connection timeout\"" + +#: ../../contributing/development.rst:594 +msgid "Bad: PPPOE, IPSEC" +msgstr "Bad: PPPOE, IPSEC" + +#: ../../contributing/development.rst:595 +msgid "Bad: pppoe, ipsec" +msgstr "Bad: pppoe, ipsec" + +#: ../../contributing/development.rst:583 +msgid "Bad: radius (unless it's about the distance between a center of a circle and any of its points)" +msgstr "Bad: radius (unless it's about the distance between a center of a circle and any of its points)" + +#: ../../contributing/debugging.rst:160 +msgid "Beeing brave and running the latest rolling releases will sometimes trigger bugs due to corner cases we missed in our design. Those bugs should be filed via Phabricator_ but you can help us to narrow doen the issue. Login to your VyOS system and change into configuration mode by typing ``configure``. Now re-load your boot configuration by simply typing ``load`` followed by return." +msgstr "Beeing brave and running the latest rolling releases will sometimes trigger bugs due to corner cases we missed in our design. Those bugs should be filed via Phabricator_ but you can help us to narrow doen the issue. Login to your VyOS system and change into configuration mode by typing ``configure``. Now re-load your boot configuration by simply typing ``load`` followed by return." + +#: ../../contributing/debugging.rst:170 +msgid "Boot Timing" +msgstr "Boot Timing" + +#: ../../contributing/issues-features.rst:10 +msgid "Bug Report/Issue" +msgstr "Bug Report/Issue" + +#: ../../contributing/build-vyos.rst:785 +msgid "Build" +msgstr "Build" + +#: ../../contributing/build-vyos.rst:60 +msgid "Build Container" +msgstr "Build Container" + +#: ../../contributing/build-vyos.rst:182 +msgid "Build ISO" +msgstr "Build ISO" + +#: ../../contributing/build-vyos.rst:5 +msgid "Build VyOS" +msgstr "Build VyOS" + +#: ../../contributing/build-vyos.rst:85 +msgid "Build from source" +msgstr "Build from source" + +#: ../../contributing/build-vyos.rst:582 +msgid "Building Out-Of-Tree Modules" +msgstr "Building Out-Of-Tree Modules" + +#: ../../contributing/build-vyos.rst:435 +msgid "Building The Kernel" +msgstr "Building The Kernel" + +#: ../../contributing/build-vyos.rst:246 +msgid "Building VyOS on Windows WSL2 with Docker integrated into WSL2 will work like a charm. No problems are known so far!" +msgstr "Building VyOS on Windows WSL2 with Docker integrated into WSL2 will work like a charm. No problems are known so far!" + +#: ../../contributing/build-vyos.rst:705 +msgid "Building an ISO with any customized package is in no way different than building a regular (customized or not) ISO image. Simply place your modified `*.deb` package inside the `packages` folder within `vyos-build`. The build process will then pickup your custom package and integrate it into your ISO." +msgstr "Building an ISO with any customized package is in no way different than building a regular (customized or not) ISO image. Simply place your modified `*.deb` package inside the `packages` folder within `vyos-build`. The build process will then pickup your custom package and integrate it into your ISO." + +#: ../../contributing/build-vyos.rst:584 +msgid "Building the kernel is one part, but now you also need to build the required out-of-tree modules so everything is lined up and the ABIs match. To do so, you can again take a look at ``vyos-build/packages/linux-kernel/Jenkinsfile`` to see all of the required modules and their selected versions. We will show you how to build all the current required modules." +msgstr "Building the kernel is one part, but now you also need to build the required out-of-tree modules so everything is lined up and the ABIs match. To do so, you can again take a look at ``vyos-build/packages/linux-kernel/Jenkinsfile`` to see all of the required modules and their selected versions. We will show you how to build all the current required modules." + +#: ../../contributing/build-vyos.rst:475 +msgid "Building the kernel will take some time depending on the speed and quantity of your CPU/cores and disk speed. Expect 20 minutes (or even longer) on lower end hardware." +msgstr "Building the kernel will take some time depending on the speed and quantity of your CPU/cores and disk speed. Expect 20 minutes (or even longer) on lower end hardware." + +#: ../../contributing/build-vyos.rst:13 +msgid "Building using a :ref:`build_docker` container, although not the only way, is the easiest way as all dependencies are managed for you. However, you can also set up your own build machine and run a :ref:`build_native`." +msgstr "Building using a :ref:`build_docker` container, although not the only way, is the easiest way as all dependencies are managed for you. However, you can also set up your own build machine and run a :ref:`build_native`." + +#: ../../contributing/development.rst:247 +msgid "But we are here to assist you and want to guide you through how you can become a good VyOS contributor. The rules we have are not there to punish you - the rules are in place to help us all. What does it mean? By having a consistent coding style it becomes very easy for new contributors and also longtime contributors to navigate through the sources and all the implied logic of the spaghetti code." +msgstr "But we are here to assist you and want to guide you through how you can become a good VyOS contributor. The rules we have are not there to punish you - the rules are in place to help us all. What does it mean? By having a consistent coding style it becomes very easy for new contributors and also longtime contributors to navigate through the sources and all the implied logic of the spaghetti code." + +#: ../../contributing/development.rst:686 +msgid "C++ Backend Code" +msgstr "C++ Backend Code" + +#: ../../contributing/development.rst:551 +msgid "Capitalization and punctuation" +msgstr "Capitalization and punctuation" + +#: ../../contributing/build-vyos.rst:448 +msgid "Check out the required kernel version - see ``vyos-build/data/defaults.json`` file (example uses kernel 4.19.146):" +msgstr "Check out the required kernel version - see ``vyos-build/data/defaults.json`` file (example uses kernel 4.19.146):" + +#: ../../contributing/development.rst:149 +msgid "Clone: ``git clone https://github.com/<user>/vyos-1x.git``" +msgstr "Clone: ``git clone https://github.com/<user>/vyos-1x.git``" + +#: ../../contributing/build-vyos.rst:441 +msgid "Clone the kernel source to `vyos-build/packages/linux-kernel/`:" +msgstr "Clone the kernel source to `vyos-build/packages/linux-kernel/`:" + +#: ../../contributing/development.rst:187 +msgid "Coding Guidelines" +msgstr "Coding Guidelines" + +#: ../../contributing/development.rst:490 +msgid "Command definitions are purely declarative, and cannot contain any logic. All logic for generating config files for target applications, restarting services and so on is implemented in configuration scripts instead." +msgstr "Command definitions are purely declarative, and cannot contain any logic. All logic for generating config files for target applications, restarting services and so on is implemented in configuration scripts instead." + +#: ../../contributing/development.rst:168 +msgid "Commit the changes by calling ``git commit``. Please use a meaningful commit headline (read above) and don't forget to reference the Phabricator_ ID." +msgstr "Commit the changes by calling ``git commit``. Please use a meaningful commit headline (read above) and don't forget to reference the Phabricator_ ID." + +#: ../../contributing/testing.rst:151 +msgid "Config Load Tests" +msgstr "Config Load Tests" + +#: ../../contributing/debugging.rst:132 +msgid "Config Migration Scripts" +msgstr "Config Migration Scripts" + +#: ../../contributing/debugging.rst:158 +msgid "Configuration Error on System Boot" +msgstr "Configuration Error on System Boot" + +#: ../../contributing/development.rst:260 +msgid "Configuration Script Structure and Behaviour" +msgstr "Configuration Script Structure and Behaviour" + +#: ../../contributing/issues-features.rst:24 +msgid "Consult the documentation_ to ensure that you have configured your system correctly" +msgstr "Consult the documentation_ to ensure that you have configured your system correctly" + +#: ../../contributing/development.rst:705 +msgid "Continuous Integration" +msgstr "Continuous Integration" + +#: ../../contributing/build-vyos.rst:255 +msgid "Customize" +msgstr "Customize" + +#: ../../contributing/testing.rst:100 +msgid "DHCP client and DHCPv6 prefix delegation" +msgstr "DHCP client and DHCPv6 prefix delegation" + +#: ../../contributing/upstream-packages.rst:46 +msgid "DMVPN patches are added by this commit: https://github.com/vyos/vyos-strongswan/commit/1cf12b0f2f921bfc51affa3b81226" +msgstr "DMVPN patches are added by this commit: https://github.com/vyos/vyos-strongswan/commit/1cf12b0f2f921bfc51affa3b81226" + +#: ../../contributing/build-vyos.rst:713 +msgid "Debian APT is not very verbose when it comes to errors. If your ISO build breaks for whatever reason and you suspect it's a problem with APT dependencies or installation you can add this small patch which increases the APT verbosity during ISO build." +msgstr "Debian APT is not very verbose when it comes to errors. If your ISO build breaks for whatever reason and you suspect it's a problem with APT dependencies or installation you can add this small patch which increases the APT verbosity during ISO build." + +#: ../../contributing/build-vyos.rst:154 +msgid "Debian Bullseye for VyOS 1.4 (sagitta, current) - aka the rolling release" +msgstr "Debian Bullseye for VyOS 1.4 (sagitta, current) - aka the rolling release" + +#: ../../contributing/build-vyos.rst:153 +msgid "Debian Buster for VyOS 1.3 (equuleus)" +msgstr "Debian Buster for VyOS 1.3 (equuleus)" + +#: ../../contributing/build-vyos.rst:152 +msgid "Debian Jessie for VyOS 1.2 (crux)" +msgstr "Debian Jessie for VyOS 1.2 (crux)" + +#: ../../contributing/upstream-packages.rst:31 +msgid "Debian does keep their package in git, but it's upstream tarball imported into git without its original commit history. To be able to merge new tags in, we keep a fork of the upstream repository with packaging files imported from Debian at https://github.com/vyos/keepalived-upstream" +msgstr "Debian does keep their package in git, but it's upstream tarball imported into git without its original commit history. To be able to merge new tags in, we keep a fork of the upstream repository with packaging files imported from Debian at https://github.com/vyos/keepalived-upstream" + +#: ../../contributing/debugging.rst:5 +msgid "Debugging" +msgstr "Debugging" + +#: ../../contributing/debugging.rst:96 +msgid "Debugging Python Code with PDB" +msgstr "Debugging Python Code with PDB" + +#: ../../contributing/development.rst:503 +msgid "Description" +msgstr "Description" + +#: ../../contributing/development.rst:120 +msgid "Determinine source package" +msgstr "Determinine source package" + +#: ../../contributing/development.rst:5 +msgid "Development" +msgstr "Development" + +#: ../../contributing/development.rst:643 +msgid "Do not add angle brackets around the format, they will be inserted automatically" +msgstr "Do not add angle brackets around the format, they will be inserted automatically" + +#: ../../contributing/build-vyos.rst:33 +msgid "Docker" +msgstr "Docker" + +#: ../../contributing/build-vyos.rst:73 +msgid "Dockerhub" +msgstr "Dockerhub" + +#: ../../contributing/build-vyos.rst:50 +msgid "Doing so grants privileges equivalent to the ``root`` user! It is recommended to remove the non-root user from the ``docker`` group after building the VyOS ISO. See also `Docker as non-root`_." +msgstr "Doing so grants privileges equivalent to the ``root`` user! It is recommended to remove the non-root user from the ``docker`` group after building the VyOS ISO. See also `Docker as non-root`_." + +#: ../../contributing/upstream-packages.rst:17 +msgid "Due to issues in the upstream version that sometimes set interfaces down, a modified version is used." +msgstr "Due to issues in the upstream version that sometimes set interfaces down, a modified version is used." + +#: ../../contributing/debugging.rst:172 +msgid "During the migration and extensive rewrite of functionality from Perl into Python a significant increase in the overall system boottime was noticed. The system boot time can be analysed and a graph can be generated in the end which shows in detail who called whom during the system startup phase." +msgstr "During the migration and extensive rewrite of functionality from Perl into Python a significant increase in the overall system boottime was noticed. The system boot time can be analysed and a graph can be generated in the end which shows in detail who called whom during the system startup phase." + +#: ../../contributing/development.rst:717 +msgid "Each module is build on demand if a new commit on the branch in question is found. After a successful run the resulting Debian Package(s) will be deployed to our Debian repository which is used during build time. It is located here: http://dev.packages.vyos.net/repositories/." +msgstr "Each module is build on demand if a new commit on the branch in question is found. After a successful run the resulting Debian Package(s) will be deployed to our Debian repository which is used during build time. It is located here: http://dev.packages.vyos.net/repositories/." + +#: ../../contributing/build-vyos.rst:407 +msgid "Each of those modules holds a dependency on the kernel version and if you are lucky enough to receive an ISO build error which sounds like:" +msgstr "Each of those modules holds a dependency on the kernel version and if you are lucky enough to receive an ISO build error which sounds like:" + +#: ../../contributing/development.rst:504 +msgid "Enabled/Disabled" +msgstr "Enabled/Disabled" + +#: ../../contributing/issues-features.rst:29 +msgid "Ensure the problem is reproducible" +msgstr "Ensure the problem is reproducible" + +#: ../../contributing/development.rst:104 +msgid "Every change set must be consistent (self containing)! Do not fix multiple bugs in a single commit. If you already worked on multiple fixes in the same file use `git add --patch` to only add the parts related to the one issue into your upcoming commit." +msgstr "Every change set must be consistent (self containing)! Do not fix multiple bugs in a single commit. If you already worked on multiple fixes in the same file use `git add --patch` to only add the parts related to the one issue into your upcoming commit." + +#: ../../contributing/development.rst:412 +#: ../../contributing/testing.rst:65 +msgid "Example:" +msgstr "Example:" + +#: ../../contributing/development.rst:559 +#: ../../contributing/development.rst:571 +#: ../../contributing/development.rst:580 +#: ../../contributing/development.rst:591 +#: ../../contributing/development.rst:602 +#: ../../contributing/development.rst:616 +msgid "Examples:" +msgstr "Examples:" + +#: ../../contributing/development.rst:377 +msgid "Exceptions, including ``VyOSError`` (which is raised by ``vyos.config.Config`` on improper config operations, such as trying to use ``list_nodes()`` on a non-tag node) should not be silenced or caught and re-raised as config error. Sure this will not look pretty on user's screen, but it will make way better bug reports, and help users (and most VyOS users are IT professionals) do their own debugging as well." +msgstr "Exceptions, including ``VyOSError`` (which is raised by ``vyos.config.Config`` on improper config operations, such as trying to use ``list_nodes()`` on a non-tag node) should not be silenced or caught and re-raised as config error. Sure this will not look pretty on user's screen, but it will make way better bug reports, and help users (and most VyOS users are IT professionals) do their own debugging as well." + +#: ../../contributing/development.rst:182 +msgid "Export last commit to patch file: ``git format-patch`` or export the last two commits into its appropriate patch files: ``git format-patch -2``" +msgstr "Export last commit to patch file: ``git format-patch`` or export the last two commits into its appropriate patch files: ``git format-patch -2``" + +#: ../../contributing/development.rst:657 +msgid "External arithmetic validator may be added if there's demand, complex validation is better left to commit-time scripts" +msgstr "External arithmetic validator may be added if there's demand, complex validation is better left to commit-time scripts" + +#: ../../contributing/debugging.rst:87 +msgid "FRR" +msgstr "FRR" + +#: ../../contributing/issues-features.rst:68 +msgid "Feature Request" +msgstr "Feature Request" + +#: ../../contributing/build-vyos.rst:560 +msgid "Firmware" +msgstr "Firmware" + +#: ../../contributing/build-vyos.rst:593 +msgid "First, clone the source code and check out the appropriate version by running:" +msgstr "First, clone the source code and check out the appropriate version by running:" + +#: ../../contributing/development.rst:177 +msgid "Follow the above steps on how to \"Fork repository to submit a Patch\". Instead of uploading \"pushing\" your changes to GitHub you can export the patches/ commits and send it to maintainers@vyos.net or attach it directly to the bug (preferred over email)" +msgstr "Follow the above steps on how to \"Fork repository to submit a Patch\". Instead of uploading \"pushing\" your changes to GitHub you can export the patches/ commits and send it to maintainers@vyos.net or attach it directly to the bug (preferred over email)" + +#: ../../contributing/development.rst:85 +msgid "Followed by a message which describes all the details like:" +msgstr "Followed by a message which describes all the details like:" + +#: ../../contributing/debugging.rst:48 +msgid "For each feature, a file called ``vyos.feature.debug`` can be created to toggle the feature on. If a parameter is required it can be placed inside the file as its first line." +msgstr "For each feature, a file called ``vyos.feature.debug`` can be created to toggle the feature on. If a parameter is required it can be placed inside the file as its first line." + +#: ../../contributing/development.rst:384 +msgid "For easy orientation we suggest you take a look on the ``ntp.py`` or ``interfaces-bonding.py`` (for tag nodes) implementation. Both files can be found in the vyos-1x_ repository." +msgstr "For easy orientation we suggest you take a look on the ``ntp.py`` or ``interfaces-bonding.py`` (for tag nodes) implementation. Both files can be found in the vyos-1x_ repository." + +#: ../../contributing/debugging.rst:55 +msgid "For example, ``/tmp/vyos.ifconfig.debug`` can be created to enable interface debugging." +msgstr "For example, ``/tmp/vyos.ifconfig.debug`` can be created to enable interface debugging." + +#: ../../contributing/debugging.rst:61 +msgid "For example running, ``export VYOS_IFCONFIG_DEBUG=\"\"`` on your vbash, will have the same effect as ``touch /tmp/vyos.ifconfig.debug``." +msgstr "For example running, ``export VYOS_IFCONFIG_DEBUG=\"\"`` on your vbash, will have the same effect as ``touch /tmp/vyos.ifconfig.debug``." + +#: ../../contributing/build-vyos.rst:170 +msgid "For the packages required, you can refer to the ``docker/Dockerfile`` file in the repository_. The ``./build-vyos-image`` script will also warn you if any dependencies are missing." +msgstr "For the packages required, you can refer to the ``docker/Dockerfile`` file in the repository_. The ``./build-vyos-image`` script will also warn you if any dependencies are missing." + +#: ../../contributing/development.rst:151 +msgid "Fork: ``git remote add myfork https://github.com/<user>/vyos-1x.git``" +msgstr "Fork: ``git remote add myfork https://github.com/<user>/vyos-1x.git``" + +#: ../../contributing/development.rst:138 +msgid "Fork Repository and submit Patch" +msgstr "Fork Repository and submit Patch" + +#: ../../contributing/development.rst:140 +msgid "Forking the repository and submitting a GitHub pull-request is the preferred way of submitting your changes to VyOS. You can fork any VyOS repository to your very own GitHub account by just appending ``/fork`` to any repository's URL on GitHub. To e.g. fork the ``vyos-1x`` repository, open the following URL in your favourite browser: https://github.com/vyos/vyos-1x/fork" +msgstr "Forking the repository and submitting a GitHub pull-request is the preferred way of submitting your changes to VyOS. You can fork any VyOS repository to your very own GitHub account by just appending ``/fork`` to any repository's URL on GitHub. To e.g. fork the ``vyos-1x`` repository, open the following URL in your favourite browser: https://github.com/vyos/vyos-1x/fork" + +#: ../../contributing/development.rst:200 +msgid "Formatting" +msgstr "Formatting" + +#: ../../contributing/development.rst:495 +msgid "GNU Preprocessor" +msgstr "GNU Preprocessor" + +#: ../../contributing/issues-features.rst:26 +msgid "Get community support via Slack_ or our Forum_" +msgstr "Get community support via Slack_ or our Forum_" + +#: ../../contributing/development.rst:618 +msgid "Good: \"Disable IPv6 forwarding\"" +msgstr "Good: \"Disable IPv6 forwarding\"" + +#: ../../contributing/development.rst:561 +msgid "Good: \"Frobnication algorithm\"" +msgstr "Good: \"Frobnication algorithm\"" + +#: ../../contributing/development.rst:573 +#: ../../contributing/development.rst:604 +msgid "Good: \"TCP connection timeout\"" +msgstr "Good: \"TCP connection timeout\"" + +#: ../../contributing/development.rst:593 +msgid "Good: PPPoE, IPsec" +msgstr "Good: PPPoE, IPsec" + +#: ../../contributing/development.rst:582 +msgid "Good: RADIUS (as in remote authentication for dial-in user services)" +msgstr "Good: RADIUS (as in remote authentication for dial-in user services)" + +#: ../../contributing/build-vyos.rst:244 +msgid "Good luck!" +msgstr "Good luck!" + +#: ../../contributing/development.rst:535 +msgid "Guidelines" +msgstr "Guidelines" + +#: ../../contributing/development.rst:545 +msgid "Help String" +msgstr "Help String" + +#: ../../contributing/development.rst:51 +msgid "Help future maintainers of VyOS (it could be you!) to find out why certain things have been changed in the codebase or why certain features have been added" +msgstr "Help future maintainers of VyOS (it could be you!) to find out why certain things have been changed in the codebase or why certain features have been added" + +#: ../../contributing/development.rst:575 +msgid "Horrible: \"Tcp connection timeout\"" +msgstr "Horrible: \"Tcp connection timeout\"" + +#: ../../contributing/development.rst:564 +msgid "Horrible: \"frobnication algorithm.\"" +msgstr "Horrible: \"frobnication algorithm.\"" + +#: ../../contributing/issues-features.rst:63 +msgid "How can we reproduce this Bug?" +msgstr "How can we reproduce this Bug?" + +#: ../../contributing/testing.rst:102 +msgid "IP and IPv6 options" +msgstr "IP and IPv6 options" + +#: ../../contributing/build-vyos.rst:308 +msgid "ISO Build Issues" +msgstr "ISO Build Issues" + +#: ../../contributing/debugging.rst:12 +msgid "ISO image build" +msgstr "ISO image build" + +#: ../../contributing/issues-features.rst:19 +msgid "I have found a bug, what should I do?" +msgstr "I have found a bug, what should I do?" + +#: ../../contributing/development.rst:607 +msgid "If a verb is essential, keep it. For example, in the help text of ``set system ipv6 disable-forwarding``, \"Disable IPv6 forwarding on all interfaces\" is a perfectly justified wording." +msgstr "If a verb is essential, keep it. For example, in the help text of ``set system ipv6 disable-forwarding``, \"Disable IPv6 forwarding on all interfaces\" is a perfectly justified wording." + +#: ../../contributing/development.rst:94 +msgid "If applicable a reference to a previous commit should be made linking those commits nicely when browsing the history: ``After commit abcd12ef (\"snmp: this is a headline\") a Python import statement is missing, throwing the following exception: ABCDEF``" +msgstr "If applicable a reference to a previous commit should be made linking those commits nicely when browsing the history: ``After commit abcd12ef (\"snmp: this is a headline\") a Python import statement is missing, throwing the following exception: ABCDEF``" + +#: ../../contributing/development.rst:64 +msgid "If there is no Phabricator_ reference in the commits of your pull request, we have to ask you to amend the commit message. Otherwise we will have to reject it." +msgstr "If there is no Phabricator_ reference in the commits of your pull request, we have to ask you to amend the commit message. Otherwise we will have to reject it." + +#: ../../contributing/build-vyos.rst:699 +msgid "If you are brave enough to build yourself an ISO image containing any modified package from our GitHub organisation - this is the place to be." +msgstr "If you are brave enough to build yourself an ISO image containing any modified package from our GitHub organisation - this is the place to be." + +#: ../../contributing/build-vyos.rst:562 +msgid "If you upgrade your kernel or include new drivers you may need new firmware. Build a new ``vyos-linux-firmware`` package with the included helper scripts." +msgstr "If you upgrade your kernel or include new drivers you may need new firmware. Build a new ``vyos-linux-firmware`` package with the included helper scripts." + +#: ../../contributing/development.rst:39 +msgid "In a big system, such as VyOS, that is comprised of multiple components, it's impossible to keep track of all the changes and bugs/feature requests in one's head. We use a bugtracker known as Phabricator_ for it (\"issue tracker\" would be a better term, but this one stuck)." +msgstr "In a big system, such as VyOS, that is comprised of multiple components, it's impossible to keep track of all the changes and bugs/feature requests in one's head. We use a bugtracker known as Phabricator_ for it (\"issue tracker\" would be a better term, but this one stuck)." + +#: ../../contributing/development.rst:267 +msgid "In addition this also helps when browsing the GitHub codebase on a mobile device if you happen to be a crazy scientist." +msgstr "In addition this also helps when browsing the GitHub codebase on a mobile device if you happen to be a crazy scientist." + +#: ../../contributing/issues-features.rst:56 +msgid "In order to open up a bug-report/feature request you need to create yourself an account on VyOS Phabricator_. On the left side of the specific project (VyOS 1.2 or VyOS 1.3) you will find quick-links for opening a bug-report/feature request." +msgstr "In order to open up a bug-report/feature request you need to create yourself an account on VyOS Phabricator_. On the left side of the specific project (VyOS 1.2 or VyOS 1.3) you will find quick-links for opening a bug-report/feature request." + +#: ../../contributing/development.rst:153 +msgid "In order to record you as the author of the fix please identify yourself to Git by setting up your name and email. This can be done local for this one and only repository ``git config`` or globally using ``git config --global``." +msgstr "In order to record you as the author of the fix please identify yourself to Git by setting up your name and email. This can be done local for this one and only repository ``git config`` or globally using ``git config --global``." + +#: ../../contributing/debugging.rst:81 +msgid "In order to retrieve the debug output on the command-line you need to disable ``vyos-configd`` in addition. This can be run either one-time by calling ``sudo systemctl stop vyos-configd`` or make this reboot-safe by calling ``sudo systemctl disable vyos-configd``." +msgstr "In order to retrieve the debug output on the command-line you need to disable ``vyos-configd`` in addition. This can be run either one-time by calling ``sudo systemctl stop vyos-configd`` or make this reboot-safe by calling ``sudo systemctl disable vyos-configd``." + +#: ../../contributing/development.rst:80 +msgid "In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together." +msgstr "In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together." + +#: ../../contributing/build-vyos.rst:554 +msgid "In the end you will be presented with the kernel binary packages which you can then use in your custom ISO build process, by placing all the `*.deb` files in the vyos-build/packages folder where they will be used automatically when building VyOS as documented above." +msgstr "In the end you will be presented with the kernel binary packages which you can then use in your custom ISO build process, by placing all the `*.deb` files in the vyos-build/packages folder where they will be used automatically when building VyOS as documented above." + +#: ../../contributing/upstream-packages.rst:22 +msgid "In the future, we may switch to using systemd infrastructure instead. Building it doesn't require a special procedure." +msgstr "In the future, we may switch to using systemd infrastructure instead. Building it doesn't require a special procedure." + +#: ../../contributing/issues-features.rst:45 +msgid "Include output" +msgstr "Include output" + +#: ../../contributing/debugging.rst:106 +msgid "Insert the following statement right before the section where you want to investigate a problem (e.g. a statement you see in a backtrace): ``import pdb; pdb.set_trace()`` Optionally you can surrounded this statement by an ``if`` which only triggers under the condition you are interested in." +msgstr "Insert the following statement right before the section where you want to investigate a problem (e.g. a statement you see in a backtrace): ``import pdb; pdb.set_trace()`` Optionally you can surrounded this statement by an ``if`` which only triggers under the condition you are interested in." + +#: ../../contributing/build-vyos.rst:810 +msgid "Install" +msgstr "Install" + +#: ../../contributing/upstream-packages.rst:53 +msgid "Install https://pypi.org/project/stdeb/" +msgstr "Install https://pypi.org/project/stdeb/" + +#: ../../contributing/build-vyos.rst:35 +msgid "Installing Docker_ and prerequisites:" +msgstr "Installing Docker_ and prerequisites:" + +#: ../../contributing/development.rst:506 +msgid "Instead of supplying all those XML nodes multiple times there are now include files with predefined features. Brief overview:" +msgstr "Instead of supplying all those XML nodes multiple times there are now include files with predefined features. Brief overview:" + +#: ../../contributing/build-vyos.rst:632 +msgid "Intel NIC" +msgstr "Intel NIC" + +#: ../../contributing/build-vyos.rst:404 +msgid "Intel NIC drivers" +msgstr "Intel NIC drivers" + +#: ../../contributing/build-vyos.rst:661 +msgid "Intel QAT" +msgstr "Intel QAT" + +#: ../../contributing/build-vyos.rst:405 +msgid "Inter QAT" +msgstr "Inter QAT" + +#: ../../contributing/testing.rst:90 +msgid "Interface based tests" +msgstr "Interface based tests" + +#: ../../contributing/issues-features.rst:5 +msgid "Issues/Feature requests" +msgstr "Issues/Feature requests" + +#: ../../contributing/issues-features.rst:12 +msgid "Issues or bugs are found in any software project. VyOS is not an exception." +msgstr "Issues or bugs are found in any software project. VyOS is not an exception." + +#: ../../contributing/upstream-packages.rst:85 +msgid "It's an Ada program and requires GNAT and gprbuild for building, dependencies are properly specified so just follow debuild's suggestions." +msgstr "It's an Ada program and requires GNAT and gprbuild for building, dependencies are properly specified so just follow debuild's suggestions." + +#: ../../contributing/debugging.rst:58 +msgid "It is also possible to set up the debugging using environment variables. In that case, the name will be (in uppercase) VYOS_FEATURE_DEBUG." +msgstr "It is also possible to set up the debugging using environment variables. In that case, the name will be (in uppercase) VYOS_FEATURE_DEBUG." + +#: ../../contributing/testing.rst:17 +msgid "Jenkins CI" +msgstr "Jenkins CI" + +#: ../../contributing/build-vyos.rst:816 +msgid "Just install using the following commands:" +msgstr "Just install using the following commands:" + +#: ../../contributing/development.rst:46 +msgid "Keep track of the progress (what we've already done in this branch and what we still need to do)." +msgstr "Keep track of the progress (what we've already done in this branch and what we still need to do)." + +#: ../../contributing/upstream-packages.rst:28 +msgid "Keepalived normally isn't updated to newer feature releases between Debian versions, so we are building it from source." +msgstr "Keepalived normally isn't updated to newer feature releases between Debian versions, so we are building it from source." + +#: ../../contributing/debugging.rst:25 +msgid "Kernel" +msgstr "Kernel" + +#: ../../contributing/build-vyos.rst:787 +msgid "Launch Docker container and build package" +msgstr "Launch Docker container and build package" + +#: ../../contributing/development.rst:633 +msgid "Leaf nodes (nodes with values) use <leafNode> tag instead" +msgstr "Leaf nodes (nodes with values) use <leafNode> tag instead" + +#: ../../contributing/development.rst:240 +msgid "Let's face it: VyOS is full of spaghetti code where logic for reading the VyOS config, generating daemon configs, and restarting processes is all mixed up." +msgstr "Let's face it: VyOS is full of spaghetti code where logic for reading the VyOS config, generating daemon configs, and restarting processes is all mixed up." + +#: ../../contributing/debugging.rst:101 +msgid "Let us assume you want to debug a Python script that is called by an op-mode command. After you found the script by looking up the op-mode-defitions you can edit the script in the live system using e.g. vi: ``vi /usr/libexec/vyos/op_mode/show_xyz.py``" +msgstr "Let us assume you want to debug a Python script that is called by an op-mode command. After you found the script by looking up the op-mode-defitions you can edit the script in the live system using e.g. vi: ``vi /usr/libexec/vyos/op_mode/show_xyz.py``" + +#: ../../contributing/development.rst:189 +msgid "Like any other project we have some small guidelines about our source code, too. The rules we have are not there to punish you - the rules are in place to help us all. By having a consistent coding style it becomes very easy for new and also longtime contributors to navigate through the sources and all the implied logic of any one source file.." +msgstr "Like any other project we have some small guidelines about our source code, too. The rules we have are not there to punish you - the rules are in place to help us all. By having a consistent coding style it becomes very easy for new and also longtime contributors to navigate through the sources and all the implied logic of any one source file.." + +#: ../../contributing/development.rst:109 +msgid "Limits:" +msgstr "Limits:" + +#: ../../contributing/build-vyos.rst:390 +msgid "Linux Kernel" +msgstr "Linux Kernel" + +#: ../../contributing/debugging.rst:42 +msgid "Live System" +msgstr "Live System" + +#: ../../contributing/testing.rst:101 +msgid "MTU size" +msgstr "MTU size" + +#: ../../contributing/development.rst:162 +msgid "Make your changes and save them. Do the following for all changes files to record them in your created Git commit:" +msgstr "Make your changes and save them. Do the following for all changes files to record them in your created Git commit:" + +#: ../../contributing/testing.rst:60 +msgid "Manual Smoketest Run" +msgstr "Manual Smoketest Run" + +#: ../../contributing/testing.rst:168 +msgid "Manual config load test" +msgstr "Manual config load test" + +#: ../../contributing/upstream-packages.rst:6 +msgid "Many base system packages are pulled straight from Debian's main and contrib repositories, but there are exceptions." +msgstr "Many base system packages are pulled straight from Debian's main and contrib repositories, but there are exceptions." + +#: ../../contributing/development.rst:622 +msgid "Migrating old CLI" +msgstr "Migrating old CLI" + +#: ../../contributing/development.rst:677 +msgid "Move default values to scripts" +msgstr "Move default values to scripts" + +#: ../../contributing/build-vyos.rst:147 +msgid "Native Build" +msgstr "Native Build" + +#: ../../contributing/development.rst:629 +msgid "New syntax" +msgstr "New syntax" + +#: ../../contributing/development.rst:230 +msgid "No code incompatible with Python3" +msgstr "No code incompatible with Python3" + +#: ../../contributing/development.rst:228 +msgid "No new features in Perl" +msgstr "No new features in Perl" + +#: ../../contributing/development.rst:229 +msgid "No old style command definitions" +msgstr "No old style command definitions" + +#: ../../contributing/upstream-packages.rst:68 +#: ../../contributing/upstream-packages.rst:76 +msgid "No special build procedure is required." +msgstr "No special build procedure is required." + +#: ../../contributing/development.rst:649 +#: ../../contributing/development.rst:656 +#: ../../contributing/development.rst:676 +#: ../../contributing/development.rst:679 +#: ../../contributing/development.rst:682 +msgid "None" +msgstr "None" + +#: ../../contributing/development.rst:630 +msgid "Notes" +msgstr "Notes" + +#: ../../contributing/build-vyos.rst:199 +msgid "Now a fresh build of the VyOS ISO can begin. Change directory to the ``vyos-build`` directory and run:" +msgstr "Now a fresh build of the VyOS ISO can begin. Change directory to the ``vyos-build`` directory and run:" + +#: ../../contributing/build-vyos.rst:184 +msgid "Now as you are aware of the prerequisites we can continue and build our own ISO from source. For this we have to fetch the latest source code from GitHub. Please note as this will differ for both `current` and `crux`." +msgstr "Now as you are aware of the prerequisites we can continue and build our own ISO from source. For this we have to fetch the latest source code from GitHub. Please note as this will differ for both `current` and `crux`." + +#: ../../contributing/build-vyos.rst:384 +msgid "Now it's time to fix the package mirror and rerun the last step until the package installation succeeds again!" +msgstr "Now it's time to fix the package mirror and rerun the last step until the package installation succeeds again!" + +#: ../../contributing/build-vyos.rst:469 +msgid "Now we can use the helper script ``build-kernel.sh`` which does all the necessary voodoo by applying required patches from the `vyos-build/packages/linux-kernel/patches` folder, copying our kernel configuration ``x86_64_vyos_defconfig`` to the right location, and finally building the Debian packages." +msgstr "Now we can use the helper script ``build-kernel.sh`` which does all the necessary voodoo by applying required patches from the `vyos-build/packages/linux-kernel/patches` folder, copying our kernel configuration ``x86_64_vyos_defconfig`` to the right location, and finally building the Debian packages." + +#: ../../contributing/build-vyos.rst:133 +msgid "Now you are prepared with two new aliases ``vybld`` and ``vybld_crux`` to spawn your development containers in your current working directory." +msgstr "Now you are prepared with two new aliases ``vybld`` and ``vybld_crux`` to spawn your development containers in your current working directory." + +#: ../../contributing/development.rst:628 +msgid "Old concept/syntax" +msgstr "Old concept/syntax" + +#: ../../contributing/testing.rst:62 +msgid "On the other hand - as each test is contain in its own file - one can always execute a single Smoketest by hand by simply running the Python test scripts." +msgstr "On the other hand - as each test is contain in its own file - one can always execute a single Smoketest by hand by simply running the Python test scripts." + +#: ../../contributing/build-vyos.rst:174 +msgid "Once you have the required dependencies installed, you may proceed with the steps described in :ref:`build_iso`." +msgstr "Once you have the required dependencies installed, you may proceed with the steps described in :ref:`build_iso`." + +#: ../../contributing/debugging.rst:112 +msgid "Once you run ``show xyz`` and your condition is triggered you should be dropped into the python debugger:" +msgstr "Once you run ``show xyz`` and your condition is triggered you should be dropped into the python debugger:" + +#: ../../contributing/testing.rst:170 +msgid "One is not bound to load all configurations one after another but can also load individual test configurations on his own." +msgstr "One is not bound to load all configurations one after another but can also load individual test configurations on his own." + +#: ../../contributing/testing.rst:7 +msgid "One of the major advantages introduced in VyOS 1.3 is an autmated test framework. When assembling an ISO image multiple things can go wrong badly and publishing a faulty ISO makes no sense. The user is disappointed by the quality of the image and the developers get flodded with bug reports over and over again." +msgstr "One of the major advantages introduced in VyOS 1.3 is an autmated test framework. When assembling an ISO image multiple things can go wrong badly and publishing a faulty ISO makes no sense. The user is disappointed by the quality of the image and the developers get flodded with bug reports over and over again." + +#: ../../contributing/development.rst:665 +msgid "Only applicable to leaf nodes" +msgstr "Only applicable to leaf nodes" + +#: ../../contributing/build-vyos.rst:401 +msgid "Other packages (e.g. vyos-1x) add dependencies to the ISO build procedure on e.g. the wireguard-modules package which itself adds a dependency on the kernel version used due to the module it ships. This may change (for WireGuard) in future kernel releases but as long as we have out-of-tree modules." +msgstr "Other packages (e.g. vyos-1x) add dependencies to the ISO build procedure on e.g. the wireguard-modules package which itself adds a dependency on the kernel version used due to the module it ships. This may change (for WireGuard) in future kernel releases but as long as we have out-of-tree modules." + +#: ../../contributing/upstream-packages.rst:39 +msgid "Our StrongSWAN build differs from the upstream:" +msgstr "Our StrongSWAN build differs from the upstream:" + +#: ../../contributing/testing.rst:19 +msgid "Our `VyOS CI`_ system is based on Jenkins and builds all our required packages for VyOS 1.2 to 1.4. In addition to the package build, there is the vyos-build Job which builds and tests the VyOS ISO image which is published after a successfull test drive." +msgstr "Our `VyOS CI`_ system is based on Jenkins and builds all our required packages for VyOS 1.2 to 1.4. In addition to the package build, there is the vyos-build Job which builds and tests the VyOS ISO image which is published after a successfull test drive." + +#: ../../contributing/development.rst:10 +msgid "Our code is split into several modules. VyOS is composed of multiple individual packages, some of them are forks of upstream packages and are periodically synced with upstream, so keeping the whole source under a single repository would be very inconvenient and slow. There is now an ongoing effort to consolidate all VyOS-specific framework/config packages into vyos-1x package, but the basic structure is going to stay the same, just with fewer and fewer packages while the base code is rewritten from Perl/BASH into Python using and XML based interface definition for the CLI." +msgstr "Our code is split into several modules. VyOS is composed of multiple individual packages, some of them are forks of upstream packages and are periodically synced with upstream, so keeping the whole source under a single repository would be very inconvenient and slow. There is now an ongoing effort to consolidate all VyOS-specific framework/config packages into vyos-1x package, but the basic structure is going to stay the same, just with fewer and fewer packages while the base code is rewritten from Perl/BASH into Python using and XML based interface definition for the CLI." + +#: ../../contributing/upstream-packages.rst:49 +msgid "Our op mode scripts use the python-vici module, which is not included in Debian's build, and isn't quite easy to integrate in that build. For this reason we debianize that module by hand now, using this procedure:" +msgstr "Our op mode scripts use the python-vici module, which is not included in Debian's build, and isn't quite easy to integrate in that build. For this reason we debianize that module by hand now, using this procedure:" + +#: ../../contributing/testing.rst:92 +msgid "Our smoketests not only test daemons and serives, but also check if what we configure for an interface works. Thus there is a common base classed named: ``base_interfaces_test.py`` which holds all the common code that an interface supports and is tested." +msgstr "Our smoketests not only test daemons and serives, but also check if what we configure for an interface works. Thus there is a common base classed named: ``base_interfaces_test.py`` which holds all the common code that an interface supports and is tested." + +#: ../../contributing/build-vyos.rst:697 +#: ../../contributing/build-vyos.rst:766 +msgid "Packages" +msgstr "Packages" + +#: ../../contributing/development.rst:27 +msgid "Patches are always more than welcome. To have a clean and easy to maintain repository we have some guidelines when working with Git. A clean repository eases the automatic generation of a changelog file." +msgstr "Patches are always more than welcome. To have a clean and easy to maintain repository we have some guidelines when working with Git. A clean repository eases the automatic generation of a changelog file." + +#: ../../contributing/upstream-packages.rst:42 +msgid "Patches for DMVPN are merged in" +msgstr "Patches for DMVPN are merged in" + +#: ../../contributing/development.rst:661 +msgid "Please leave a comment explaining why the priority was chosen (e.g. \"after interfaces are configured\")" +msgstr "Please leave a comment explaining why the priority was chosen (e.g. \"after interfaces are configured\")" + +#: ../../contributing/development.rst:115 +msgid "Please submit your patches using the well-known GitHub pull-request against our repositories found in the VyOS GitHub organisation at https://github.com/vyos" +msgstr "Please submit your patches using the well-known GitHub pull-request against our repositories found in the VyOS GitHub organisation at https://github.com/vyos" + +#: ../../contributing/development.rst:254 +msgid "Please use the following template as good starting point when developing new modules or even rewrite a whole bunch of code in the new style XML/Pyhon interface." +msgstr "Please use the following template as good starting point when developing new modules or even rewrite a whole bunch of code in the new style XML/Pyhon interface." + +#: ../../contributing/testing.rst:103 +msgid "Port description" +msgstr "Port description" + +#: ../../contributing/testing.rst:104 +msgid "Port disable" +msgstr "Port disable" + +#: ../../contributing/development.rst:612 +msgid "Prefer infinitives" +msgstr "Prefer infinitives" + +#: ../../contributing/development.rst:37 +msgid "Prepare patch/commit" +msgstr "Prepare patch/commit" + +#: ../../contributing/development.rst:49 +msgid "Prepare release notes for upcoming releases" +msgstr "Prepare release notes for upcoming releases" + +#: ../../contributing/build-vyos.rst:9 +msgid "Prerequisites" +msgstr "Prerequisites" + +#: ../../contributing/debugging.rst:188 +msgid "Priorities" +msgstr "Priorities" + +#: ../../contributing/issues-features.rst:61 +msgid "Provide as much information as you can" +msgstr "Provide as much information as you can" + +#: ../../contributing/development.rst:234 +msgid "Python" +msgstr "Python" + +#: ../../contributing/development.rst:202 +msgid "Python: Tabs **shall not** be used. Every indentation level should be 4 spaces" +msgstr "Python: Tabs **shall not** be used. Every indentation level should be 4 spaces" + +#: ../../contributing/development.rst:195 +msgid "Python 3 **shall** be used. How long can we keep Python 2 alive anyway? No considerations for Python 2 compatibility **should** be taken at any time." +msgstr "Python 3 **shall** be used. How long can we keep Python 2 alive anyway? No considerations for Python 2 compatibility **should** be taken at any time." + +#: ../../contributing/development.rst:243 +msgid "Python (or any other language, for that matter) does not provide automatic protection from bad design, so we need to also devise design guidelines and follow them to keep the system extensible and maintainable." +msgstr "Python (or any other language, for that matter) does not provide automatic protection from bad design, so we need to also devise design guidelines and follow them to keep the system extensible and maintainable." + +#: ../../contributing/build-vyos.rst:745 +msgid "QEMU" +msgstr "QEMU" + +#: ../../contributing/development.rst:556 +msgid "Rationale: this seems to be the unwritten standard in network device CLIs, and a good aesthetic compromise." +msgstr "Rationale: this seems to be the unwritten standard in network device CLIs, and a good aesthetic compromise." + +#: ../../contributing/debugging.rst:89 +msgid "Recent versions use the ``vyos.frr`` framework. The Python class is located inside our ``vyos-1x:python/vyos/frr.py``. It comes with an embedded debugging/ (print style) debugger as vyos.ifconfig does." +msgstr "Recent versions use the ``vyos.frr`` framework. The Python class is located inside our ``vyos-1x:python/vyos/frr.py``. It comes with an embedded debugging/ (print style) debugger as vyos.ifconfig does." + +#: ../../contributing/issues-features.rst:54 +msgid "Report a Bug" +msgstr "Report a Bug" + +#: ../../contributing/build-vyos.rst:747 +msgid "Run the following command after building the ISO image." +msgstr "Run the following command after building the ISO image." + +#: ../../contributing/build-vyos.rst:756 +msgid "Run the following command after building the QEMU image." +msgstr "Run the following command after building the QEMU image." + +#: ../../contributing/build-vyos.rst:637 +#: ../../contributing/build-vyos.rst:666 +msgid "Simply use our wrapper script to build all of the driver modules." +msgstr "Simply use our wrapper script to build all of the driver modules." + +#: ../../contributing/build-vyos.rst:102 +msgid "Since VyOS has switched to Debian (11) Bullseye in its ``current`` branch, you will require individual container for `current`, `equuleus` and `crux` builds." +msgstr "Since VyOS has switched to Debian (11) Bullseye in its ``current`` branch, you will require individual container for `current`, `equuleus` and `crux` builds." + +#: ../../contributing/testing.rst:29 +msgid "Smoketests" +msgstr "Smoketests" + +#: ../../contributing/testing.rst:31 +msgid "Smoketests executes predefined VyOS CLI commands and checks if the desired daemon/service configuration is rendert - that is how to put it \"short\"." +msgstr "Smoketests executes predefined VyOS CLI commands and checks if the desired daemon/service configuration is rendert - that is how to put it \"short\"." + +#: ../../contributing/testing.rst:44 +msgid "So if you plan to build your own custom ISO image and wan't to make use of our smoketests, ensure that you have the `vyos-1x-smoketest` package installed." +msgstr "So if you plan to build your own custom ISO image and wan't to make use of our smoketests, ensure that you have the `vyos-1x-smoketest` package installed." + +#: ../../contributing/build-vyos.rst:136 +msgid "Some VyOS packages (namely vyos-1x) come with build-time tests which verify some of the internal library calls that they work as expected. Those tests are carried out through the Python Unittest module. If you want to build the ``vyos-1x`` package (which is our main development package) you need to start your Docker container using the following argument: ``--sysctl net.ipv6.conf.lo.disable_ipv6=0``, otherwise those tests will fail." +msgstr "Some VyOS packages (namely vyos-1x) come with build-time tests which verify some of the internal library calls that they work as expected. Those tests are carried out through the Python Unittest module. If you want to build the ``vyos-1x`` package (which is our main development package) you need to start your Docker container using the following argument: ``--sysctl net.ipv6.conf.lo.disable_ipv6=0``, otherwise those tests will fail." + +#: ../../contributing/development.rst:586 +msgid "Some abbreviations are traditionally written in mixed case. Generally, if it contains words \"over\" or \"version\", the letter **should** be lowercase. If there's an accepted spelling (especially if defined by an RFC or another standard), it **must** be followed." +msgstr "Some abbreviations are traditionally written in mixed case. Generally, if it contains words \"over\" or \"version\", the letter **should** be lowercase. If there's an accepted spelling (especially if defined by an RFC or another standard), it **must** be followed." + +#: ../../contributing/testing.rst:201 +msgid "Some of the configurations have preconditions which need to be met. Those most likely include generation of crypographic keys before the config can be applied - you will get a commit error otherwise. If you are interested how those preconditions are fulfilled check the vyos-build_ repository and the ``scripts/check-qemu-install`` file." +msgstr "Some of the configurations have preconditions which need to be met. Those most likely include generation of crypographic keys before the config can be applied - you will get a commit error otherwise. If you are interested how those preconditions are fulfilled check the vyos-build_ repository and the ``scripts/check-qemu-install`` file." + +#: ../../contributing/debugging.rst:98 +msgid "Sometimes it might be useful to debug Python code interactively on the live system rather than a IDE. This can be achieved using pdb." +msgstr "Sometimes it might be useful to debug Python code interactively on the live system rather than a IDE. This can be achieved using pdb." + +#: ../../contributing/build-vyos.rst:229 +msgid "Start the build:" +msgstr "Start the build:" + +#: ../../contributing/build-vyos.rst:17 +msgid "Starting with VyOS 1.2 the release model of VyOS has changed. VyOS is now **free as in speech, but not as in beer**. This means that while VyOS is still an open source project, the release ISOs are no longer free and can only be obtained via subscription, or by contributing to the community." +msgstr "Starting with VyOS 1.2 the release model of VyOS has changed. VyOS is now **free as in speech, but not as in beer**. This means that while VyOS is still an open source project, the release ISOs are no longer free and can only be obtained via subscription, or by contributing to the community." + +#: ../../contributing/development.rst:25 +msgid "Submit a Patch" +msgstr "Submit a Patch" + +#: ../../contributing/development.rst:171 +msgid "Submit the patch ``git push`` and create the GitHub pull-request." +msgstr "Submit the patch ``git push`` and create the GitHub pull-request." + +#: ../../contributing/development.rst:223 +msgid "Summary" +msgstr "Summary" + +#: ../../contributing/development.rst:122 +msgid "Suppose you want to make a change in the webproxy script but yet you do not know which of the many VyOS packages ship this file. You can determine the VyOS package name in question by using Debian's ``dpkg -S`` command of your running VyOS installation." +msgstr "Suppose you want to make a change in the webproxy script but yet you do not know which of the many VyOS packages ship this file. You can determine the VyOS package name in question by using Debian's ``dpkg -S`` command of your running VyOS installation." + +#: ../../contributing/debugging.rst:18 +msgid "System Startup" +msgstr "System Startup" + +#: ../../contributing/development.rst:214 +msgid "Template processor **should** be used for generating config files. Built-in string formatting **may** be used for simple line-oriented formats where every line is self-contained, such as iptables rules. Template processor **must** be used for structured, multi-line formats such as those used by ISC DHCPd." +msgstr "Template processor **should** be used for generating config files. Built-in string formatting **may** be used for simple line-oriented formats where every line is self-contained, such as iptables rules. Template processor **must** be used for structured, multi-line formats such as those used by ISC DHCPd." + +#: ../../contributing/testing.rst:5 +msgid "Testing" +msgstr "Testing" + +#: ../../contributing/development.rst:212 +msgid "Text generation" +msgstr "Text generation" + +#: ../../contributing/development.rst:688 +msgid "The CLI parser used in VyOS is a mix of bash, bash-completion helper and the C++ backend library [vyatta-cfg](https://github.com/vyos/vyatta-cfg). This section is a reference of common CLI commands and the respective entry point in the C/C++ code." +msgstr "The CLI parser used in VyOS is a mix of bash, bash-completion helper and the C++ backend library [vyatta-cfg](https://github.com/vyos/vyatta-cfg). This section is a reference of common CLI commands and the respective entry point in the C/C++ code." + +#: ../../contributing/build-vyos.rst:634 +msgid "The Intel NIC drivers do not come from a Git repository, instead we just fetch the tarballs from our mirror and compile them." +msgstr "The Intel NIC drivers do not come from a Git repository, instead we just fetch the tarballs from our mirror and compile them." + +#: ../../contributing/build-vyos.rst:662 +msgid "The Intel QAT (Quick Assist Technology) drivers do not come from a Git repository, instead we just fetch the tarballs from 01.org, Intel's open-source website." +msgstr "The Intel QAT (Quick Assist Technology) drivers do not come from a Git repository, instead we just fetch the tarballs from 01.org, Intel's open-source website." + +#: ../../contributing/build-vyos.rst:392 +msgid "The Linux kernel used by VyOS is heavily tied to the ISO build process. The file ``data/defaults.json`` hosts a JSON definition of the kernel version used ``kernel_version`` and the ``kernel_flavor`` of the kernel which represents the kernel's LOCAL_VERSION. Both together form the kernel version variable in the system:" +msgstr "The Linux kernel used by VyOS is heavily tied to the ISO build process. The file ``data/defaults.json`` hosts a JSON definition of the kernel version used ``kernel_version`` and the ``kernel_flavor`` of the kernel which represents the kernel's LOCAL_VERSION. Both together form the kernel version variable in the system:" + +#: ../../contributing/development.rst:22 +msgid "The README.md file will guide you to use the this top level repository." +msgstr "The README.md file will guide you to use the this top level repository." + +#: ../../contributing/development.rst:370 +msgid "The ``apply()`` and ``generate()`` functions may ``raise ConfigError`` if, for example, the daemon failed to start with the updated config. It shouldn't be a substitute for proper config checking in the ``verify()`` function. All reasonable effort should be made to verify that generated configuration is valid and will be accepted by the daemon, including, when necessary, cross- checks with other VyOS configuration subtrees." +msgstr "The ``apply()`` and ``generate()`` functions may ``raise ConfigError`` if, for example, the daemon failed to start with the updated config. It shouldn't be a substitute for proper config checking in the ``verify()`` function. All reasonable effort should be made to verify that generated configuration is valid and will be accepted by the daemon, including, when necessary, cross- checks with other VyOS configuration subtrees." + +#: ../../contributing/development.rst:351 +msgid "The ``apply()`` function applies the generated configuration to the live system. It should use non-disruptive reload whenever possible. It may execute disruptive operations such as daemon process restart if a particular component does not support non-disruptive reload, or when the expected service degradation is minimal (for example, in case of auxiliary services such as LLDPd). In case of high impact services such as VPN daemon and routing protocols, when non- disruptive reload is supported for some but not all types of configuration changes, scripts authors should make effort to determine if a configuration change can be done in a non-disruptive way and only resort to disruptive restart if it cannot be avoided." +msgstr "The ``apply()`` function applies the generated configuration to the live system. It should use non-disruptive reload whenever possible. It may execute disruptive operations such as daemon process restart if a particular component does not support non-disruptive reload, or when the expected service degradation is minimal (for example, in case of auxiliary services such as LLDPd). In case of high impact services such as VPN daemon and routing protocols, when non- disruptive reload is supported for some but not all types of configuration changes, scripts authors should make effort to determine if a configuration change can be done in a non-disruptive way and only resort to disruptive restart if it cannot be avoided." + +#: ../../contributing/development.rst:349 +msgid "The ``generate()`` function generates config files for system components." +msgstr "The ``generate()`` function generates config files for system components." + +#: ../../contributing/development.rst:328 +msgid "The ``get_config()`` function must convert the VyOS config to an abstract, internal representation. No other function is allowed to call the ``vyos.config. Config`` object method directly. The rationale for it is that when config reads are mixed with other logic, it's very hard to change the config syntax since you need to weed out every occurrence of the old syntax. If syntax-specific code is confined to a single function, the rest of the code can be left untouched as long as the internal representation remains compatible." +msgstr "The ``get_config()`` function must convert the VyOS config to an abstract, internal representation. No other function is allowed to call the ``vyos.config. Config`` object method directly. The rationale for it is that when config reads are mixed with other logic, it's very hard to change the config syntax since you need to weed out every occurrence of the old syntax. If syntax-specific code is confined to a single function, the rest of the code can be left untouched as long as the internal representation remains compatible." + +#: ../../contributing/testing.rst:47 +msgid "The ``make test`` command from the vyos-build_ repository will launch a new QEmu instance and the ISO image is first installed to the virtual harddisk." +msgstr "The ``make test`` command from the vyos-build_ repository will launch a new QEmu instance and the ISO image is first installed to the virtual harddisk." + +#: ../../contributing/development.rst:340 +msgid "The ``verify()`` function takes your internal representation of the config and checks if it's valid, otherwise it must raise ``ConfigError`` with an error message that describes the problem and possibly suggests how to fix it. It must not make any changes to the system. The rationale for it is again testability and, in the future when the config backend is ready and every script is rewritten in this fashion, ability to execute commit dry run (\"commit test\" like in JunOS) and abort commit before making any changes to the system if an error is found in any component." +msgstr "The ``verify()`` function takes your internal representation of the config and checks if it's valid, otherwise it must raise ``ConfigError`` with an error message that describes the problem and possibly suggests how to fix it. It must not make any changes to the system. The rationale for it is again testability and, in the future when the config backend is ready and every script is rewritten in this fashion, ability to execute commit dry run (\"commit test\" like in JunOS) and abort commit before making any changes to the system if an error is found in any component." + +#: ../../contributing/development.rst:392 +msgid "The bash (or better vbash) completion in VyOS is defined in *templates*. Templates are text files (called ``node.def``) stored in a directory tree. The directory names define the command names, and template files define the command behaviour. Before VyOS 1.2 (crux) this files were created by hand. After a complex redesign process_ the new style template are automatically generated from a XML input file." +msgstr "The bash (or better vbash) completion in VyOS is defined in *templates*. Templates are text files (called ``node.def``) stored in a directory tree. The directory names define the command names, and template files define the command behaviour. Before VyOS 1.2 (crux) this files were created by hand. After a complex redesign process_ the new style template are automatically generated from a XML input file." + +#: ../../contributing/build-vyos.rst:54 +msgid "The build process needs to be built on a local file system, building on SMB or NFS shares will result in the container failing to build properly! VirtualBox Drive Share is also not an option as block device operations are not implemented and the drive is always mounted as \"nodev\"" +msgstr "The build process needs to be built on a local file system, building on SMB or NFS shares will result in the container failing to build properly! VirtualBox Drive Share is also not an option as block device operations are not implemented and the drive is always mounted as \"nodev\"" + +#: ../../contributing/testing.rst:158 +msgid "The configurations are all derived from production systems and can not only act as a testcase but also as reference if one wants to enable a certain feature. The configurations can be found here: https://github.com/vyos/vyos-1x/tree/current/smoketest/configs" +msgstr "The configurations are all derived from production systems and can not only act as a testcase but also as reference if one wants to enable a certain feature. The configurations can be found here: https://github.com/vyos/vyos-1x/tree/current/smoketest/configs" + +#: ../../contributing/build-vyos.rst:87 +msgid "The container can also be built directly from source:" +msgstr "The container can also be built directly from source:" + +#: ../../contributing/build-vyos.rst:62 +msgid "The container can be built by hand or by fetching the pre-built one from DockerHub. Using the pre-built containers from the `VyOS DockerHub organisation`_ will ensure that the container is always up-to-date. A rebuild is triggered once the container changes (please note this will take 2-3 hours after pushing to the vyos-build repository)." +msgstr "The container can be built by hand or by fetching the pre-built one from DockerHub. Using the pre-built containers from the `VyOS DockerHub organisation`_ will ensure that the container is always up-to-date. A rebuild is triggered once the container changes (please note this will take 2-3 hours after pushing to the vyos-build repository)." + +#: ../../contributing/development.rst:219 +msgid "The default template processor for VyOS code is Jinja2_." +msgstr "The default template processor for VyOS code is Jinja2_." + +#: ../../contributing/build-vyos.rst:773 +msgid "The easiest way to compile your package is with the above mentioned :ref:`build_docker` container, it includes all required dependencies for all VyOS related packages." +msgstr "The easiest way to compile your package is with the above mentioned :ref:`build_docker` container, it includes all required dependencies for all VyOS related packages." + +#: ../../contributing/testing.rst:163 +msgid "The entire test is controlled by the main wrapper script ``/usr/bin/vyos-configtest`` which behaves in the same way as the main smoketest script. It scans the folder for potential configuration files and issues a ``load`` command one after another." +msgstr "The entire test is controlled by the main wrapper script ``/usr/bin/vyos-configtest`` which behaves in the same way as the main smoketest script. It scans the folder for potential configuration files and issues a ``load`` command one after another." + +#: ../../contributing/debugging.rst:52 +msgid "The file can be placed in ``/tmp`` for one time debugging (as the file will be removed on reboot) or placed in '/config' to stay permanently." +msgstr "The file can be placed in ``/tmp`` for one time debugging (as the file will be removed on reboot) or placed in '/config' to stay permanently." + +#: ../../contributing/development.rst:553 +msgid "The first word of every help string **must** be capitalized. There **must not** be a period at the end of help strings." +msgstr "The first word of every help string **must** be capitalized. There **must not** be a period at the end of help strings." + +#: ../../contributing/development.rst:71 +msgid "The format should be and is inspired by: https://git-scm.com/book/ch5-2.html It is also worth reading https://chris.beams.io/posts/git-commit/" +msgstr "The format should be and is inspired by: https://git-scm.com/book/ch5-2.html It is also worth reading https://chris.beams.io/posts/git-commit/" + +#: ../../contributing/development.rst:404 +msgid "The great thing about schemas is not only that people can know the complete grammar for certain, but also that it can be automatically verified. The `scripts/build-command-templates` script that converts the XML definitions to old style templates also verifies them against the schema, so a bad definition will cause the package build to fail. I do agree that the format is verbose, but there is no other format now that would allow this. Besides, a specialized XML editor can alleviate the issue with verbosity." +msgstr "The great thing about schemas is not only that people can know the complete grammar for certain, but also that it can be automatically verified. The `scripts/build-command-templates` script that converts the XML definitions to old style templates also verifies them against the schema, so a bad definition will cause the package build to fail. I do agree that the format is verbose, but there is no other format now that would allow this. Besides, a specialized XML editor can alleviate the issue with verbosity." + +#: ../../contributing/development.rst:44 +msgid "The information is used in three ways:" +msgstr "The information is used in three ways:" + +#: ../../contributing/build-vyos.rst:437 +msgid "The kernel build is quite easy, most of the required steps can be found in the ``vyos-build/packages/linux-kernel/Jenkinsfile`` but we will walk you through it." +msgstr "The kernel build is quite easy, most of the required steps can be found in the ``vyos-build/packages/linux-kernel/Jenkinsfile`` but we will walk you through it." + +#: ../../contributing/build-vyos.rst:425 +msgid "The most obvious reasons could be:" +msgstr "The most obvious reasons could be:" + +#: ../../contributing/upstream-packages.rst:83 +msgid "The original repo is at https://github.com/dmbaturin/hvinfo" +msgstr "The original repo is at https://github.com/dmbaturin/hvinfo" + +#: ../../contributing/testing.rst:153 +msgid "The other part of our tests are called \"config load tests\". The config load tests will load - one after another - arbitrary configuration files to test if the configuration migration scripts work as designed and that a given set of functionality still can be loaded with a fresh VyOS ISO image." +msgstr "The other part of our tests are called \"config load tests\". The config load tests will load - one after another - arbitrary configuration files to test if the configuration migration scripts work as designed and that a given set of functionality still can be loaded with a fresh VyOS ISO image." + +#: ../../contributing/issues-features.rst:47 +msgid "The output you get when you find a bug can provide lots of information. If you get an error message on the screen, copy it exactly. Having the exact message can provide detail that the developers can use. Like wise if you have any log messages that also are from the time of the issue, include those. They may also contain information that is helpful for the development team." +msgstr "The output you get when you find a bug can provide lots of information. If you get an error message on the screen, copy it exactly. Having the exact message can provide detail that the developers can use. Like wise if you have any log messages that also are from the time of the issue, include those. They may also contain information that is helpful for the development team." + +#: ../../contributing/upstream-packages.rst:60 +msgid "The package ends up in deb_dist dir." +msgstr "The package ends up in deb_dist dir." + +#: ../../contributing/debugging.rst:148 +msgid "The reason is that the configuration migration backend is rewritten and uses a new form of \"magic string\" which is applied on demand when real config migration is run on boot. When runnint individual migrators for testing, you need to convert the \"magic string\" on your own by:" +msgstr "The reason is that the configuration migration backend is rewritten and uses a new form of \"magic string\" which is applied on demand when real config migration is run on boot. When runnint individual migrators for testing, you need to convert the \"magic string\" on your own by:" + +#: ../../contributing/development.rst:19 +msgid "The repository that contains all the ISO build scripts is: https://github.com/vyos/vyos-build" +msgstr "The repository that contains all the ISO build scripts is: https://github.com/vyos/vyos-build" + +#: ../../contributing/testing.rst:53 +msgid "The script only searches for executable \"test-cases\" under ``/usr/libexec/vyos/tests/smoke/cli/`` and executes them one by one." +msgstr "The script only searches for executable \"test-cases\" under ``/usr/libexec/vyos/tests/smoke/cli/`` and executes them one by one." + +#: ../../contributing/build-vyos.rst:23 +msgid "The source code remains public and an ISO can be built using the process outlined in this chapter." +msgstr "The source code remains public and an ISO can be built using the process outlined in this chapter." + +#: ../../contributing/upstream-packages.rst:44 +msgid "The source is at https://github.com/vyos/vyos-strongswan" +msgstr "The source is at https://github.com/vyos/vyos-strongswan" + +#: ../../contributing/upstream-packages.rst:20 +msgid "The source is located at https://github.com/vyos/vyos-netplug" +msgstr "The source is located at https://github.com/vyos/vyos-netplug" + +#: ../../contributing/development.rst:236 +msgid "The switch to the Python programming language for new code is not merely a change of the language, but a chance to rethink and improve the programming approach." +msgstr "The switch to the Python programming language for new code is not merely a change of the language, but a chance to rethink and improve the programming approach." + +#: ../../contributing/debugging.rst:20 +msgid "The system startup can be debugged (like loading in the configuration file from ``/config/config.boot``. This can be achieve by extending the Kernel command-line in the bootloader." +msgstr "The system startup can be debugged (like loading in the configuration file from ``/config/config.boot``. This can be achieve by extending the Kernel command-line in the bootloader." + +#: ../../contributing/build-vyos.rst:310 +msgid "There are (rare) situations where building an ISO image is not possible at all due to a broken package feed in the background. APT is not very good at reporting the root cause of the issue. Your ISO build will likely fail with a more or less similar looking error message:" +msgstr "There are (rare) situations where building an ISO image is not possible at all due to a broken package feed in the background. APT is not very good at reporting the root cause of the issue. Your ISO build will likely fail with a more or less similar looking error message:" + +#: ../../contributing/build-vyos.rst:11 +msgid "There are different ways you can build VyOS." +msgstr "There are different ways you can build VyOS." + +#: ../../contributing/development.rst:205 +msgid "There are extensions to e.g. VIM (xmllint) which will help you to get your indention levels correct. Add to following to your .vimrc file: ``au FileType xml setlocal equalprg=xmllint\\ --format\\ --recover\\ -\\ 2>/dev/null`` now you can call the linter using ``gg=G`` in command mode." +msgstr "There are extensions to e.g. VIM (xmllint) which will help you to get your indention levels correct. Add to following to your .vimrc file: ``au FileType xml setlocal equalprg=xmllint\\ --format\\ --recover\\ -\\ 2>/dev/null`` now you can call the linter using ``gg=G`` in command mode." + +#: ../../contributing/debugging.rst:7 +msgid "There are two flags available to aid in debugging configuration scripts. Since configuration loading issues will manifest during boot, the flags are passed as kernel boot parameters." +msgstr "There are two flags available to aid in debugging configuration scripts. Since configuration loading issues will manifest during boot, the flags are passed as kernel boot parameters." + +#: ../../contributing/build-vyos.rst:257 +msgid "This ISO can be customized with the following list of configure options. The full and current list can be generated with ``./build-vyos-image --help``:" +msgstr "This ISO can be customized with the following list of configure options. The full and current list can be generated with ``./build-vyos-image --help``:" + +#: ../../contributing/debugging.rst:185 +msgid "This can also be done permanently by changing ``/boot/grub/grub.cfg``." +msgstr "This can also be done permanently by changing ``/boot/grub/grub.cfg``." + +#: ../../contributing/upstream-packages.rst:9 +msgid "This chapter lists those exceptions and gives you a brief overview what we have done on those packages. If you only want to build yourself a fresh ISO you can completely skip this chapter. It may become interesting once you have a VyOS deep dive." +msgstr "This chapter lists those exceptions and gives you a brief overview what we have done on those packages. If you only want to build yourself a fresh ISO you can completely skip this chapter. It may become interesting once you have a VyOS deep dive." + +#: ../../contributing/debugging.rst:177 +msgid "This is done by utilizing the ``systemd-bootchart`` package which is now installed by default on the VyOS 1.3 (equuleus) branch. The configuration is also versioned so we get comparable results. ``systemd-bootchart`` is configured using this file: bootchart.conf_" +msgstr "This is done by utilizing the ``systemd-bootchart`` package which is now installed by default on the VyOS 1.3 (equuleus) branch. The configuration is also versioned so we get comparable results. ``systemd-bootchart`` is configured using this file: bootchart.conf_" + +#: ../../contributing/development.rst:132 +msgid "This means the file in question (``/opt/vyatta/sbin/vyatta-update-webproxy.pl``) is located in the ``vyatta-webproxy`` package which can be found here: https://github.com/vyos/vyatta-webproxy" +msgstr "This means the file in question (``/opt/vyatta/sbin/vyatta-update-webproxy.pl``) is located in the ``vyatta-webproxy`` package which can be found here: https://github.com/vyos/vyatta-webproxy" + +#: ../../contributing/upstream-packages.rst:65 +msgid "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/mdns-repeater" +msgstr "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/mdns-repeater" + +#: ../../contributing/upstream-packages.rst:73 +msgid "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/udp-broadcast-relay" +msgstr "This package doesn't exist in Debian. A debianized fork is kept at https://github.com/vyos/udp-broadcast-relay" + +#: ../../contributing/build-vyos.rst:572 +msgid "This tries to automatically detect which blobs are needed based on which drivers were built. If it fails to find the correct files you can add them manually to ``vyos-build/packages/linux-kernel/build-linux-firmware.sh``:" +msgstr "This tries to automatically detect which blobs are needed based on which drivers were built. If it fails to find the correct files you can add them manually to ``vyos-build/packages/linux-kernel/build-linux-firmware.sh``:" + +#: ../../contributing/build-vyos.rst:26 +msgid "This will guide you through the process of building a VyOS ISO using Docker_. This process has been tested on clean installs of Debian Jessie, Stretch, and Buster." +msgstr "This will guide you through the process of building a VyOS ISO using Docker_. This process has been tested on clean installs of Debian Jessie, Stretch, and Buster." + +#: ../../contributing/testing.rst:147 +msgid "This will limit the `bond` interface test to only make use of `eth1` and `eth2` as member ports." +msgstr "This will limit the `bond` interface test to only make use of `eth1` and `eth2` as member ports." + +#: ../../contributing/testing.rst:97 +msgid "Those common tests consists out of:" +msgstr "Those common tests consists out of:" + +#: ../../contributing/build-vyos.rst:107 +msgid "Tips and Tricks" +msgstr "Tips and Tricks" + +#: ../../contributing/build-vyos.rst:46 +msgid "To be able to use Docker_ without ``sudo``, the current non-root user must be added to the ``docker`` group by calling: ``sudo usermod -aG docker yourusername``." +msgstr "To be able to use Docker_ without ``sudo``, the current non-root user must be added to the ``docker`` group by calling: ``sudo usermod -aG docker yourusername``." + +#: ../../contributing/build-vyos.rst:149 +msgid "To build VyOS natively you require a properly configured build host with the following Debian versions installed:" +msgstr "To build VyOS natively you require a properly configured build host with the following Debian versions installed:" + +#: ../../contributing/development.rst:711 +msgid "To build our modules we utilize a CI/CD Pipeline script. Each and every VyOS component comes with it's own ``Jenkinsfile`` which is (more or less) a copy. The Pipeline utilizes the Docker container from the :ref:`build_iso` section - but instead of building it from source on every run, we rather always fetch a fresh copy (if needed) from Dockerhub_." +msgstr "To build our modules we utilize a CI/CD Pipeline script. Each and every VyOS component comes with it's own ``Jenkinsfile`` which is (more or less) a copy. The Pipeline utilizes the Docker container from the :ref:`build_iso` section - but instead of building it from source on every run, we rather always fetch a fresh copy (if needed) from Dockerhub_." + +#: ../../contributing/debugging.rst:196 +msgid "To debug issues in priorities or to see what's going on in the background you can use the ``/opt/vyatta/sbin/priority.pl`` script which lists to you the execution order of the scripts." +msgstr "To debug issues in priorities or to see what's going on in the background you can use the ``/opt/vyatta/sbin/priority.pl`` script which lists to you the execution order of the scripts." + +#: ../../contributing/build-vyos.rst:333 +msgid "To debug the build process and gain additional information of what could be the root cause, you need to use `chroot` to change into the build directry. This is explained in the following step by step procedure:" +msgstr "To debug the build process and gain additional information of what could be the root cause, you need to use `chroot` to change into the build directry. This is explained in the following step by step procedure:" + +#: ../../contributing/debugging.rst:182 +msgid "To enable boot time graphing change the Kernel commandline and add the folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" +msgstr "To enable boot time graphing change the Kernel commandline and add the folowing string: ``init=/usr/lib/systemd/systemd-bootchart``" + +#: ../../contributing/debugging.rst:93 +msgid "To enable debugging just run: ``$ touch /tmp/vyos.frr.debug``" +msgstr "To enable debugging just run: ``$ touch /tmp/vyos.frr.debug``" + +#: ../../contributing/development.rst:547 +msgid "To ensure uniform look and feel, and improve readability, we should follow a set of guidelines consistently." +msgstr "To ensure uniform look and feel, and improve readability, we should follow a set of guidelines consistently." + +#: ../../contributing/development.rst:55 +msgid "To make this approach work, every change must be associated with a task number (prefixed with **T**) and a component. If there is no bug report/feature request for the changes you are going to make, you have to create a Phabricator_ task first. Once there is an entry in Phabricator_, you should reference its id in your commit message, as shown below:" +msgstr "To make this approach work, every change must be associated with a task number (prefixed with **T**) and a component. If there is no bug report/feature request for the changes you are going to make, you have to create a Phabricator_ task first. Once there is an entry in Phabricator_, you should reference its id in your commit message, as shown below:" + +#: ../../contributing/build-vyos.rst:75 +msgid "To manually download the container from DockerHub, run:" +msgstr "To manually download the container from DockerHub, run:" + +#: ../../contributing/build-vyos.rst:156 +msgid "To start, clone the repository to your local machine:" +msgstr "To start, clone the repository to your local machine:" + +#: ../../contributing/build-vyos.rst:812 +msgid "To take your newly created package on a test drive you can simply SCP it to a running VyOS instance and install the new `*.deb` package over the current running one." +msgstr "To take your newly created package on a test drive you can simply SCP it to a running VyOS instance and install the new `*.deb` package over the current running one." + +#: ../../contributing/build-vyos.rst:711 +msgid "Troubleshooting" +msgstr "Troubleshooting" + +#: ../../contributing/development.rst:362 +msgid "Unless absolutely necessary, configuration scripts should not modify the active configuration of system components directly. Whenever at all possible, scripts should generate a configuration file or files that can be applied with a single command such as reloading a service through systemd init. Inserting statements one by one is particularly discouraged, for example, when configuring netfilter rules, saving them to a file and loading it with iptables-restore should always be preferred to executing iptables directly." +msgstr "Unless absolutely necessary, configuration scripts should not modify the active configuration of system components directly. Whenever at all possible, scripts should generate a configuration file or files that can be applied with a single command such as reloading a service through systemd init. Inserting statements one by one is particularly discouraged, for example, when configuring netfilter rules, saving them to a file and loading it with iptables-restore should always be preferred to executing iptables directly." + +#: ../../contributing/upstream-packages.rst:4 +msgid "Upstream packages" +msgstr "Upstream packages" + +#: ../../contributing/development.rst:567 +msgid "Use of abbreviations and acronyms" +msgstr "Use of abbreviations and acronyms" + +#: ../../contributing/development.rst:538 +msgid "Use of numbers" +msgstr "Use of numbers" + +#: ../../contributing/development.rst:540 +msgid "Use of numbers in command names **should** be avoided unless a number is a part of a protocol name or similar. Thus, ``protocols ospfv3`` is perfectly fine, but something like ``server-1`` is questionable at best." +msgstr "Use of numbers in command names **should** be avoided unless a number is a part of a protocol name or similar. Thus, ``protocols ospfv3`` is perfectly fine, but something like ``server-1`` is questionable at best." + +#: ../../contributing/development.rst:598 +msgid "Use of verbs" +msgstr "Use of verbs" + +#: ../../contributing/development.rst:650 +msgid "Use regex" +msgstr "Use regex" + +#: ../../contributing/debugging.rst:125 +msgid "Useful commands are:" +msgstr "Useful commands are:" + +#: ../../contributing/development.rst:501 +msgid "VIF (incl. VIF-S/VIF-C)" +msgstr "VIF (incl. VIF-S/VIF-C)" + +#: ../../contributing/testing.rst:105 +msgid "VLANs (QinQ and regular 802.1q)" +msgstr "VLANs (QinQ and regular 802.1q)" + +#: ../../contributing/build-vyos.rst:754 +msgid "VMware" +msgstr "VMware" + +#: ../../contributing/development.rst:614 +msgid "Verbs, when they are necessary, **should** be in their infinitive form." +msgstr "Verbs, when they are necessary, **should** be in their infinitive form." + +#: ../../contributing/development.rst:600 +msgid "Verbs **should** be avoided. If a verb can be omitted, omit it." +msgstr "Verbs **should** be avoided. If a verb can be omitted, omit it." + +#: ../../contributing/build-vyos.rst:742 +msgid "Virtualization Platforms" +msgstr "Virtualization Platforms" + +#: ../../contributing/debugging.rst:190 +msgid "VyOS CLI is all about priorities. Every CLI node has a corresponding ``node.def`` file and possibly an attached script that is executed when the node is present. Nodes can have a priority, and on system bootup - or any other ``commit`` to the config all scripts are executed from lowest to higest priority. This is good as this gives a deterministic behavior." +msgstr "VyOS CLI is all about priorities. Every CLI node has a corresponding ``node.def`` file and possibly an attached script that is executed when the node is present. Nodes can have a priority, and on system bootup - or any other ``commit`` to the config all scripts are executed from lowest to higest priority. This is good as this gives a deterministic behavior." + +#: ../../contributing/build-vyos.rst:768 +msgid "VyOS itself comes with a bunch of packages that are specific to our system and thus cannot be found in any Debian mirror. Those packages can be found at the `VyOS GitHub project`_ in their source format can easily be compiled into a custom Debian (`*.deb`) package." +msgstr "VyOS itself comes with a bunch of packages that are specific to our system and thus cannot be found in any Debian mirror. Those packages can be found at the `VyOS GitHub project`_ in their source format can easily be compiled into a custom Debian (`*.deb`) package." + +#: ../../contributing/development.rst:707 +msgid "VyOS makes use of Jenkins_ as our Continuous Integration (CI) service. Our `VyOS CI`_ server is publicly accessible here: https://ci.vyos.net. You can get a brief overview of all required components shipped in a VyOS ISO." +msgstr "VyOS makes use of Jenkins_ as our Continuous Integration (CI) service. Our `VyOS CI`_ server is publicly accessible here: https://ci.vyos.net. You can get a brief overview of all required components shipped in a VyOS ISO." + +#: ../../contributing/build-vyos.rst:600 +msgid "We again make use of a helper script and some patches to make the build work. Just run the following command:" +msgstr "We again make use of a helper script and some patches to make the build work. Just run the following command:" + +#: ../../contributing/testing.rst:24 +msgid "We differentiate in two independent tests, which are both run in parallel by two separate QEmu instances which are launched via ``make test`` and ``make testc`` from within the vyos-build_ repository." +msgstr "We differentiate in two independent tests, which are both run in parallel by two separate QEmu instances which are launched via ``make test`` and ``make testc`` from within the vyos-build_ repository." + +#: ../../contributing/build-vyos.rst:349 +msgid "We now are free to run any command we would like to use for debugging, e.g. re-installing the failed package after updating the repository." +msgstr "We now are free to run any command we would like to use for debugging, e.g. re-installing the failed package after updating the repository." + +#: ../../contributing/build-vyos.rst:341 +msgid "We now need to mount some required, volatile filesystems" +msgstr "We now need to mount some required, volatile filesystems" + +#: ../../contributing/development.rst:111 +msgid "We only accept bugfixes in packages other than https://github.com/vyos/vyos-1x as no new functionality should use the old style templates (``node.def`` and Perl/BASH code. Use the new style XML/Python interface instead." +msgstr "We only accept bugfixes in packages other than https://github.com/vyos/vyos-1x as no new functionality should use the old style templates (``node.def`` and Perl/BASH code. Use the new style XML/Python interface instead." + +#: ../../contributing/development.rst:87 +msgid "What/why/how something has been changed, makes everyone's life easier when working with `git bisect`" +msgstr "What/why/how something has been changed, makes everyone's life easier when working with `git bisect`" + +#: ../../contributing/issues-features.rst:42 +msgid "What commands did you use? Use e.g. ``run show configuration commands``" +msgstr "What commands did you use? Use e.g. ``run show configuration commands``" + +#: ../../contributing/issues-features.rst:41 +msgid "What was the configuration prior to the change?" +msgstr "What was the configuration prior to the change?" + +#: ../../contributing/issues-features.rst:40 +msgid "What were you attempting to achieve?" +msgstr "What were you attempting to achieve?" + +#: ../../contributing/testing.rst:34 +msgid "When and ISO image is assembled by the `VyOS CI`_, the ``BUILD_SMOKETEST`` parameter is enabled by default, which will extend the ISO configuration line with the following packages:" +msgstr "When and ISO image is assembled by the `VyOS CI`_, the ``BUILD_SMOKETEST`` parameter is enabled by default, which will extend the ISO configuration line with the following packages:" + +#: ../../contributing/debugging.rst:14 +msgid "When having trouble compiling your own ISO image or debugging Jenkins issues you can follow the steps at :ref:`iso_build_issues`." +msgstr "When having trouble compiling your own ISO image or debugging Jenkins issues you can follow the steps at :ref:`iso_build_issues`." + +#: ../../contributing/development.rst:225 +msgid "When modifying the source code, remember these rules of the legacy elimination campaign:" +msgstr "When modifying the source code, remember these rules of the legacy elimination campaign:" + +#: ../../contributing/build-vyos.rst:241 +msgid "When the build is successful, the resulting iso can be found inside the ``build`` directory as ``live-image-[architecture].hybrid.iso``." +msgstr "When the build is successful, the resulting iso can be found inside the ``build`` directory as ``live-image-[architecture].hybrid.iso``." + +#: ../../contributing/debugging.rst:134 +msgid "When writing a new configuration migrator it may happen that you see an error when you try to invoke it manually on a development system. This error will look like:" +msgstr "When writing a new configuration migrator it may happen that you see an error when you try to invoke it manually on a development system. This error will look like:" + +#: ../../contributing/issues-features.rst:31 +msgid "When you are able to verify that it is actually a bug, spend some time to document how to reproduce the issue. This documentation can be invaluable." +msgstr "When you are able to verify that it is actually a bug, spend some time to document how to reproduce the issue. This documentation can be invaluable." + +#: ../../contributing/testing.rst:108 +msgid "When you are working on interface configuration and you also wan't to test if the Smoketests pass you would normally loose the remote SSH connection to your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the interface based tests can be called with an environment variable beforehand to limit the number of interfaces used in the test. By default all interface e.g. all Ethernet interfaces are used." +msgstr "When you are working on interface configuration and you also wan't to test if the Smoketests pass you would normally loose the remote SSH connection to your :abbr:`DUT (Device Under Test)`. To handle this issue, some of the interface based tests can be called with an environment variable beforehand to limit the number of interfaces used in the test. By default all interface e.g. all Ethernet interfaces are used." + +#: ../../contributing/issues-features.rst:21 +msgid "When you believe you have found a bug, it is always a good idea to verify the issue prior to opening a bug request." +msgstr "When you believe you have found a bug, it is always a good idea to verify the issue prior to opening a bug request." + +#: ../../contributing/issues-features.rst:34 +msgid "When you wish to have a developer fix a bug that you found, helping them reproduce the issue is beneficial to everyone. Be sure to include information about the hardware you are using, commands that you were running, any other activities that you may have been doing at the time. This additional information can be very useful." +msgstr "When you wish to have a developer fix a bug that you found, helping them reproduce the issue is beneficial to everyone. Be sure to include information about the hardware you are using, commands that you were running, any other activities that you may have been doing at the time. This additional information can be very useful." + +#: ../../contributing/issues-features.rst:62 +msgid "Which version of VyOS are you using? ``run show version``" +msgstr "Which version of VyOS are you using? ``run show version``" + +#: ../../contributing/build-vyos.rst:406 +#: ../../contributing/build-vyos.rst:595 +msgid "WireGuard" +msgstr "WireGuard" + +#: ../../contributing/development.rst:69 +msgid "Writing good commit messages" +msgstr "Writing good commit messages" + +#: ../../contributing/development.rst:203 +msgid "XML: Tabs **shall not** be used. Every indentation level should be 2 spaces" +msgstr "XML: Tabs **shall not** be used. Every indentation level should be 2 spaces" + +#: ../../contributing/development.rst:390 +msgid "XML (used for CLI definitions)" +msgstr "XML (used for CLI definitions)" + +#: ../../contributing/development.rst:497 +msgid "XML interface definition files use the `xml.in` file extension which was implemented in :vytask:`T1843`. XML interface definitions tend to have a lot of duplicated code in areas such as:" +msgstr "XML interface definition files use the `xml.in` file extension which was implemented in :vytask:`T1843`. XML interface definitions tend to have a lot of duplicated code in areas such as:" + +#: ../../contributing/development.rst:399 +msgid "XML interface definitions for VyOS come with a RelaxNG schema and are located in the vyos-1x_ module. This schema is a slightly modified schema from VyConf_ alias VyOS 2.0 So VyOS 1.2.x interface definitions will be reusable in Nextgen VyOS Versions with very minimal changes." +msgstr "XML interface definitions for VyOS come with a RelaxNG schema and are located in the vyos-1x_ module. This schema is a slightly modified schema from VyConf_ alias VyOS 2.0 So VyOS 1.2.x interface definitions will be reusable in Nextgen VyOS Versions with very minimal changes." + +#: ../../contributing/build-vyos.rst:827 +msgid "You can also place the generated `*.deb` into your ISO build environment to include it in a custom iso, see :ref:`build_custom_packages` for more information." +msgstr "You can also place the generated `*.deb` into your ISO build environment to include it in a custom iso, see :ref:`build_custom_packages` for more information." + +#: ../../contributing/build-vyos.rst:109 +msgid "You can create yourself some handy Bash aliases to always launch the latest - per release train (`current` or `crux`) - container. Add the following to your ``.bash_aliases`` file:" +msgstr "You can create yourself some handy Bash aliases to always launch the latest - per release train (`current` or `crux`) - container. Add the following to your ``.bash_aliases`` file:" + +#: ../../contributing/debugging.rst:122 +msgid "You can type ``help`` to get an overview of the available commands, and ``help command`` to get more information on each command." +msgstr "You can type ``help`` to get an overview of the available commands, and ``help command`` to get more information on each command." + +#: ../../contributing/issues-features.rst:70 +msgid "You have an idea of how to make VyOS better or you are in need of a specific feature which all users of VyOS would benefit from? To send a feature request please search Phabricator_ if there is already a request pending. You can enhance it or if you don't find one, create a new one by use the quick link in the left side under the specific project." +msgstr "You have an idea of how to make VyOS better or you are in need of a specific feature which all users of VyOS would benefit from? To send a feature request please search Phabricator_ if there is already a request pending. You can enhance it or if you don't find one, create a new one by use the quick link in the left side under the specific project." + +#: ../../contributing/build-vyos.rst:430 +msgid "You have your own custom kernel `*.deb` packages in the `packages` folder but neglected to create all required out-of tree modules like Accel-PPP, Intel QAT or Intel NIC drivers" +msgstr "You have your own custom kernel `*.deb` packages in the `packages` folder but neglected to create all required out-of tree modules like Accel-PPP, Intel QAT or Intel NIC drivers" + +#: ../../contributing/build-vyos.rst:434 +msgid "You have your own custom kernel `*.deb` packages in the `packages` folder but neglected to create all required out-of tree modules like Accel-PPP, WireGuard, Intel QAT, Intel NIC" +msgstr "You have your own custom kernel `*.deb` packages in the `packages` folder but neglected to create all required out-of tree modules like Accel-PPP, WireGuard, Intel QAT, Intel NIC" + +#: ../../contributing/debugging.rst:166 +msgid "You shoudl now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." +msgstr "You shoudl now see a Python backtrace which will help us to handle the issue, please attach it to the Phabricator_ task." + +#: ../../contributing/development.rst:146 +msgid "You then can proceed with cloning your fork or add a new remote to your local repository:" +msgstr "You then can proceed with cloning your fork or add a new remote to your local repository:" + +#: ../../contributing/development.rst:262 +msgid "Your configuration script or operation mode script which is also written in Python3 should have a line break on 80 characters. This seems to be a bit odd nowadays but as some people also work remotely or program using vi(m) this is a fair good standard which I hope we can rely on." +msgstr "Your configuration script or operation mode script which is also written in Python3 should have a line break on 80 characters. This seems to be a bit odd nowadays but as some people also work remotely or program using vi(m) this is a fair good standard which I hope we can rely on." + +#: ../../contributing/testing.rst:106 +msgid "..." +msgstr "..." + +#: ../../contributing/development.rst:509 +msgid "`IPv4, IPv6 and DHCP(v6)`_ address assignment" +msgstr "`IPv4, IPv6 and DHCP(v6)`_ address assignment" + +#: ../../contributing/development.rst:510 +msgid "`IPv4, IPv6`_ address assignment" +msgstr "`IPv4, IPv6`_ address assignment" + +#: ../../contributing/development.rst:512 +msgid "`MAC address`_ assignment" +msgstr "`MAC address`_ assignment" + +#: ../../contributing/development.rst:511 +msgid "`VLAN (VIF)`_ definition" +msgstr "`VLAN (VIF)`_ definition" + +#: ../../contributing/upstream-packages.rst:55 +msgid "`./configure --enable-python-eggs`" +msgstr "`./configure --enable-python-eggs`" + +#: ../../contributing/development.rst:62 +msgid "``Jenkins: add current Git commit ID to build description``" +msgstr "``Jenkins: add current Git commit ID to build description``" + +#: ../../contributing/debugging.rst:67 +msgid "``command`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." +msgstr "``command`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." + +#: ../../contributing/development.rst:699 +msgid "``commit``" +msgstr "``commit``" + +#: ../../contributing/development.rst:61 +msgid "``ddclient: T1030: auto create runtime directories``" +msgstr "``ddclient: T1030: auto create runtime directories``" + +#: ../../contributing/debugging.rst:70 +msgid "``developer`` - Should a command fail, instead of printing a message to the user explaining how to report issues, the python interpreter will start a PBD post-mortem session to allow the developer to debug the issue. As the debugger will wait from input from the developer, it has the capacity to prevent a router to boot and therefore should only be permanently set up on production if you are ready to see the OS fail to boot." +msgstr "``developer`` - Should a command fail, instead of printing a message to the user explaining how to report issues, the python interpreter will start a PBD post-mortem session to allow the developer to debug the issue. As the debugger will wait from input from the developer, it has the capacity to prevent a router to boot and therefore should only be permanently set up on production if you are ready to see the OS fail to boot." + +#: ../../contributing/debugging.rst:64 +msgid "``ifconfig`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." +msgstr "``ifconfig`` - Once set, all commands used, and their responses received from the OS, will be presented on the screen for inspection." + +#: ../../contributing/debugging.rst:77 +msgid "``log`` - In some rare cases, it may be useful to see what the OS is doing, including during boot. This option sends all commands used by VyOS to a file. The default file is ``/tmp/full-log`` but it can be changed." +msgstr "``log`` - In some rare cases, it may be useful to see what the OS is doing, including during boot. This option sends all commands used by VyOS to a file. The default file is ``/tmp/full-log`` but it can be changed." + +#: ../../contributing/development.rst:693 +msgid "``set``" +msgstr "``set``" + +#: ../../contributing/build-vyos.rst:427 +msgid "``vyos-build`` repo is outdated, please ``git pull`` to update to the latest release kernel version from us." +msgstr "``vyos-build`` repo is outdated, please ``git pull`` to update to the latest release kernel version from us." + +#: ../../contributing/debugging.rst:33 +msgid "``vyos-config-debug`` - During development, coding errors can lead to a commit failure on boot, possibly resulting in a failed initialization of the CLI. In this circumstance, the kernel boot parameter ``vyos-config-debug`` will ensure access to the system as user ``vyos``, and will log a Python stack trace to the file ``/tmp/boot-config-trace``. File ``boot-config-trace`` will generate only if config loaded with a failure status." +msgstr "``vyos-config-debug`` - During development, coding errors can lead to a commit failure on boot, possibly resulting in a failed initialization of the CLI. In this circumstance, the kernel boot parameter ``vyos-config-debug`` will ensure access to the system as user ``vyos``, and will log a Python stack trace to the file ``/tmp/boot-config-trace``. File ``boot-config-trace`` will generate only if config loaded with a failure status." + +#: ../../contributing/debugging.rst:27 +msgid "``vyos-debug`` - Adding the parameter to the linux boot line will produce timing results for the execution of scripts during commit. If one is seeing an unexpected delay during manual or boot commit, this may be useful in identifying bottlenecks. The internal flag is ``VYOS_DEBUG``, and is found in vyatta-cfg_. Output is directed to ``/var/log/vyatta/cfg-stdout.log``." +msgstr "``vyos-debug`` - Adding the parameter to the linux boot line will produce timing results for the execution of scripts during commit. If one is seeing an unexpected delay during manual or boot commit, this may be useful in identifying bottlenecks. The internal flag is ``VYOS_DEBUG``, and is found in vyatta-cfg_. Output is directed to ``/var/log/vyatta/cfg-stdout.log``." + +#: ../../contributing/upstream-packages.rst:56 +msgid "`cd src/libcharon/plugins/vici/python`" +msgstr "`cd src/libcharon/plugins/vici/python`" + +#: ../../contributing/upstream-packages.rst:54 +msgid "`cd vyos-strongswan`" +msgstr "`cd vyos-strongswan`" + +#: ../../contributing/upstream-packages.rst:57 +msgid "`make`" +msgstr "`make`" + +#: ../../contributing/upstream-packages.rst:58 +msgid "`python3 setup.py --command-packages=stdeb.command bdist_deb`" +msgstr "`python3 setup.py --command-packages=stdeb.command bdist_deb`" + +#: ../../contributing/development.rst:672 +msgid "allowed: /path/to/script" +msgstr "allowed: /path/to/script" + +#: ../../contributing/development.rst:669 +msgid "allowed: cli-shell-api listNodes vpn ipsec esp-group" +msgstr "allowed: cli-shell-api listNodes vpn ipsec esp-group" + +#: ../../contributing/development.rst:666 +msgid "allowed: echo foo bar" +msgstr "allowed: echo foo bar" + +#: ../../contributing/development.rst:681 +msgid "begin:/create:/delete:" +msgstr "begin:/create:/delete:" + +#: ../../contributing/development.rst:678 +msgid "commit:expression:" +msgstr "commit:expression:" + +#: ../../contributing/debugging.rst:128 +msgid "contine execution using ``cont``" +msgstr "contine execution using ``cont``" + +#: ../../contributing/development.rst:675 +msgid "default:" +msgstr "default:" + +#: ../../contributing/debugging.rst:127 +msgid "examine variables using ``pp(var)``" +msgstr "examine variables using ``pp(var)``" + +#: ../../contributing/debugging.rst:129 +msgid "get a backtrace using ``bt``" +msgstr "get a backtrace using ``bt``" + +#: ../../contributing/development.rst:637 +msgid "help: My node" +msgstr "help: My node" + +#: ../../contributing/development.rst:701 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/commit/commit-algorithm.cpp#L1252" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/commit/commit-algorithm.cpp#L1252" + +#: ../../contributing/development.rst:696 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L2549" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L2549" + +#: ../../contributing/development.rst:695 +msgid "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L352" +msgstr "https://github.com/vyos/vyatta-cfg/blob/0f42786a0b3/src/cstore/cstore.cpp#L352" + +#: ../../contributing/upstream-packages.rst:79 +msgid "hvinfo" +msgstr "hvinfo" + +#: ../../contributing/upstream-packages.rst:26 +msgid "keepalived" +msgstr "keepalived" + +#: ../../contributing/upstream-packages.rst:63 +msgid "mdns-repeater" +msgstr "mdns-repeater" + +#: ../../contributing/development.rst:663 +msgid "multi:" +msgstr "multi:" + +#: ../../contributing/development.rst:631 +msgid "mynode/node.def" +msgstr "mynode/node.def" + +#: ../../contributing/development.rst:634 +msgid "mynode/node.tag , tag:" +msgstr "mynode/node.tag , tag:" + +#: ../../contributing/development.rst:659 +msgid "priority: 999" +msgstr "priority: 999" + +#: ../../contributing/upstream-packages.rst:37 +msgid "strongswan" +msgstr "strongswan" + +#: ../../contributing/upstream-packages.rst:41 +msgid "strongswan-nm package build is disabled since we don't use NetworkManager" +msgstr "strongswan-nm package build is disabled since we don't use NetworkManager" + +#: ../../contributing/development.rst:648 +msgid "syntax:expression: $VAR(@) in \"foo\", \"bar\", \"baz\"" +msgstr "syntax:expression: $VAR(@) in \"foo\", \"bar\", \"baz\"" + +#: ../../contributing/development.rst:655 +msgid "syntax:expression: (arithmetic expression)" +msgstr "syntax:expression: (arithmetic expression)" + +#: ../../contributing/development.rst:651 +msgid "syntax:expression: exec ..." +msgstr "syntax:expression: exec ..." + +#: ../../contributing/development.rst:645 +msgid "syntax:expression: pattern" +msgstr "syntax:expression: pattern" + +#: ../../contributing/upstream-packages.rst:71 +msgid "udp-broadcast-relay" +msgstr "udp-broadcast-relay" + +#: ../../contributing/development.rst:640 +msgid "val_help: <format>; some string" +msgstr "val_help: <format>; some string" + +#: ../../contributing/upstream-packages.rst:15 +msgid "vyos-netplug" +msgstr "vyos-netplug" |