[bug#78760] gnu: nginx: Update to 1.28.0.

Message ID yFaSsvKIzBheVcEPnFo1xCUAFsQeSYA6ntNxPSZp5YYsW4hp01YuKvqkDOtoHpdLgrv45J5SEzyovl9IaSYPYYsf_22xdsnL2wpXgJsojLw=@proton.me
State New
Headers
Series [bug#78760] gnu: nginx: Update to 1.28.0. |

Commit Message

Arthur Rodrigues June 11, 2025, 4:11 p.m. UTC
  Change-Id: I31bab5d18c546bb2592db464035ca249305c84b4
---
 gnu/packages/web.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


base-commit: a2fe8a4726f8f3931a4f953b950f5f99026f05ff
  

Comments

Ashish SHUKLA June 11, 2025, 10:09 p.m. UTC | #1
Hi,

As per the comment in the source, and the nginx documentation[0], the 
mainline version is recommended over stable version.

Also, I submitted an update with HTTP/3 support sometime ago, in case 
you wish to give it a shot[1].

References:
[0] 
https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/
[1] https://issues.guix.gnu.org/78302

Thanks!
  

Patch

diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
index 22369cd3f5..e69e8d18de 100644
--- a/gnu/packages/web.scm
+++ b/gnu/packages/web.scm
@@ -567,14 +567,14 @@  (define-public nginx
     ;; Track the ‘mainline’ branch.  Upstream considers it more reliable than
     ;; ’stable’ and recommends that “in general you deploy the NGINX mainline
     ;; branch at all times” (https://www.nginx.com/blog/nginx-1-6-1-7-released/)
-    (version "1.27.3")
+    (version "1.28.0")
     (source (origin
               (method url-fetch)
               (uri (string-append "https://nginx.org/download/nginx-"
                                   version ".tar.gz"))
               (sha256
                (base32
-                "00vrkdx0a6fpy8n0n7m9xws0dfa7dbb9pqnh3jv3c824ixbaj8xs"))))
+                "0sppdxbmz61y3hfcfyc20gk0ky8f3m60hppzlcy9vpy0hsqcddf6"))))
     (build-system gnu-build-system)
     (inputs (list libxcrypt libxml2 libxslt openssl pcre zlib))
     (arguments