Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Jan Willem Stumpel
Package: xterm
Version: 6.8.2.dfsg.1-11
Severity: normal
Tags: l10n


xterm -u8 does not start xterm in UTF-8 mode, nor does specifying 
xterm*VT100*utf8: in ~/.Xresources make xterm start in UTF-8 mode by default. 

Xterm can be switched to UTF-8 manually (control-rightclick) in both cases, but 
I'd like it to be in UTF-8 mode by default. This is possible with xterm
version 200, but not with the current Sid version (202).  

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.1
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages xterm depends on:
ii  libc62.3.5-8.1   GNU C Library: Shared libraries an
ii  libexpat11.95.8-3XML parsing C library - runtime li
ii  libfontconfig1   2.3.2-1.1   generic font configuration library
ii  libfreetype6 2.1.10-1FreeType 2 font engine, shared lib
ii  libice6  6.8.2.dfsg.1-11 Inter-Client Exchange library
ii  libncurses5  5.5-1   Shared libraries for terminal hand
ii  libsm6   6.8.2.dfsg.1-11 X Window System Session Management
ii  libxaw8  6.8.2.dfsg.1-11 X Athena widget set library
ii  libxext6 6.8.2.dfsg.1-11 X Window System miscellaneous exte
ii  libxft2  2.1.7-1 FreeType-based font drawing librar
ii  libxmu6  6.8.2.dfsg.1-11 X Window System miscellaneous util
ii  libxp6   6.8.2.dfsg.1-11 X Window System printing extension
ii  libxpm4  6.8.2.dfsg.1-11 X pixmap library
ii  libxrender1  1:0.9.0-2   X Rendering Extension client libra
ii  libxt6   6.8.2.dfsg.1-11 X Toolkit Intrinsics
ii  xlibs-data   6.8.2.dfsg.1-11 X Window System client data

Versions of packages xterm recommends:
ii  xutils   6.8.2.dfsg.1-11 X Window System utility programs

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread David Martínez Moreno
El viernes, 2 de diciembre de 2005 09:56, Jan Willem Stumpel escribió:
> Package: xterm
> Version: 6.8.2.dfsg.1-11
> Severity: normal
> Tags: l10n
>
>
> xterm -u8 does not start xterm in UTF-8 mode, nor does specifying
> xterm*VT100*utf8: in ~/.Xresources make xterm start in UTF-8 mode by
> default.
>
> Xterm can be switched to UTF-8 manually (control-rightclick) in both cases,
> but I'd like it to be in UTF-8 mode by default. This is possible with xterm
> version 200, but not with the current Sid version (202).

Could you please test latest version (204-0pre1) from experimental and 
see if 
it works? It works for me (I use ISO8859-15):

[EMAIL PROTECTED]:~$ xterm -u8
xterm$ cat > /tmp/lala

^D
xterm$ exit

Then I open the file in my usual environment and it is full of UTF-8 
characters:

[EMAIL PROTECTED]:~$ cat /tmp/lele
ññññíííí

If it is the same for you, please report us, in order to close the bug 
with 
the next release.

Best regards,


Ender.
-- 
We accidentally replaced your heart with a baked potato. You have
 about three seconds to live.
-- Dr. Doctor to Kenny (South Park).
--
Desarrollador de Debian
Debian developer


pgpVEeT4M2Aao.pgp
Description: PGP signature


Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Sven Luther
On Fri, Dec 02, 2005 at 01:51:00PM +0100, David Martínez Moreno wrote:
> El viernes, 2 de diciembre de 2005 09:56, Jan Willem Stumpel escribió:
> > Package: xterm
> > Version: 6.8.2.dfsg.1-11
> > Severity: normal
> > Tags: l10n
> >
> >
> > xterm -u8 does not start xterm in UTF-8 mode, nor does specifying
> > xterm*VT100*utf8: in ~/.Xresources make xterm start in UTF-8 mode by
> > default.
> >
> > Xterm can be switched to UTF-8 manually (control-rightclick) in both cases,
> > but I'd like it to be in UTF-8 mode by default. This is possible with xterm
> > version 200, but not with the current Sid version (202).
> 
>   Could you please test latest version (204-0pre1) from experimental and 
> see if 
> it works? It works for me (I use ISO8859-15):

