On Fri, Jul 17, Ludwig Nussel wrote:
Thorsten Kukuk wrote:
On Fri, Jul 17, Ludwig Nussel wrote:
What's the point of the documented change process that I tried to follow here then if people just randomly modify the wiki?
The change process is for changing guidelines, not for fixing a wrong example.
The examples are part of the guidelines. Jan even claimed that the %{?systemd_odering} you suggested is pointless. So that deserves investigation before it spreads.
Jans claim is wrong, he only need to read the RPM documentation. And he also wrote himself that this leaving systemd_ordering can lead to a broken system since systemd will ignore important new settings. Even if he thinks this can be ignored :( I don't think that risking that a service does not start correctly anymore after an update is acceptable and fits with a "rolling release". The real problem is, that we change, adjust and fix code, but nobody takes care to adjust the guidelines. So systemd should have never accepted in Factory with the new macros as they violate the guidelines?
Do zypp resp libsolv actually do anything with it?
If not it's a libsolv bug, RPM does something with it. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org