Control: tags 1097862 + patch
Control: tags 1097862 + pending
Control: tags 1106961 + patch
Control: tags 1106961 + pending

Dear maintainer,

I've prepared an NMU for screen (versioned as 4.9.1-3.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diffstat for screen-4.9.1 screen-4.9.1

 changelog |    9 +++++++++
 control   |    1 +
 rules     |    2 +-
 3 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru screen-4.9.1/debian/changelog screen-4.9.1/debian/changelog
--- screen-4.9.1/debian/changelog	2025-05-19 01:42:42.000000000 +0300
+++ screen-4.9.1/debian/changelog	2026-01-05 23:09:23.000000000 +0200
@@ -1,3 +1,12 @@
+screen (4.9.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -std=gnu17 to workaround FTBFS with GCC 15.
+    (Closes: #1097862)
+  * Build-Depends: libcrypt-dev. (Closes: #1106961)
+
+ -- Adrian Bunk <[email protected]>  Mon, 05 Jan 2026 23:09:23 +0200
+
 screen (4.9.1-3) unstable; urgency=medium
 
   [ Salvatore Bonaccorso ]
diff -Nru screen-4.9.1/debian/control screen-4.9.1/debian/control
--- screen-4.9.1/debian/control	2025-05-19 01:26:08.000000000 +0300
+++ screen-4.9.1/debian/control	2026-01-05 23:09:23.000000000 +0200
@@ -6,6 +6,7 @@
 Standards-Version: 4.6.2
 Build-Depends: debhelper-compat (= 13),
                dpkg-dev (>= 1.16.1~),
+               libcrypt-dev,
                libncurses-dev,
                libpam0g-dev,
                texinfo
diff -Nru screen-4.9.1/debian/rules screen-4.9.1/debian/rules
--- screen-4.9.1/debian/rules	2025-05-19 01:26:08.000000000 +0300
+++ screen-4.9.1/debian/rules	2026-01-05 23:09:23.000000000 +0200
@@ -9,7 +9,7 @@
 #export DH_VERBOSE=1
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
-export DEB_CFLAGS_MAINT_APPEND=-Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers
+export DEB_CFLAGS_MAINT_APPEND=-Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -std=gnu17
 
 ROOT := $(CURDIR)/debian/screen
 ROOT_UDEB := $(CURDIR)/debian/screen-udeb

Reply via email to