Notice that some locales have shifted to UTF-8 by default for etch (like
french, but i think a couple other european languages too, i saw it in
german too i think). Will xterm default to the right thing in this case ?

Friendly,

Sven Luther




Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Denis Barbier
On Fri, Dec 02, 2005 at 02:23:32PM +0100, Sven Luther wrote:
> Notice that some locales have shifted to UTF-8 by default for etch (like
> french, but i think a couple other european languages too, i saw it in
> german too i think). Will xterm default to the right thing in this case ?

I do not remember why exactly, but Branden decided to add a new wrapper
called lxterm for this purpose, instead of modifying xterm and/or
uxterm.

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Jan Willem Stumpel

David Martínez Moreno wrote:



Could you please test latest version (204-0pre1) from
experimental and see if it works? It works for me (I use
ISO8859-15):


No, it does not work. I have to set UTF-8 manually just like with
version 202. Version 200 is OK.

It it true that 204 has the binary in /usr/bin? It has always been 
in /usr/X11/bin.


Regards, Jan





Re: Modular Packaging: Font Aliases

2005-12-02 Thread David Nusinow
On Fri, Dec 02, 2005 at 08:03:16AM +0100, Sven Luther wrote:
> On Fri, Dec 02, 2005 at 12:22:50AM -0500, David Nusinow wrote:
> >Either way, we have to decide what to do with the aliases shipped by
> > upstream. Do we ship an xfonts-aliases package that includes all the
> > aliases in font/alias? Alternately, we can copy the individual font.alias
> > files installed by the upstream alias module to their individual packages.
> > Upstream has grouped them by 100dpi, 75dpi, misc, and cyrillic, which
> > matches our own previous and current package structure currently, so there
> > shouldn't be a problem. I'd just drop them in the debian dir and install
> > them. I'm leaning towards this latter solution, although I'm not sure this
> > is the correct method. Comments?
> 
> I think this seems the most sensible solution to me. Not sure if the debian
> dir is the right place, you could probably just provide a patch putting them
> in the right place and such, but it would be more work.

Yeah, that was basically my thinking. We can just drop in the updated
aliases whenever we want without having to muck around with a patch.
Granted, quilt makes it pretty easy to make a patch, but I don't want to
have to engage the system if I don't have to.

 - David Nusinow


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread David Nusinow
On Fri, Dec 02, 2005 at 02:51:58PM +0100, Jan Willem Stumpel wrote:
> It it true that 204 has the binary in /usr/bin? It has always been 
> in /usr/X11/bin.

/usr/X11R6/bin is happily going away in the Xorg 7.0 release, which we're
currently working on packaging. X will finally be FHS compliant!

 - David Nusinow


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



X Strike Force X.Org X11 SVN commit: r919 - trunk/xsfbs

2005-12-02 Thread X Strike Force SVN Repository Admin
Author: dnusinow
Date: 2005-12-02 12:43:01 -0500 (Fri, 02 Dec 2005)
New Revision: 919

Added:
   trunk/xsfbs/xsfbs.sh
Log:
Add shell-lib.sh to xsfbs and rename as xsfbs.sh

Added: trunk/xsfbs/xsfbs.sh
===
--- trunk/xsfbs/xsfbs.sh2005-12-02 05:13:08 UTC (rev 918)
+++ trunk/xsfbs/xsfbs.sh2005-12-02 17:43:01 UTC (rev 919)
@@ -0,0 +1,865 @@
+# $Id: shell-lib.sh 586 2005-09-03 18:37:47Z branden $
+
[EMAIL PROTECTED]@
[EMAIL PROTECTED]@
+
+# Use special abnormal exit codes so that problems with this library are more
+# easily tracked down.
+SHELL_LIB_INTERNAL_ERROR=86
+SHELL_LIB_THROWN_ERROR=74
+SHELL_LIB_USAGE_ERROR=99
+
+# old -> new variable names
+if [ -z "$DEBUG_XORG_PACKAGE" ] && [ -n "$DEBUG_XFREE86_PACKAGE" ]; then
+  DEBUG_XORG_PACKAGE="$DEBUG_XFREE86_PACKAGE"
+fi
+if [ -z "$DEBUG_XORG_DEBCONF" ] && [ -n "$DEBUG_XFREE86_DEBCONF" ]; then
+  DEBUG_XORG_DEBCONF="$DEBUG_XFREE86_DEBCONF"
+fi
+
+# initial sanity checks
+if [ -z "$THIS_PACKAGE" ]; then
+  cat >&2  on the World Wide Web for
+instructions, read the file /usr/share/doc/debian/bug-reporting.txt from the
+"doc-debian" package, or install the "reportbug" package and use the command of
+the same name to file a report against version $SOURCE_VERSION of this package.
+EOF
+  exit $SHELL_LIB_USAGE_ERROR
+fi
+
+if [ -z "$THIS_SCRIPT" ]; then
+  cat >&2  on the World Wide Web for
+instructions, read the file /usr/share/doc/debian/bug-reporting.txt from the
+"doc-debian" package, or install the "reportbug" package and use the command of
+the same name to file a report against version $SOURCE_VERSION of the
+"$THIS_PACKAGE" package.
+EOF
+  exit $SHELL_LIB_USAGE_ERROR
+fi
+
+trap "message;\
+  message \"Received signal.  Aborting $THIS_PACKAGE package $THIS_SCRIPT 
script.\";\
+  message;\
+  exit 1" HUP INT QUIT TERM
+
+reject_nondigits () {
+  # syntax: reject_nondigits [ operand ... ]
+  #
+  # scan operands (typically shell variables whose values cannot be trusted) 
for
+  # characters other than decimal digits and barf if any are found
+  while [ -n "$1" ]; do
+# does the operand contain anything but digits?
+if ! expr "$1" : "[[:digit:]]\+$" > /dev/null 2>&1; then
+  # can't use die(), because it wraps message() which wraps this function
+  echo "$THIS_PACKAGE $THIS_SCRIPT error: reject_nondigits() encountered" \
+   "possibly malicious garbage \"$1\"" >&2
+  exit $SHELL_LIB_THROWN_ERROR
+fi
+shift
+  done
+}
+
+reject_whitespace () {
+  # syntax: reject_whitespace [ operand ]
+  #
+  # scan operand (typically a shell variable whose value cannot be trusted) for
+  # whitespace characters and barf if any are found
+  if [ -n "$1" ]; then
+# does the operand contain any whitespace?
+if expr "$1" : "[[:space:]]" > /dev/null 2>&1; then
+  # can't use die(), because I want to avoid forward references
+  echo "$THIS_PACKAGE $THIS_SCRIPT error: reject_whitespace() encountered" 
\
+   "possibly malicious garbage \"$1\"" >&2
+  exit $SHELL_LIB_THROWN_ERROR
+fi
+  fi
+}
+
+reject_unlikely_path_chars () {
+  # syntax: reject_unlikely_path_chars [ operand ... ]
+  #
+  # scan operands (typically shell variables whose values cannot be trusted) 
for
+  # characters unlikely to be seen in a path and which the shell might
+  # interpret and barf if any are found
+  while [ -n "$1" ]; do
+# does the operand contain any funny characters?
+if expr "$1" : '.*[!$&()*;<>?|].*' > /dev/null 2>&1; then
+  # can't use die(), because I want to avoid forward references
+  echo "$THIS_PACKAGE $THIS_SCRIPT error: reject_unlikely_path_chars()" \
+   "encountered possibly malicious garbage \"$1\"" >&2
+  exit $SHELL_LIB_THROWN_ERROR
+fi
+shift
+  done
+}
+
+# Query the terminal to establish a default number of columns to use for
+# displaying messages to the user.  This is used only as a fallback in the
+# event the COLUMNS variable is not set.  ($COLUMNS can react to SIGWINCH while
+# the script is running, and this cannot, only being calculated once.)
+DEFCOLUMNS=$(stty size 2> /dev/null | awk '{print $2}') || true
+if ! expr "$DEFCOLUMNS" : "[[:digit:]]\+$" > /dev/null 2>&1; then
+  DEFCOLUMNS=80
+fi
+
+message () {
+  # pretty-print messages of arbitrary length
+  reject_nondigits "$COLUMNS"
+  echo "$*" | fmt -t -w ${COLUMNS:-$DEFCOLUMNS} >&2
+}
+
+observe () {
+  # syntax: observe message ...
+  #
+  # issue observational message suitable for logging someday when support for
+  # it exists in dpkg
+  if [ -n "$DEBUG_XORG_PACKAGE" ]; then
+message "$THIS_PACKAGE $THIS_SCRIPT note: $*"
+  fi
+}
+
+warn () {
+  # syntax: warn message ...
+  #
+  # issue warning message suitable for logging someday when support for
+  # it exists in dpkg; also send to standard error
+  message "$THIS_PACKAGE $THIS_SCRIPT warni

X Strike Force X.Org X11 SVN commit: r920 - trunk/xsfbs

2005-12-02 Thread X Strike Force SVN Repository Admin
Author: dnusinow
Date: 2005-12-02 13:14:03 -0500 (Fri, 02 Dec 2005)
New Revision: 920

Modified:
   trunk/xsfbs/xsfbs.mk
Log:
Add genscripts target so we can process the xsfbs shell lib

Modified: trunk/xsfbs/xsfbs.mk
===
--- trunk/xsfbs/xsfbs.mk2005-12-02 17:43:01 UTC (rev 919)
+++ trunk/xsfbs/xsfbs.mk2005-12-02 18:14:03 UTC (rev 920)
@@ -304,4 +304,41 @@
  echo "done."; \
fi
 
+# Generate the maintainer scripts.
+.PHONY: genscripts
+stampdir_targets+=genscripts
+genscripts: $(STAMP_DIR)/genscripts
+$(STAMP_DIR)/genscripts: $(STAMP_DIR)/stampdir
+   for FILE in debian/*.config.in \
+   debian/*.postinst.in \
+   debian/*.postrm.in \
+   debian/*.preinst.in \
+   debian/*.prerm.in; do \
+ if [ -e "$$FILE" ]; then \
+   MAINTSCRIPT=$$(echo $$FILE | sed 's/.in$$//'); \
+   sed -n '1,/^#INCLUDE_SHELL_LIB#$$/p' <$$FILE \
+ | sed -e '/^#INCLUDE_SHELL_LIB#$$/d' >$$MAINTSCRIPT.tmp; \
+   cat debian/shell-lib.sh >>$$MAINTSCRIPT.tmp; \
+   sed -n '/^#INCLUDE_SHELL_LIB#$$/,$$p' <$$FILE \
+ | sed -e '/^#INCLUDE_SHELL_LIB#$$/d' >>$$MAINTSCRIPT.tmp; \
+   sed -e 's/@SOURCE_VERSION@/$(SOURCE_VERSION)/' \
+   -e 's/@OFFICIAL_BUILD@/$(OFFICIAL_BUILD)/' \
+   -e 's/@DEFAULT_DCRESOLUTIONS@/$(DEFAULT_DCRESOLUTIONS)/' \
+ <$$MAINTSCRIPT.tmp >$$MAINTSCRIPT; \
+   rm $$MAINTSCRIPT.tmp; \
+ fi; \
+   done
+   done
+   # Validate syntax of generated shell scripts.
+   sh debian/scripts/validate-posix-sh debian/*.config \
+   debian/*.postinst \
+   debian/*.postrm \
+   debian/*.preinst \
+   debian/*.prerm
+   >$@
+
+# Generate the shlibs.local file.
+debian/shlibs.local:
+   cat debian/*.shlibs >$@
+
 # vim:set noet ai sts=8 sw=8 tw=0:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



X Strike Force X.Org X11 SVN commit: r921 - trunk/xsfbs

2005-12-02 Thread X Strike Force SVN Repository Admin
Author: dnusinow
Date: 2005-12-02 13:26:22 -0500 (Fri, 02 Dec 2005)
New Revision: 921

Modified:
   trunk/xsfbs/xsfbs.mk
Log:
Make prepare target depend on genscripts target

Modified: trunk/xsfbs/xsfbs.mk
===
--- trunk/xsfbs/xsfbs.mk2005-12-02 18:14:03 UTC (rev 920)
+++ trunk/xsfbs/xsfbs.mk2005-12-02 18:26:22 UTC (rev 921)
@@ -117,7 +117,7 @@
 # Set up the package build directory as quilt expects to find it.
 .PHONY: prepare
 stampdir_targets+=prepare
-prepare: $(STAMP_DIR)/prepare $(STAMP_DIR)/patches $(STAMP_DIR)/log
+prepare: $(STAMP_DIR)/genscripts $(STAMP_DIR)/prepare $(STAMP_DIR)/patches 
$(STAMP_DIR)/log
 $(STAMP_DIR)/prepare: $(STAMP_DIR)/stampdir
if [ ! -e $(STAMP_DIR)/patches ]; then \
mkdir $(STAMP_DIR)/patches; \


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



X Strike Force X.Org X11 SVN commit: r922 - trunk/xsfbs

2005-12-02 Thread X Strike Force SVN Repository Admin
Author: dnusinow
Date: 2005-12-02 14:23:28 -0500 (Fri, 02 Dec 2005)
New Revision: 922

Modified:
   trunk/xsfbs/xsfbs.mk
Log:
Make genscripts target use re-named shell-lib.sh (xsfbs.sh)

Modified: trunk/xsfbs/xsfbs.mk
===
--- trunk/xsfbs/xsfbs.mk2005-12-02 18:26:22 UTC (rev 921)
+++ trunk/xsfbs/xsfbs.mk2005-12-02 19:23:28 UTC (rev 922)
@@ -318,7 +318,7 @@
MAINTSCRIPT=$$(echo $$FILE | sed 's/.in$$//'); \
sed -n '1,/^#INCLUDE_SHELL_LIB#$$/p' <$$FILE \
  | sed -e '/^#INCLUDE_SHELL_LIB#$$/d' >$$MAINTSCRIPT.tmp; \
-   cat debian/shell-lib.sh >>$$MAINTSCRIPT.tmp; \
+   cat debian/xsfbs/xsfbs.sh >>$$MAINTSCRIPT.tmp; \
sed -n '/^#INCLUDE_SHELL_LIB#$$/,$$p' <$$FILE \
  | sed -e '/^#INCLUDE_SHELL_LIB#$$/d' >>$$MAINTSCRIPT.tmp; \
sed -e 's/@SOURCE_VERSION@/$(SOURCE_VERSION)/' \


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Processed: email change

2005-12-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> submitter 205956 !
Bug#205956: xml-resume-library: Wrong name for jar file
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 24239 !
Bug#24239: xbase-clients: [xsm] fails to reload twm
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 31581 !
Bug#31581: project: Time between releases is too long
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 53504 !
Bug#53504: modutils: autoclean modules aren't being cleaned
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 147474 !
Bug#147474: mawk: crash due to infinite recursion
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 232730 !
Bug#232730: ftp.debian.org: orig tarball not moved when changing from contrib 
to main
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 252366 !
Bug#252366: konsole: fds not closed before execing shell
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 253885 !
Bug#253885: /usr/bin/gs-gpl: gs crashes rendering some PDF files to x11alpha 
device
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 60763 !
Bug#60763: Strange changelog.Debian: version doesn't match package version
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 217568 !
Bug#217568: /usr/bin/nm: nm --demangle does not demangle versioned symbols
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 47255 !
Bug#47255: [INSTALL-INFO] install-info: duplicates and out-of-order entries
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 33994 !
Bug#33994: [DSELECT] clears screen on 'fg' if apt method suspended
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 32489 !
Bug#32489: dselect should pause after remove or config
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 49627 !
Bug#49627: apt: Cannot -s as non-root
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 58480 !
Bug#58480: installing midentd with pidentd installed didn't change default 
identd
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 59425 !
Bug#59425: [INSTALL-INFO] install-info: don't modify info/dir directly, use 
alternate data storage
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 60116 !
Bug#60116: cvs has irritating behavior on lost network links
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 95766 !
Bug#95766: Please add --gigabytes
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 96596 !
Bug#96596: demangle doesn't work with gcc-3.0
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 97045 !
Bug#97045: could report package versions too
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 99324 !
Bug#99324: Default charset should be UTF-8
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 108451 !
Bug#108451: xserver-xfree86: [core server] want automatic backtrace on crash
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 130325 !
Bug#130325: www.debian.org: favicon missing in some domains
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 240713 !
Bug#240713: [merged] provide badblocks check
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter 261512 !
Bug#261512: partitioner does not allow setting of unknown to it mount options
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar 
Eduardo Barros <[EMAIL PROTECTED]>.

> submitter

Bug#336997: xlibmesa-dri: having issues with driver not claiming to support visuals

2005-12-02 Thread David Mulcahy
Just for the record I was having similar problems see
http://lists.debian.org/debian-x/2005/08/msg00235.html
but after upgrading to partially unstable and experimental, the libgl warnings 
have disappeared but I cannot get direct rendering to work.  Is this fixed in 
experimental and if so how does one completely upgrade all X packages using 
aptitude just to make sure.

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Thomas Dickey
On Fri, Dec 02, 2005 at 03:10:11PM +0100, Denis Barbier wrote:
> On Fri, Dec 02, 2005 at 02:23:32PM +0100, Sven Luther wrote:
> > Notice that some locales have shifted to UTF-8 by default for etch (like
> > french, but i think a couple other european languages too, i saw it in
> > german too i think). Will xterm default to the right thing in this case ?
> 
> I do not remember why exactly, but Branden decided to add a new wrapper
> called lxterm for this purpose, instead of modifying xterm and/or
> uxterm.

The reason was that it would have changed uxterm incompatibly,
to solve a problem that could be done outside it.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpJvaaMOpi6w.pgp
Description: PGP signature


Bug#341686: xterm cannot be started in utf-8 mode by default

2005-12-02 Thread Thomas Dickey
On Fri, Dec 02, 2005 at 03:10:10PM +0100, Jan Willem Stumpel wrote:
> David Mart??nez Moreno wrote:
> 
> >
> >Could you please test latest version (204-0pre1) from
> >experimental and see if it works? It works for me (I use
> >ISO8859-15):
> 
> No, it does not work. I have to set UTF-8 manually just like with
> version 202. Version 200 is OK.

I already responded to this in

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318923

also see the manpage:

   -u8 This  option  sets  the utf8 resource.  When utf8 is set, xterm
   interprets incoming data as UTF-8.   This  sets  the  wideChars
   resource  as  a  side-effect,  but  the  UTF-8 mode set by this
   option prevents it from being turned off.  If you must turn  it
   on and off, use the wideChars resource.
 
   This option and the utf8 resource are overridden by the -lc and
   -en options and locale resource.  That is, if  xterm  has  been
   compiled  to  support  luit,  and  the  locale  resource is not
   ``false'' this option is ignored.  We recommend using  the  -lc
   option  or  the ``locale: true'' resource in UTF-8 locales when
   your operating system supports locale, or -en UTF-8  option  or
   the  ``locale: UTF-8'' resource when your operating system does
   not support locale.

The default value for the locale resource is ``medium''.  If you set it to
``false'', the -u8 option will work as you want.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpHO3zOPFa8a.pgp
Description: PGP signature


Re: [Flightgear-devel] compile problem with plib

2005-12-02 Thread Josh Babcock
Curtis L. Olson wrote:
> The very first thing I would check is the contents of the config.log
> file.  That shows the details of the test and the compiler error
> signaling a failure.  That often can be quite helpful.
> 
> Curt.
> 
> 
> Josh Babcock wrote:
> 
>> I can't figure out why this is happening. If anyone has any ideas,
>> please let me know. To me it seems that I have everything I need in all
>> the right places. Here's the situation:
>>


OK,
looks like debian is broken. There was no link from libXmu.so to
libXmu.so.6 in /usr/X11R6/lib.
Thanks for the tip.

For you Debian guys:
Package Installed   PreviousNow
State
===-===-===-===-=
libxmu6 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11
install

Josh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#339308: uxterm - invalid pointer warning during startup

2005-12-02 Thread Thomas Dickey
On Tue, Nov 15, 2005 at 02:24:57PM +0100, Julien Cristau wrote:
> On Tue, Nov 15, 2005 at 08:14:58 +, Thomas Dickey wrote:
> 
> > of course uxterm is a script.  When I've run valgrind recently, I see a
> > lot of problems in glibc (that definitely aren't caused by xterm).  I'm
> > inclined to recommend that this be redirected to glibc.
> > 
> > (The dependencies don't list the version of glibc - the bug-reporting
> > tool should).
> > 
> The dependencies /do/ list the version of glibc:
> Versions of packages xterm depends on:
> ii  libc6 2.3.5-6GNU C Library: Shared libraries 
> an
> 
> This is the version which is currently in testing, sid has 2.3.5-8.

I can't reproduce the problem.  But I see that I'm running a later libc6.
I set my $PATH and locale to match the report, and uxterm comes up without
any messages.

Here's the relevant version information:

ii  xterm 6.8.2.dfsg.1-7   X terminal emulator
ii  libc6 2.3.5-8  GNU C Library: 
Shared libraries and Timezone

-- 
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature


Re: [Flightgear-devel] compile problem with plib

2005-12-02 Thread Russ Allbery
Josh Babcock <[EMAIL PROTECTED]> writes:

> OK,
> looks like debian is broken. There was no link from libXmu.so to
> libXmu.so.6 in /usr/X11R6/lib.
> Thanks for the tip.

This link is only needed for building software and as such is part of the
-dev package, not the library package.  You want to install libxmu-dev.

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: compile problem with plib

2005-12-02 Thread Alex Romosan
Josh Babcock writes:

> looks like debian is broken. There was no link from libXmu.so to
> libXmu.so.6 in /usr/X11R6/lib.
> Thanks for the tip.
>
> For you Debian guys:
> Package Installed   PreviousNow
> State
> ===-===-===-===-=
> libxmu6 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11
> install

you need to install the development packages as well. in this case you
need libxmu-dev but it's probably better to install xlibs-dev which
will pull in all the relevant packages.

--alex--

-- 
| I believe the moment is at hand when, by a paranoiac and active |
|  advance of the mind, it will be possible (simultaneously with  |
|  automatism and other passive states) to systematize confusion  |
|  and thus to help to discredit completely the world of reality. |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: [Flightgear-devel] compile problem with plib

2005-12-02 Thread Daniel Stone
On Fri, Dec 02, 2005 at 07:59:34PM -0500, Josh Babcock wrote:
> looks like debian is broken. There was no link from libXmu.so to
> libXmu.so.6 in /usr/X11R6/lib.
> Thanks for the tip.
> 
> For you Debian guys:
> Package Installed   PreviousNow
> State
> ===-===-===-===-=
> libxmu6 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11 6.8.2.dfsg.1-11
> install

You need libxmu-dev installed to compile stuff with it.


signature.asc
Description: Digital signature


Re: NOTICE: a file you sent was removed

2005-12-02 Thread gabrieality
no it wasnt a file i sent it was one i was supposed to receive
frommaildata/quarentine1 virus-2004 0727-1359331625002 courtasey of
[EMAIL PROTECTED] the worm can you look into this matter and can you tell me 
where
its origins lay yours gabrielle , hence [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]