Processed: tagging 208137
Processing commands for [EMAIL PROTECTED]: > # fixed in XSF XFree86 SVN revision 703 > tag 208137 + pending Bug#208137: xlibs-data: Compatibility with libc 2.3.2 Tags were: patch upstream Bug#200933: xlibs-data: /usr/X11R6/lib/X11/locale/locale.alias does not contain all canonical locales Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 208137, reassign 208137 to xlibs
Processing commands for [EMAIL PROTECTED]: > tag 208137 - experimental Bug#208137: xlibs-data: Compatibility with libc 2.3.2 Tags were: experimental help patch upstream Bug#200933: xlibs-data: /usr/X11R6/lib/X11/locale/locale.alias does not contain all canonical locales Tags removed: experimental > tag 208137 - help Bug#208137: xlibs-data: Compatibility with libc 2.3.2 Tags were: help patch upstream Bug#200933: xlibs-data: /usr/X11R6/lib/X11/locale/locale.alias does not contain all canonical locales Tags removed: help > reassign 208137 xlibs Bug#208137: xlibs-data: Compatibility with libc 2.3.2 Bug#200933: xlibs-data: /usr/X11R6/lib/X11/locale/locale.alias does not contain all canonical locales Bug reassigned from package `xlibs-data' to `xlibs'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
On Thu, Oct 23, 2003 at 09:03:48AM +0900, Tomohiro KUBOTA wrote: [...] > On app-defaults files: why peoples speaking some languages are > forced to modify app-default files while others don't need to do? [...] Please describe a simple scenario where changing default fonts is helpful. I do not understand why you discussed those UTF-8 issues, they does not seem related to the problems you want to solve. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X Strike Force XFree86 SVN commit: rev 703 - in trunk/debian: . patches
Author: branden Date: 2003-10-23 00:51:49 -0500 (Thu, 23 Oct 2003) New Revision: 703 Added: trunk/debian/patches/011a_recognize_euro_modifier_locales.diff Modified: trunk/debian/changelog Log: Add aliases to upstream locales.alias file for many locales using the "@euro" modifier and the ISO-8859-15 or UTF-8 character sets (thanks, Jean-Christophe Dubacq and Denis Barbier). (Closes: #208137) - debian/patches/011a_recognize_euro_modifier_locales.diff: new Modified: trunk/debian/changelog === --- trunk/debian/changelog 2003-10-23 05:10:41 UTC (rev 702) +++ trunk/debian/changelog 2003-10-23 05:51:49 UTC (rev 703) @@ -188,8 +188,13 @@ - debian/xdm.postinst.in - debian/xdm.prerm.in - -- Branden Robinson <[EMAIL PROTECTED]> Thu, 23 Oct 2003 00:04:45 -0500 + * Add aliases to upstream locales.alias file for many locales using the +"@euro" modifier and the ISO-8859-15 or UTF-8 character sets (thanks, +Jean-Christophe Dubacq and Denis Barbier). (Closes: #208137) +- debian/patches/011a_recognize_euro_modifier_locales.diff: new + -- Branden Robinson <[EMAIL PROTECTED]> Thu, 23 Oct 2003 00:45:38 -0500 + xfree86 (4.2.1-12.1) unstable; urgency=low * Fix typo in xlibs preinst. Closes: #213774, #213776 Added: trunk/debian/patches/011a_recognize_euro_modifier_locales.diff === --- trunk/debian/patches/011a_recognize_euro_modifier_locales.diff 2003-10-23 05:10:41 UTC (rev 702) +++ trunk/debian/patches/011a_recognize_euro_modifier_locales.diff 2003-10-23 05:51:49 UTC (rev 703) @@ -0,0 +1,57 @@ +$Id$ + +Add a bunch of aliases to support locale settings that use the "@euro" +modifier. From Debian bug report #208137. + +Not submitted upstream yet. + +--- xc/nls/locale.alias~ 2003-10-23 00:19:45.0 -0500 xc/nls/locale.alias2003-10-23 00:25:15.0 -0500 +@@ -838,3 +838,47 @@ + japan:ja_JP.U90 + #endif + Japanese-EUC: ja_JP.eucJP ++# additions for GNU C library 2.3.2 compatibility [EMAIL PROTECTED]: br_FR.ISO8859-15 [EMAIL PROTECTED]: ca_ES.ISO8859-15 [EMAIL PROTECTED]: ca_ES.UTF-8 [EMAIL PROTECTED]: de_AT.ISO8859-15 [EMAIL PROTECTED]: de_AT.UTF-8 [EMAIL PROTECTED]: de_BE.ISO8859-15 [EMAIL PROTECTED]: de_BE.UTF-8 [EMAIL PROTECTED]: de_DE.ISO8859-15 [EMAIL PROTECTED]: de_DE.UTF-8 [EMAIL PROTECTED]: de_LU.ISO8859-15 [EMAIL PROTECTED]: de_LU.UTF-8 [EMAIL PROTECTED]: el_GR.ISO8859-15 [EMAIL PROTECTED]: en_IE.ISO8859-15 [EMAIL PROTECTED]: en_IE.UTF-8 [EMAIL PROTECTED]: es_ES.ISO8859-15 [EMAIL PROTECTED]: es_ES.UTF-8 [EMAIL PROTECTED]: eu_ES.ISO8859-15 [EMAIL PROTECTED]: eu_ES.UTF-8 [EMAIL PROTECTED]: fi_FI.ISO8859-15 [EMAIL PROTECTED]: fi_FI.UTF-8 [EMAIL PROTECTED]: fr_BE.ISO8859-15 [EMAIL PROTECTED]: fr_BE.UTF-8 [EMAIL PROTECTED]: fr_FR.ISO8859-15 [EMAIL PROTECTED]: fr_FR.UTF-8 [EMAIL PROTECTED]: fr_LU.ISO8859-15 [EMAIL PROTECTED]: fr_LU.UTF-8 [EMAIL PROTECTED]: ga_IE.ISO8859-15 [EMAIL PROTECTED]: ga_IE.UTF-8 [EMAIL PROTECTED]: gl_ES.ISO8859-15 [EMAIL PROTECTED]: gl_ES.UTF-8 [EMAIL PROTECTED]: it_IT.ISO8859-15 [EMAIL PROTECTED]: it_IT.UTF-8 [EMAIL PROTECTED]: nl_BE.ISO8859-15 [EMAIL PROTECTED]: nl_BE.UTF-8 [EMAIL PROTECTED]: nl_NL.ISO8859-15 [EMAIL PROTECTED]: nl_NL.UTF-8 [EMAIL PROTECTED]: oc_FR.ISO8859-15 [EMAIL PROTECTED]: pt_PT.ISO8859-15 [EMAIL PROTECTED]: pt_PT.UTF-8 [EMAIL PROTECTED]: sv_FI.ISO8859-15 [EMAIL PROTECTED]: sv_FI.UTF-8 [EMAIL PROTECTED]: sv_SE.ISO8859-15 [EMAIL PROTECTED]: wa_BE.ISO8859-15 Property changes on: trunk/debian/patches/011a_recognize_euro_modifier_locales.diff ___
Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Hi, From: Branden Robinson <[EMAIL PROTECTED]> Subject: Re: Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n Date: Wed, 22 Oct 2003 22:11:56 -0500 > You are presenting me with an ultimatum: accept your patch or else. You > do not appear to feel there are any grounds upon which you will change > your mind. This is not a sound basis for a rational discussion. Please discuss. It is you who avoid discussion. How do you think about the concept of locale? Please discuss with the technical points. Why do you avoid concrete discussion? It is easy. Please explain why my idea is inferior than yours rationally. If you really think so, you can do it. Can't you? Please explain why requiring editing app-defaults is better than automatic locale detection, why uxterm approach is better than locale, and so on. If you have a good reason which I didn't think about, I will agree with closing this bug. > Neither are your assertions that I "must" remove features from XTerm > simple because I have made observations about its historical > development. You'd get along famously with Eduard Bloch, who argues the > same way. Well, what is your intention you explained xterm's "historical development"? I felt that you wanted to explain the reason why xterm must not support multibyte encodings (because VT100 and so on doesn't support it). Am I right? Then, from the exactly same reason, you must remove features which VT100 and so on doesn't have and xterm has. Of course I don't agree such an explanation and I don't think you must remove such features. I don't know Eduard Bloch. > This bug will be fixed when upstream fixes it, or when a patch that > upstream is comfortable with is submitted. Please discuss on the concrete problems, though I am now discussing with the upstream. Anyway, the patch is completely different from the patch I sent to the upstream. How many times should I say this? > Tagging "wontfix". It is acceptable because there are chance for discussion or we can refer the bug, but don't close. We must not hide problems. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X Strike Force XFree86 SVN commit: rev 702 - trunk/debian
Author: branden Date: 2003-10-23 00:10:41 -0500 (Thu, 23 Oct 2003) New Revision: 702 Modified: trunk/debian/changelog trunk/debian/xdm.postinst.in trunk/debian/xdm.prerm.in Log: Fix xdm to handle case where alternative X display managers do not provide a "daemon_name" debconf template (which is supposed to contain the file specification of the display manager daemon). If that is true, assume that the package name of the display manager is also the name of the daemon executable, and try to find it with the "which" command. If that fails as well, warn the user that we were unable to update the default X display manager file. - debian/xdm.postinst.in - debian/xdm.prerm.in Modified: trunk/debian/changelog === --- trunk/debian/changelog 2003-10-23 04:44:36 UTC (rev 701) +++ trunk/debian/changelog 2003-10-23 05:10:41 UTC (rev 702) @@ -118,7 +118,7 @@ - debian/xbase-clients.postinst.in - debian/xdm.postinst.in - debian/xdm.postrm.in -- debian/xdm.preint.in +- debian/xdm.preinst.in - debian/xdm.prerm.in - debian/xfs.preinst.in - debian/xfree86-common.config.in @@ -178,8 +178,18 @@ (partially addresses #207537) - debian/xserver-xfree86.config.in - -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 23:39:27 -0500 + * Fix xdm to handle case where alternative X display managers do not provide +a "daemon_name" debconf template (which is supposed to contain the file +specification of the display manager daemon). If that is true, assume +that the package name of the display manager is also the name of the +daemon executable, and try to find it with the "which" command. If that +fails as well, warn the user that we were unable to update the default X +display manager file. +- debian/xdm.postinst.in +- debian/xdm.prerm.in + -- Branden Robinson <[EMAIL PROTECTED]> Thu, 23 Oct 2003 00:04:45 -0500 + xfree86 (4.2.1-12.1) unstable; urgency=low * Fix typo in xlibs preinst. Closes: #213774, #213776 Modified: trunk/debian/xdm.postinst.in === --- trunk/debian/xdm.postinst.in2003-10-23 04:44:36 UTC (rev 701) +++ trunk/debian/xdm.postinst.in2003-10-23 05:10:41 UTC (rev 702) @@ -35,11 +35,24 @@ DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager if [ ! -e "$DEFAULT_DISPLAY_MANAGER_FILE" ]; then safe_debconf db_get shared/default-x-display-manager - if [ -n "$RET" ]; then -safe_debconf db_get "$RET"/daemon_name -if [ -n "$RET" ]; then - echo "$RET" > "$DEFAULT_DISPLAY_MANAGER_FILE" + DEFAULT_DISPLAY_MANAGER="$RET" + if [ -n "$DEFAULT_DISPLAY_MANAGER" ]; then +safe_debconf db_get "$DEFAULT_DISPLAY_MANAGER"/daemon_name +DAEMON_NAME="$RET" +if [ ! -n "$DAEMON_NAME" ]; then + # if we were unable to determine the name of the selected daemon (for + # instance, if the selected default display manager doesn't provide a + # daemon_name question), guess + DAEMON_NAME=$(which "$DEFAULT_DISPLAY_MANAGER" 2>/dev/null) + if [ ! -n "$DAEMON_NAME" ]; then +warn "unable to determine path to default X display manager" \ + "$DEFAULT_DISPLAY_MANAGER; not updating" \ + "$DEFAULT_DISPLAY_MANAGER_FILE" + fi fi +if [ -n "$DAEMON_NAME" ]; then + echo "$DAEMON_NAME" > "$DEFAULT_DISPLAY_MANAGER_FILE" +fi fi fi Modified: trunk/debian/xdm.prerm.in === --- trunk/debian/xdm.prerm.in 2003-10-23 04:44:36 UTC (rev 701) +++ trunk/debian/xdm.prerm.in 2003-10-23 05:10:41 UTC (rev 702) @@ -92,11 +92,12 @@ safe_debconf db_metaget shared/default-x-display-manager owners safe_debconf db_subst shared/default-x-display-manager choices "$RET" safe_debconf db_get shared/default-x-display-manager + DEFAULT_DISPLAY_MANAGER="$RET" # are we removing the currently selected display manager? - if [ -n "$RET" ]; then -if [ "$THIS_PACKAGE" = "$RET" ]; then + if [ -n "$DEFAULT_DISPLAY_MANAGER" ]; then +if [ "$THIS_PACKAGE" = "$DEFAULT_DISPLAY_MANAGER" ]; then if [ -e "$DEFAULT_DISPLAY_MANAGER_FILE" ]; then -safe_debconf db_get "$RET/daemon_name" +safe_debconf db_get "$DEFAULT_DISPLAY_MANAGER/daemon_name" # does the display manager file reference the current default? if # so, remove it because it will now be wrong if [ -n "$RET" ]; then @@ -109,18 +110,31 @@ safe_debconf db_fset shared/default-x-display-manager seen false safe_debconf db_input critical shared/default-x-display-manager safe_debconf db_go - # if the display manager file doesn't exist, write it with the path - # to the new default display manager + # if the default display man
Bug#207537: xserver-xfree86: autodetection is not used
retitle 207537 xserver-xfree86: want way to re-do autodetection within config script
after initial install
severity 207537 wishlist
thanks
On Wed, Aug 27, 2003 at 08:37:08PM +0200, Goswin Brederlow wrote:
> You only ever run the autodetection on an initial install. What you
> fail to see is that people upgrading or reconfiguring might still want
> to use this method.
No, I'm aware of it, but it's difficult to implement.
> It would also be good to keep the previous selected values of any
> questions as default (thats rather a must) and to mark the probed
> values (or mention them in the text) for reference.
That's complicated to implement with current debconf technology.
> You might noticed that autodetecting the mouse fails and loops. I
> selected yes a few time for good measure. After failing it could move
> on.
I don't see what the harm is in letting people try as many times as they
want.
> I also saw a lot of questions apearing as medium in the log which I
> should have never been asked. From the logs it looks like debconf is
> to blame. I can't find a bug in auto_answere that would explain it.
> The log says medium and debconf is configured to critical.
>
>
> But you have some priority bugs in the script too:
>
> ${PRIORITY_CEILING:-$PRIORITY}
> Thats raising the priority of some questions rather than lowering it
> (e.g. cases where PRIORITY would be low otherwise).
> ${PRIORITY_CEILING:-low} => raises
> ${PRIORITY_CEILING:-medium} => pointless with ceiling to medium
> ${PRIORITY_CEILING:-high}=> lowers (which was the idea of it, right)
>
> A little functions picking the lower of $PRIORITY_CEILING and its
> argument might be better suited.
>
> There you go. Happy fixing.
Yes, I've written one and it's been committed to the X Strike Force
XFree86 SVN repository in revision 701. That issue will be fixed in the
next release.
As it's the only issue you raised which I consider a flaw, I'm
downgrading the severity of this bug and narrowing its scope.
--
G. Branden Robinson| "Why do we have to hide from the
Debian GNU/Linux | police, Daddy?"
[EMAIL PROTECTED] | "Because we use vi, son. They use
http://people.debian.org/~branden/ | emacs."
signature.asc
Description: Digital signature
Processed: Re: Bug#207537: xserver-xfree86: autodetection is not used
Processing commands for [EMAIL PROTECTED]: > retitle 207537 xserver-xfree86: want way to re-do autodetection within config script > after initial install Bug#207537: xserver-xfree86: want way to override configured debconf values with autodetected ones Changed Bug title. > severity 207537 wishlist Bug#207537: xserver-xfree86: want way to re-do autodetection within config script after initial install Severity set to `wishlist'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X Strike Force XFree86 SVN commit: rev 701 - trunk/debian
Author: branden
Date: 2003-10-22 23:44:36 -0500 (Wed, 22 Oct 2003)
New Revision: 701
Modified:
trunk/debian/changelog
trunk/debian/xserver-xfree86.config.in
Log:
Fix "priority ceiling" logic introduced in xserver-xfree86's config script
in 4.2.1-10. We can't just use shell parameter expansion tricks to
accomplish this. Implemented new function priority_ceil() which compares
its argument, a debconf priority string, to the shell variable
PRIORITY_CEILING, another debconf priority string, and returns the lesser
of the two. Thanks to Goswin Brederlow for identifying the precise cause
of debconf question priority inflation of late.
(partially addresses #207537)
- debian/xserver-xfree86.config.in
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2003-10-23 04:04:38 UTC (rev 700)
+++ trunk/debian/changelog 2003-10-23 04:44:36 UTC (rev 701)
@@ -168,8 +168,18 @@
- debian/xserver-common.preinst.in
- debian/xserver-xfree86.preinst.in
- -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 22:55:43 -0500
+ * Fix "priority ceiling" logic introduced in xserver-xfree86's config script
+in 4.2.1-10. We can't just use shell parameter expansion tricks to
+accomplish this. Implemented new function priority_ceil() which compares
+its argument, a debconf priority string, to the shell variable
+PRIORITY_CEILING, another debconf priority string, and returns the lesser
+of the two. Thanks to Goswin Brederlow for identifying the precise cause
+of debconf question priority inflation of late.
+(partially addresses #207537)
+- debian/xserver-xfree86.config.in
+ -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 23:39:27 -0500
+
xfree86 (4.2.1-12.1) unstable; urgency=low
* Fix typo in xlibs preinst. Closes: #213774, #213776
Modified: trunk/debian/xserver-xfree86.config.in
===
--- trunk/debian/xserver-xfree86.config.in 2003-10-23 04:04:38 UTC (rev 700)
+++ trunk/debian/xserver-xfree86.config.in 2003-10-23 04:44:36 UTC (rev 701)
@@ -272,6 +272,75 @@
debug_echo "auto_answer: $TEMPLATE is \"$RET\""
}
+priority_ceil() {
+ # syntax: priority_ceil requested_priority
+ #
+ # Given a variable PRIORITY_CEILING and a "requested_priority" argument, echo
+ # a debconf priority string corresponding to the lesser of the two.
+
+ # Implementation note: a clever version of this could be done using "eval",
+ # or embedding a Perl script, but those would be more difficult to maintain.
+ # Better just to go the simple and stupid route. Yes, I know this is not
+ # very efficient.
+
+ local requested_priority
+
+ # Validate arguments.
+ if [ $# -ne 1 ]; then
+debug_echo "priority_ceil() called with empty or bogus arguments \"$*\";" \
+ "assuming argument of \"low\""
+requested_priority=low
+ else
+requested_priority="$1"
+ fi
+
+ # Ensure the value of PRIORITY_CEILING is reasonable.
+ if [ "$PRIORITY_CEILING" != "critical" \
+ -a "$PRIORITY_CEILING" != "high" \
+ -a "$PRIORITY_CEILING" != "medium" \
+ -a "$PRIORITY_CEILING" != "low" ]; then
+debug_echo "priority_ceil() called with empty or bogus value of" \
+ "\$PRIORITY_CEILING \"$PRIORITY_CEILING\"; setting to \"low\""
+PRIORITY_CEILING=low
+ fi
+
+ case "$requested_priority" in
+critical)
+ # This is the highest priority, so there is nowhere to go but down.
+ echo "$PRIORITY_CEILING"
+ ;;
+high)
+ case "$PRIORITY_CEILING" in
+critical)
+ echo "$requested_priority"
+ ;;
+high|medium|low)
+ echo "$PRIORITY_CEILING"
+ ;;
+ esac
+ ;;
+medium)
+ case "$PRIORITY_CEILING" in
+critical|high)
+ echo "$requested_priority"
+ ;;
+medium|low)
+ echo "$PRIORITY_CEILING"
+ ;;
+ esac
+ ;;
+low)
+ # This is the lowest priority, so we can't go any lower.
+ echo "$requested_priority"
+ ;;
+*)
+ debug_echo "priority_ceil() called with bogus argument" \
+ "\"$requested_priority\"; returning \"low\""
+ echo low
+ ;;
+ esac
+}
+
# analyze arguments; used by auto_answer()
if [ "$1" = "reconfigure" -o -n "$2" ]; then
# if we are reconfiguring, or already have installed the package at least
@@ -376,14 +445,14 @@
# if configuring for the first time, ask if user wants to autodetect
if [ -z "$RECONFIGURE" ]; then
if which discover > /dev/null 2>&1; then
-auto_answer db_input "${PRIORITY_CEILING:-medium}"
xserver-xfree86/autodetect_video_card "false"
+auto_answer db_input "$(priority_ceil medium)"
xserver-xfree86/autodetect_video_card "false"
db_get xserver-xfree86/autodetect_video_card
AUTODETECT_VIDEO_CARD="$RET"
if [ "$AUTODETECT_VIDEO_CARD" = "true" ]; th
X Strike Force XFree86 SVN commit: rev 700 - trunk/debian
Author: branden
Date: 2003-10-22 23:04:38 -0500 (Wed, 22 Oct 2003)
New Revision: 700
Modified:
trunk/debian/changelog
trunk/debian/xserver-common.preinst.in
trunk/debian/xserver-xfree86.preinst.in
Log:
Fix migration of configuration files from "debconf-managed" to
conffile-style management, in that the Xwrapper.config and XF86Config-4
files were marked as locally changed even if there were no changes outside
the "debconf markers". Detect this case by searching for lines outside
that range which contain anything other than whitespace or comments, and
if none are found, treat the config file as handled by the package
("automatic update mode"). This should eliminate some overly aggressive
migrations to manual update mode, though people who made changes only
within the debconf markers and didn't follow instructions may still be
incorrectly placed in automatic mode (that's why copies of the old config
files are made when migration is done). Thanks to John R. Daily for
bringing this scenario to my attention. (Closes: #214604)
- debian/xserver-common.preinst.in
- debian/xserver-xfree86.preinst.in
Modified: trunk/debian/changelog
===
--- trunk/debian/changelog 2003-10-23 03:40:42 UTC (rev 699)
+++ trunk/debian/changelog 2003-10-23 04:04:38 UTC (rev 700)
@@ -153,8 +153,23 @@
abnormally?
- debian/local/FAQ
- -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 15:21:34 -0500
+ * Fix migration of configuration files from "debconf-managed" to
+conffile-style management, in that the Xwrapper.config and XF86Config-4
+files were marked as locally changed even if there were no changes outside
+the "debconf markers". Detect this case by searching for lines outside
+that range which contain anything other than whitespace or comments, and
+if none are found, treat the config file as handled by the package
+("automatic update mode"). This should eliminate some overly aggressive
+migrations to manual update mode, though people who made changes only
+within the debconf markers and didn't follow instructions may still be
+incorrectly placed in automatic mode (that's why copies of the old config
+files are made when migration is done). Thanks to John R. Daily for
+bringing this scenario to my attention. (Closes: #214604)
+- debian/xserver-common.preinst.in
+- debian/xserver-xfree86.preinst.in
+ -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 22:55:43 -0500
+
xfree86 (4.2.1-12.1) unstable; urgency=low
* Fix typo in xlibs preinst. Closes: #213774, #213776
Modified: trunk/debian/xserver-common.preinst.in
===
--- trunk/debian/xserver-common.preinst.in 2003-10-23 03:40:42 UTC (rev 699)
+++ trunk/debian/xserver-common.preinst.in 2003-10-23 04:04:38 UTC (rev 700)
@@ -66,16 +66,23 @@
# removed, the user didn't want the file molested
if egrep -q '^### BEGIN DEBCONF SECTION' "$XWRAPPER_CONFIG" &&
egrep -q '^### END DEBCONF SECTION' "$XWRAPPER_CONFIG"; then
-# finally, people were letting debconf "manage" the config file
-# even though they complained when it did so and did not follow
-# the instructions that would make the maintainer scripts ignore
-# it, so store a backup so they can rescue themselves from their
-# own ignorance
-observe "migrating $XWRAPPER_CONFIG away from management by" \
-"debconf; backup stored in $XWRAPPER_CONFIG.dpkg-old" \
-"and checksum stored in $XWRAPPER_CONFIG_CHECKSUM"
-md5sum "$XWRAPPER_CONFIG" > "$XWRAPPER_CONFIG_CHECKSUM"
-cp "$XWRAPPER_CONFIG" "$XWRAPPER_CONFIG.dpkg-old"
+# has the user left the file untouched (except for blank lines
+# and comments) outside the debconf-marked area?
+if ! [ -n "$(sed -n '1,/^### BEGIN DEBCONF SECTION/p' \
+ < "$XWRAPPER_CONFIG" | grep -v '^[[:space:]]*#' \
+ | grep -v '^[[:space:]]*$')" -o -n \
+ "$(sed -n '/^### END DEBCONF SECTION/,$p' \
+ < "$XWRAPPER_CONFIG" | grep -v '^[[:space:]]*#' \
+ | grep -v '^[[:space:]]*$')" ]; then
+ observe "migrating $XWRAPPER_CONFIG away from management by" \
+ "debconf; backup stored in $XWRAPPER_CONFIG.dpkg-old" \
+ "and checksum stored in $XWRAPPER_CONFIG_CHECKSUM"
+ cp "$XWRAPPER_CONFIG" "$XWRAPPER_CONFIG.dpkg-old"
+ # if all of the above tests succeeded, treat the file
+ # similarly to an unmodified conffile (automatically updated
+ # by package)
+
X Strike Force XFree86 SVN commit: rev 699 - /
Author: daniel Date: 2003-10-22 22:40:42 -0500 (Wed, 22 Oct 2003) New Revision: 699 Modified: COMMITTERS Log: * COMMITTERS: [EMAIL PROTECTED] -> [EMAIL PROTECTED] Modified: COMMITTERS === --- COMMITTERS 2003-10-22 21:05:15 UTC (rev 698) +++ COMMITTERS 2003-10-23 03:40:42 UTC (rev 699) @@ -19,7 +19,7 @@ IPv6 support integration specialist Branden Robinson <[EMAIL PROTECTED]> czar, autocrat, release monkey, coordinator, scapegoat -Daniel Stone <[EMAIL PROTECTED]> +Daniel Stone <[EMAIL PROTECTED]> integrator and gadfly Matt Zimmerman <[EMAIL PROTECTED]> Debian Security Team liaison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
tag 215647 + wontfix thanks On Thu, Oct 23, 2003 at 09:30:04AM +0900, Tomohiro KUBOTA wrote: > Hi, > > I reopened this bug, because: > - I don't think the discussion finished. > - This bug is in the to-do list in the upstream. > > Please don't close this bug (the upstream agrees this should be > improved) until my patch will be adopted or a fixed upstream > version will be available as a Debian package. You are presenting me with an ultimatum: accept your patch or else. You do not appear to feel there are any grounds upon which you will change your mind. This is not a sound basis for a rational discussion. Neither are your assertions that I "must" remove features from XTerm simple because I have made observations about its historical development. You'd get along famously with Eduard Bloch, who argues the same way. This bug will be fixed when upstream fixes it, or when a patch that upstream is comfortable with is submitted. Tagging "wontfix". -- G. Branden Robinson|Optimists believe we live in the Debian GNU/Linux |best of all possible worlds. [EMAIL PROTECTED] |Pessimists are afraid the optimists http://people.debian.org/~branden/ |are right about that. signature.asc Description: Digital signature
Processed: Re: Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Processing commands for [EMAIL PROTECTED]: > tag 215647 + wontfix Bug#215647: xterm: change the encoding according to the current LC_CTYPE locale Tags were: wontfix experimental patch Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 216994 to libvte-common
Processing commands for [EMAIL PROTECTED]: > reassign 216994 libvte-common Bug#216994: libvte-common: new libvte changes gnome-terminal font size Bug reassigned from package `libxrender1' to `libvte-common'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Processing commands for [EMAIL PROTECTED]: > retitle 215647 xterm: change the encoding according to the current LC_CTYPE locale Bug#215647: xterm: want ISO 10646-1 fonts used by default instead of ISO 8559-1 Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Some patches for XFree86/experimental [2nd try]
Hello, I just installed the exec-shield kernel patch on my computer, and it turns out that XFree86 on Debian refuses to work without some fixes. Attached are 5 patches - 4 of them shamelessly extracted from Redhat rawhide source package - against XFree4.3 in experimental (snapshot from http://necrotic.deadbeast.net/xfree86/branches-4.3.0-sid-debian-2003.10.22.tar.gz) fixing various issues: * 912_elfloader_linux_non_exec_stack_v2.diff : This patch comes from the Redhat rawhide 4.3.0.40 source package (Redhat patch 9105). Original description : patch ELF loader to allow X to work on kernels with a non executable stack. * 913_patch_compile_kernel_26.diff : Simple patch to allow compilation with 2.6 kernel includes (found at http://www.mail-archive.com/xfree86@xfree86.org/msg08195.html). * 914_redhat_libgl_opt_v2.diff, 915_redhat_libgl_tls_buildfix.diff, 916_redhat_libgl_exec_shield_fixes_v2.diff : Patches from Redhat (number 10009, 10010 and 10012) to fix libGL with exec-shield. I was interested only in the last one but it looks like it depends at least from the first one... Please note that patches 914 and 916 require backing out 062_make_libGL_PIC_compliant.diff and that I have not tested them, except for the fact that they apply and compile fine (I'm not using any GL app). Patches 912 & 913 were compile and run-time tested by me. Both look fairly simple and unintrusive (in contrary to 914 and 916). Thus I'd like to know if it would be possible to have at least patches 912 and 913 applied to the packages in experimental ? With best regards, Vincent 912_elfloader_linux_non_exec_stack_v2.diff.bz2 Description: Binary data 913_patch_compile_kernel_26.diff.bz2 Description: Binary data 914_redhat_libgl_opt_v2.diff.bz2 Description: Binary data 915_redhat_libgl_tls_buildfix.diff.bz2 Description: Binary data 916_redhat_libgl_exec_shield_fixes_v2.diff.bz2 Description: Binary data
Processed: Re: Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Processing commands for [EMAIL PROTECTED]: > reopen 215647 Bug#215647: xterm: want ISO 10646-1 fonts used by default instead of ISO 8559-1 Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Hi, I reopened this bug, because: - I don't think the discussion finished. - This bug is in the to-do list in the upstream. Please don't close this bug (the upstream agrees this should be improved) until my patch will be adopted or a fixed upstream version will be available as a Debian package. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n
Hi, > You need to remember what xterm is. First and foremost, it's a VT100 > terminal emulator. It got a Tektronix 4014 emulator bolted onto it at > one point, and it added support for VT 220s (and 320s and 420s as well, > I think), but fundamentally it's still an 8-bit terminal emulator. > > XTerm simply was not written from the ground up to be a multi-byte, > highly-internationalized terminal emulator. The version first of XTerm > was written in 1984. I don't feel this is a serious discussion. If you really think so, many features must be removed from xterm. For example, xterm has been supporting UTF-8 (and therefor a multibyte software) for a long time since XFree86 4.0. Please remove the feature (and many features which VT100 and so on don't have), if you really think so. > > This is the main point. IMO, "uxterm" is an evil fork and a makeshift > > until xterm itself will be improved enough. > > Evil fork? Are you hearing yourself? uxterm can't be a fork because > it's just a shell script wrapper around xterm. Right, from technical point of view, it is a wrapper. However, from the users' point of view who never do "cat xterm", it is a fork. Evil fork, just like preparing another executable for Japanese support even when unfication is possible. > A makeshift solution? Possibly. If xterm itself renders uxterm > obsolete, a compatibility symlink can be provided for a Debian release > or so while people switch over to xterm. My patch renders uxterm obsolete. However, uxterm is an always-UTF-8 version of xterm regardless of locale, xterm cannot emulate uxterm. On the other hand, xterm is a terminal emulator which don't fully support locale yet and should be improved. > > Or, it is a version for people who don't know LANG variable or people > > who just want to temporarily test UTF-8. > > I use uxterm and neither of those descriptions fit me. Are you using a UTF-8 locale? Then, besides uxterm, xterm should be in UTF-8 mode, while the font is ISO-8859-1. This conflict will be fixed by my patch. > > However, if we were admit uxterm as a final solution, we would have to > > accept UTF-8 variants for all softwares. We would have to introduce > > uls, uwc, uperl, used, ugrep, and so on so on. > > Ah, the slippery slope argument. > > I don't have time to rebut logical fallacies. My intension is that many softwares are coming to support locale and don't supply different executables for different encodings. It is the way we should proceed. Your rebuttal softwares should be considered that they don't support locale yet or they are to be replaced by internationalized softwares in future. > Your arguments are not persuasive, especially because they're so shrill > and seem to betray a lack of understanding of the underlying software. I don't understand the meaning. > You can modify the XTerm app-defaults files on your machines as much as > you like; that's why they're conffiles. But your reasons for filing > this bug appear to boil down to a subjective personal dislike for typing > "uxterm" instead of "xterm". Outright replacement of xterm with uxterm > would cause surprising changes in behavior for some users -- at this > point, anyway. Please be calm. Since uxterm was introduced into XFree86, it must not be removed. uxterm must be an UTF-8 software regardless of locale, because it was intended as such, even if the intension is based on wrong idea. On app-defaults files: why peoples speaking some languages are forced to modify app-default files while others don't need to do? Generally, priviledged people say that there are no discrimination. If there were some technical difficulties, it might be acceptable. Also, your idea is against the concept of locale mechanism (no need for users to configure other than LANG variable) which I explained many times. Didn't you read? > Perhaps in the future that won't be so. Maybe you should ask Thomas > Dickey what you can do to help realize that future where uxterm no > longer needs to exist. Now I started this. Dickey said that my patch (you and I thought was rejected) is "still on my to-do list" and he is "interested in getting the idea implemented". He is seeking a better implementation to achieve the same thing. Of course I don't cite his whole mail and may have a bias. Please ask him by yourself if you don't trust my citation. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Can someone please reassign this to libvte-common ? Just to confirm, Xrender has nothing to do with this bug. Downgrading libvte to version 10.29-6 fixes this bug. The problem is libvte. Duraid Branden Robinson wrote: reassign 216994 libvte-common thanks On Wed, Oct 22, 2003 at 11:15:57AM +0200, Christian Marillat wrote: reopen 216994 reassign 216994 libxrender1 thanks Duraid Madina <[EMAIL PROTECTED]> writes: [Please respect the Carboin copy to the BTS] A screenshot is attached. ...which you didn't provide to the people to whom you're reassigning the bug. Please mail the screenshot to the bug. This bug is related to xrender downgrading to 0.8.3-2 solve this bug. You haven't explained why you think it's Xrender's fault. Reassigning back to you until you provide an adequate explanation in comprehensible English. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Still, no change. I now suspect (once again) this is something with libvte. Duraid Christian Marillat wrote: Duraid Madina <[EMAIL PROTECTED]> writes: I restarted X. Do I still need to rerun fc-cache in that case? Yes, under root. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#202128: DONATION FOR THE LORD.
From: Mrs Serena Jones PLEASE ENDEAVOUR TO USED IT FOR THE CHILDREN OF GOD. I am the above named person from Kuwait. I am married to Dr. Harry Jones who worked with Kuwait embassy in Ivory Co ast for nine years before he died in the year 2000. We were married for eleven years without a child. He died a fter a brief illness that lasted for only four days. Before his death we were both born again Christia ns.Since his death I decided not to re- marry or get a child outside my matrimonial home which the Bi ble is against.When my late husband was alive he deposited the sum of$8.6Million (Eight Million six hundred thousand U.S. D ollars) with one finance/security company in Amsterderm Hollan d. Presently, this money is still with the Security Company. Recently, my Doctor told me that I would not last for the next three months due to cancer problem. Though what disturbs me most i s my stroke sickness. Having known my condition I decided to donate this fund to church or better still a christian individ ual that will utilize this money the way I am going to instruc t here in. I want a church that will use this fund to fund chu rches, orphanages and widows propagating the word of God and t o ensure that the house of God is maintained. The Bible made us to understand that Blessed is the hand that giveth. I took this decision because I don?t have any child that wil l inherit this money and my husband relatives are not Christi ans and I don?t want my husband?s hard earned money to be misu sed by unbelievers. I don?t want a situation where this money will be used in an ungodly manner. Hence the reason for taking this bold decision. I am not afraid of death hence I know whe re I am going. I know that I am going to be in the bosom of th e Lord. Exodus 14 VS 14 says that the lord will fight my case and I shall hold my peace. I don?t need any telephone communi cation in this regard because of my health because of the pres ence of my husband?s relatives around me always. I don?t want them to know about this development. With God all things are p ossible. As soon as I receive your reply I shall give you the contact of the Finance/Security Company in Amsterderm Holland . I will also issue you a letter of authority that will prove you as the original- beneficiary of this fund. I want you and the church to always pray for me because the lord is my shephard. My happiness is that I lived a life of a worthy Christian. Whoe ver that wants to serve the Lord must serve him in spirit and truth. Please always be prayerful all through your life. Any d elay in your reply will give me room in sourcing for a chuch or christian individual for this same purpose. Please assure me that you will act accordingly as I stated herein. Hoping to hearing from you. N.B- PLEASE I WILL ADVICE YOU TO GIVE THE LAWYER IN CHARGE A CALL IN HOLLAND IMMEDIATELY, HE DOES EVERYTHING ON MY BEHALF AND HE'S VERY UNDERSTANDING AND I BELIEVE HE WILL LEAD YOU TO YOUR SUCCESS IN JESUS NAME, THE LAWYER'S NAME IS GERRY SLY HIS CONTACT PHONE NUMBER IS 00-31-620-668-086. Remain blessed in the name of the Lord. Yours in Christ, Mrs Serena Jones
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Duraid Madina <[EMAIL PROTECTED]> writes: > I restarted X. Do I still need to rerun fc-cache in that case? Yes, under root. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#217068: acknowledged by developer (Re: Bug#217068: xserver-xfree86: X won't run, unknown reason)
On Wed, 22 Oct 2003, Debian Bug Tracking System wrote: > It has been closed by one of the developers, namely > Branden Robinson <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact the developer, by replying to this email. > > [Update, I have now gotten X to run from kdm (gdm still dies). > > Tale of the story below. I don't know if you want to adjust > > the severity level as things now run, but without reconfiguring > > X and switching from gdm to kdm I would still not be running. > > Whatever the problem is, mozilla/galeon is now broken. ] > > You no longer have an X problem. Even if you had, the severity of this > report would have been inflated. Please file bugs at normal severity > and trust the package maintainer(s) to upgrade it to the appropriate > severity. (Only if xserver-xfree86 didn't work for anyone would the > "grave" severity be appropriate.) When people file bug reports, they commonly only have their own experiences to work from. If you guys do not want us to file grave reports, perhaps you should remove that choice from what reportbug gives us. Looking at the descriptions of the various levels provided, grave seemed the most appropriate. If I felt I no longer had a problem, I wouldn't have filed a bug report. The steps I went through were not things that I thought most people would use in trying to track down a problem. > > The first possibility I looked at, was that the last error showing in > > the logs or ~/.xsession-errors dealt with /dev/input/mice. Since I > > don't have a USB mouse, I first tried creating /dev/input and making > > mice a symlink to /dev/ttyS0 (I should have used /dev/psaux in after > > thought). > > This probably was not a necessary thing to do and I would revert it. > Fatal errors are generally described as such in the server output. This whole episode has been plagued by a lack of any kind of output. It was reverted shortly after. I was just documenting how I was trying to go through what output I could find, in order to try and figure out what the problem was. > > There were also messages about some missing symbols in=20 > > libGLcore.a and libspeedo.a. > > Also completely harmless. Is this fact documented somewhere? If so, I missed it. > > X still wouldn't start. I then edited ~/.gnome2/gdm so that it > > wouldn't use "Debian" (KDE) as the window manager. This didn't help. > > I then started editing /etc/X11/XF86Config-4 (as you can see below). > > I started by editing out the font path to speedo, and the modules load > > stuff for speedo and GLcore. Trying to startx again, I got another > > error which led me to trying to also comment out glx, leaving me at > > the config you see below. This still doesn't work. > > I wouldn't have expected them to. You seem to have been shooting in the > dark. The folks on the debian-user mailing list can probably help you > with troubleshooting in the future. Shooting in the dark. I was getting messages in log files and .xsession-errors files, having to do with what looked like XFree86 misconfiguration. How is trying to correct this misconfiguration shooting in the dark? > > I have known for a while, that the management of the configuration > > for X has changed in Debian (to what it has now). I don't remember > > as to whether there were any minor problems in the transition. After > > the first edit to /etc/X11/XF86Config-4, I followed the instructions > > at the top of the file vis a vis saving a custom configuration. > > Okay. Given that you have the X server itself working again, I'm > guessing there weren't any actual problems here. Who knows? I am certainly not happy with how I "solved" (hacked would be a better description) the problem. If I knew what was wrong in the first place, I probably could have done a better job in trying to track down what to change/fix. But nothing shows up in the logs or on stderr. > > I am getting a DeprecationWarning about xreadlines when I do this > > (dpkg-reconfigure xserver-xfree86) followed by a configlet in path > > is bad. > > That's a Python error, and neither xserver-xfree86's configuration > script nor debconf are written in Python. Fine. How does a python script get run when I dpkg-reconfigure your package, if nothing uses python? > > Other people in my lug have suggested things. Some kind of problem with > > libfreetype6 conflicting with gsfonts-other. I've looked in bug reports > > for xserver-xfree86, libfreetype6, gsfonts-other and see nothing which > > really looks similar to this problem, with a recent time frame. Well, > > there is one report, which was closed because a virus was found in a > > followup message? > > That probably has something to do with your problem. That a piece of > spam closed a bug report should not be taken as evidence that a bug was > actually resolved, by the w
X Strike Force XFree86 SVN commit: rev 698 - in branches/4.3.0/sid/debian: . patches
Author: branden Date: 2003-10-22 16:05:15 -0500 (Wed, 22 Oct 2003) New Revision: 698 Removed: branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 branches/4.3.0/sid/debian/patches/001a_move-gnu-common.diff branches/4.3.0/sid/debian/patches/001b_gnu_common_split.diff branches/4.3.0/sid/debian/patches/001c_move-gnu-lib.diff branches/4.3.0/sid/debian/patches/001d_gnu-lib_split.diff branches/4.3.0/sid/debian/patches/800a_gnu_more_fixes.diff branches/4.3.0/sid/debian/patches/803_gnu_xdm_chooser.diff branches/4.3.0/sid/debian/xbase-clients.install.hurd-i386 branches/4.3.0/sid/debian/xfree86-common.docs.hurd-i386 branches/4.3.0/sid/debian/xlibmesa-gl-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibmesa-glu-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibosmesa4-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibs-data.install.hurd-i386 branches/4.3.0/sid/debian/xlibs-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xterm.docs.hurd-i386 Modified: branches/4.3.0/sid/debian/changelog branches/4.3.0/sid/debian/patches/002_xdm_fixes.diff branches/4.3.0/sid/debian/patches/003a_damn_cpp_3.3_to_hell.diff branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff branches/4.3.0/sid/debian/patches/800_gnu_config.diff Log: Revert revision 696. Robert's going to groom that changeset over in people/rmh first. Modified: branches/4.3.0/sid/debian/changelog === --- branches/4.3.0/sid/debian/changelog 2003-10-22 20:24:48 UTC (rev 697) +++ branches/4.3.0/sid/debian/changelog 2003-10-22 21:05:15 UTC (rev 698) @@ -138,26 +138,6 @@ - debian/patches/056_i810_make_i830_usable.diff: only access pI830 when XF86DRI is defined. - * Split gnu.cf into gnu-common.cf (for common GNU/* stuff) and gnu.cf (for -GNU/Hurd stuff). It will be included by non-Linux only for now since -linux.cf has many kernel-specific kludges. [Robert Millan] -- debian/patches/001a_move-gnu-common.diff: Move gnu.cf to gnu-common.cf. -- debian/patches/001c_move-gnu-lib.diff: Ditto for gnuLib.*. -- debian/patches/001b_gnu_common_split.diff: Create a new gnu.cf that - includes gnu-common.cf and move Hurd-specific stuff into it. -- debian/patches/001d_gnu-lib_split.diff: Ditto for gnuLib.*. -- debian/patches/002_xdm_fixes.diff: Re-diff for new gnu.cf. -- debian/patches/003a_damn_cpp_3.3_to_hell.diff: s/gnu.cf/gnu-common.cf/g -- debian/patches/004_imake_manpage_handling_overhaul.diff: Likewise. -- debian/patches/800_gnu_config.diff: Likewise. - - * More GNU/Hurd build fixes. [Robert Millan] -- debian/patches/800a_gnu_more_fixes.diff: Add new macros to gnu-common.cf - as pointed out by ISHIKAWA Mutsumi some time ago. -- debian/patches/803_gnu_xdm_chooser.diff: New. GNU/Hurd build fixes. -- debian/*.hurd-i386: Update to sync with MANIFEST.hurd-i386 (the MANIFEST - itself is unchanged). - -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 00:13:12 -0500 xfree86 (4.3.0-0pre1v3) experimental; urgency=high Deleted: branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 === --- branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 2003-10-22 20:24:48 UTC (rev 697) +++ branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 2003-10-22 21:05:15 UTC (rev 698) @@ -1 +0,0 @@ -usr/X11R6/lib/libXaw.so.6.1 Deleted: branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 === --- branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 2003-10-22 20:24:48 UTC (rev 697) +++ branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 2003-10-22 21:05:15 UTC (rev 698) @@ -1 +0,0 @@ -usr/X11R6/lib/libXaw.so.7.0 Deleted: branches/4.3.0/sid/debian/patches/001a_move-gnu-common.diff === --- branches/4.3.0/sid/debian/patches/001a_move-gnu-common.diff 2003-10-22 20:24:48 UTC (rev 697) +++ branches/4.3.0/sid/debian/patches/001a_move-gnu-common.diff 2003-10-22 21:05:15 UTC (rev 698) @@ -1,381 +0,0 @@ - - Simply moves gnu.cf to gnu-common.cf, and nothing else. - -diff -Nur xc/config/cf.old/gnu-common.cf xc/config/cf/gnu-common.cf xc/config/cf.old/gnu-common.cf 1970-01-01 01:00:00.0 +0100 -+++ xc/config/cf/gnu-common.cf 2001-02-28 19:58:49.0 +0100 -@@ -0,0 +1,185 @@ -+XCOMM platform: $XFree86: xc/config/cf/gnu.cf,v 1.11 2001/02/28 18:58:49 dawes Exp $ -+ -+#ifndef OSName -+#define OSNameDefaultOSName -+#endif -+ -+#ifndef OSVendor -+#define OSVendor /**/ -+#endif -+#ifndef OSMajorVersion -+#define OSMajorVersionDefaultOSMajorVersion -+#endif -+#ifndef OSMinorVersion -+#define OSMinorVersionDef
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Duraid Madina <[EMAIL PROTECTED]> writes: > Actually, downgrading libxrender1 (tried several versions, back to > 0.8.2-1) doesn't fix this problem for me. Do you have re-run fc-cache ? FYI the latest libfreetype6 was broken (See the BTS for fontconfig bugs) and fonts caches was not generated correctly. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
I restarted X. Do I still need to rerun fc-cache in that case? Duraid Christian Marillat wrote: Duraid Madina <[EMAIL PROTECTED]> writes: Actually, downgrading libxrender1 (tried several versions, back to 0.8.2-1) doesn't fix this problem for me. Do you have re-run fc-cache ? FYI the latest libfreetype6 was broken (See the BTS for fontconfig bugs) and fonts caches was not generated correctly. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Processing commands for [EMAIL PROTECTED]: > reassign 216994 libxrender1 Bug#216994: libvte-common: new libvte changes gnome-terminal font size Bug reassigned from package `libvte-common' to `libxrender1'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Actually, downgrading libxrender1 (tried several versions, back to 0.8.2-1) doesn't fix this problem for me. Duraid Christian Marillat wrote: reassign 216994 libxrender1 thanks On Wed, Oct 22, 2003 at 11:15:57AM +0200, Christian Marillat wrote: reopen 216994 reassign 216994 libxrender1 thanks Duraid Madina <[EMAIL PROTECTED]> writes: [Please respect the Carboin copy to the BTS] A screenshot is attached. ...which you didn't provide to the people to whom you're reassigning the bug. Please mail the screenshot to the bug. This bug is related to xrender downgrading to 0.8.3-2 solve this bug. You haven't explained why you think it's Xrender's fault. Are you blind or what ? DOWNGRADING TO LIBXRENDER1 0.8.3-2 SOLVE THIS BUG. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X Strike Force XFree86 SVN commit: rev 697 - in trunk/debian: . local
Author: branden Date: 2003-10-22 15:24:48 -0500 (Wed, 22 Oct 2003) New Revision: 697 Modified: trunk/debian/changelog trunk/debian/local/FAQ Log: Add several new entries to the FAQ: + The X server log says there was an error and it's disabling DRI. Is that why the X server won't start? + The X server log says there was an error opening my "core pointer" or the file /dev/input/mice. Is that why the X server won't start? + The X server log says it's skipping modules due to "No symbols found" errors. Is that why the X server won't start? + The X server log says "AddScreen/ScreenInit failed for driver 0". Is that why the X server won't start? + How can I tell if it's the X server crashing, or my X session exiting abnormally? - debian/local/FAQ Modified: trunk/debian/changelog === --- trunk/debian/changelog 2003-10-22 17:53:46 UTC (rev 696) +++ trunk/debian/changelog 2003-10-22 20:24:48 UTC (rev 697) @@ -140,8 +140,21 @@ output is sure to be generated. - debian/xserver-xfree86.config.in - -- Branden Robinson <[EMAIL PROTECTED]> Tue, 21 Oct 2003 23:47:15 -0500 + * Add several new entries to the FAQ: ++ The X server log says there was an error and it's disabling DRI. Is + that why the X server won't start? ++ The X server log says there was an error opening my "core pointer" or + the file /dev/input/mice. Is that why the X server won't start? ++ The X server log says it's skipping modules due to "No symbols found" + errors. Is that why the X server won't start? ++ The X server log says "AddScreen/ScreenInit failed for driver 0". Is + that why the X server won't start? ++ How can I tell if it's the X server crashing, or my X session exiting + abnormally? +- debian/local/FAQ + -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 15:21:34 -0500 + xfree86 (4.2.1-12.1) unstable; urgency=low * Fix typo in xlibs preinst. Closes: #213774, #213776 Modified: trunk/debian/local/FAQ === --- trunk/debian/local/FAQ 2003-10-22 17:53:46 UTC (rev 696) +++ trunk/debian/local/FAQ 2003-10-22 20:24:48 UTC (rev 697) @@ -107,6 +107,16 @@ achieve that? *) How do I add custom sections to a dexconf-generated XF86Config or XF86Config-4 file? +*) The X server log says there was an error and it's disabling DRI. Is that + why the X server won't start? +*) The X server log says there was an error opening my "core pointer" or + the file /dev/input/mice. Is that why the X server won't start? +*) The X server log says it's skipping modules due to "No symbols found" + errors. Is that why the X server won't start? +*) The X server log says "AddScreen/ScreenInit failed for driver 0". Is that + why the X server won't start? +*) How can I tell if it's the X server crashing, or my X session exiting + abnormally? GENERAL QUESTIONS @@ -1615,4 +1625,117 @@ server configuration, and XF86Config-4(5x) for more information on XFree86 4.x X server configuration. +*) The X server log says there was an error and it's disabling DRI. Is that + why the X server won't start? + +No. If DRI (Direct Rendering Infrastructure) is disabled, then 3D-accelerated +applications such as games may not run satisfactorily or at full speed, but +this doesn't prevent the X server from working. A disabled DRI doesn't +prevent your desktop from coming up, or programs like XTerm or Mozilla from +running. + +If your X server is failing to start and you think this error message is the +problem, look elsewhere; the problem is something else. + +*) The X server log says there was an error opening my "core pointer" or + the file /dev/input/mice. Is that why the X server won't start? + +Errors about "failure to initialize core devices" are usually fatal. Errors +about failing to open "/dev/input/mice" usually aren't if they're not +accompanied by a "failure to initialize core devices" message. + +If you have non-USB mouse configured, the Debian default XFree86 X server +configuration sets up an extra input device so that you can just plug a USB +mouse in and use it as well. + +It's easy enough to determine whether errors opening /dev/input/mice are +really the cause of a failing X server. As root, run the following command: + +# X -allowMouseOpenFail + +(If you get a message like "Server already active for display 0", then you're +probably already running X somewhere. Try specifying a display for the X +server to run on: + +# X :50 -allowMouseOpenFail + +See the Xserver(1x) and XFree86(1x) manual pages for more information.) + +If the X server does not start, then the mouse device is not your problem. +Search the X server's log (in the above examples, /var/log/XFree86.0.log or +/var/log/XFree86.50.log) for other errors. + +If the X server *does* start, then you *do* have a mouse problem. Use +"dpkg
Re: Some patches for XFree86/experimental
On Wed, Oct 22, 2003 at 06:15:58PM +0200, Vince wrote: > I apologize : I just realized that I have sent the wrong (uncompressed) > versions for patches 914 and 915 and 914 is around 400KB. :-( > Please let me know if by luck my previous mail was blocked by the > list-manager and I'll resent a compressed version. They didn't show up, so please send them again in compressed form, along with your explanation of them. -- G. Branden Robinson| Debian GNU/Linux | Music is the brandy of the damned. [EMAIL PROTECTED] | -- George Bernard Shaw http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#217068: marked as done (xserver-xfree86: X won't run, unknown reason)
Your message dated Wed, 22 Oct 2003 14:22:00 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#217068: xserver-xfree86: X won't run, unknown reason has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 22 Oct 2003 14:22:56 + >From [EMAIL PROTECTED] Wed Oct 22 09:22:50 2003 Return-path: <[EMAIL PROTECTED]> Received: from h64-42-245-133.gtcust.grouptelecom.net (newmain.materia) [64.42.245.133] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1ACJsm-0003pP-00; Wed, 22 Oct 2003 09:22:41 -0500 Received: from ghaverla by newmain.materia with local (Exim 3.36 #1 (Debian)) id 1ACJsj-0004VP-00; Wed, 22 Oct 2003 08:22:37 -0600 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Gordon Haverland <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: xserver-xfree86: X won't run, unknown reason X-Mailer: reportbug 2.34 Date: Wed, 22 Oct 2003 08:22:37 -0600 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-5.8 required=4.0 tests=BAYES_10,HAS_PACKAGE,MAILTO_TO_SPAM_ADDR version=2.53-bugs.debian.org_2003_10_21 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_21 (1.174.2.15-2003-03-30-exp) Package: xserver-xfree86 Version: 4.2.1-12.1 Severity: grave Justification: renders package unusable I am not exactly sure where the problem lies on this one. I normally just upgrade a package or two as need be. I had just upgraded a bunch of KDE stuff, and so closed all X sessions and then let apt-get install everything. After apt-get was finished, gdm could not start the login session for a user which had KDE (Debian) as the session manager. Since then, every attempt to start X has failed. [Update, I have now gotten X to run from kdm (gdm still dies). Tale of the story below. I don't know if you want to adjust the severity level as things now run, but without reconfiguring X and switching from gdm to kdm I would still not be running. Whatever the problem is, mozilla/galeon is now broken. ] The first possibility I looked at, was that the last error showing in the logs or ~/.xsession-errors dealt with /dev/input/mice. Since I don't have a USB mouse, I first tried creating /dev/input and making mice a symlink to /dev/ttyS0 (I should have used /dev/psaux in after thought). There were also messages about some missing symbols in libGLcore.a and libspeedo.a. X still wouldn't start. I then edited ~/.gnome2/gdm so that it wouldn't use "Debian" (KDE) as the window manager. This didn't help. I then started editing /etc/X11/XF86Config-4 (as you can see below). I started by editing out the font path to speedo, and the modules load stuff for speedo and GLcore. Trying to startx again, I got another error which led me to trying to also comment out glx, leaving me at the config you see below. This still doesn't work. I have known for a while, that the management of the configuration for X has changed in Debian (to what it has now). I don't remember as to whether there were any minor problems in the transition. After the first edit to /etc/X11/XF86Config-4, I followed the instructions at the top of the file vis a vis saving a custom configuration. I am getting a DeprecationWarning about xreadlines when I do this (dpkg-reconfigure xserver-xfree86) followed by a configlet in path is bad. (I wonder where debconf got a screen size of 17"? This monitor is 21", and has always been here.) Other people in my lug have suggested things. Some kind of problem with libfreetype6 conflicting with gsfonts-other. I've looked in bug reports for xserver-xfree86, libfreetype6, gsfonts-other and see nothing which really looks similar to this problem, with a recent time frame. Well, there is one report, which was closed because a virus was found in a followup message? I'll try reconfiguring all of X (xserver-xfree86) with xf86cfg and then purging gsfonts-other, and after that installing older versions of xserver-xfree86. If you have suggestions as to how to trace things (as I am not receiving error messages now, but it still won't start) or where the problem lies, I'ld be happy to hear them. Running xf86cfg (after moving /etc/X11/XF86Config-4 aside), I went through the configuration process, setting values to what they should be for keyboard, mouse, card and monitor. When I go to save things, it asks if I
Bug#215647: marked as done (xterm: want ISO 10646-1 fonts used by default instead of ISO 8559-1)
Your message dated Wed, 22 Oct 2003 13:50:09 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#215647: [patch] xterm 4.3.0-0pre1v3 i18n has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 13 Oct 2003 22:41:11 + >From [EMAIL PROTECTED] Mon Oct 13 17:40:21 2003 Return-path: <[EMAIL PROTECTED]> Received: from c147001.vh.plala.or.jp (mps4.plala.or.jp) [210.150.147.1] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1A9BMS-0002Gz-00; Mon, 13 Oct 2003 17:40:20 -0500 Received: from msvc2.plala.or.jp ([172.23.8.210]) by mps4.plala.or.jp with SMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Tue, 14 Oct 2003 07:40:19 +0900 Received: ( 6700 invoked from network); 14 Oct 2003 07:41:54 +0900 Received: from unknown (HELO mpb1.plala.or.jp) (172.23.8.16) by msvc2 with SMTP; 14 Oct 2003 07:41:53 +0900 Received: from localhost ([210.153.68.106]) by mpb1.plala.or.jp with ESMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Tue, 14 Oct 2003 07:40:14 +0900 Date: Tue, 14 Oct 2003 07:40:20 +0900 (JST) Message-Id: <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xterm 4.3.0-0pre1v3 i18n From: Tomohiro KUBOTA <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> X-Mailer: Mew version 3.3rc1 on Emacs 20.7 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Tue_Oct_14_07:40:20_2003_179)--" Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-7.9 required=4.0 tests=HAS_PACKAGE,PATCH_UNIFIED_DIFF autolearn=ham version=2.53-bugs.debian.org_2003_10_13 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_13 (1.174.2.15-2003-03-30-exp) Next_Part(Tue_Oct_14_07:40:20_2003_179)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Package: xterm Version: 4.3.0-0pre1v3 Tags: experimental,patch XFree86 4.3.0's xterm has a feature to use UTF-8 mode and "luit" automatically so that xterm will use the character encoding of the current locale. For example, by using this feature, German people will be able to use Euro sign without any special settings for xterm. (Of course LANG variable must be set - but it is not xterm-specific setting and is needed for all softwares anyway). Of course, it is not limited to German - "luit" supports various encodings including ISO-8859 encodings, KOI8 encodings, and some Asian encodings. However, this feature is not perfectly implemented and many people are left not knowing this feature. Moreover, some people suffer from "mojibake" problem. At first, font setting is not proper. Since this feature is implemented using UTF-8 mode, *-iso10646-1 fonts must be used. However, the default font of xterm is *-iso8859-1. Thus, the default font should be *-iso10646-1. I attached a patch for /etc/X11/app-defaults/XTerm to modify font settings. This is not harmful for ISO-8859-1 people because U+ - U+00FF range of Unicode is exactly same as ISO-8859-1. In Debian system, this modification has one more merit that non-ISO-8859-1 people won't need to install xfonts-base-transcoded (for xterm). Next, this feature is enabled only for east Asian locales and Thai. Thus, other non-ISO-8859-1 people are left not knowing this feature. To solve this problem, my patch adds "*VT100*locale: true" line for /etc/X11/app-defaults/XTerm file. This patch is not for UXTerm. It is xterm that automatically follows the current locale and needs *-iso10646-1 fonts. See http://www.debian.or.jp/~kubota/mojibake/xterm.html for screenshots. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ Next_Part(Tue_Oct_14_07:40:20_2003_179)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="XTerm.diff" --- XTerm.old 2003-09-28 20:56:32.0 +0900 +++ XTerm 2003-10-13 14:32:07.0 +0900 @@ -9,6 +9,9 @@ ! it is useless, and if it does, it is harmful. !XTerm.JoinSession:False +*VT100*font: -misc-fixed-medium-r-semicondensed--13-*-iso10646-1 +*VT100*locale: true + *SimpleMenu*BackingStore: NotUseful *SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-* *SimpleMenu*menuLabel.vertSpace: 100 @@ -75,15 +78,15 @@ *VT100*font1: nil2 *IconFont: nil2 *fontMenu*
Processed: severity of 217068 is normal, tagging 217068
Processing commands for [EMAIL PROTECTED]: > severity 217068 normal Bug#217068: xserver-xfree86: X won't run, unknown reason Severity set to `normal'. > tag 217068 + moreinfo Bug#217068: xserver-xfree86: X won't run, unknown reason There were no tags set. Tags added: moreinfo > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Processing commands for [EMAIL PROTECTED]: > reassign 216994 libvte-common Bug#216994: libvte-common: new libvte changes gnome-terminal font size Bug reassigned from package `libxrender1' to `libvte-common'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X Strike Force XFree86 SVN commit: rev 696 - in branches/4.3.0/sid/debian: . patches
Author: rmh Date: 2003-10-22 12:53:46 -0500 (Wed, 22 Oct 2003) New Revision: 696 Added: branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 branches/4.3.0/sid/debian/patches/001a_move-gnu-common.diff branches/4.3.0/sid/debian/patches/001b_gnu_common_split.diff branches/4.3.0/sid/debian/patches/001c_move-gnu-lib.diff branches/4.3.0/sid/debian/patches/001d_gnu-lib_split.diff branches/4.3.0/sid/debian/patches/800a_gnu_more_fixes.diff branches/4.3.0/sid/debian/patches/803_gnu_xdm_chooser.diff branches/4.3.0/sid/debian/xbase-clients.install.hurd-i386 branches/4.3.0/sid/debian/xfree86-common.docs.hurd-i386 branches/4.3.0/sid/debian/xlibmesa-gl-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibmesa-glu-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibosmesa4-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xlibs-data.install.hurd-i386 branches/4.3.0/sid/debian/xlibs-dbg.install.hurd-i386 branches/4.3.0/sid/debian/xterm.docs.hurd-i386 Modified: branches/4.3.0/sid/debian/changelog branches/4.3.0/sid/debian/patches/002_xdm_fixes.diff branches/4.3.0/sid/debian/patches/003a_damn_cpp_3.3_to_hell.diff branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff branches/4.3.0/sid/debian/patches/800_gnu_config.diff Log: * Split gnu.cf into gnu-common.cf (for common GNU/* stuff) and gnu.cf (for GNU/Hurd stuff). It will be included by non-Linux only for now since linux.cf has many kernel-specific kludges. [Robert Millan] - debian/patches/001a_move-gnu-common.diff: Move gnu.cf to gnu-common.cf. - debian/patches/001c_move-gnu-lib.diff: Ditto for gnuLib.*. - debian/patches/001b_gnu_common_split.diff: Create a new gnu.cf that includes gnu-common.cf and move Hurd-specific stuff into it. - debian/patches/001d_gnu-lib_split.diff: Ditto for gnuLib.*. - debian/patches/002_xdm_fixes.diff: Re-diff for new gnu.cf. - debian/patches/003a_damn_cpp_3.3_to_hell.diff: s/gnu.cf/gnu-common.cf/g - debian/patches/004_imake_manpage_handling_overhaul.diff: Likewise. - debian/patches/800_gnu_config.diff: Likewise. * More GNU/Hurd build fixes. [Robert Millan] - debian/patches/800a_gnu_more_fixes.diff: Add new macros to gnu-common.cf as pointed out by ISHIKAWA Mutsumi some time ago. - debian/patches/803_gnu_xdm_chooser.diff: New. GNU/Hurd build fixes. - debian/*.hurd-i386: Update to sync with MANIFEST.hurd-i386 (the MANIFEST itself is unchanged). Modified: branches/4.3.0/sid/debian/changelog === --- branches/4.3.0/sid/debian/changelog 2003-10-22 05:16:55 UTC (rev 695) +++ branches/4.3.0/sid/debian/changelog 2003-10-22 17:53:46 UTC (rev 696) @@ -138,6 +138,26 @@ - debian/patches/056_i810_make_i830_usable.diff: only access pI830 when XF86DRI is defined. + * Split gnu.cf into gnu-common.cf (for common GNU/* stuff) and gnu.cf (for +GNU/Hurd stuff). It will be included by non-Linux only for now since +linux.cf has many kernel-specific kludges. [Robert Millan] +- debian/patches/001a_move-gnu-common.diff: Move gnu.cf to gnu-common.cf. +- debian/patches/001c_move-gnu-lib.diff: Ditto for gnuLib.*. +- debian/patches/001b_gnu_common_split.diff: Create a new gnu.cf that + includes gnu-common.cf and move Hurd-specific stuff into it. +- debian/patches/001d_gnu-lib_split.diff: Ditto for gnuLib.*. +- debian/patches/002_xdm_fixes.diff: Re-diff for new gnu.cf. +- debian/patches/003a_damn_cpp_3.3_to_hell.diff: s/gnu.cf/gnu-common.cf/g +- debian/patches/004_imake_manpage_handling_overhaul.diff: Likewise. +- debian/patches/800_gnu_config.diff: Likewise. + + * More GNU/Hurd build fixes. [Robert Millan] +- debian/patches/800a_gnu_more_fixes.diff: Add new macros to gnu-common.cf + as pointed out by ISHIKAWA Mutsumi some time ago. +- debian/patches/803_gnu_xdm_chooser.diff: New. GNU/Hurd build fixes. +- debian/*.hurd-i386: Update to sync with MANIFEST.hurd-i386 (the MANIFEST + itself is unchanged). + -- Branden Robinson <[EMAIL PROTECTED]> Wed, 22 Oct 2003 00:13:12 -0500 xfree86 (4.3.0-0pre1v3) experimental; urgency=high Added: branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 === --- branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 2003-10-22 05:16:55 UTC (rev 695) +++ branches/4.3.0/sid/debian/libxaw6-dbg.install.hurd-i386 2003-10-22 17:53:46 UTC (rev 696) @@ -0,0 +1 @@ +usr/X11R6/lib/libXaw.so.6.1 Added: branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 === --- branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 2003-10-22 05:16:55 UTC (rev 695) +++ branches/4.3.0/sid/debian/libxaw7-dbg.install.hurd-i386 2003-10-22 17:53:46 UTC (rev 69
Bug#216970: acknowledged by developer (Re: Bug#216970: [startx] Does not use $HOME/.xsession as documented.)
On Tue, Oct 21, 2003 at 07:29:25PM -0400, Norbert Veber wrote: > Yes, you are right. The machine which has this problem has an xinitrc > which does not source /etc/X11/Xsession. It is attached. > > I have never edited the file, at least not as far as I recall. Since > the file is marked as a conffile, I would expect to see an > /etc/X11/xinit/xinitrc.dpkg-dist, but it is not there either. I have no > idea why it was not replaced with the new version. It looks like the stock sample xinitrc that ships with XFree86. Perhaps at some point you installed XFree86 from the upstream source or binary distribution. -- G. Branden Robinson|When we call others dogmatic, what Debian GNU/Linux |we really object to is their [EMAIL PROTECTED] |holding dogmas that are different http://people.debian.org/~branden/ |from our own. -- Charles Issawi signature.asc Description: Digital signature
Re: X Strike Force XFree86 SVN commit: rev 684 - in branches/4.3.0/sid/debian: . patches
On Tue, Oct 21, 2003 at 05:55:11PM -0500, X Strike Force SVN Repository Admin wrote: > Author: rmh > Date: 2003-10-21 17:54:56 -0500 (Tue, 21 Oct 2003) > New Revision: 684 > > Modified: >branches/4.3.0/sid/debian/changelog >branches/4.3.0/sid/debian/patches/056_i810_make_i830_usable.diff > Log: > * Fix build error when NOT_BUILDING_X_SERVER=yes. The "pI830" variable > introduced in patch 056 is used unconditionaly, but only declared when > XF86DRI macro is defined. [Robert Millan] > - debian/patches/056_i810_make_i830_usable.diff: only access pI830 when > XF86DRI is defined. Say what? Why is the source file xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c being dealt with at all when NOT_BUILDING_X_SERVER is defined? (Oh, I get it. You're using NOT_BUILDING_X_SERVER prescriptively, by defining it when you run debian/rules or something similar, not descriptively. I'm not sure that's a good idea. If I'd meant NOT_BUILDING_X_SERVER to be used prescriptively, I'd have called it DO_NOT_BUILD_X_SERVER.) Can you please post the build failure to the list? Either way, we need to come up with a better commit log and changelog entry. Your description of the error is not meaningful in the context of the XFree86 build itself. -- G. Branden Robinson| The National Security Agency is Debian GNU/Linux | working on the Fourth Amendment [EMAIL PROTECTED] | thing. http://people.debian.org/~branden/ | -- Phil Lago, Deputy XD, CIA signature.asc Description: Digital signature
Bug#215997: stripes in full-screen mode (XVideo, nv, NV17, TFT, XGA)
On Wed, Oct 22, 2003 at 11:10:49AM +0200, Eduard Bloch wrote:
> #include
> * Branden Robinson [Tue, Oct 21 2003, 05:20:50PM]:
>
> > > > Thanks!
> > >
> > > Okay, and do you intend to apply it? I cannot see the pending tag...
> > > If not, what is the reason?
> >
> > Would you settle down? The pending tag is not applied until after a fix
> > is actually committed to the repo. I haven't even confirmed that the
> > patch applies cleanly or doesn't break the build yet.
>
> Okay, that is the answer I wished to see. Nothing more, nothing less.
In the future you won't get even that if you don't improve your
attitude.
> experiences with your politics for acceptance of not-invented-here fixes>
Why, surely you're right, which explains the utter absence of credit and
gratitude extended to other people in my changelog for authoring fixes.
Indeed, the string "thanks" appears not even once.
% zgrep -ci thanks /usr/share/doc/xfree86-common/changelog.Debian.{,old.}gz
/usr/share/doc/xfree86-common/changelog.Debian.gz:184
/usr/share/doc/xfree86-common/changelog.Debian.old.gz:168
Well, the assertion is true in Eduard Bloch's delusional, solipsistic
universe, at any rate.
--
G. Branden Robinson| That's the saving grace of humor:
Debian GNU/Linux | if you fail, no one is laughing at
[EMAIL PROTECTED] | you.
http://people.debian.org/~branden/ | -- A. Whitney Brown
signature.asc
Description: Digital signature
Fixed in upload of xfree86 4.3.0-0pre1v4 to experimental
tag 215997 + fixed-in-experimental
tag 216896 + fixed-in-experimental
quit
This message was generated automatically in response to an
upload to the experimental distribution. The .changes file follows.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 22 Oct 2003 00:13:12 -0500
Source: xfree86
Binary: xlibosmesa-dev libxaw7-dbg xlibs-dev xlibs-dbg xlibosmesa4-dbg xlibosmesa4
xbase-clients xlibmesa-gl-dev libdps1 xlibs-data xfonts-75dpi xfonts-100dpi-transcoded
xfonts-scalable xlibmesa-dev xlibmesa-glu-dev xterm xlibs-static-pic lbxproxy
x-window-system-core xmh xfonts-100dpi xlibmesa-gl-dbg xvfb libdps-dev xfree86-common
xlibs-pic xnest libxaw7-dev xprt libdps1-dbg xserver-common libxaw6-dev
xfonts-base-transcoded libxaw7 xlibmesa-glu-dbg xspecs xfonts-base
xfonts-75dpi-transcoded xfwp libxaw6-dbg x-window-system xutils xserver-xfree86-dbg
xdm xlibmesa3-dbg xlibs xfs xlibmesa3 twm proxymngr libxaw6 xserver-xfree86
xlibmesa-dri xfonts-cyrillic xlibmesa-gl xlibmesa-glu
Architecture: source powerpc all
Version: 4.3.0-0pre1v4
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force <[EMAIL PROTECTED]>
Changed-By: Branden Robinson <[EMAIL PROTECTED]>
Description:
lbxproxy - Low Bandwidth X (LBX) proxy server
libdps-dev - Display PostScript (DPS) client library development files
libdps1- Display PostScript (DPS) client library
libdps1-dbg - Display PostScript (DPS) client library (unstripped)
libxaw6- X Athena widget set library (version 6)
libxaw6-dbg - X Athena widget set library (version 6) (unstripped)
libxaw6-dev - X Athena widget set library development files (version 6)
libxaw7- X Athena widget set library
libxaw7-dbg - X Athena widget set library (unstripped)
libxaw7-dev - X Athena widget set library development files
proxymngr - X proxy services manager
twm- Tab window manager
x-window-system - X Window System
x-window-system-core - X Window System core components
xbase-clients - miscellaneous X clients
xdm- X display manager
xfonts-100dpi - 100 dpi fonts for X
xfonts-100dpi-transcoded - 100 dpi fonts for X (transcoded from ISO 10646-1)
xfonts-75dpi - 75 dpi fonts for X
xfonts-75dpi-transcoded - 75 dpi fonts for X (transcoded from ISO 10646-1)
xfonts-base - standard fonts for X
xfonts-base-transcoded - standard fonts for X (transcoded from ISO 10646-1)
xfonts-cyrillic - Cyrillic fonts for X
xfonts-scalable - scalable fonts for X
xfree86-common - X Window System (XFree86) infrastructure
xfs- X font server
xfwp - X firewall proxy server
xlibmesa-dev - XFree86 Mesa development libraries pseudopackage
xlibmesa-dri - Mesa 3D graphics library modules [XFree86]
xlibmesa-gl - Mesa 3D graphics library [XFree86]
xlibmesa-gl-dbg - Mesa 3D graphics library (unstripped) [XFree86]
xlibmesa-gl-dev - Mesa 3D graphics library development files [XFree86]
xlibmesa-glu - Mesa OpenGL utility library [XFree86]
xlibmesa-glu-dbg - Mesa OpenGL utility library (unstripped) [XFree86]
xlibmesa-glu-dev - Mesa OpenGL utility library development files [XFree86]
xlibmesa3 - XFree86 Mesa libraries pseudopackage
xlibmesa3-dbg - XFree86 Mesa unstripped libraries pseudopackage
xlibosmesa-dev - Mesa off-screen rendering library development files [XFree86]
xlibosmesa4 - Mesa off-screen rendering library [XFree86]
xlibosmesa4-dbg - Mesa off-screen rendering library (unstripped) [XFree86]
xlibs - X Window System client libraries
xlibs-data - X Window System client data
xlibs-dbg - X Window System client libraries (unstripped)
xlibs-dev - X Window System client library development files
xlibs-pic - XFree86 static PIC libraries pseudopackage
xlibs-static-pic - X Window System client extension library PIC archives
xmh- X interface to the MH mail system
xnest - nested X server
xprt - X print server (XFree86 version)
xserver-common - files and utilities common to all X servers
xserver-xfree86 - the XFree86 X server
xserver-xfree86-dbg - the XFree86 X server (static version with debugging symbols)
xspecs - X protocol, extension, and library technical specifications
xterm - X terminal emulator
xutils - X Window System utility programs
xvfb - virtual framebuffer X server
Closes: 215997 216896
Changes:
xfree86 (4.3.0-0pre1v4) experimental; urgency=low
.
* Add missing symbolic links for libXTrap. [ISHIKAWA Mutsumi]
- debian/xlibs-dev.links: add libXTrap link
- debian/xlibs-dbg.links: add libXTrap link
.
* Restore m68k package support. Thanks, Adam Conrad!
- {MANIFEST,xserver-xfree86.docs,xserver-xfree86.install,
xutils.install}.m68k: added
.
* Add missing libXv to xlibs-dbg. [ISHIKAWA Mutsumi]
- debian/xlibs-dbg.install: add libXv.so.1.0
- debian/xlibs-dbg.links: add libXv link
.
* Grab latest fixes to upstream CVS xf-4_3-branch.
- debian/patches/000_post430.diff:
+ (xc/programs/xdm/genauth.c):
Accepted xfree86 4.3.0-0pre1v4 (powerpc all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 22 Oct 2003 00:13:12 -0500
Source: xfree86
Binary: xlibosmesa-dev libxaw7-dbg xlibs-dev xlibs-dbg xlibosmesa4-dbg xlibosmesa4
xbase-clients xlibmesa-gl-dev libdps1 xlibs-data xfonts-75dpi xfonts-100dpi-transcoded
xfonts-scalable xlibmesa-dev xlibmesa-glu-dev xterm xlibs-static-pic lbxproxy
x-window-system-core xmh xfonts-100dpi xlibmesa-gl-dbg xvfb libdps-dev xfree86-common
xlibs-pic xnest libxaw7-dev xprt libdps1-dbg xserver-common libxaw6-dev
xfonts-base-transcoded libxaw7 xlibmesa-glu-dbg xspecs xfonts-base
xfonts-75dpi-transcoded xfwp libxaw6-dbg x-window-system xutils xserver-xfree86-dbg
xdm xlibmesa3-dbg xlibs xfs xlibmesa3 twm proxymngr libxaw6 xserver-xfree86
xlibmesa-dri xfonts-cyrillic xlibmesa-gl xlibmesa-glu
Architecture: source powerpc all
Version: 4.3.0-0pre1v4
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force <[EMAIL PROTECTED]>
Changed-By: Branden Robinson <[EMAIL PROTECTED]>
Description:
lbxproxy - Low Bandwidth X (LBX) proxy server
libdps-dev - Display PostScript (DPS) client library development files
libdps1- Display PostScript (DPS) client library
libdps1-dbg - Display PostScript (DPS) client library (unstripped)
libxaw6- X Athena widget set library (version 6)
libxaw6-dbg - X Athena widget set library (version 6) (unstripped)
libxaw6-dev - X Athena widget set library development files (version 6)
libxaw7- X Athena widget set library
libxaw7-dbg - X Athena widget set library (unstripped)
libxaw7-dev - X Athena widget set library development files
proxymngr - X proxy services manager
twm- Tab window manager
x-window-system - X Window System
x-window-system-core - X Window System core components
xbase-clients - miscellaneous X clients
xdm- X display manager
xfonts-100dpi - 100 dpi fonts for X
xfonts-100dpi-transcoded - 100 dpi fonts for X (transcoded from ISO 10646-1)
xfonts-75dpi - 75 dpi fonts for X
xfonts-75dpi-transcoded - 75 dpi fonts for X (transcoded from ISO 10646-1)
xfonts-base - standard fonts for X
xfonts-base-transcoded - standard fonts for X (transcoded from ISO 10646-1)
xfonts-cyrillic - Cyrillic fonts for X
xfonts-scalable - scalable fonts for X
xfree86-common - X Window System (XFree86) infrastructure
xfs- X font server
xfwp - X firewall proxy server
xlibmesa-dev - XFree86 Mesa development libraries pseudopackage
xlibmesa-dri - Mesa 3D graphics library modules [XFree86]
xlibmesa-gl - Mesa 3D graphics library [XFree86]
xlibmesa-gl-dbg - Mesa 3D graphics library (unstripped) [XFree86]
xlibmesa-gl-dev - Mesa 3D graphics library development files [XFree86]
xlibmesa-glu - Mesa OpenGL utility library [XFree86]
xlibmesa-glu-dbg - Mesa OpenGL utility library (unstripped) [XFree86]
xlibmesa-glu-dev - Mesa OpenGL utility library development files [XFree86]
xlibmesa3 - XFree86 Mesa libraries pseudopackage
xlibmesa3-dbg - XFree86 Mesa unstripped libraries pseudopackage
xlibosmesa-dev - Mesa off-screen rendering library development files [XFree86]
xlibosmesa4 - Mesa off-screen rendering library [XFree86]
xlibosmesa4-dbg - Mesa off-screen rendering library (unstripped) [XFree86]
xlibs - X Window System client libraries
xlibs-data - X Window System client data
xlibs-dbg - X Window System client libraries (unstripped)
xlibs-dev - X Window System client library development files
xlibs-pic - XFree86 static PIC libraries pseudopackage
xlibs-static-pic - X Window System client extension library PIC archives
xmh- X interface to the MH mail system
xnest - nested X server
xprt - X print server (XFree86 version)
xserver-common - files and utilities common to all X servers
xserver-xfree86 - the XFree86 X server
xserver-xfree86-dbg - the XFree86 X server (static version with debugging symbols)
xspecs - X protocol, extension, and library technical specifications
xterm - X terminal emulator
xutils - X Window System utility programs
xvfb - virtual framebuffer X server
Closes: 215997 216896
Changes:
xfree86 (4.3.0-0pre1v4) experimental; urgency=low
.
* Add missing symbolic links for libXTrap. [ISHIKAWA Mutsumi]
- debian/xlibs-dev.links: add libXTrap link
- debian/xlibs-dbg.links: add libXTrap link
.
* Restore m68k package support. Thanks, Adam Conrad!
- {MANIFEST,xserver-xfree86.docs,xserver-xfree86.install,
xutils.install}.m68k: added
.
* Add missing libXv to xlibs-dbg. [ISHIKAWA Mutsumi]
- debian/xlibs-dbg.install: add libXv.so.1.0
- debian/xlibs-dbg.links: add libXv link
.
* Grab latest fixes to upstream CVS xf-4_3-branch.
- debian/patches/000_post430.diff:
+ (xc/programs/xdm/genauth.c):
Build fixes (Branden Robinson, Matthieu Herrb).
+ (xc/programs/xdm/session.c):
Use pam_strerror() to print an error message after pam_setcred()
fails, C style unifica
Processed: Fixed in upload of xfree86 4.3.0-0pre1v4 to experimental
Processing commands for [EMAIL PROTECTED]: > tag 215997 + fixed-in-experimental Bug#215997: xserver-xfree86: [nv] stripes when using XVideo in full-screen mode with TFT display at high resolution on NV17 [GeForce4 420 Go] rev 163 Tags were: upstream patch Tags added: fixed-in-experimental > tag 216896 + fixed-in-experimental Bug#216896: xserver-xfree86: [ati/radeon] patch needed for radeon 9200SE support Tags were: patch upstream Tags added: fixed-in-experimental > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xfree86_4.3.0-0pre1v4_powerpc.changes ACCEPTED
Accepted: lbxproxy_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/lbxproxy_4.3.0-0pre1v4_powerpc.deb libdps-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libdps-dev_4.3.0-0pre1v4_powerpc.deb libdps1-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libdps1-dbg_4.3.0-0pre1v4_powerpc.deb libdps1_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libdps1_4.3.0-0pre1v4_powerpc.deb libxaw6-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw6-dbg_4.3.0-0pre1v4_powerpc.deb libxaw6-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw6-dev_4.3.0-0pre1v4_powerpc.deb libxaw6_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw6_4.3.0-0pre1v4_powerpc.deb libxaw7-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw7-dbg_4.3.0-0pre1v4_powerpc.deb libxaw7-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw7-dev_4.3.0-0pre1v4_powerpc.deb libxaw7_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/libxaw7_4.3.0-0pre1v4_powerpc.deb proxymngr_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/proxymngr_4.3.0-0pre1v4_powerpc.deb twm_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/twm_4.3.0-0pre1v4_powerpc.deb x-window-system-core_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/x-window-system-core_4.3.0-0pre1v4_powerpc.deb x-window-system_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/x-window-system_4.3.0-0pre1v4_all.deb xbase-clients_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xbase-clients_4.3.0-0pre1v4_powerpc.deb xdm_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xdm_4.3.0-0pre1v4_powerpc.deb xfonts-100dpi-transcoded_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-100dpi-transcoded_4.3.0-0pre1v4_all.deb xfonts-100dpi_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-100dpi_4.3.0-0pre1v4_all.deb xfonts-75dpi-transcoded_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-75dpi-transcoded_4.3.0-0pre1v4_all.deb xfonts-75dpi_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-75dpi_4.3.0-0pre1v4_all.deb xfonts-base-transcoded_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-base-transcoded_4.3.0-0pre1v4_all.deb xfonts-base_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-base_4.3.0-0pre1v4_all.deb xfonts-cyrillic_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-cyrillic_4.3.0-0pre1v4_all.deb xfonts-scalable_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfonts-scalable_4.3.0-0pre1v4_all.deb xfree86-common_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xfree86-common_4.3.0-0pre1v4_all.deb xfree86_4.3.0-0pre1v4.diff.gz to pool/main/x/xfree86/xfree86_4.3.0-0pre1v4.diff.gz xfree86_4.3.0-0pre1v4.dsc to pool/main/x/xfree86/xfree86_4.3.0-0pre1v4.dsc xfs_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xfs_4.3.0-0pre1v4_powerpc.deb xfwp_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xfwp_4.3.0-0pre1v4_powerpc.deb xlibmesa-dev_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xlibmesa-dev_4.3.0-0pre1v4_all.deb xlibmesa-dri_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-dri_4.3.0-0pre1v4_powerpc.deb xlibmesa-gl-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-gl-dbg_4.3.0-0pre1v4_powerpc.deb xlibmesa-gl-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-gl-dev_4.3.0-0pre1v4_powerpc.deb xlibmesa-gl_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-gl_4.3.0-0pre1v4_powerpc.deb xlibmesa-glu-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-glu-dbg_4.3.0-0pre1v4_powerpc.deb xlibmesa-glu-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-glu-dev_4.3.0-0pre1v4_powerpc.deb xlibmesa-glu_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibmesa-glu_4.3.0-0pre1v4_powerpc.deb xlibmesa3-dbg_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xlibmesa3-dbg_4.3.0-0pre1v4_all.deb xlibmesa3_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xlibmesa3_4.3.0-0pre1v4_all.deb xlibosmesa-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibosmesa-dev_4.3.0-0pre1v4_powerpc.deb xlibosmesa4-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibosmesa4-dbg_4.3.0-0pre1v4_powerpc.deb xlibosmesa4_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibosmesa4_4.3.0-0pre1v4_powerpc.deb xlibs-data_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xlibs-data_4.3.0-0pre1v4_all.deb xlibs-dbg_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibs-dbg_4.3.0-0pre1v4_powerpc.deb xlibs-dev_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibs-dev_4.3.0-0pre1v4_powerpc.deb xlibs-pic_4.3.0-0pre1v4_all.deb to pool/main/x/xfree86/xlibs-pic_4.3.0-0pre1v4_all.deb xlibs-static-pic_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibs-static-pic_4.3.0-0pre1v4_powerpc.deb xlibs_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xlibs_4.3.0-0pre1v4_powerpc.deb xmh_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xmh_4.3.0-0pre1v4_powerpc.deb xnest_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree86/xnest_4.3.0-0pre1v4_powerpc.deb xprt_4.3.0-0pre1v4_powerpc.deb to pool/main/x/xfree8
xfree86 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): xlibs-pic_4.3.0-0pre1v4_all.deb: package says section is oldlibs, override says libdevel. xlibs-pic_4.3.0-0pre1v4_all.deb: package says priority is extra, override says optional. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 217052 to xbase-clients: [xwd] would like feature to take multiple screenshots ...
Processing commands for [EMAIL PROTECTED]: > retitle 217052 xbase-clients: [xwd] would like feature to take multiple screenshots Bug#217052: /usr/X11R6/bin/xwd: should be able to take more than one snapshot Changed Bug title. > tag 217052 + upstream Bug#217052: xbase-clients: [xwd] would like feature to take multiple screenshots Tags were: patch Tags added: upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Some patches for XFree86/experimental
I apologize : I just realized that I have sent the wrong (uncompressed) versions for patches 914 and 915 and 914 is around 400KB. :-( Please let me know if by luck my previous mail was blocked by the list-manager and I'll resent a compressed version. V. I wrote: Hello, I just installed the exec-shield kernel patch on my computer, and it turns out that XFree86 on Debian refuses to work without some fixes. Attached are 4 patches against XFree4.3 in experimental (snapshot from http://necrotic.deadbeast.net/xfree86/branches-4.3.0-sid-debian-2003.10.21.tar.gz) fixing various issues: * 912_elfloader_linux_non_exec_stack_v2.diff : This patch comes from the Redhat rawhide 4.3.0.40 source package (original name: XFree86-4.3.0-elfloader-linux-non-exec-stack-v2.patch). It fixes the xfree86 loader on linux to work with a non-exec stack (exec-shield kernel patch). * 913_patch_compile_kernel_26.diff : Simple patch to allow compilation with 2.6 kernel includes (found using google). * 914_redhat_libGL_opt_v2.diff & 915_redhat_libGL_exec_shield_fixes_v2.diff Patches from Redhat (XFree86-4.3.0-redhat-libGL-opt-v2.patch and XFree86-4.3.0-redhat-libGL-exec-shield-fixes-v2.patch) to fix libGL with exec-shield. It looks like the second one depends from the first one, that's why I had to include it... Please note that patches 914 and 915 require backing out 062_make_libGL_PIC_compliant.diff and that I have not tested them, except for the fact that they apply fine (I don't use any GL app). Patches 912 & 913 were compile and run-time tested by me. Both look fairly simple and unintrusive (in contrary to 914 and 915). Thus I'd like to know if it would be possible to have at least patches 912 and 913 applied to the packages in experimental ? With best regards, Vincent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#217068: xserver-xfree86: X won't run, unknown reason
Package: xserver-xfree86 Version: 4.2.1-12.1 Severity: grave Justification: renders package unusable I am not exactly sure where the problem lies on this one. I normally just upgrade a package or two as need be. I had just upgraded a bunch of KDE stuff, and so closed all X sessions and then let apt-get install everything. After apt-get was finished, gdm could not start the login session for a user which had KDE (Debian) as the session manager. Since then, every attempt to start X has failed. [Update, I have now gotten X to run from kdm (gdm still dies). Tale of the story below. I don't know if you want to adjust the severity level as things now run, but without reconfiguring X and switching from gdm to kdm I would still not be running. Whatever the problem is, mozilla/galeon is now broken. ] The first possibility I looked at, was that the last error showing in the logs or ~/.xsession-errors dealt with /dev/input/mice. Since I don't have a USB mouse, I first tried creating /dev/input and making mice a symlink to /dev/ttyS0 (I should have used /dev/psaux in after thought). There were also messages about some missing symbols in libGLcore.a and libspeedo.a. X still wouldn't start. I then edited ~/.gnome2/gdm so that it wouldn't use "Debian" (KDE) as the window manager. This didn't help. I then started editing /etc/X11/XF86Config-4 (as you can see below). I started by editing out the font path to speedo, and the modules load stuff for speedo and GLcore. Trying to startx again, I got another error which led me to trying to also comment out glx, leaving me at the config you see below. This still doesn't work. I have known for a while, that the management of the configuration for X has changed in Debian (to what it has now). I don't remember as to whether there were any minor problems in the transition. After the first edit to /etc/X11/XF86Config-4, I followed the instructions at the top of the file vis a vis saving a custom configuration. I am getting a DeprecationWarning about xreadlines when I do this (dpkg-reconfigure xserver-xfree86) followed by a configlet in path is bad. (I wonder where debconf got a screen size of 17"? This monitor is 21", and has always been here.) Other people in my lug have suggested things. Some kind of problem with libfreetype6 conflicting with gsfonts-other. I've looked in bug reports for xserver-xfree86, libfreetype6, gsfonts-other and see nothing which really looks similar to this problem, with a recent time frame. Well, there is one report, which was closed because a virus was found in a followup message? I'll try reconfiguring all of X (xserver-xfree86) with xf86cfg and then purging gsfonts-other, and after that installing older versions of xserver-xfree86. If you have suggestions as to how to trace things (as I am not receiving error messages now, but it still won't start) or where the problem lies, I'ld be happy to hear them. Running xf86cfg (after moving /etc/X11/XF86Config-4 aside), I went through the configuration process, setting values to what they should be for keyboard, mouse, card and monitor. When I go to save things, it asks if I want to write /usr/X11R6/lib/X11/XF86Config. I can't say I've seen that location for a X config file before. :-) Okay, change it to /etc/X11/XF86Config-4. Now it wants to write a keyboard config file to lib/X11/xkb/X0-config.keyboard. No idea what the leading directory is, and my system never had a X0-config.keyboard file before. /etc/X11/xkb doesn't contain any files like this, nor does it seem to be the place to put this. And there is no /etc/X11/lib. Since /usr/X11R6/lib/X11/xkb seems to be a symlink to /etc/X11/xkb, I guess I can let it write this file and see if PWD is pointing to /usr/X11R6. If I run X -probeonly after reconfiguring with xf86cfg, I again get these symbol errors: Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o": No symbols found Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found Other than those 2 Skipping ... messages, everything in /var/log/XFree86.0.log looks normal. startx succesfully starts X, gdm still won't start X (tries 4 times and quits). Nothing strange (besides the Skipping ... messages) in XFree86.0.log or gdm/:0.log. Editing /etc/init.d/kdm to change the HEED_DEFAULT_DISPLAY_MANAGER to false, I find that kdm will work, and both X and KDE seem to start okay. -- Package-specific info: 01:05.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) 01:05.0 Class 0300: 10de:0110 (rev b2) # XF86Config-4 (XFree86 X server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of
Processed: oops
Processing commands for [EMAIL PROTECTED]: > forwarded 198385 [EMAIL PROTECTED] Bug#198385: xpdf should be able to read pdf's from STDIN Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] > reassign 198386 xserver-xfree86 Bug#198386: xserver-xfree86: [vesa] driver slows down system clock on S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] Bug reassigned from package `xpdf-reader' to `xserver-xfree86'. > reassign 198385 xpdf-reader Bug#198385: xpdf should be able to read pdf's from STDIN Bug reassigned from package `xpdf' to `xpdf-reader'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: cleanup3
Processing commands for [EMAIL PROTECTED]: > reassign 198386 xpdf-reader Bug#198386: xserver-xfree86: [vesa] driver slows down system clock on S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] Bug reassigned from package `xserver-xfree86' to `xpdf-reader'. > reassign 205208 xpdf-reader Bug#205208: xpdf: Find input should resize on dialog box resize Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 174990 xpdf-reader Bug#174990: xpdf: Automatic handling of .pdf.gz files would be nice Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 184070 xpdf-reader Bug#184070: xpdf does not show the text in one PDF Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 185950 xpdf-reader Bug#185950: xpdf: Gfx::doImage doesn't deal correctly with ImageMask Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 188532 xpdf-reader Bug#188532: xpdf: punctuation disappears in this PDF file Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 211887 xpdf-reader Bug#211887: Missing manpage for xpdf.bin Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 212990 xpdf-reader Bug#212990: xpdf: segfaults Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 194124 xpdf-common Bug#194124: Backup files and RCS files should be ignored by update-xpdfrc Bug reassigned from package `xpdf' to `xpdf-common'. > reassign 200466 xpdf-reader Bug#200466: xpdf: Should remember last print command after document reload Bug reassigned from package `xpdf' to `xpdf-reader'. > reassign 179015 xpdf-reader Bug#179015: xpdf: Correction for /etc/mailcap? Bug reassigned from package `xpdf' to `xpdf-reader'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#217052: /usr/X11R6/bin/xwd: should be able to take more than one snapshot
Package: xbase-clients
Version: 4.2.1-12.1
Severity: wishlist
File: /usr/X11R6/bin/xwd
Tags: patch
Bonjour,
I would like to take snapshots of an animated window.
Searching the net, I could not find a program to do so. But I found
evidence that other people where looking for the same functionnality.
It is possible but very slow to use a shell loop to do so. I could
whip a small patch to enable this feature. I you are interested, I
maybe could update the man page.
The new option are :
-n number of snapshots (defaults to 1)
-w number of microseconds to wait between snapshots
-out file is now mandatory if more than one snapshots are to be taken.
It is then prefixed with the image number.
Be indulgent with my code, I haven't coded in C for ages.
I could be more efficient, but I went for the simple approach.
Hoping to be helpful,
Bernard
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages xbase-clients depends on:
ii cpp-3.2 1:3.2.3-8 The GNU C preprocessor
ii libc6 2.3.2-8GNU C Library: Shared
libraries an
ii libdps1 4.2.1-12.1 Display PostScript (DPS)
client li
ii libfreetype6 2.1.5-2FreeType 2 font engine,
shared lib
ii libncurses5 5.3.20030719-3 Shared libraries for
terminal hand
ii libxaw7 4.2.1-12.1 X Athena widget set
library
ii xlibmesa3-gl [libgl1] 4.2.1-12.1 Mesa 3D graphics library
[XFree86]
ii xlibmesa3-glu [libglu1] 4.2.1-12.1 Mesa OpenGL utility
library [XFree
ii xlibs 4.2.1-12.1 X Window System client
libraries
-- debconf information:
* xbase-clients/default_100dpi:
* xbase-clients/default_nolisten_tcp:
--- xwd.c 2002-09-19 02:19:56.0 +0200
+++ myxwd.c 2003-10-22 14:50:13.0 +0200
@@ -1,5 +1,4 @@
/* $Xorg: xwd.c,v 1.5 2001/02/09 02:06:03 xorgcvs Exp $ */
-
/*
Copyright 1987, 1998 The Open Group
@@ -70,7 +69,8 @@
#include
#include
#include
-
+#include
+#include
#include
#include
@@ -108,10 +108,36 @@
extern int Get_XColors(XWindowAttributes *, XColor **);
extern void _swapshort(register char *, register unsigned);
extern void _swaplong(register char *, register unsigned);
+static char *make_filename(char *, long, long);
static long parse_long(char *);
static int Get24bitDirectColors(XColor **);
static int ReadColors(Visual *, Colormap, XColor **);
+/*
+ * If necessary (limit >1), prefixes filename with numbers starting from 0.
+ * Number of digits is computed to represent the maximum value.
+ */
+
+static char *make_filename(char *filename, long current, long limit){
+ /*
+ * if only one take, filename is to be used unprefixed
+ */
+ if (limit == 1)
+return strdup(filename);
+ /*
+ * compute number of digit to represent (max-1)
+ * I know it's dumb to recompute nb_digits and realloc result every time
+ */
+ int nb_digits=1;
+ long i;
+ for(i=10; i = argc) usage();
- if (!(out_file = fopen(argv[i], "wb")))
- Fatal_Error("Can't open output file as specified.");
+ filename=argv[i];
standard_out = False;
continue;
}
@@ -181,6 +208,16 @@
add_pixel_value = parse_long (argv[i]);
continue;
}
+ if (!strcmp(argv[i], "-w")){
+ if (++i >= argc) usage();
+ wait_value = parse_long (argv[i]);
+ continue;
+ }
+ if (!strcmp(argv[i], "-n")){
+ if (++i >= argc) usage();
+ nb_takes = parse_long (argv[i]);
+ continue;
+ }
if (!strcmp(argv[i], "-frame")) {
frame_only = True;
continue;
@@ -195,6 +232,10 @@
if (standard_out)
_setmode(fileno(out_file), _O_BINARY);
#endif
+/*
+ * Standard output is not allowed if nb_takes >1
+ */
+if( standard_out && (nb_takes >1)) usage();
/*
* Let the user select the target window.
@@ -214,18 +255,29 @@
target_win = XmuClientWindow (dpy, target_win);
}
}
-
-
-/*
- * Dump it!
- */
-Window_Dump(target_win, out_file);
-
-XCloseDisplay(dpy);
-if (fclose(out_file)) {
+long current_take;
+for(current_take=0; current_take != nb_takes; ++current_take){
+if (!standard_out){
+ char *current_filename=make_filename(filename, current_take, nb_takes);
+ if (!(out_file = fopen(current_filename, "wb")))
+ Fatal_Error("Can't open output file as specified.");
+ free(current_filename);
+ }
+
+ /*
+ * Dump it!
+ */
+
+ Window_Dump(target_win, out_file);
+
+ if (fclose(out_file)) {
perror("xwd");
exit(1);
+ }
+ if(wait_value)
+ usleep(wait_value);
}
+XCloseDisplay(dpy);
exit(0);
}
@@ -535,7 +587,8 @@
fprintf (stderr,
"usage: %s [-display host:dpy] [-debug] [-help] %s [-nobdrs] [-out ]",
prog
Bug#131155: xterm: -fa is respected, but provided font is ignored without error message
Hi! Marc Wilson schrieb: > On Sat, Oct 11, 2003 at 02:56:32PM +0200, Friedrich Delgado Friedrichs wrote: > > This also doesn't explain why the font looks so ugly. Every character > > is in the upper left region of a rectangular box, with quite a lot of > > space between the characters. > This sounds more like you don't have any monospaced font that your xft > configuration can fall back to, and it's substituting a proportional > one. Nope, that looks different. > Snerf around the 'net and find a copy of the 'Andale Mono' or > 'Monotype.com' TTF fonts. They'll look pretty good for you. I have the Andale Mono font installed... Ok, I'll attach a screenshot now, to clarify this. The attached screenshot was taken from a line of /usr/X11R6/bin/xterm -fa "andale mono" -fs 10 The displayed font is in no way Andale Mono (the digit '0' in Andale Mono has a small dot in the middle). I have to clarify that the horizontal spacing seems to be correct, but the vertical spacing seems to be too large in comparison to the letters. In this way I need to give "-fs 10" in order to get the same amount of lines into an xterm with the same physical geometry and the '-misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1' font. Kind regards Friedel -- Friedrich Delgado Friedrichs <[EMAIL PROTECTED]> <>
Play time yg
Receive an absolutely free 3 day 2 night vaction voucher to your choice of several fantastic destinations around the world. Think this is too good to be true? Hotels frequently give away free rooms in order to get you in their hotels hoping you will spend money on their services. Visit the link to claim yours http://best-deals2u.biz/tnl/ Update list preference: best-deals2u.biz/re Applicant said if he was hired he would demonstrate his loyalty by having the corporate logo tattooed on his forearm.,"`How do you feel?' he asked him. "Why aren't you in a more interesting business?" "`The best way to get a drink out of a Vogon is to stick your finger down his throat...'" pmnf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#216994: libvte-common: new libvte changes gnome-terminal font size
Processing commands for [EMAIL PROTECTED]: > reopen 216994 Bug#216994: libvte-common: new libvte changes gnome-terminal font size Bug is already open, cannot reopen. > reassign 216994 libxrender1 Bug#216994: libvte-common: new libvte changes gnome-terminal font size Bug reassigned from package `libvte-common' to `libxrender1'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#216994: libvte-common: new libvte changes gnome-terminal font size
reopen 216994 reassign 216994 libxrender1 thanks Duraid Madina <[EMAIL PROTECTED]> writes: [Please respect the Carboin copy to the BTS] > A screenshot is attached. This bug is related to xrender downgrading to 0.8.3-2 solve this bug. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#215997: stripes in full-screen mode (XVideo, nv, NV17, TFT, XGA)
#include * Branden Robinson [Tue, Oct 21 2003, 05:20:50PM]: > > > Thanks! > > > > Okay, and do you intend to apply it? I cannot see the pending tag... > > If not, what is the reason? > > Would you settle down? The pending tag is not applied until after a fix > is actually committed to the repo. I haven't even confirmed that the > patch applies cleanly or doesn't break the build yet. Okay, that is the answer I wished to see. Nothing more, nothing less. MfG, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
