October 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: package-get-base.el issues (was Re: [patch] enhancements to package-ui.el) 26 years, 1 month

Greg Klanderman

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: >> Automatic access to package-get-base.el is dangerous. sb> sb> Yup. How do you feel about what I proposed in response to Stephen Turnbull's message last week, ie, automatic fetching from ftp.xemacs.org with PGP signature checking?

1 participants
0 comments

Re: [CRASH] xemacs-21.2-b2 in pgnus 26 years, 1 month

Adrian Aichner

There exists a bug in XEmacs which will crash it on Windows NT (native build) during GC. I have sent two reports to xemacs-nt on this. It also typically happens inside Gnus and has something to do with a corrupted modeline. Currently I run without use of (display-time) in the hope this may avoid the crashes since it updates the modeline. Andrew, you might want to rebuild XEmacs to include symbolic debug information. Regards, Adrian -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: efs-load/require sllloooooowwww 26 years, 1 month

Adrian Aichner

>>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> Michael> writes: Michael> The reason is that the abstractions around/between path Michael> searching and Fload are all totally wrong, and there's no Michael> good place for EFS to intercept things. This means *all* Michael> the path searching happens within EFS (in Elisp, that is) Michael> which gives you the huge slowdown. APA> Hello Michael, APA> is there a plan to make EFS work with natively built APA> XEmacs-21.0 on Windows NT (all the \-breakage, Du weißt APA> schon)? Michael> Actually, the xemacs-nt folks have been very secretive Michael> about what the actual problems with EFS on NT are. Michael> However, I've received some mails about this, and I Michael> absolutely intend to do what I can to fix the problems Michael> once I understand them and their proposed solutions. Hallo Michael! I am happily using EFS on Windows NT in (version) "XEmacs 21.0 \"Pyrenean-pre2\" [Lucid] (i386-pc-win32) of Sun Oct 11 1998 on TWILIGHT" after applying the following patch: > Date: Mon, 07 Sep 1998 16:10:09 +0100 > From: Jonathan Harris <jhar(a)tardis.ed.ac.uk> > To: Michael Sperber <sperber(a)informatik.uni-tuebingen.de> > CC: XEmacs NT List <xemacs-nt(a)xemacs.org> > Subject: Changes to efs to run on XEmacs on windowsnt (WinNT and Win95) Jonathan has documented his patch in very much detail. At the minimum I hope this patch can be integrated into the next release of EFS. I can't do without it, now that I have left my UNIX nutshell. Best regards, Adrian Michael> This will have to wait until after the 21.0 release, Michael> though, I'm afraid. Michael> -- Cheers =8-} Chipsy Friede, Völkerverständigung und Michael> überhaupt blabla -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

package-get-base.el issues (was Re: [patch] enhancements to package-ui.el) 26 years, 1 month

SL Baur

