Re: proposed X Strike Force commit/changelog policy
On Tue, Jun 10, 2003 at 10:31:40PM -0500, Branden Robinson wrote: On Wed, Jun 11, 2003 at 08:49:32AM +1000, Daniel Stone wrote: On Tue, Jun 10, 2003 at 12:22:01PM -0500, Branden Robinson wrote: The goal is NOT to make the package changelogs less massive. The goal is to make them more useful. My package changelogs have been doing double-duty for years because I didn't have them under revision control. Now they simply need to do what a changelog should do -- log changes. That's what I meant, really. Right now, some of the changelogs (like the 293-line changelog for 4.3.0-0ds4) are pretty unnavigable. Well, I rudely purged your changelog entries from the 4.3.0/sid branch, so I don't see them and they don't bother me. :) Well, yeah. Behold, an example. :P -- Daniel Stone [EMAIL PROTECTED] [EMAIL PROTECTED] KDE: Konquering a desktop near you - http://www.kde.org pgp0.pgp Description: PGP signature
Re: -pre1v1 (from DanielS) m68k build logs (failure)
On Wed, 11 Jun 2003, Daniel Stone wrote: My money's on groff screwing up, but we really need to see for ourselves what's going on - if we could get the output of those commands done separately, it'd be nice. Fabio, have you purged your builddir already? If not, could you please run the commands separately and get any error output? Confirmed... groff dies without any error message. Fabio -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree86's HasLinuxInput symbol and m68k
On Tue, 10 Jun 2003, Branden Robinson wrote: But it's true, my Mac does not boot with 2.4.20, and yours probably neither. Its just none of the mac users noticed yet. And I have no reports about Atari, and the three VMEs. Is it important for XFree86, I mean will 4.3 only work with a 2.4 kernel? I heard Ray Knight is trying to get some improvements from the powerpc kernel. If somebody can make it work on Macs, its Ray... Please don't freak about this. That symbol has very limited effect: My post was more paranoid than anything else. I was sure you evaluated the impact already. Thanks Fabio -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: proposed X Strike Force commit/changelog policy
On Tue, Jun 10, 2003 at 02:20:45PM -0400, Joey Hess wrote: Branden Robinson wrote: * When doing a commit that should be logged in the debian/changelog file, edit the debian/changelog file before doing the commit and commit the change to it along with the rest of your change set. As a point of interest, do you ever find yourself working on more than one thing at a time in the same checkout, and how do you juggle the debian/changelog changes then? I tend to changelog everything I do as I do it, then when I'm about to commit I copy the working changelog aside and trim debian/changelog down so that the diff shows only one changeset. After I commit, I move the working changelog back. * Here's a new one that I myself didn't realize was important until this morning: always include the name of each file being changed in your commit log. This seems redundant until you realize that svn log operations can be run on directories. Of course subversion knows what files that change touched. This sounds more like a deficiency of svn log; it should be able to list the files. It can; use the -v option. I do tend to err towards verbose log messages anyway, though. What do you guys think? I'm not part of your team, but I have some interest in subversion and some of the same issues, so pardon me for weighing in.. Ditto. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: X Strike Force SVN commit: rev 175 - branches/4.3.0/sid/debian
Branden, Is this part still needed? + * #003_linux.cf_and_xfree86.cf.diff: +- Always disable `FontLibSharedFreeType' for compatiblity between + normal XFree86 server and XFree86-dbg server. + We should drop this change, when we can build the Loader Server + liked against external FreeType2 [ISHIKAWA Mutsimi] + The offending cvs changes were regressed out in the latest 2.1.4-4 freetype package. The compilation error doesn't occur anymore when building last weeks XFree86 4.3.0-0pre1v1 and the resulting XFree86 packages seem to work fine. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X Strike Force SVN commit: rev 175 - branches/4.3.0/sid/debian
In [EMAIL PROTECTED] Jack Howarth [EMAIL PROTECTED] wrote: Branden, Is this part still needed? + * #003_linux.cf_and_xfree86.cf.diff: +- Always disable `FontLibSharedFreeType' for compatiblity between + normal XFree86 server and XFree86-dbg server. + We should drop this change, when we can build the Loader Server + liked against external FreeType2 [ISHIKAWA Mutsimi] + The offending cvs changes were regressed out in the latest 2.1.4-4 freetype package. The compilation error doesn't occur anymore when building last weeks XFree86 4.3.0-0pre1v1 and the resulting XFree86 packages seem to work fine. There are two purposes in this change. 1) FreeType2 incompatible problem between freetype 2.1.4-2 and 2.1.4-3, you described above. It is solved by freetype2_2.1.4-4 package. 2) We would like to use same FreeType2 code between Normal Loader X Server (included in xserver-xfree86 package) and Static build Debug X server (included in xserver-xfree86-dbg. Static build X server can build with external shared FreeType2 library, but curretly we can not build X loader server with external FreeType2 shared library(X loader server's freetype font backend module uses `source code level inclusion' scheme of FreeType2). FreeType2 code included in xfree86 source tree and libfreetype6's one are not same (diffrent version and too difficult to sync..), so if debug X server linked with external FreeType2 and normal loader server does not, we can not debug X server internal FreeType2 related thigs. Yes, 1) problem is gone. But 2) problem is remaing. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree86's HasLinuxInput symbol and m68k
On Tue, Jun 10, 2003 at 10:54:36PM -0500, Branden Robinson wrote:
#ifdef LINUX_INPUT
if (xf86SetBoolOption(local-options, USB, (common-wcmOpen ==
xf86WcmUSBOpen))) {
local-read_input=xf86WcmReadUSBInput;
common-wcmOpen=xf86WcmUSBOpen;
xf86Msg(X_CONFIG, %s: reading USB link\n, dev-identifier);
#else
if (xf86SetBoolOption(local-options, USB, 0)) {
ErrorF(The USB version of the driver isn't available for your
platform\n);
#endif
Will it kill anyone to have this code in the XFree86 packages for m68k?
No USB on m68k as far as I know (I can hear already the shouts but there
is this cool USB Adapter for Amiga), so this should never be executed on
m68k. Maybe not even compiled (I did not read the code too thoroughly).
Christian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GCC Bug affecting KDM
I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. If you wish to reply to me, you must CC me. Peace Love, David Meiser __ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree86's HasLinuxInput symbol and m68k
On Wed, 11 Jun 2003, Christian T. Steigies wrote:
On Tue, Jun 10, 2003 at 10:54:36PM -0500, Branden Robinson wrote:
#ifdef LINUX_INPUT
if (xf86SetBoolOption(local-options, USB, (common-wcmOpen ==
xf86WcmUSBOpen))) {
local-read_input=xf86WcmReadUSBInput;
common-wcmOpen=xf86WcmUSBOpen;
xf86Msg(X_CONFIG, %s: reading USB link\n, dev-identifier);
#else
if (xf86SetBoolOption(local-options, USB, 0)) {
ErrorF(The USB version of the driver isn't available for your
platform\n);
#endif
Will it kill anyone to have this code in the XFree86 packages for m68k?
No USB on m68k as far as I know (I can hear already the shouts but there
is this cool USB Adapter for Amiga), so this should never be executed on
m68k. Maybe not even compiled (I did not read the code too thoroughly).
The input core does compile on m68k if you really want to, but no devices use
it (for now). So as soon as we get this USB support, the input core will be
ready ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X Strike Force SVN commit: rev 177 - in branches/4.3.0/sid/debian: . patches
Author: ishikawa Date: 2003-06-11 10:29:35 -0500 (Wed, 11 Jun 2003) New Revision: 177 Modified: branches/4.3.0/sid/debian/changelog branches/4.3.0/sid/debian/patches/003_linux.cf_and_xfree86.cf.diff branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff Log: remove special-case logic in linux.cf that defined HasLinuxInput to NO for Mc68020Architecture (sync with svn trunk/debian revision 176) #003_linux.cf_and_xfree86.cf.diff: - remove special-case logic in linux.cf that defined HasLinuxInput to NO for Mc68020Architecture; m68k is now supported by the Linux 2.4.20 kernel (at least in Debian), so we let this symbol be defined to YES just like all the other architectures. This only really affects the Wacom input driver and should not cause any regressions. (thanks to James Troup for pointing out this no-longer-needed conditional) #004_imake_manpage_handling_overhaul.diff: - line offset adjust with #003 change Modified: branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff == --- branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff 2003-06-11 04:43:13 UTC (rev 176) +++ branches/4.3.0/sid/debian/patches/004_imake_manpage_handling_overhaul.diff 2003-06-11 15:29:35 UTC (rev 177) @@ -305,7 +305,7 @@ /* The TT/Meltho fonts are all under non-free licenses. */ # define BuildTrueTypeFonts NO # define BuildBethMarduthoFonts NO -@@ -971,26 +971,6 @@ +@@ -968,26 +968,6 @@ # define ConnectionFlags -DUNIXCONN -DTCPCONN #endif Modified: branches/4.3.0/sid/debian/patches/003_linux.cf_and_xfree86.cf.diff == --- branches/4.3.0/sid/debian/patches/003_linux.cf_and_xfree86.cf.diff 2003-06-11 04:43:13 UTC (rev 176) +++ branches/4.3.0/sid/debian/patches/003_linux.cf_and_xfree86.cf.diff 2003-06-11 15:29:35 UTC (rev 177) @@ -49,8 +49,8 @@ # endif #endif xc/config/cf/linux.cf.orig Fri Jan 3 11:54:53 2003 -+++ xc/config/cf/linux.cf Fri Jan 3 11:56:08 2003 +--- xc/config/cf/linux.cf.orig 2003-06-11 23:55:12.0 +0900 xc/config/cf/linux.cf 2003-06-12 00:01:31.0 +0900 @@ -87,17 +87,23 @@ XCOMM binutils: (LinuxBinUtilsMajorVersion) @@ -77,7 +77,7 @@ # define XF86SetupUsesStaticTcl NO /* un-comment this when it is un-broken */ /* # define JoystickSupport YES */ -@@ -146,10 +152,55 @@ +@@ -146,14 +152,56 @@ # define SpecsDocDirsCTEXT GL ICCCM X11 Xext Xv i18n xterm # define BuildRman NO # define BuildHtmlManPages NO @@ -118,6 +118,10 @@ /* we build-depend on libfreetype6-dev (FreeType 2.x) */ # define BuildFreetype2Library NO # define HasFreetype2 YES +-/* m68k has no 2.4 kernel yet */ +-# ifndef Mc68020Architecture +-#define HasLinuxInput YES +-# endif + +/* + We need to build both XFree86 server (loader server) and XFree86-dbg @@ -130,10 +134,11 @@ +*/ +# define FontLibSharedFreeType NO + - /* m68k has no 2.4 kernel yet */ - # ifndef Mc68020Architecture - #define HasLinuxInput YES -@@ -701,7 +714,7 @@ ++# define HasLinuxInput YES + # define HasXdmAuth YES + # define HasLatex YES + /* at present, glide2 only works on i386 */ +@@ -701,7 +749,7 @@ #if UseElfFormat # ifndef DoLoadableServer @@ -142,7 +147,7 @@ # define DoLoadableServer NO # else # define DoLoadableServer YES -@@ -746,7 +759,7 @@ +@@ -746,7 +794,7 @@ #ifdef AlphaArchitecture # ifndef OptimizedCDebugFlags @@ -151,7 +156,7 @@ # endif # define LinuxMachineDefines -D__alpha__ # define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET -@@ -759,7 +772,7 @@ +@@ -759,7 +807,7 @@ #ifdef Arm32Architecture # define DefaultCCOptions -fsigned-char # ifndef OptimizedCDebugFlags @@ -160,7 +165,7 @@ # endif # define LinuxMachineDefines -D__arm__ -D__arm32__ -U__arm -Uarm # define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET -@@ -767,7 +780,7 @@ +@@ -767,7 +815,7 @@ #endif /* Arm32Achitecture */ #ifdef HPArchitecture @@ -169,7 +174,7 @@ # define LinuxMachineDefines -D__hppa__ # define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET # define ServerExtraDefines -DGCCUSESGAS XFree86ServerDefines -@@ -775,7 +788,7 @@ +@@ -775,7 +823,7 @@ #ifdef i386Architecture # ifndef OptimizedCDebugFlags @@ -178,7 +183,7 @@ # endif # define LinuxMachineDefines -D__i386__ # define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET -@@ -784,7 +797,7 @@ +@@ -784,7 +832,7 @@ #ifdef ia64Architecture # ifndef OptimizedCDebugFlags @@ -187,7 +192,7 @@ # endif # define LinuxMachineDefines -D__ia64__ #
dpkg error (while performing dist-upgrade)
Hello, I tried to upgrade my Debian distribution but following happened during the configuration process. I was instructed to e-mail the error report here. --- ... ... Setting up xbase-clients (4.2.1-3) ... ERROR: /usr/X11R6/lib/X11/xinit symbolic link does not exist. Either the package didn't ship the symbolic link (a bug in the package), or dpkg failed to unpack it to the filesystem (a bug in dpkg). Please report the package name, version, and the text of the above error message(s) to [EMAIL PROTECTED]. dpkg: error processing xbase-clients (--configure): subprocess post-installation script returned error exit status 1 --- So, could you tell me if the package is broken or is it just my system that is causing problems? Thanks in advance. Best regards, Tero Laitinen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#197058: xserver-xfree86: [savage] XVideo broken - blue window
Package: xserver-xfree86 Version: 4.2.1-8 Severity: normal As promised on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185403, now that it has reached sid, I file a bug. When trying to use XVideo on an IBM Thinkpad T21, instead of the movie, I have uniform blue. Tim Roberts' driver version 1.27t, which I was using before, doesn't have this problem: XVideo works fine. Tim Roberts page: http://www.probo.com/timr/savage40.html http://www.probo.com/timr/savage-1.1.27t.zip -- Package-specific info: 01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11) 01:00.0 Class 0300: 5333:8c12 (rev 11) ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 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.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/CID FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc102 Option XkbLayout intl Option XkbOptionsinet:thinkpad EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/misc/psaux Option Protocol PS/2 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 EndSection Section Device Identifier Thinkpad S3 Savage/IX-MV Driver savage EndSection Section Monitor Identifier Thinkpad LCD HorizSync 30-200 VertRefresh 50-100 Option DPMS EndSection Section Screen Identifier Default Screen Device Thinkpad S3 Savage/IX-MV Monitor Thinkpad LCD DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Generic Mouse EndSection Section DRI Mode0666 EndSection ### END DEBCONF SECTION This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.1.1 (Debian 4.2.1-8 20030609132746
Re: GCC Bug affecting KDM
On Wed, Jun 11, 2003 at 10:56:36AM -0400, [EMAIL PROTECTED] wrote: I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. Well, that's just not possible, according to Jack Howarth. :-P :-P :-P Would one of the committers like to merge revisions 162 and 171 onto branches/4.3.0/sid? -- G. Branden Robinson| Never underestimate the power of Debian GNU/Linux | human stupidity. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | pgp0.pgp Description: PGP signature
Re: -pre1v1 (from DanielS) m68k build logs (failure)
On Wed, Jun 11, 2003 at 10:42:59AM +0200, Fabio Massimo Di Nitto wrote: On Wed, 11 Jun 2003, Daniel Stone wrote: My money's on groff screwing up, but we really need to see for ourselves what's going on - if we could get the output of those commands done separately, it'd be nice. Fabio, have you purged your builddir already? If not, could you please run the commands separately and get any error output? Confirmed... groff dies without any error message. Sounds like you need to make Colin Watson unhappy, then. (I.e., file a bug report against groff.) -- G. Branden Robinson|The basic test of freedom is Debian GNU/Linux |perhaps less in what we are free to [EMAIL PROTECTED] |do than in what we are free not to http://people.debian.org/~branden/ |do. -- Eric Hoffer pgp0.pgp Description: PGP signature
XFree86 X server and FreeType
On Wed, Jun 11, 2003 at 11:22:00PM +0900, ISHIKAWA Mutsumi wrote: There are two purposes in this change. 1) FreeType2 incompatible problem between freetype 2.1.4-2 and 2.1.4-3, you described above. It is solved by freetype2_2.1.4-4 package. 2) We would like to use same FreeType2 code between Normal Loader X Server (included in xserver-xfree86 package) and Static build Debug X server (included in xserver-xfree86-dbg. Static build X server can build with external shared FreeType2 library, but curretly we can not build X loader server with external FreeType2 shared library(X loader server's freetype font backend module uses `source code level inclusion' scheme of FreeType2). FreeType2 code included in xfree86 source tree and libfreetype6's one are not same (diffrent version and too difficult to sync..), so if debug X server linked with external FreeType2 and normal loader server does not, we can not debug X server internal FreeType2 related thigs. Yes, 1) problem is gone. But 2) problem is remaing. Okay, just to make sure I understand the situation: 1) we want to be sure that the normal X server package (xserver-xfree86) and the debugging X server package (xserver-xfree86-dbg) use the same FreeType library. 2) we'd *like* it if we could achieve this by both packages dynamically linking against the system's FreeType library; however, 3) The normal X server package (xserver-xfree86) *cannot* be built dynamically linked against the FreeType library because of upstream code/design issues; 4) Therefore, we encapsulate XFree86's internal fork of the FreeType library into *both* xserver-xfree86 and xserver-xfree86-dbg. Have I got that correct? -- G. Branden Robinson| There's nothing an agnostic can't Debian GNU/Linux | do if he doesn't know whether he [EMAIL PROTECTED] | believes in it or not. http://people.debian.org/~branden/ | -- Graham Chapman pgp0.pgp Description: PGP signature
X Strike Force SVN commit: rev 178 - branches/4.3.0/sid/debian
Author: branden Date: 2003-06-11 14:10:38 -0500 (Wed, 11 Jun 2003) New Revision: 178 Modified: branches/4.3.0/sid/debian/changelog Log: * debian/changelog: stop putting trailing whitespace in my changelog! Modified: branches/4.3.0/sid/debian/changelog == --- branches/4.3.0/sid/debian/changelog 2003-06-11 15:29:35 UTC (rev 177) +++ branches/4.3.0/sid/debian/changelog 2003-06-11 19:10:38 UTC (rev 178) @@ -14,7 +14,7 @@ - m68k is now supported by the Linux 2.4.20 kernel (at least in Debian), so we let this symbol be defined to YES just like all the other architectures. This only really affects the Wacom input driver - and should not cause any regressions. + and should not cause any regressions. (thanks to James Troup for pointing out this no-longer-needed conditional) - patch #003 update - sync with trunk/debian svn revision 176 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree86's HasLinuxInput symbol and m68k
On Wed, Jun 11, 2003 at 05:12:56PM +0200, Geert Uytterhoeven wrote: The input core does compile on m68k if you really want to, but no devices use it (for now). So as soon as we get this USB support, the input core will be ready ;-) The 2.4.x version of ADB support depends on the input core, so it will be needed whenever the m68k Mac support is fixed. The old drivers for ADB in 2.2.x were a custom hack, and while they hung around as an option in the move to 2.4, I would hope that someone will get the newer ADB code running eventually. Brad Boyer [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: -pre1v1 (from DanielS) m68k build logs (failure)
On Wed, 11 Jun 2003, Branden Robinson wrote: On Wed, Jun 11, 2003 at 10:42:59AM +0200, Fabio Massimo Di Nitto wrote: On Wed, 11 Jun 2003, Daniel Stone wrote: My money's on groff screwing up, but we really need to see for ourselves what's going on - if we could get the output of those commands done separately, it'd be nice. Fabio, have you purged your builddir already? If not, could you please run the commands separately and get any error output? Confirmed... groff dies without any error message. Sounds like you need to make Colin Watson unhappy, then. (I.e., file a bug report against groff.) He is already aware of the problem and we (Daniel and me) provided him all the info he asked for, but yes opening a bug for tracking it is a good idea anyway. Fabio -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
backing store not enabled by default?
Looking for an education... On hpux 11.11 the following produces: xdpyinfo | grep backing options:backing-store YES, save-unders YES In woody the following produces: xdpyinfo | grep backing options:backing-store NO, save-unders NO Which appears to mean that application requests such as the following have no effect. (This is very old code and I am not an X11 programmer so I will just assume up front that some types will have changed.) XSetWindowAttributes attr; unsigned long vm = CWBackingStore; attr.backing_store = Always; XChangeWindowAttributes(XtDisplay(graphics),XtWindow(graphics),vm,attr); Which means that at least this application does not get any backing store and is very slow when processing window events. This application is an in house graphics program which has a very old cold base. I am not an X programmer myself and am just helping out other folks with this problem. With backing store it has fine performance. So I am confused and looking for information. Are there no applications which need backing store these days? I would have assumed that many applications would have benefited from this and being available was normal. Or perhaps something completely different is needed or is going on? The current train of thought here is to require that X on linux always runs with backing store. Which means starting the X server with +bs or adding 'Option backingstore' to the XF86Config-4 file. I don't really like either of those options since it would seem to lead to a messy configuration problem. Words of wisdom? Thanks Bob pgp0.pgp Description: PGP signature
Re: GCC Bug affecting KDM
On Wed, Jun 11, 2003 at 12:36:12PM -0500, Branden Robinson wrote: On Wed, Jun 11, 2003 at 10:56:36AM -0400, [EMAIL PROTECTED] wrote: I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. Well, that's just not possible, according to Jack Howarth. :-P :-P :-P Would one of the committers like to merge revisions 162 and 171 onto branches/4.3.0/sid? I'll do this tonight; I've been making up a list of stuff to merge from trunk/ to branches/. I was going to do it last night but real life rudely interrupted, grabbed me by the shoulders, and shook vigorously. I'll be home in a few hours, and able to do it then. -- Daniel Stone [EMAIL PROTECTED] [EMAIL PROTECTED] KDE: Konquering a desktop near you - http://www.kde.org pgp0.pgp Description: PGP signature
Re: dpkg error (while performing dist-upgrade)
On Wed, Jun 11, 2003 at 06:58:00PM +0300, Tero Laitinen wrote:
I tried to upgrade my Debian distribution but following happened during the
configuration process. I was instructed to e-mail the error report here.
---
...
...
Setting up xbase-clients (4.2.1-3) ...
ERROR: /usr/X11R6/lib/X11/xinit symbolic link does not exist. Either the
package didn't ship the symbolic link (a bug in the package), or dpkg failed
to
unpack it to the filesystem (a bug in dpkg).
Please report the package name, version, and the text of the above error
message(s) to [EMAIL PROTECTED].
dpkg: error processing xbase-clients (--configure):
subprocess post-installation script returned error exit status 1
---
So, could you tell me if the package is broken or is it just my system that
is causing problems? Thanks in advance.
Sure, run the following shell script with an argument of
/usr/X11R6/lib/X11/xinit.
#!/bin/sh
message () {
# pretty-print messages of arbitrary length
echo $* | fold -s -w ${COLUMNS:-80} 2;
}
message Searching for overlapping packages...
DPKG_INFO_DIR=/var/lib/dpkg/info
if [ -d $DPKG_INFO_DIR ]; then
if [ $(echo $DPKG_INFO_DIR/*.list) != $DPKG_INFO_DIR/*.list ]; then
POSSIBLE_CULPRITS=$(ls -1 $DPKG_INFO_DIR/*.list | egrep -v \
(xbase-clients|xfree86-common|xfs|xlibs))
SMOKING_GUNS=$(grep -l $1 $POSSIBLE_CULPRITS)
if [ -n $SMOKING_GUNS ]; then
BAD_PACKAGES=$(printf \\n)
for F in $SMOKING_GUNS; do
# too bad you can't nest parameter expansion voodoo
P=${F%*.list} # strip off the trailing .list
PACKAGE=${P##*/} # strip off the directories
BAD_PACKAGES=$(printf %s\n%s $BAD_PACKAGES $PACKAGE)
done
message The following packages appear to have file overlaps \
with the XFree86 packages; these packages are either very \
old, or in violation of Debian Policy. Try upgrading each of \
these packages to the latest available version if possible: \
for example, with the command \apt-get install\. If no \
newer version of a package is available, you will have to \
remove it: for example, with the command \apt-get remove\. \
If even the latest available version of the package has this \
file overlap, please file a bug against that package with the \
Debian Bug Tracking System. You may want to refer the package \
maintainer to section 12.8 of the Debian Policy manual.
message The overlapping packages are: $BAD_PACKAGES
else
message no overlaps found.
fi
else
message cannot search; no matches for $DPKG_INFO_DIR/*.list.
fi
else
message cannot search; $DPKG_INFO_DIR does not exist.
fi
exit 0
(The above functionality is built-in to XFree86 4.2.1-7 and later.)
--
G. Branden Robinson|You can have my PGP passphrase when
Debian GNU/Linux |you pry it from my cold, dead
[EMAIL PROTECTED] |brain.
http://people.debian.org/~branden/ |-- Adam Thornton
pgp0.pgp
Description: PGP signature
Re: XFree86 X server and FreeType
In [EMAIL PROTECTED] Branden Robinson [EMAIL PROTECTED] wrote: On Wed, Jun 11, 2003 at 11:22:00PM +0900, ISHIKAWA Mutsumi wrote: Okay, just to make sure I understand the situation: 1) we want to be sure that the normal X server package (xserver-xfree86) and the debugging X server package (xserver-xfree86-dbg) use the same FreeType library. 2) we'd *like* it if we could achieve this by both packages dynamically linking against the system's FreeType library; however, 3) The normal X server package (xserver-xfree86) *cannot* be built dynamically linked against the FreeType library because of upstream code/design issues; 4) Therefore, we encapsulate XFree86's internal fork of the FreeType library into *both* xserver-xfree86 and xserver-xfree86-dbg. Have I got that correct? Exactly yes. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
XFree86's HasLinuxInput symbol and m68k
[[[ Background for debian-68k readers:
On Tue, Jun 10, 2003 at 01:32:16PM +0100, James Troup wrote:
X Strike Force SVN Admin [EMAIL PROTECTED] writes:
+ /* m68k has no 2.4 kernel yet */
+ # ifndef Mc68020Architecture
+ #define HasLinuxInput YES
@@ -701,7 +714,7 @@
This seems out-of-date?
[Branden wrote the following]
Hmm, yes, but only recently so. :)
I'll handle this for the trunk. Daniel or ISHIKAWA-san, can you merge
the change over to branches/4.3.0/sid once I have fixed it on the trunk?
]]]
On Tue, Jun 10, 2003 at 04:58:57PM -0400, Christian T. Steigies wrote:
On Tue, Jun 10, 2003 at 02:56:45PM -0500, Branden Robinson wrote:
afaik 2.4 doesn't boot on all the m68k (ex)vendors... amiga does... mac
does not.. :/
That's not what I seem to recall from recent traffic on debian-68k.
But it's true, my Mac does not boot with 2.4.20, and yours probably neither.
Its just none of the mac users noticed yet. And I have no reports about
Atari, and the three VMEs. Is it important for XFree86, I mean will 4.3 only
work with a 2.4 kernel? I heard Ray Knight is trying to get some
improvements from the powerpc kernel. If somebody can make it work on Macs,
its Ray...
Please don't freak about this. That symbol has very limited effect:
[0] [EMAIL PROTECTED]:~/packages/xfree86/4.2.1/xfree86-4.2.1/build-tree/xc %
grep -r HasLinuxInput *
config/cf/linux.cf:#define HasLinuxInputYES
config/cf/linux.cf:#ifndef HasLinuxInput
config/cf/linux.cf:# define HasLinuxInput YES
config/cf/xfree86.cf:#ifndef HasLinuxInput
config/cf/xfree86.cf:# define HasLinuxInput NO
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile:#if HasLinuxInput
programs/Xserver/hw/xfree86/input/wacom/Imakefile:#if HasLinuxInput
[0] [EMAIL PROTECTED]:~/packages/xfree86/4.2.1/xfree86-4.2.1/build-tree/xc %
grep -2 HasLinuxInput programs/Xserver/hw/xfree86/input/hyperpen/Imakefile
programs/Xserver/hw/xfree86/input/wacom/Imakefile
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile-#include Server.tmpl
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile-
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile:#if HasLinuxInput
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile-DEFINES = -DLINUX_INPUT
programs/Xserver/hw/xfree86/input/hyperpen/Imakefile-#endif
--
programs/Xserver/hw/xfree86/input/wacom/Imakefile-#include Server.tmpl
programs/Xserver/hw/xfree86/input/wacom/Imakefile-
programs/Xserver/hw/xfree86/input/wacom/Imakefile:#if HasLinuxInput
programs/Xserver/hw/xfree86/input/wacom/Imakefile-DEFINES = -DLINUX_INPUT
programs/Xserver/hw/xfree86/input/wacom/Imakefile-#endif
And the only actual C file that appears to do anything with this is the
wacom input driver:
[0] [EMAIL
PROTECTED]:~/packages/xfree86/4.2.1/xfree86-4.2.1/build-tree/xc/programs/Xserver/hw/xfree86/input
% grep -r LINUX_INPUT *
acecad/acecad.c:#ifdef LINUX_INPUT
hyperpen/Imakefile:DEFINES = -DLINUX_INPUT
wacom/Imakefile:DEFINES = -DLINUX_INPUT
wacom/xf86Wacom.c:#ifdef LINUX_INPUT
wacom/xf86Wacom.c:#ifdef LINUX_INPUT
wacom/xf86Wacom.c:#ifdef LINUX_INPUT
wacom/xf86Wacom.c:#endif /* LINUX_INPUT */
wacom/xf86Wacom.c:#ifdef LINUX_INPUT
wacom/xf86Wacom.c:#ifdef LINUX_INPUT
(The acecad driver references it, but there's no way for it to be
defined in the build environment. The hyperpen Imakefile will define
it, but the hyperpen code doesn't use it. These are typical examples of
the close attention paid to input drivers in XFree86 ;-) )
And here are the relevant chunks of xf86Wacom.c:
#ifdef LINUX_INPUT
#include asm/types.h
#include linux/input.h
/* max number of input events to read in one read call */
#define MAX_EVENTS 50
/* keithp - a hack to avoid redefinitions of these in xf86str.h */
#ifdef BUS_PCI
#undef BUS_PCI
#endif
#ifdef BUS_ISA
#undef BUS_ISA
#endif
#endif
[...]
#ifdef LINUX_INPUT
static void xf86WcmReadUSBInput(LocalDevicePtr);
static Bool xf86WcmUSBOpen(LocalDevicePtr);
#endif
[...]
#ifdef LINUX_INPUT
/*
***
*
* xf86WcmIsUSBLine --
* Test if the attached device is a USB one.
*
***
*/
static int
xf86WcmIsUSBLine(intfd)
{
int version;
int err;
SYSCALL(err = ioctl(fd, EVIOCGVERSION, version));
if (!err) {
ErrorF(%s Wacom Kernel Input driver version is %d.%d.%d\n,
XCONFIG_PROBED,
version 16, (version 8) 0xff, version 0xff);
return 1;
} else {
return 0;
}
}
/*
***
*
* xf86WcmReadUSBInput --
* Read the new events from the device, and enqueue them.
*
***
*/
static void
xf86WcmReadUSBInput(LocalDevicePtr local)
{
X Strike Force SVN commit: rev 176 - in trunk/debian: . patches
Author: branden Date: 2003-06-10 23:43:13 -0500 (Tue, 10 Jun 2003) New Revision: 176 Added: trunk/debian/patches/001b_m68k_haslinuxinput_too.diff Modified: trunk/debian/changelog trunk/debian/patches/077_man_dir_and_suffix_cleanup.diff trunk/debian/patches/085_bigass_imake_manpage_handling_overhaul.diff trunk/debian/patches/100_sparc_pci_domains.diff Log: * debian/patches/100_sparc_pci_domains.diff: remove special-case logic in linux.cf that defined HasLinuxInput to NO for Mc68020Architecture; m68k is now supported by the Linux 2.4.20 kernel (at least in Debian), so we let this symbol be defined to YES just like all the other architectures. This only really affects the Wacom input driver and should not cause any regressions. (thanks to James Troup for pointing out this no-longer-needed conditional) * debian/patches/085_bigass_imake_manpage_handling_overhaul.diff, debian/patches/077_man_dir_and_suffix_cleanup.diff, debian/patches/100_sparc_pci_domains.diff: resync Modified: trunk/debian/patches/100_sparc_pci_domains.diff == --- trunk/debian/patches/100_sparc_pci_domains.diff 2003-06-10 20:45:46 UTC (rev 175) +++ trunk/debian/patches/100_sparc_pci_domains.diff 2003-06-11 04:43:13 UTC (rev 176) @@ -2,7 +2,7 @@ --- xc/config/cf/linux.cf.orig 2002-09-07 03:43:34.0 -0500 +++ xc/config/cf/linux.cf 2002-09-07 03:43:35.0 -0500 -@@ -774,7 +774,7 @@ +@@ -771,7 +771,7 @@ # endif # define LinuxMachineDefines -D__sparc__ # define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET Added: trunk/debian/patches/001b_m68k_haslinuxinput_too.diff == --- trunk/debian/patches/001b_m68k_haslinuxinput_too.diff 2003-06-10 20:45:46 UTC (rev 175) +++ trunk/debian/patches/001b_m68k_haslinuxinput_too.diff 2003-06-11 04:43:13 UTC (rev 176) @@ -0,0 +1,14 @@ +--- xc/config/cf/linux.cf~ 2003-06-10 23:10:58.0 -0500 xc/config/cf/linux.cf 2003-06-10 23:11:45.0 -0500 +@@ -157,10 +157,7 @@ + /* we build-depend on libfreetype6-dev (FreeType 2.x) */ + # define BuildFreetype2Library NO + # define HasFreetype2 YES +-/* m68k has no 2.4 kernel yet */ +-# ifndef Mc68020Architecture +-#define HasLinuxInput YES +-# endif ++# define HasLinuxInput YES + # define HasXdmAuth YES + # define HasLatex YES + /* at present, glide2 only works on i386 */ Modified: trunk/debian/patches/085_bigass_imake_manpage_handling_overhaul.diff == --- trunk/debian/patches/085_bigass_imake_manpage_handling_overhaul.diff 2003-06-10 20:45:46 UTC (rev 175) +++ trunk/debian/patches/085_bigass_imake_manpage_handling_overhaul.diff 2003-06-11 04:43:13 UTC (rev 176) @@ -377,7 +377,7 @@ /* we build-depend on libfreetype6-dev (FreeType 2.x) */ # define BuildFreetype2Library NO -@@ -834,38 +835,6 @@ +@@ -831,38 +832,6 @@ # define ConnectionFlags -DUNIXCONN -DTCPCONN #endif Modified: trunk/debian/patches/077_man_dir_and_suffix_cleanup.diff == --- trunk/debian/patches/077_man_dir_and_suffix_cleanup.diff2003-06-10 20:45:46 UTC (rev 175) +++ trunk/debian/patches/077_man_dir_and_suffix_cleanup.diff2003-06-11 04:43:13 UTC (rev 176) @@ -122,7 +122,7 @@ #define StaticLibrary(libpath,libname) -Wl,-Bstatic Concat(-L,libpath) Concat(-l,libname) -Wl,-Bdynamic --- xc/config/cf/linux.cf.orig 2002-09-07 03:40:05.0 -0500 +++ xc/config/cf/linux.cf 2002-09-07 03:40:07.0 -0500 -@@ -844,8 +844,14 @@ +@@ -841,8 +841,14 @@ #ifndef LibManSuffix # define LibManSuffix 3x #endif @@ -139,7 +139,7 @@ #endif #ifndef FileManSuffix # define FileManSuffix5x -@@ -853,6 +859,12 @@ +@@ -850,6 +856,12 @@ #ifndef FileManDir # define FileManDir $(MANSOURCEPATH)5 #endif Modified: trunk/debian/changelog == --- trunk/debian/changelog 2003-06-10 20:45:46 UTC (rev 175) +++ trunk/debian/changelog 2003-06-11 04:43:13 UTC (rev 176) @@ -1,5 +1,12 @@ xfree86 (4.2.1-9) unstable; urgency=low + * patch #001b: remove special-case logic in linux.cf that defined +HasLinuxInput to NO for Mc68020Architecture; m68k is now supported by +the Linux 2.4.20 kernel (at least in Debian), so we let this symbol be +defined to YES just like all the other architectures. This only really +affects the Wacom input driver and should not cause any regressions. +(thanks to James Troup for pointing out this no-longer-needed conditional) + * debian/control: move xlibs-pic from section devel to section
Re: proposed X Strike Force commit/changelog policy
On Tue, Jun 10, 2003 at 10:31:40PM -0500, Branden Robinson wrote: On Wed, Jun 11, 2003 at 08:49:32AM +1000, Daniel Stone wrote: On Tue, Jun 10, 2003 at 12:22:01PM -0500, Branden Robinson wrote: The goal is NOT to make the package changelogs less massive. The goal is to make them more useful. My package changelogs have been doing double-duty for years because I didn't have them under revision control. Now they simply need to do what a changelog should do -- log changes. That's what I meant, really. Right now, some of the changelogs (like the 293-line changelog for 4.3.0-0ds4) are pretty unnavigable. Well, I rudely purged your changelog entries from the 4.3.0/sid branch, so I don't see them and they don't bother me. :) Well, yeah. Behold, an example. :P -- Daniel Stone [EMAIL PROTECTED] [EMAIL PROTECTED] KDE: Konquering a desktop near you - http://www.kde.org pgpOdltq7g8Od.pgp Description: PGP signature
Re: -pre1v1 (from DanielS) m68k build logs (failure)
On Wed, 11 Jun 2003, Daniel Stone wrote: My money's on groff screwing up, but we really need to see for ourselves what's going on - if we could get the output of those commands done separately, it'd be nice. Fabio, have you purged your builddir already? If not, could you please run the commands separately and get any error output? Confirmed... groff dies without any error message. Fabio -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html
Re: XFree86's HasLinuxInput symbol and m68k
On Tue, 10 Jun 2003, Branden Robinson wrote: But it's true, my Mac does not boot with 2.4.20, and yours probably neither. Its just none of the mac users noticed yet. And I have no reports about Atari, and the three VMEs. Is it important for XFree86, I mean will 4.3 only work with a 2.4 kernel? I heard Ray Knight is trying to get some improvements from the powerpc kernel. If somebody can make it work on Macs, its Ray... Please don't freak about this. That symbol has very limited effect: My post was more paranoid than anything else. I was sure you evaluated the impact already. Thanks Fabio -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp4.html
Re: proposed X Strike Force commit/changelog policy
On Tue, Jun 10, 2003 at 02:20:45PM -0400, Joey Hess wrote: Branden Robinson wrote: * When doing a commit that should be logged in the debian/changelog file, edit the debian/changelog file before doing the commit and commit the change to it along with the rest of your change set. As a point of interest, do you ever find yourself working on more than one thing at a time in the same checkout, and how do you juggle the debian/changelog changes then? I tend to changelog everything I do as I do it, then when I'm about to commit I copy the working changelog aside and trim debian/changelog down so that the diff shows only one changeset. After I commit, I move the working changelog back. * Here's a new one that I myself didn't realize was important until this morning: always include the name of each file being changed in your commit log. This seems redundant until you realize that svn log operations can be run on directories. Of course subversion knows what files that change touched. This sounds more like a deficiency of svn log; it should be able to list the files. It can; use the -v option. I do tend to err towards verbose log messages anyway, though. What do you guys think? I'm not part of your team, but I have some interest in subversion and some of the same issues, so pardon me for weighing in.. Ditto. Cheers, -- Colin Watson [EMAIL PROTECTED]
re: X Strike Force SVN commit: rev 175 - branches/4.3.0/sid/debian
Branden, Is this part still needed? + * #003_linux.cf_and_xfree86.cf.diff: +- Always disable `FontLibSharedFreeType' for compatiblity between + normal XFree86 server and XFree86-dbg server. + We should drop this change, when we can build the Loader Server + liked against external FreeType2 [ISHIKAWA Mutsimi] + The offending cvs changes were regressed out in the latest 2.1.4-4 freetype package. The compilation error doesn't occur anymore when building last weeks XFree86 4.3.0-0pre1v1 and the resulting XFree86 packages seem to work fine. Jack
Re: X Strike Force SVN commit: rev 175 - branches/4.3.0/sid/debian
In [EMAIL PROTECTED] Jack Howarth [EMAIL PROTECTED] wrote: Branden, Is this part still needed? + * #003_linux.cf_and_xfree86.cf.diff: +- Always disable `FontLibSharedFreeType' for compatiblity between + normal XFree86 server and XFree86-dbg server. + We should drop this change, when we can build the Loader Server + liked against external FreeType2 [ISHIKAWA Mutsimi] + The offending cvs changes were regressed out in the latest 2.1.4-4 freetype package. The compilation error doesn't occur anymore when building last weeks XFree86 4.3.0-0pre1v1 and the resulting XFree86 packages seem to work fine. There are two purposes in this change. 1) FreeType2 incompatible problem between freetype 2.1.4-2 and 2.1.4-3, you described above. It is solved by freetype2_2.1.4-4 package. 2) We would like to use same FreeType2 code between Normal Loader X Server (included in xserver-xfree86 package) and Static build Debug X server (included in xserver-xfree86-dbg. Static build X server can build with external shared FreeType2 library, but curretly we can not build X loader server with external FreeType2 shared library(X loader server's freetype font backend module uses `source code level inclusion' scheme of FreeType2). FreeType2 code included in xfree86 source tree and libfreetype6's one are not same (diffrent version and too difficult to sync..), so if debug X server linked with external FreeType2 and normal loader server does not, we can not debug X server internal FreeType2 related thigs. Yes, 1) problem is gone. But 2) problem is remaing. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Re: XFree86's HasLinuxInput symbol and m68k
On Tue, Jun 10, 2003 at 10:54:36PM -0500, Branden Robinson wrote:
#ifdef LINUX_INPUT
if (xf86SetBoolOption(local-options, USB, (common-wcmOpen ==
xf86WcmUSBOpen))) {
local-read_input=xf86WcmReadUSBInput;
common-wcmOpen=xf86WcmUSBOpen;
xf86Msg(X_CONFIG, %s: reading USB link\n, dev-identifier);
#else
if (xf86SetBoolOption(local-options, USB, 0)) {
ErrorF(The USB version of the driver isn't available for your
platform\n);
#endif
Will it kill anyone to have this code in the XFree86 packages for m68k?
No USB on m68k as far as I know (I can hear already the shouts but there
is this cool USB Adapter for Amiga), so this should never be executed on
m68k. Maybe not even compiled (I did not read the code too thoroughly).
Christian
GCC Bug affecting KDM
I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. If you wish to reply to me, you must CC me. Peace Love, David Meiser __ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
Re: XFree86's HasLinuxInput symbol and m68k
On Wed, 11 Jun 2003, Christian T. Steigies wrote:
On Tue, Jun 10, 2003 at 10:54:36PM -0500, Branden Robinson wrote:
#ifdef LINUX_INPUT
if (xf86SetBoolOption(local-options, USB, (common-wcmOpen ==
xf86WcmUSBOpen))) {
local-read_input=xf86WcmReadUSBInput;
common-wcmOpen=xf86WcmUSBOpen;
xf86Msg(X_CONFIG, %s: reading USB link\n, dev-identifier);
#else
if (xf86SetBoolOption(local-options, USB, 0)) {
ErrorF(The USB version of the driver isn't available for your
platform\n);
#endif
Will it kill anyone to have this code in the XFree86 packages for m68k?
No USB on m68k as far as I know (I can hear already the shouts but there
is this cool USB Adapter for Amiga), so this should never be executed on
m68k. Maybe not even compiled (I did not read the code too thoroughly).
The input core does compile on m68k if you really want to, but no devices use
it (for now). So as soon as we get this USB support, the input core will be
ready ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: GCC Bug affecting KDM
On Wed, Jun 11, 2003 at 10:56:36AM -0400, [EMAIL PROTECTED] wrote: I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. Well, that's just not possible, according to Jack Howarth. :-P :-P :-P Would one of the committers like to merge revisions 162 and 171 onto branches/4.3.0/sid? -- G. Branden Robinson| Never underestimate the power of Debian GNU/Linux | human stupidity. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | pgp1f918C9Mzs.pgp Description: PGP signature
Re: -pre1v1 (from DanielS) m68k build logs (failure)
On Wed, Jun 11, 2003 at 10:42:59AM +0200, Fabio Massimo Di Nitto wrote: On Wed, 11 Jun 2003, Daniel Stone wrote: My money's on groff screwing up, but we really need to see for ourselves what's going on - if we could get the output of those commands done separately, it'd be nice. Fabio, have you purged your builddir already? If not, could you please run the commands separately and get any error output? Confirmed... groff dies without any error message. Sounds like you need to make Colin Watson unhappy, then. (I.e., file a bug report against groff.) -- G. Branden Robinson|The basic test of freedom is Debian GNU/Linux |perhaps less in what we are free to [EMAIL PROTECTED] |do than in what we are free not to http://people.debian.org/~branden/ |do. -- Eric Hoffer pgpI9C1eIV2tM.pgp Description: PGP signature
Re: proposed X Strike Force commit/changelog policy
On Wed, Jun 11, 2003 at 05:52:43AM -0500, Colin Watson wrote: On Tue, Jun 10, 2003 at 02:20:45PM -0400, Joey Hess wrote: Branden Robinson wrote: * Here's a new one that I myself didn't realize was important until this morning: always include the name of each file being changed in your commit log. This seems redundant until you realize that svn log operations can be run on directories. Of course subversion knows what files that change touched. This sounds more like a deficiency of svn log; it should be able to list the files. It can; use the -v option. I do tend to err towards verbose log messages anyway, though. Ooh, that's nice. I wish -v were the default. Still, I continue to advocate the format I advised above. I'm not part of your team, but I have some interest in subversion and some of the same issues, so pardon me for weighing in.. Ditto. And as I told Joey, please speak up anytime. -- G. Branden Robinson| Debian GNU/Linux | Ab abusu ad usum non valet [EMAIL PROTECTED] | consequentia. http://people.debian.org/~branden/ | pgpuJE5adMB5R.pgp Description: PGP signature
backing store not enabled by default?
Looking for an education... On hpux 11.11 the following produces: xdpyinfo | grep backing options:backing-store YES, save-unders YES In woody the following produces: xdpyinfo | grep backing options:backing-store NO, save-unders NO Which appears to mean that application requests such as the following have no effect. (This is very old code and I am not an X11 programmer so I will just assume up front that some types will have changed.) XSetWindowAttributes attr; unsigned long vm = CWBackingStore; attr.backing_store = Always; XChangeWindowAttributes(XtDisplay(graphics),XtWindow(graphics),vm,attr); Which means that at least this application does not get any backing store and is very slow when processing window events. This application is an in house graphics program which has a very old cold base. I am not an X programmer myself and am just helping out other folks with this problem. With backing store it has fine performance. So I am confused and looking for information. Are there no applications which need backing store these days? I would have assumed that many applications would have benefited from this and being available was normal. Or perhaps something completely different is needed or is going on? The current train of thought here is to require that X on linux always runs with backing store. Which means starting the X server with +bs or adding 'Option backingstore' to the XF86Config-4 file. I don't really like either of those options since it would seem to lead to a messy configuration problem. Words of wisdom? Thanks Bob pgpaBfmLacH99.pgp Description: PGP signature
Re: GCC Bug affecting KDM
On Wed, Jun 11, 2003 at 12:36:12PM -0500, Branden Robinson wrote: On Wed, Jun 11, 2003 at 10:56:36AM -0400, [EMAIL PROTECTED] wrote: I have packages compiled from the 4.3.0 trunk in the subversion repository from June 9 and the problem still exists there using the current version of sid. Well, that's just not possible, according to Jack Howarth. :-P :-P :-P Would one of the committers like to merge revisions 162 and 171 onto branches/4.3.0/sid? I'll do this tonight; I've been making up a list of stuff to merge from trunk/ to branches/. I was going to do it last night but real life rudely interrupted, grabbed me by the shoulders, and shook vigorously. I'll be home in a few hours, and able to do it then. -- Daniel Stone [EMAIL PROTECTED] [EMAIL PROTECTED] KDE: Konquering a desktop near you - http://www.kde.org pgpsPFHwspAqG.pgp Description: PGP signature
Re: dpkg error (while performing dist-upgrade)
On Wed, Jun 11, 2003 at 06:58:00PM +0300, Tero Laitinen wrote:
I tried to upgrade my Debian distribution but following happened during the
configuration process. I was instructed to e-mail the error report here.
---
...
...
Setting up xbase-clients (4.2.1-3) ...
ERROR: /usr/X11R6/lib/X11/xinit symbolic link does not exist. Either the
package didn't ship the symbolic link (a bug in the package), or dpkg failed
to
unpack it to the filesystem (a bug in dpkg).
Please report the package name, version, and the text of the above error
message(s) to debian-x@lists.debian.org.
dpkg: error processing xbase-clients (--configure):
subprocess post-installation script returned error exit status 1
---
So, could you tell me if the package is broken or is it just my system that
is causing problems? Thanks in advance.
Sure, run the following shell script with an argument of
/usr/X11R6/lib/X11/xinit.
#!/bin/sh
message () {
# pretty-print messages of arbitrary length
echo $* | fold -s -w ${COLUMNS:-80} 2;
}
message Searching for overlapping packages...
DPKG_INFO_DIR=/var/lib/dpkg/info
if [ -d $DPKG_INFO_DIR ]; then
if [ $(echo $DPKG_INFO_DIR/*.list) != $DPKG_INFO_DIR/*.list ]; then
POSSIBLE_CULPRITS=$(ls -1 $DPKG_INFO_DIR/*.list | egrep -v \
(xbase-clients|xfree86-common|xfs|xlibs))
SMOKING_GUNS=$(grep -l $1 $POSSIBLE_CULPRITS)
if [ -n $SMOKING_GUNS ]; then
BAD_PACKAGES=$(printf \\n)
for F in $SMOKING_GUNS; do
# too bad you can't nest parameter expansion voodoo
P=${F%*.list} # strip off the trailing .list
PACKAGE=${P##*/} # strip off the directories
BAD_PACKAGES=$(printf %s\n%s $BAD_PACKAGES $PACKAGE)
done
message The following packages appear to have file overlaps \
with the XFree86 packages; these packages are either very \
old, or in violation of Debian Policy. Try upgrading each of \
these packages to the latest available version if possible: \
for example, with the command \apt-get install\. If no \
newer version of a package is available, you will have to \
remove it: for example, with the command \apt-get remove\. \
If even the latest available version of the package has this \
file overlap, please file a bug against that package with the \
Debian Bug Tracking System. You may want to refer the package \
maintainer to section 12.8 of the Debian Policy manual.
message The overlapping packages are: $BAD_PACKAGES
else
message no overlaps found.
fi
else
message cannot search; no matches for $DPKG_INFO_DIR/*.list.
fi
else
message cannot search; $DPKG_INFO_DIR does not exist.
fi
exit 0
(The above functionality is built-in to XFree86 4.2.1-7 and later.)
--
G. Branden Robinson|You can have my PGP passphrase when
Debian GNU/Linux |you pry it from my cold, dead
[EMAIL PROTECTED] |brain.
http://people.debian.org/~branden/ |-- Adam Thornton
pgp8tLJgC0xt6.pgp
Description: PGP signature
Re: XFree86 X server and FreeType
In [EMAIL PROTECTED] Branden Robinson [EMAIL PROTECTED] wrote: On Wed, Jun 11, 2003 at 11:22:00PM +0900, ISHIKAWA Mutsumi wrote: Okay, just to make sure I understand the situation: 1) we want to be sure that the normal X server package (xserver-xfree86) and the debugging X server package (xserver-xfree86-dbg) use the same FreeType library. 2) we'd *like* it if we could achieve this by both packages dynamically linking against the system's FreeType library; however, 3) The normal X server package (xserver-xfree86) *cannot* be built dynamically linked against the FreeType library because of upstream code/design issues; 4) Therefore, we encapsulate XFree86's internal fork of the FreeType library into *both* xserver-xfree86 and xserver-xfree86-dbg. Have I got that correct? Exactly yes. -- ISHIKAWA Mutsumi [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
