Johannes Kastl [10.01.2017 12:57]:
> Hi,
>
> thanks for your answer.
>
> On 10.01.17 12:40 Jean-Yves LENHOF wrote:
>
>> Because some part of your error is in German...
>
> This is just because the error messages are displayed in another
> locale, but there are still error messages:
>
> fatal: [XXX]: FAILED! => {"changed": false, "cmd": ["/usr/bin/zypper",
> "--quiet", "--non-interactive", "--xmlout", "refresh", "--dry-run"],
> "failed": true, "msg": "Zypper run command failed with return code
> 2.", "rc": 2, "stderr": "Unknown option '--dry-run'\n", "stdout":
> "<?xml version='1.0'?>\n<stream>\n</stream>\n", "stdout_lines":
> ["<?xml version='1.0'?>", "<stream>", "</stream>"]}
>
> zypper does not have a --dry-run switch (anymore) apparently.
>
> Johannes
>
Johannes,
I do not think so.
On Leap 42.2, I get
---snip---
# rpm -qa '*zypp*' | sort
PackageKit-backend-zypp-1.1.3-2.3.x86_64
etckeeper-zypp-plugin-1.18.5-11.3.x86_64
libzypp-16.3.2-3.1.x86_64
snapper-zypp-plugin-0.3.3-2.2.noarch
zypp-plugin-python-0.5-5.3.x86_64
zypper-1.13.14-3.1.x86_64
zypper-aptitude-1.13.14-3.1.noarch
zypper-log-1.13.14-3.1.noarch
---pins---
Yes, there was a patch for zypper, I think it came in yesterday. The
command I took as sample ("zypper in --dry-run ossec-hids") finished
without errors.
Maybe it helps to patch zypper via "zypper patch" :)
Regards,
Werner
--
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/4b953a41-8f1e-71ae-3a77-621585afcdb1%40ufz.de.
For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
