summaryrefslogtreecommitdiff
path: root/po
Commit message (Collapse)AuthorAgeFilesLines
* bluetooth: refactor BlueZ handling and let NMBluezManager cache ↵Thomas Haller2019-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ObjectManager data This is a complete refactoring of the bluetooth code. Now that BlueZ 4 support was dropped, the separation of NMBluezManager and NMBluez5Manager makes no sense. They should be merged. At that point, notice that BlueZ 5's D-Bus API is fully centered around D-Bus's ObjectManager interface. Using that interface, we basically only call GetManagedObjects() once and register to InterfacesAdded, InterfacesRemoved and PropertiesChanged signals. There is no need to fetch individual properties ever. Note how NMBluezDevice used to query the D-Bus properties itself by creating a GDBusProxy. This is redundant, because when using the ObjectManager interfaces, we have all information already. Instead, let NMBluezManager basically become the client-side cache of all of BlueZ's ObjectManager interface. NMBluezDevice was mostly concerned about caching the D-Bus interface's state, tracking suitable profiles (pan_connection), and moderate between bluez and NMDeviceBt. These tasks don't get simpler by moving them to a seprate file. Let them also be handled by NMBluezManager. I mean, just look how it was previously: NMBluez5Manager registers to ObjectManager interface and sees a device appearing. It creates a NMBluezDevice object and registers to its "initialized" and "notify:usable" signal. In the meantime, NMBluezDevice fetches the relevant information from D-Bus (although it was already present in the data provided by the ObjectManager) and eventually emits these usable and initialized signals. Then, NMBlue5Manager emits a "bdaddr-added" signal, for which NMBluezManager creates the NMDeviceBt instance. NMBluezManager, NMBluez5Manager and NMBluezDevice are strongly cooperating to the point that it is simpler to merge them. This is not mere refactoring. This patch aims to make everything asynchronously and always cancellable. Also, it aims to fix races and inconsistencies of the state. - Registering to a NAP server now waits for the response and delays activation of the NMDeviceBridge accordingly. - For NAP connections we now watch the bnep0 interface in platform, and tear down the device when it goes away. Bluez doesn't send us a notification on D-Bus in that case. - Rework establishing a DUN connection. It no longer uses blocking connect() and does not block until rfcomm device appears. It's all async now. It also watches the rfcomm file descriptor for POLLERR/POLLHUP to notice disconnect. - drop nm_device_factory_emit_component_added() and instead let NMDeviceBt directly register to the WWan factory's "added" signal.
* po: fixed typo in it.poDavide Palma2019-09-031-2/+2
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/259
* core: fix a typoLubomir Rintel2019-09-0365-65/+65
| | | | s/grater/greater/
* po: RHEL 8.1 translationsLudek Janda2019-08-154-13419/+11232
| | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/242 (cherry picked from commit 9e57873e9c5cda8976d0cf00e08283ae080c52a9)
* po: update Ukrainian translationYuri Chornoivan2019-08-151-1900/+2074
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/240
* po: update Polish (pl) translationPiotr Drąg2019-08-121-4314/+1725
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/239
* po: update Brazilian Portuguese (pt_BR) translationRafael Fontenelle2019-07-151-1843/+1912
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/204/
* po: fix a typo in the French translationLuclu72019-07-101-2/+2
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/200
* po: update Chinese Taiwan (zh_TW) translationHsiu-Ming Chang2019-06-291-1417/+1420
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/190
* settings: drop ibft settings pluginth/drop-ibft-settings-pluginThomas Haller2019-06-201-1/+0
| | | | | | | | | | | | | | | The functionality of the ibft settings plugin is now handled by nm-initrd-generator. There is no need for it anymore, drop it. Note that ibft called iscsiadm, which requires CAP_SYS_ADMIN to work ([1]). We really want to drop this capability, so the current solution of a settings plugin (as it is implemented) is wrong. The solution instead is nm-initrd-generator. Also, on Fedora the ibft was disabled and probably on most other distributions as well. This was only used on RHEL. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1371201#c7
* all: drop emacs file variables from source filesThomas Haller2019-06-111-1/+0
| | | | | | | | | | | | | | | | | | | | | | We no longer add these. If you use Emacs, configure it yourself. Also, due to our "smart-tab" usage the editor anyway does a subpar job handling our tabs. However, on the upside every user can choose whatever tab-width he/she prefers. If "smart-tabs" are used properly (like we do), every tab-width will work. No manual changes, just ran commands: F=($(git grep -l -e '-\*-')) sed '1 { /\/\* *-\*- *[mM]ode.*\*\/$/d }' -i "${F[@]}" sed '1,4 { /^\(#\|--\|dnl\) *-\*- [mM]ode/d }' -i "${F[@]}" Check remaining lines with: git grep -e '-\*-' The ultimate purpose of this is to cleanup our files and eventually use SPDX license identifiers. For that, first get rid of the boilerplate lines.
* po: RHEL 7.7 translations - fr,ja,zh-CNLudek Janda2019-05-283-1002/+1004
| | | | | | | | [lkundrak@v3.sk: make update-po] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/164 (cherry picked from commit 548bacd24e1b7d1d5b37dd83768c1e425a6b5cee)
* po: update-poLubomir Rintel2019-05-2866-149117/+168267
| | | | (cherry picked from commit 9de7c0542c6ee44cb0c54c0fcdb5155d00ef3a31)
* po: update Brazilian Portuguese (pt_BR) translationRafael Fontenelle2019-05-271-1197/+1162
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/165/commits
* libnm: rework team handling of JSON configThomas Haller2019-05-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Completely refactor the team/JSON handling in libnm's NMSettingTeam and NMSettingTeamPort. - team handling was added as rh#1398925. The goal is to have a more convenient way to set properties than constructing JSON. This requires libnm to implement the hard task of parsing JSON (and exposing well-understood properties) and generating JSON (based on these "artificial" properties). But not only libnm. In particular nmcli and the D-Bus API must make this "simpler" API accessible. - since NMSettingTeam and NMSettingTeamPort are conceptually the same, add "libnm-core/nm-team-utils.h" and NMTeamSetting that tries to handle the similar code side-by-sdie. The setting classes now just delegate for everything to NMTeamSetting. - Previously, there was a very fuzzy understanding of the provided JSON config. Tighten that up, when setting a JSON config it regenerates/parses all other properties and tries to make the best of it. When modifying any abstraction property, the entire JSON config gets regenerated. In particular, don't try to merge existing JSON config with the new fields. If the user uses the abstraction API, then the entire JSON gets replaced. For example note that nm_setting_team_add_link_watcher() would not be reflected in the JSON config (a bug). That only accidentally worked because client would serializing the changed link watcher to GVariant/D-Bus, then NetworkManager would set it via g_object_set(), which would renerate the JSON, and finally persist it to disk. But as far as libnm is concerned, nm_setting_team_add_link_watcher() would bring the settings instance in an inconsistent state where JSON and the link watcher property disagree. Setting any property must immediately update both the JSON and the abstraction API. - when constucting a team setting from D-Bus, we would previously parse both "config" and abstraction properties. That is wrong. Since our settings plugins only support JSON, all information must be present in the JSON config anyway. So, when "config" is present, only the JSON must be parsed. In the best case, the other information is redudant and contributes nothing. In the worse case, they information differs (which might happen if the client version differs from the server version). As the settings plugin only supports JSON, it's wrong to consider redundant, differing information from D-Bus. - we now only convert string to JSON or back when needed. Previously, setting a property resulted in parsing several JSON multiple times (per property). All operations should now scale well and be reasonably efficient. - also the property-changed signals are now handled correctly. Since NMTeamSetting knows the current state of all attributes, it can emit the exact property changed signals for what changed. - we no longer use libjansson to generate the JSON. JSON is supposed to be a machine readable exchange format, hence a major goal is to be easily handled by applications. While parsing JSON is not so trivial, writing a well-known set of values to JSON is. The advantage is that when you build libnm without libjansson support, then we still can convert the artificial properties to JSON. - Requiring libjansson in libnm is a burden, because most of the time it is not needed (as most users don't create team configurations). With this change we only require it to parse the team settings (no longer to write them). It should be reasonably simple to use a more minimalistic JSON parser that is sufficient for us, so that we can get rid of the libjansson dependency (for libnm). This also avoids the pain that we have due to the symbol collision of libjansson and libjson-glib. https://bugzilla.redhat.com/show_bug.cgi?id=1691619
* ifcfg-rh: don't check for errors reading team settings in ifcfg-rhThomas Haller2019-05-231-0/+1
| | | | | | | | | | | | | | | | | We have nm_setting_verify() for a purpose. The checks that ifcfg-rh reader does are either - redundant (and thus unnecessary) - wrong (and thus we cannot read valid settings) - should belong to libnm's nm_setting_verify(). NMSettingTeam/NMSettingTeamPort are already very libraral and don't do almost any strict validation. Previously, ifcfg reader would be even more liberal. If there is totally invalid data in the profile, reading the profile should fail.
* po: update Slovak translationJose Riha2019-05-151-510/+501
| | | | https://github.com/NetworkManager/NetworkManager/pull/350
* po/sk: update-poLubomir Rintel2019-05-151-2366/+2521
|
* po: update Spanish (es) translationRodrigo Lledó2019-05-041-2399/+2987
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/135
* po: update Spanish (es) translationRodrigo Lledó2019-05-011-32/+30
| | | | | | | | | Changing "Token" translation from "identificador" to "testigo" as discussed in the GNOME Spanish Translation Team's mailing list. Special thanks to Daniel Mustieles our coordinator. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/130
* po: update Ukrainian (uk) translationYuri Chornoivan2019-05-011-2518/+2618
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/128
* cli: refactor team-link-watcher to/from stringsThomas Haller2019-04-251-0/+1
| | | | | | | | Stricter parsing of the string: - reject attributes that don't make sense depending on the type. - reject duplicate attributes.
* po: updated Panjabi (pa) TranslationA S Alam2019-04-201-964/+831
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/120
* shared: move most of "shared/nm-utils" to "shared/nm-glib-aux"Thomas Haller2019-04-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | From the files under "shared/nm-utils" we build an internal library that provides glib-based helper utilities. Move the files of that basic library to a new subdirectory "shared/nm-glib-aux" and rename the helper library "libnm-core-base.la" to "libnm-glib-aux.la". Reasons: - the name "utils" is overused in our code-base. Everything's an "utils". Give this thing a more distinct name. - there were additional files under "shared/nm-utils", which are not part of this internal library "libnm-utils-base.la". All the files that are part of this library should be together in the same directory, but files that are not, should not be there. - the new name should better convey what this library is and what is isn't: it's a set of utilities and helper functions that extend glib with funcitonality that we commonly need. There are still some files left under "shared/nm-utils". They have less a unifying propose to be in their own directory, so I leave them there for now. But at least they are separate from "shared/nm-glib-aux", which has a very clear purpose.
* po: update Spanish (es) translationRodrigo Lledó2019-04-171-3022/+3017
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/116
* all: goodbye libnm-glibLubomir Rintel2019-04-161-31/+0
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* po: update Polish (pl) translationPiotr Drąg2019-04-151-1123/+1192
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/111
* cli: fix typo in nmcli usage outputThomas Haller2019-04-1266-76/+76
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/157
* po: update Brazilian Portuguese (pt_BR) translationRafael Fontenelle2019-04-061-2091/+2544
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/104
* Revert "all: goodbye libnm-glib"Lubomir Rintel2019-04-031-0/+31
| | | | | | We need this for a little little longer :( This reverts commit 1de8383ad9fdfc8f552117e5d109bdfa7005634b.
* po: update Italian (it) translationMilo Casagrande2019-04-021-3677/+3681
| | | | | | | * Fixed translation errors. * Completed untranslated strings. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/102
* all: goodbye libnm-glibLubomir Rintel2019-03-191-31/+0
| | | | | | | | | | | | | | | | | | | | | | | This removes libnm-glib, libnm-glib-vpn, and libnm-util for good. The it has been replaced with libnm since NetworkManager 1.0, disabled by default since 1.12 and no up-to-date distributions ship it for years now. Removing the libraries allows us to: * Remove the horrible hacks that were in place to deal with accidental use of both the new and old library in a single process. * Relief the translators of maintenance burden of similar yet different strings. * Get rid of known bad code without chances of ever getting fixed (libnm-glib/nm-object.c and libnm-glib/nm-object-cache.c) * Generally lower the footprint of the releases and our workspace If there are some really really legacy users; they can just build libnm-glib and friends from the NetworkManager-1.16 distribution. The D-Bus API is stable and old libnm-glib will keep working forever. https://github.com/NetworkManager/NetworkManager/pull/308
* po: update Esperanto (eo) translationKristjan SCHMIDT2019-02-261-1837/+2034
| | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/86 (cherry picked from commit da100581188f71f60f1a59f4af368c431d860298)
* po: update Polish (pl) translationPiotr Drąg2019-02-251-4242/+1855
| | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/91 (cherry picked from commit 01b7b32afb3805dacd2cc38846789e0211131dec)
* Mark broken strings in translations as fuzzyPiotr Drąg2019-02-256-16/+16
| | | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/89 (cherry picked from commit bccf68da1bbe100bd52c2f880598d1cbc0f3687f)
* libnm,cli: add NMSettingWireGuardThomas Haller2019-02-221-0/+1
| | | | | | | | | | | | | | For now only add the core settings, no peers' data. To support peers and the allowed-ips of the peers is more complicated and will be done later. It's more complicated because these are nested lists (allowed-ips) inside a list (peers). That is quite unusual and to conveniently support that in D-Bus API, in keyfile format, in libnm, and nmcli, is a effort. Also, it's further complicated by the fact that each peer has a secret (the preshared-key). Thus we probably need secret flags for each peer, which is a novelty as well (until now we require a fixed set of secrets per profile that is well known).
* po: update Danish (da) translationscootergrisen2019-02-131-1382/+1925
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/82
* wifi-p2p: rename files for consistent Wi-Fi P2P namingThomas Haller2019-02-011-6/+6
| | | | | | | | | | | | | | | | | | | | | | | We named the types inconsistently: - "p2p-wireless" ("libnm-core/nm-setting-p2p-wireless.h") - "p2p" ("libnm/nm-p2p-peer.h") - "p2p-wifi" ("src/devices/wifi/nm-device-p2p-wifi.h") It seems to me, "libnm/nm-p2p-peer.h" should be qualified with a "Wi-Fi" specific name. It's not just peer-to-peer, it's Wi-Fi P2P. Yes, there is an inconsistency now, because there is already "libnm/nm-access-point.h". It seems to me (from looking at the internet), that the name "Wi-Fi P2P" is more common than "P2P Wi-Fi" -- although both are used. There is also the name "Wi-Fi Direct". But it's not clear which name should be preferred here, so stick to "Wi-Fi P2P". In this first commit only rename the files. The following commit will rename the content.
* po: update Brazilian Portuguese (pt_BR) translationRafael Fontenelle2019-01-291-962/+1014
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/71
* libnm: Add NMDeviceP2PWifiBenjamin Berg2019-01-271-0/+1
|
* core: Add basic P2P Wi-Fi SettingsBenjamin Berg2019-01-271-0/+1
| | | | | The support is rather basic and only allows connecting to a specific peer. However, this is actually already enough for many usecases.
* Update Ukrainian translationYuri Chornoivan2019-01-241-585/+589
|
* po/de: fix typoDennis Brakhane2019-01-241-1/+1
| | | | https://github.com/NetworkManager/NetworkManager/pull/289
* po: translations from the Red Hat translatorsLubomir Rintel2019-01-0810-3066/+11273
|
* po: update-po for the translations that are going to be updatedLubomir Rintel2019-01-0866-160353/+221340
| | | | Just so that we get a nicer diff when pulling from the Red Hat Zanata.
* keyfile: add nm_keyfile_plugin_kf_get_int64() helperThomas Haller2019-01-071-0/+1
|
* all: say Wi-Fi instead of "wifi" or "WiFi"Lubomir Rintel2018-11-2966-683/+680
| | | | | | | | Correct the spelling across the *entire* tree, including translations, comments, etc. It's easier that way. Even the places where it's not exposed to the user, such as tests, so that we learn how is it spelled correctly.
* po: update zh_CN.po fix "Infra" translationgarywill2018-11-161-1/+1
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/48
* po: update Ukrainian (uk) translation (#36)Yuri Chornoivan2018-10-261-2259/+2483
| | | | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/36
* po: update from Red Hat translatorsLubomir Rintel2018-10-169-17945/+20876
| | | | | https://bugzilla.redhat.com/show_bug.cgi?id=1608323 (cherry picked from commit d7d085a88d6207c8362834adf407e807e9a89b68)
View Lorry Controller Status