delta/NetworkManager.git, branch th/printf

core: escape percent characters for printf format string

2014-08-25T10:29:45+00:00

Signed-off-by: Thomas Haller

libnm-core: add _nm_utils_str_printf_escape() function

2014-08-25T10:13:45+00:00

Signed-off-by: Thomas Haller

po: fix an error in a plural form of a Russian translation (bgo #735186)

2014-08-25T07:47:54+00:00

The error was produced by:
msgfmt -vc ru.po

https://bugzilla.gnome.org/show_bug.cgi?id=735186

cli: simplify do_connections() now that we don't wait for "connection-read"

2014-08-22T21:33:04+00:00

nm_remote_settings_list_connections() ensures the connections are loaded first.
We check "help" commands before getting connections, because it is time
intensive action.

cli: fix 'nmcli connection' so that it returns correct exit code

2014-08-22T21:33:04+00:00

It was broken by commit 57e802f3aa2aac8daba9a7a442a2393ab5888dba, which made
nmcli always return success.

For example:
$ nmcli con add type blabla

libnm-core: fix compile warning about unused-result

2014-08-22T21:11:59+00:00

Merge branch 'th/bgo696936_normalize_settings'

2014-08-22T13:30:50+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=696936

Signed-off-by: Thomas Haller

libnm-util: properly disconnect "notify" signal for settings in NMConnection

2014-08-22T13:26:34+00:00

When removing/replacing a NMSetting in an NMConnection, we have
to disconnect setting_changed_cb() from the "notify" signal.

Backport commit dfba4ce1e1c5bd0c1ae798bc538b5fab3e3faded from
libnm-core.

Signed-off-by: Thomas Haller

libnm-core: fix NMSettingConnection:verify() not to modify interface-name

2014-08-22T13:24:31+00:00

verify() used to modify interface-name of the base settings. This is
discouraged, because verify() should not touch the connection.

For libnm-core we can change behavior and only modify the connection
in normalize().

Also, be more strict not to verify() sucessfully on invalid
interface-name.

Signed-off-by: Thomas Haller

libnm-core: allow nm_setting_verify() to succeed individually without @all_settings

2014-08-22T13:24:31+00:00

When calling nm_setting_verify() without providing any settings in @all_settings,
we assume that the setting on its own might be valid.
Only when checked together with all settings, we want to consider the setting
in the full context. nm_connection_verify() ensures to pass on a list of settings.

Signed-off-by: Thomas Haller