Bug#385078: xserver-xorg: impossible mouse configuration other than /dev/input/mice
Mario 'BitKoenig' Holbe escribió: Well, I would like to try it, but since I've changed my VGA-card recently, I hit #375689 and thus went over to a fully self-managed xorg.conf. It's ok. That's actually why I'm not testing this myself. Hm, I think (or better I strongly hope :)) the xorg-maintainers are hardly working on the package-configuration thingies, so I personally would not suggest to NMU currently. Indeed. I do not mean to steal their work (and actually the Developer's Reference specifies a protocol for this) but I think it would be irresponsible from my part if I release a patched source package without new entries in the changelog stating my name and email address. About the diff, I used debdiff. If you think the produced diff is misleading, please let me know. Jose -- José M. Parrella - Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela - ucvlug.info
Bug#385078: xserver-xorg: impossible mouse configuration other than /dev/input/mice
tags 385078 +patch
thank you
Please try this patch. I'm not a bash (nor debconf!) guru but I think
that it address your concerns regarding the non-interactivity for the
mouse device setting. Please let me know if the patch works for you.
Therefore I'm providing:
1) A full, NMU-ready, source package in [1]
2) i386 binary packages in [1], and
3) A diff regarding the config.in, which you'll find attached
Note that this upload does not fix several Lintian warnings that my
build system reports. I will be glad to fix this if the patch works.
Thank you very much for your time and attention to details.
Jose
[1] http://debian.bureado.com.ve/xorg/
--
José M. Parrella - Debian Sid, k2.6.17.13
Escuela de Ingenieria Electrica
Universidad Central de Venezuela - ucvlug.info
diff -Nru /tmp/R5Q1ya1nbL/xorg-7.0.23/debian/xserver-xorg.config.in /tmp/poysleOqJV/xorg-7.0.23/debian/xserver-xorg.config.in
--- /tmp/R5Q1ya1nbL/xorg-7.0.23/debian/xserver-xorg.config.in 2006-09-17 17:11:38.0 -0400
+++ /tmp/poysleOqJV/xorg-7.0.23/debian/xserver-xorg.config.in 2006-07-19 01:16:26.0 -0400
@@ -1136,22 +1136,11 @@
MAY_BE_NULL=yes auto_answer validate_string_db_input $(priority_ceil $PRIORITY) xserver-xorg/config/inputdevice/keyboard/options $XKBOPTIONS
-# Ask the user about their mouse port
-db_input medium xserver-xorg/config/inputdevice/mouse/port
+AUTODETECTED_PORT=/dev/input/mice
+AUTODETECTED_PROTOCOL=ImPS/2
-# If the user wasn't asked, see if a previous answer was set
-if [ $_ = 30 ]
-then
- db_get xserver-xorg/config/inputdevice/mouse/port
- if [ -z $RET ]
- then
-# If a previous answer wasn't set, then we should use our defaults
- AUTODETECTED_PORT=/dev/input/mice
- AUTODETECTED_PROTOCOL=ImPS/2
- db_subst xserver-xorg/config/inputdevice/mouse/port choices $AUTODETECTED_PORT
- auto_answer db_input $(priority_ceil low) xserver-xorg/config/inputdevice/mouse/port ${AUTODETECTED_PORT}
- fi
-fi
+db_subst xserver-xorg/config/inputdevice/mouse/port choices $AUTODETECTED_PORT
+auto_answer db_input $(priority_ceil low) xserver-xorg/config/inputdevice/mouse/port ${AUTODETECTED_PORT}
db_get xserver-xorg/config/inputdevice/mouse/port
case $RET in
Bug#386938: xorg-server - FTBFS: Error: Unrecognized opcode: `sti'
This package already implements the previous experiences from other Debian maintainers regarding recent gcc and binutils interaction in s390 (that is, usage of -DNO_INLINE and correct --build and --host options for the configure script) It seems to me that sti doesn't belong here (from the interpretation of the Principles of Operation [1]) so this might be either a problem in the configure script (- autoconf) or an upstream bug in binutils. This is just my speculation, however. Jose [1] http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar008/CCONTENTS -- José M. Parrella - Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela - ucvlug.info
Bug#386938: xorg-server - FTBFS: Error: Unrecognized opcode: `sti'
José Parrella escribió: It seems to me that sti doesn't belong here (from the interpretation of the Principles of Operation [1]) so this might be either a problem in the configure script (- autoconf) or an upstream bug in binutils. This is just my speculation, however. I stand corrected. Gerardo Curiel ([javamaniac], from Debian Venezuela) has suggested that adding libklibc-dev (or any particular kernel headers) to Build-Depends might solve this problem (since include/asm-s390/system.h defines several system support routines, including sti()). Could anyone (with access to raptor or any other S/390 machine) try this? Thank you very much for your time and patience. Jose -- José M. Parrella - Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela - ucvlug.info
