Packaging a Grafix Driver, Conflicts xlibmesa-gl
Dpkg newb. here. Been installing my grafix card's closed source driver - ugly, ugly business. But I'm in love w/ the "Debian way", so I thought I'd have a go at installing it using Debian package management tools. So far so good. The driver comes w/ its own "libGL.so.1.3.0" - it's installer ( <- I don't like the installer) *purges* all other libGL. So if I role a package - it's supposed to work w/ xfree86 - should I make it "Provides: libgl1" or "Provides: xlibmesa-gl"? Should it be "Conflicts: xlibmesa-gl", so xlibmesa-gl's libGL.so.1 is removed? Thanks 4 any tips! Jack
XFree86: MIT-KERBEROS-5
I gather that XFree86 for Debian is not compiled with Kerberos support? --- hostname:~> xhost krb:username xhost: not compiled for Kerberos 5 --- Before I go galloping off to recompile it, I should probably ask if this is appropriate? Why isn't XFree86 available w/ Kerberos? I'm not the X guru I'd like to be ... I want to authorize xclients to connect to a remote xserver, provided they are run by the same person who's running the server. I have a working Kerberos setup and read about the "MIT-KERBEROS-5" security mechanism in the man pages. It's not like I've used this mechanism before ... I thought I'd give it a go. Not much help from Google. Can you spot any problems already? Thanks! Jack
Bug#354178: MIT-KERBEROS-5
Package: xorg-x11 Version: 6.9.0.dfsg.1-4 Struggling to build X.Org with MIT Kerberos - [...] gcc -m32 -c -ansi -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-de cls -Wnested-externs -Wundef-I../.. -I../../exports/include -Dlinux -D__i3 86__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN _SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DXTHREAD S -D_REENTRANT -DXUSE_MTSAFE_API -g -O2 -fno-strict-aliasing -g -fPIC k5 encode.c -o unshared/k5encode.o k5encode.c:75: warning: function declaration isn't a prototype k5encode.c:81:34: error: macro "krb5_princ_realm" requires 2 arguments, but only 1 given k5encode.c: In function 'XauKrb5Encode': k5encode.c:81: error: 'krb5_princ_realm' undeclared (first use in this function) k5encode.c:81: error: (Each undeclared identifier is reported only once k5encode.c:81: error: for each function it appears in.) k5encode.c:82:37: error: macro "krb5_princ_size" requires 2 arguments, but only 1 given k5encode.c:82: error: 'krb5_princ_size' undeclared (first use in this function) [...] I used xorg-x11 6.9.0.dfsg.1-4 & libkrb5-dev 1.4.3-6 I used this patch to build-depend on libkrb5-dev & set HasKrb5, Krb5Includes & Krb5Libraries - http://cgi.sfu.ca/~jdbates/tmp/xorg/200602230/patch There is probably a better place for HasKrb5, Krb5Includes & Krb5Libraries - but I couldn't find where? Many thanks - Jack >On Tue, Apr 13, 2004 at 03:41:20AM -0700, ms419 freezone.co.uk >wrote: >> I gather that XFree86 for Debian is not compiled with Kerberos >> support? >[...] > >Historical reasons and inertia. Way back in the day, crypto wasn't in >main, and having XFree86 depend on libraries outside of non-us to build >and work would have meant putting XFree86 itself into non-us. > >Since crypto has gone into main, the primary reason is lack of anyone >with the right combination of clues, will, and working patches. > >> Before I go galloping off to recompile it, I should probably ask if >> this is appropriate? Why isn't XFree86 available w/ Kerberos? > >No good reason; please do engage in this experiment and report your >findings back to this list if you'd like. > >I personally have no objection to including Kerberos support in XFree86, >and I doubt anyone else does either. If they do, now's the time to >speak up. :) > >> I'm not the X guru I'd like to be ... I want to authorize xclients to >> connect to a remote xserver, provided they are run by the same person >> who's running the server. I have a working Kerberos setup and read >> about the "MIT-KERBEROS-5" security mechanism in the man pages. It's >> not like I've used this mechanism before ... I thought I'd give it a >> go. Not much help from Google. Can you spot any problems already? > >I tried to educate myself on this a few years ago, but failed for the >same reasons you apparently did. There's just not many people who both >use anything more than MIT-MAGIC-COOKIE-1 or XDM-AUTHORIZATION-1, and >have documented their experiences publicly enough for Google to snag >them. > >-- >G. Branden Robinson|People with power understand >Debian GNU/Linux |exactly one thing: violence. >branden debian.org |-- Noam Chomsky >http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#355202: MIT-KERBEROS-5
Encountered same problem building libxau 1.0.0-1 - [...] gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../include -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wall -g -O2 -MT k5encode.lo -MD -MP -MF .deps/k5encode.Tpo -c ../k5encode.c -fPIC -DPIC -o .libs/k5encode.o ../k5encode.c:75: warning: function declaration isn't a prototype ../k5encode.c:81:34: error: macro "krb5_princ_realm" requires 2 arguments, but only 1 given ../k5encode.c: In function 'XauKrb5Encode': ../k5encode.c:81: error: 'krb5_princ_realm' undeclared (first use in this function) ../k5encode.c:81: error: (Each undeclared identifier is reported only once ../k5encode.c:81: error: for each function it appears in.) ../k5encode.c:82:37: error: macro "krb5_princ_size" requires 2 arguments, but only 1 given ../k5encode.c:82: error: 'krb5_princ_size' undeclared (first use in this function) ../k5encode.c:86:41: error: macro "krb5_princ_component" requires 3 arguments, but only 2 given ../k5encode.c:86: error: 'krb5_princ_component' undeclared (first use in this function) [...] Used this patch to build-depend on libkrb5-dev & to enable Kerberos support - http://cgi.sfu.ca/~jdbates/tmp/xorg/200603030/patch signature.asc Description: Digital signature
Fatal server error: could not open default font 'fixed'
I get this error trying to start xdm 1.0.1-1 - [...] Could not init font path element /usr/share/fonts/X11, removing from list! Fatal server error: could not open default font 'fixed' [...] I think all the necessary xfonts packages are installed - ii xfonts-100dpi 1.0.0-1 100 dpi fonts for X ii xfonts-75dpi1.0.0-1 100 dpi fonts for X ii xfonts-base 1.0.0-1 standard fonts for X ii xfonts-encodings1.0.0-1 Encodings for X.Org fonts ii xfonts-utils1.0.0-1 X Window System font utility programs Also /usr/share/fonts/X11 exists & contains some font stuff - tor:~# ls -l /usr/share/fonts/X11 total 43 drwxr-xr-x 2 root root 13328 Mar 2 16:10 100dpi drwxr-xr-x 2 root root 13328 Mar 2 16:09 75dpi drwxr-xr-x 3 root root 1384 Mar 2 15:54 encodings drwxr-xr-x 2 root root 15880 Mar 2 16:04 misc drwxr-xr-x 2 root root 600 Mar 2 15:54 util tor:~# Can anyone tell me a bit more about what this error means? Can anyone help me solve it - should I file a bug against xdm 1.0.1-1 - or should I wait for xdm 1.0.1-1 to reach unstable? Many thanks - Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
