xterm: Changes to 'debian-unstable'
debian/changelog | 8 ++++++++
debian/rules | 1 +
2 files changed, 9 insertions(+)
New commits:
commit 0aa37f76fb31c8c5c06569dd7c12dc65514edc3c
Author: Julien Cristau <jcristau@debian.org>
Date: Wed Aug 12 22:25:21 2009 +0200
Prepare changelog for upload
diff --git a/debian/changelog b/debian/changelog
index 932d850..105960b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,10 @@
-xterm (244-2) UNRELEASED; urgency=low
+xterm (244-2) unstable; urgency=low
* Configure with --disable-fifo-lines to work around a crash in the new
saved-lines handling code (closes: #541236, #541160, #541132, #541109).
Thanks to Thomas Dickey for the workaround.
- -- Julien Cristau <jcristau@debian.org> Wed, 12 Aug 2009 22:18:53 +0200
+ -- Julien Cristau <jcristau@debian.org> Wed, 12 Aug 2009 22:25:16 +0200
xterm (244-1) unstable; urgency=low
commit b27b703a9cbfebfdb70d88f46ce7bab2204a4002
Author: Julien Cristau <jcristau@debian.org>
Date: Wed Aug 12 22:21:47 2009 +0200
Configure with --disable-fifo-lines
This should work around a crash in the new saved-lines handling code
(closes: #541236, #541160, #541132, #541109). Thanks to Thomas Dickey
for the workaround.
diff --git a/debian/changelog b/debian/changelog
index 4566b9f..932d850 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+xterm (244-2) UNRELEASED; urgency=low
+
+ * Configure with --disable-fifo-lines to work around a crash in the new
+ saved-lines handling code (closes: #541236, #541160, #541132, #541109).
+ Thanks to Thomas Dickey for the workaround.
+
+ -- Julien Cristau <jcristau@debian.org> Wed, 12 Aug 2009 22:18:53 +0200
+
xterm (244-1) unstable; urgency=low
* New upstream release
diff --git a/debian/rules b/debian/rules
index 4782a6f..bb14db2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -66,6 +66,7 @@ $(STAMP_DIR)/configure: $(STAMP_DIR)/patch
--enable-narrowproto \
--enable-exec-xterm \
--enable-dabbrev \
+ --disable-fifo-lines \
$(confflags) \
DESKTOP_FLAGS="$(DESKTOP_FLAGS)" \
CFLAGS="$(CFLAGS)" \
Reply to: