Hello community, here is the log from the commit of package nginx-ingress-controller for openSUSE:Factory checked in at 2018-07-31 16:02:24 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/nginx-ingress-controller (Old) and /work/SRC/openSUSE:Factory/.nginx-ingress-controller.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "nginx-ingress-controller" Tue Jul 31 16:02:24 2018 rev:2 rq:626455 version:0.15.0 Changes: -------- --- /work/SRC/openSUSE:Factory/nginx-ingress-controller/nginx-ingress-controller.changes 2018-06-29 22:34:26.366103924 +0200 +++ /work/SRC/openSUSE:Factory/.nginx-ingress-controller.new/nginx-ingress-controller.changes 2018-07-31 16:02:25.275854493 +0200 @@ -1,0 +2,6 @@ +Sat Jul 28 18:30:46 UTC 2018 - jengelh@inai.de + +- Fix the silly backslash escapes in the description. +- Trim non-telling part of the description. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ nginx-ingress-controller.spec ++++++ --- /var/tmp/diff_new_pack.yWysFG/_old 2018-07-31 16:02:26.123855935 +0200 +++ /var/tmp/diff_new_pack.yWysFG/_new 2018-07-31 16:02:26.127855942 +0200 @@ -1,5 +1,5 @@ # -# spec file for package nginx +# spec file for package nginx-ingress-controller # # Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany. # @@ -15,6 +15,7 @@ # Please submit bugfixes or comments via http://bugs.opensuse.org/ # + Name: nginx-ingress-controller Version: 0.15.0 Release: 0 @@ -27,28 +28,23 @@ BuildRequires: go1.10 %description -Configuring a webserver or loadbalancer is harder than it should be. Most -webserver configuration files are very similar. There are some applications that -have weird little quirks that tend to throw a wrench in things, but for the most -part you can apply the same logic to them and achieve a desired result. - -The Ingress resource embodies this idea, and an Ingress controller is meant to -handle all the quirks associated with a specific \"class\" of Ingress. +An Ingress controller is meant to handle all the quirks associated +with a specific "class" of Ingress. An Ingress Controller is a daemon, deployed as a Kubernetes Pod, that watches -the apiserver\'s /ingresses endpoint for updates to the Ingress resource. Its +the apiserver's /ingresses endpoint for updates to the Ingress resource. Its job is to satisfy requests for Ingresses. %package -n kubernetes-404-server -Summary: 404-server is a webserver needed for the Kubernetes ingress functionality +Summary: Webserver needed for the Kubernetes ingress functionality Group: Productivity/Networking/Web/Proxy %description -n kubernetes-404-server -404-server is a simple webserver that satisfies the Kubernetes ingress, which +404-server is a webserver that satisfies the Kubernetes ingress, which means it has to do two things: -* Serves a 404 page at / -* Serves 200 on a /healthz +* Serve a 404 page at / +* Serve 200 on a /healthz %prep mkdir -p %{name}-%{version}/src/k8s.io/ingress-nginx