Merge forward
Merge forward
Hint PF type if bracket enclosed IPv6 address
Remove the (often erroneous) missing arguments warning

TypeErrors are indeed thrown when missing arguments issues happen.
However, the overwhelming majority of instances where this is thrown,
it's actually inaccurate and confusing to users. The exception itself
should be sufficient.
Fix stupid error
Add info on upgrading to ZeroMQ 4
Add info on upgrading to ZeroMQ 4
Add soem release notes updates
Fix output of pkg.list_repo_pkgs (yumpkg)

This allows for the full list of available packages in each repo to be
returned. This was my original intention when I wrote this function, but
I didn't realize that I was missing versions in the output until I
researched github issue #16467.

The structure of the return dict had to be changed slightly to
accommodate the new behavior.

Additionally, rather than just sorting each list in place, this sorts
all versions for a given package in a given repo using
distuils.version.LooseVersion, to give an accurate sorting of versions,
and put the newest versions at the top of the list.
Merge branch 'develop' of github.com:cro/salt into develop
reliably stop windows services

`net stop` issues a stop command to the target service and waits
briefly (~30s), but will give up if the service takes too long to stop
with a misleading "service could not be stopped" message. `net stop`
will report failure, but some time later the service may actually stop
on it's own.

The common solution for really knowing when a service is stopped is to
poll using `sc query`, which is what this patch does for failed `net
stop` commands.

Adds two configuration constants which might need tweaking:

* `SERVICE_STOP_DELAY_SECONDS` - how many seconds to wait in between poll
  attempts
* `SERVICE_STOP_POLL_MAX_ATTEMPTS` - how many poll attempts to make
  before giving up

Most of the batch-file based solutions posted by windows admins are
unbounded polling, but I'm not comfortable with infinite loops so I
added the max attempts guard.

Right now I have these set to 15s and 5 attempts, so salt will wait 5*15
= 75s for services to stop, which might need some tweaking.

See also:

* http://stackoverflow.com/questions/3325081/how-to-check-if-a-service-is-running-via-batch-file-and-start-it-if-it-is-not-r
* ​http://stackoverflow.com/questions/1405372/stopping-starting-a-remote-windows-service-and-waiting-for-it-to-open-close
`net stop` return code is misleading, check stdout

When `net stop` gives up waiting for a service to stop, it still has
retcode 0, so we need to check the actual output to tell if it worked or
not. If we see "service was stopped" we consider it good, otherwise
start polling.

Sample `cmd.run_all` output for the `net stop` failure case:

    pid:
        6360
    retcode:
        0
    stderr:

    stdout:
        The NSClient++ (Win32) service is stopping........
        The NSClient++ (Win32) service could not be stopped.

Sample `cmd.run` output for the when `net stop` works as intended:

    The NSClient++ (Win32) service is stopping...
    The NSClient++ (Win32) service was stopped successfully.
log when we stop waiting for a service to stop

Leave some evidence of the failure for the ops folks.
Merge commit, resolve conflict
account for stop failures when restarting services

During restarts, only try to start the service if it successfully
stopped
Merge commit, resolve conflict
Revert comment
Merge branch 'develop' of github.com:saltstack/salt into develop
Fix #16085 pam auth module was not closeing PamHandle. moreinfo: http://pubs.opengroup.org/onlinepubs/8329799/pam_end.htm
pep8