Salt configuration management for openSUSE
The project contains Salt from SaltStack and it's _hard_ requirements (aka Requires)
It does _not_ contain soft requirements (aka Suggests) for specific Salt modules. Those are in devel:languages:python
Refresh
| Name | Changed |
|---|
Comments 6
The python-singlespec changes in d:l:python appear to have created a large number of unresolvable failures for the SLE distributions. Can this be fixed, perhaps by linkpac python-rpm-macros ?
Hello...anyone?
Sigh, another try. It seems my comment is truncated at an in-code-block "<"…
I'm seeing in zypper:
Repository: Saltstack
Key Name: systemsmanagement OBS Project <systemsmanagement@build.opensuse.org> Key Fingerprint: 68D33874 99670AEB D9882DB3 2ABFA143 A0E46E11
Key Created: Sun Mar 15 17:19:59 2015
Key Expires: Tue May 23 18:19:59 2017 (EXPIRED)
Rpm Name: gpg-pubkey-a0e46e11-5505b12f
Is this a mirror problem or did the key expire?
$> osc signkey | LANG=C gpg pub 1024D/A0E46E11 2010-11-09 [expires: 2019-07-18] uid systemsmanagement OBS Project systemsmanagement@build.opensuse.org
So it is not expired? I think you use the download URL for the key. Which one. Maybe we just need to enforce a rebuild of the repository.
here too ...
$> osc signkey | LANG=C gpg pub 1024D/A0E46E11 2010-11-09 [expires: 2019-07-18] uid systemsmanagement OBS Project <systemsmanagement@build.opensuse.org>
Seems it is not expired. I think you use a download URL for the key. Which one? maybe we just need to enforce a rebuild of the repo.
Argh, sorry for the noise, completely my fault… I was looking at a 42.1 system, so the mirror was stale (we're using a local mirror of ftp.gwdg.de, 42.1 doesn't exist there, but we still have the stale 42.1… my bad).