Pete Ware <ware(a)cis.ohio-state.edu> writes in xemacs-beta(a)xemacs.org: > greg(a)alphatech.com (Greg Klanderman) writes: >> All this package-get-base.el stuff is such a pain. Now there's the >> incremental updates to deal with... blech. I wish we could just >> reliably and automagically snarf the current one off ftp.xemacs.org. O.K. >> Suggestions anyone? > When I originally wrote the code, one thing I was concerned about was > XEmacs being easily exploited for trojan horse attacks. In > particular, a talented hacker could intercept ftp requests to > ftp.xemacs.org and substitude their own versions of packages -- hence > the md5 checksum for each package. I consider these to be valid concerns. > But then the problem becomes grabing package-get-base.el -- if that > gets intercepted then there is a problem. Bogus md5sum's can be > substituted, host names changed, package locations, etc. Right. > I pictured two distribution methods for package-get-base.el. It > either gets sent with the entire distribution (which are signed). If > that is corrupted, well you have bigger problems anyway. Distributing with the core isn't working and I've removed it from the core. I am willing to revisit this decision if there is some assurance of reliability. > The second was a periodic posting to a newsgroup/mailing list. > Presumably, such an article would be PGP signed and could be > verified as being from the poster. That's a reasonable idea. We need to revisit the issue of signing anyway. I'm currently signing with PGP 2.6, but it is incompatible with GNUPG, which I am informed conforms to what will become the OpenPGP standard about to be created. I'm not signing the individual packages because of time constraints -- the passphrase must be typed for each signature. This isn't much of an issue when signing distributions, but it doesn't scale up into dozens of files. Signing package-get-base.el isn't a problem and sounds like a good idea. > Automatic access to package-get-base.el is dangerous. Yup. What we need is some utility code for manipulating package-get-base.el. I've modified the format somewhat to make it easier to process with very little specialized support like the autoloads generation requires. It now looks like: ;; Package Index file -- Do not edit manually. (setq package-get-base '( ;;;＠＠＠ (zenirc (standards-version 1.0 version "1.03" author-version "2.112" date "1998-08-15" build-date "1998-10-12" maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>" distribution stable priority medium category "comm" dump nil description "ZENIRC IRC Client." filename "zenirc-1.03-pkg.tar.gz" md5sum "cf85b0358688c286d2ce16ab7f4cc95b" size 276114 provides (zenirc) requires (zenirc) type regular )) ;;;＠＠＠ (w3 (standards-version 1.0 version "1.10" author-version "4.0pre23" date "1998-07-18" build-date "1998-10-12" maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>" distribution experimental priority high category "comm" dump nil description "A Web browser." filename "w3-1.10-pkg.tar.gz" md5sum "6113b455f82c5903b8bd6f4ca48afb00" size 612442 provides (w3 url) requires (w3 mail-lib xemacs-base) type regular )) ;;;＠＠＠ (vm ... The rudimentary support I'm using to make updates is attached. There are plenty of possible enhancements. In terms of needed features, we need the following: QA code to loop over each entry in a package-index file and verify that the md5sum in the index matches the tarball in the same directory. Code to merge multiple entries. It would also be nice if we could add as a fetch interface something MIMEish where one can create a MIME multipart entry that contains a package-info file that can be clicked on to retrieve/verify/install the associated package.

1 participants
0 comments

Re: efs-load/require sllloooooowwww 26 years, 1 month

Michael Sperber

>>>>> "APA" == Adrian Aichner <aichner(a)ecf.teradyne.com> writes: >>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: Michael> The reason is that the abstractions around/between path Michael> searching and Fload are all totally wrong, and there's no Michael> good place for EFS to intercept things. This means *all* Michael> the path searching happens within EFS (in Elisp, that is) Michael> which gives you the huge slowdown. APA> Hello Michael, APA> is there a plan to make EFS work with natively built XEmacs-21.0 on APA> Windows NT (all the \-breakage, Du weißt schon)? Actually, the xemacs-nt folks have been very secretive about what the actual problems with EFS on NT are. However, I've received some mails about this, and I absolutely intend to do what I can to fix the problems once I understand them and their proposed solutions. This will have to wait until after the 21.0 release, though, I'm afraid. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: efs-load/require sllloooooowwww 26 years, 1 month

Michael Sperber

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Valdis Kletnieks <Valdis.Kletnieks(a)vt.edu> writes in xemacs-beta(a)xemacs.org: >> On 08 Oct 1998 20:43:31 +0200, you said: >>> I would like to fix this only once along with the Great Load Path >>> Overhaul due for 21.2, if it's alright with you folks. This should >>> make disabling EFS for load/require superfluous. >> Umm.. Urp. >> Explain please? I always get worried anytime my brain finds a match >> for the regexp 'Great .* Overhaul'. ;) sb> I don't know what Michael has in mind. A priority of mine is the sb> capability to install lisp packages into one big lisp/ directory to sb> speed up startup and load path searching. One of the main goals will be to partition the various paths so you can safely recreate their values without messing with any changes the user has made. Effectively what's now `load-path' will be empty by default, and the actual load path will be assembled on the fly. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

XEmacs package update 1998-10-12-1 26 years, 1 month

SL Baur

[The upload is going slowly. Allow about a half hour from the timestamp on this message for all the tarballs to get copied.] I've updated all the packages and incremented every version number. The only user-visible changes are to gnats and tm. The scripts that formerly lived in the XEmacs core are now distributed with their respective package. This is a test release and if something goes wrong, I will repackage everything under the same version number until I get it right. The package-get-base.el file is at: ftp://ftp.xemacs.org/pub/xemacs/packages/package-index-1998-10-12-1 Build changes: There is support for `make install'. To use it, you must set STAGING to point to the package area to install to, eg. $ make STAGING=/usr/local/lib/xemacs/xemacs-packages install There is support for multiple lisp directories (as in leim), multiple data directories (as in Gnus), and attached scripts (as in tm). I've changed the way package-get-base.el is generated. The build procedure installs the package-info information into a copy as the package is built. Hopefully this change will resolve the problems of the database getting out of date. Tip of the day: If you have checked out a previous version of the XEmacs package lisp source from CVS and wish to get a new package, the following procedure is the easiest way to do it (illustrating with the newly added bbdb package): $ cd xemacs-packages/comm $ mkdir bbdb $ cvs add bbdb $ cd bbdb $ cvs update -d Enjoy and beat me up if this still doesn't go right.

1 participants
0 comments

Re: pcl-cvs provides still wrong [was Re: Package update] 26 years, 1 month

Greg Klanderman

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> sb> $ cvs diff -u prog/pcl-cvs/package-info.in sb> $ grep provides prog/pcl-cvs/package-info.in sb> provides (pcl-cvs dll elib-node generic-sc) sb> >> Doh! Thanks for fixing it - for some reason I thought it was not >> set within the pcl-cvs package. Eventually I'll get all this stuff >> figured out... sb> sb> It's getting easier. I've gotten the package Makefiles down to sb> listing files. It seems most of package-info.in is generated from values set in the Makefile (or generated via md5). Why not just put make variables in the Makefile for the other couple static things and auto-generate it? greg

1 participants
0 comments

[CRASH] xemacs-21.2-b2 in pgnus 26 years, 1 month

Andrew Hobson

I've had a problem for many betas with xemacs crashing in gnus. I finally started xemacs under gdb. Unfortunately, this problem is not easily reproducible. Sometimes I can go many days without it crashing and some times it happens twice a day. I'm now running pgnus-0.33, but still having the same problem. The bug seems to be triggered when I hit 'g' in Gnus to get new news. I have a pretty standard setup with some mail and some news. I do have one "foreign server" that I read news from. The stack trace and my Installation file are included below. I still have the process under gdb's control, so if you'd like for me to muck with it some more, I can. This is under FreeBSD 3.0-CURRENT. If this is not enough information, I apologize. Please let me know how I can provide the proper information. Drew Program received signal SIGPIPE, Broken pipe. 0x103f72c1 in write () (gdb) bt #0 0x103f72c1 in write () #1 0x1260ee in sys_write_1 (fildes=8, buf=0x11dab00, nbyte=63, allow_quit=0) at sysdep.c:2695 #2 0x12618e in sys_write (fildes=8, buf=0x11dab00, nbyte=63) at sysdep.c:2718 #3 0xd4aa9 in filedesc_writer (stream=0xa48900, data=0x11dab00 "LIST ACTIVE comp.unix.admin\r\nLIST ACTIVE comp.unix.programmer\r\nr\r\non\r\n", size=63) at lstream.c:984 #4 0xd3a6c in Lstream_flush_out (lstr=0xa48900) at lstream.c:343 #5 0xd3b1d in Lstream_flush (lstr=0xa48900) at lstream.c:372 #6 0x65ee7 in encoding_flusher (stream=0xb84100) at file-coding.c:2342 #7 0xd3afb in Lstream_flush_out (lstr=0xb84100) at lstream.c:364 #8 0xd3b1d in Lstream_flush (lstr=0xb84100) at lstream.c:372 #9 0x7e419 in unix_send_process (proc=544814464, lstream=0x4f9a80) at process-unix.c:1212 #10 0xe25ea in send_process (proc=544814464, relocatable=1628734740, nonrelocatable=0x0, start=0, len=34) at process.c:974 #11 0xe29f7 in Fprocess_send_string (process=544814464, string=1628734740, from=-1607802876, to=-1607802876) at process.c:1104 #12 0x3e25e in funcall_recording_as (recorded_as=-1607694892, nargs=2, args=0xefbfc118) at eval.c:3193 #13 0x3e6cd in Ffuncall (nargs=3, args=0xefbfc118) at eval.c:3238 #14 0x11f0a in Fbyte_code (bytestr=1617645836, vector=-2140656640, maxdepth=7) at bytecode.c:416 #15 0x3f322 in funcall_lambda (fun=543412452, nargs=2, arg_vector=0xefbfc2c4) at eval.c:3597 #16 0x3e5cc in funcall_recording_as (recorded_as=-1607033172, nargs=2, args=0xefbfc2c0) at eval.c:3200 #17 0x3e6cd in Ffuncall (nargs=3, args=0xefbfc2c0) at eval.c:3238 #18 0x11f0a in Fbyte_code (bytestr=1617317008, vector=-2142487328, maxdepth=3) at bytecode.c:416 #19 0x3f322 in funcall_lambda (fun=543700432, nargs=2, arg_vector=0xefbfcf0c) at eval.c:3597 #20 0x3e5cc in funcall_recording_as (recorded_as=-1605572996, nargs=2, args=0xefbfcf08) at eval.c:3200 #21 0x3e6cd in Ffuncall (nargs=3, args=0xefbfcf08) at eval.c:3238 #22 0x11f0a in Fbyte_code (bytestr=1616106688, vector=-2143764480, maxdepth=6) at bytecode.c:416 #23 0x3f322 in funcall_lambda (fun=544071936, nargs=0, arg_vector=0xefbfd220) at eval.c:3597 #24 0x3e5cc in funcall_recording_as (recorded_as=-1605055116, nargs=0, args=0xefbfd21c) at eval.c:3200 #25 0x3e6cd in Ffuncall (nargs=1, args=0xefbfd21c) at eval.c:3238 #26 0x11f0a in Fbyte_code (bytestr=1615108616, vector=-2139656192, maxdepth=3) at bytecode.c:416 #27 0x3f322 in funcall_lambda (fun=544765756, nargs=1, arg_vector=0xefbfd36c) at eval.c:3597 #28 0x3e5cc in funcall_recording_as (recorded_as=-1605324580, nargs=1, args=0xefbfd368) at eval.c:3200 #29 0x3e6cd in Ffuncall (nargs=2, args=0xefbfd368) at eval.c:3238 #30 0x16295 in Fcall_interactively (function=-1605324580, record_flag=-1607802876, keys=-1607802876) at callint.c:949 #31 0x3cc86 in Fcommand_execute (cmd=-1605324580, record=-1607802876, keys=-1607802876) at eval.c:2584 #32 0x8523b in execute_command_event (command_builder=0x413c40, event=552189300) at event-stream.c:4346 #33 0x85824 in Fdispatch_event (event=552189300) at event-stream.c:4637 #34 0x1cfdf in Fcommand_loop_1 () at cmdloop.c:579 #35 0x1cde8 in command_loop_1 (dummy=-1607802876) at cmdloop.c:494 #36 0x3b7ae in condition_case_1 (handlers=-1607802780, bfun=0x1cdcd <command_loop_1>, barg=-1607802876, hfun=0x1c74a <cmd_error>, harg=-1607802876) at eval.c:1653 #37 0x1c8a3 in command_loop_3 () at cmdloop.c:256 #38 0x1c8c4 in command_loop_2 (dummy=-1607802876) at cmdloop.c:267 #39 0x3b421 in internal_catch (tag=-1607724908, func=0x1c8bc <command_loop_2>, arg=-1607802876, threw=0x0) at eval.c:1328 #40 0x1ca86 in initial_command_loop (load_me=-1607802876) at cmdloop.c:305 #41 0x36c76 in xemacs_21_2_b2_i386_unknown_freebsd3_0 (argc=3, argv=0xefbfd714, envp=0xefbfd724, restart=0) at emacs.c:1698 #42 0x37a20 in main (argc=3, argv=0xefbfd714, envp=0xefbfd724) at emacs.c:2115 Here is my Installation file: uname -a: FreeBSD computer.eng.mindspring.net 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Wed Aug 26 18:17:23 EDT 1998 ahobson＠computer.eng.mindspring.net:/a/src/sys/compile/COMPUTER i386 /home/ahobson/src/xemacs/xemacs-21.2-b2/configure '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--error-checking=none' '--with-database=berkdb' '--with-mule' '--with-menubars=lucid' '--with-scrollbars=lucid' '--with-dialogs=athena' '--cflags=-fno-caller-saves -fno-strength-reduce -m486 -malign-loops=0 -malign-jumps=0 -malign-functions=0 -g' XEmacs 21.2-b2 "Aether" configured for `i386-unknown-freebsd3.0'. Where should the build process find the source code? /home/ahobson/src/xemacs/xemacs-21.2-b2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/freebsd.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -fno-caller-saves -fno-strength-reduce -m486 -malign-loops=0 -malign-jumps=0 -malign-functions=0 -g Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /usr/local/lib:/usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. Reason: PNG library version and header file don't match! WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "flock" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. -- "I would gladly give one hundred and fifty thousand dollars to have it proved there is no hell." -- Charteres

1 participants
0 comments

Re: pcl-cvs provides still wrong [was Re: Package update] 26 years, 1 month

SL Baur

[The changes I made to pcl-cvs are committed.] Greg Klanderman <greg(a)alphatech.com> writes in xemacs-beta(a)xemacs.org: >>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> sb> Greg Klanderman <greg(a)alphatech.com> writes in xemacs-beta(a)xemacs.org: sb> provides (pcl-cvs dll elib-node generic-sc) sb> >>> Oops, I thought dll and elib-node were outta there. sb> sb> Oops indeed. I didn't check before packaging: sb> sb> $ cvs diff -u prog/pcl-cvs/package-info.in sb> $ grep provides prog/pcl-cvs/package-info.in sb> provides (pcl-cvs dll elib-node generic-sc) > Doh! Thanks for fixing it - for some reason I thought it was not > set within the pcl-cvs package. Eventually I'll get all this stuff > figured out... It's getting easier. I've gotten the package Makefiles down to listing files.

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta October 1998