searching for Raul Miller
Does anyone know if Raul Miller is active ? I and others have looked for him a bit. He took over pdl from me a couple years ago. I'd like to get it back (if he wants to get rid of it, of course). I sent a mail a few days ago and didn't hear anything. Thanks, John
Re: List of packages needing a new maintainer
*Martin Michlmayr wrote: > Below is a listing of packages needing a new maintainer. I know that In case someone wants to pick up a package, I'll note which packages (of mine) I think are likely to have some reasonably sized user base. Some others may be popular too, I just don't know about them. > #68203 O: slatec 68204 -- numerical computation library This is used for courses at the University here. > #68308 O: dstool -- dynamical systems investigation > #68309 O: dstool-doc -- documents for dstool (dynamical systems investigation) > #68311 O: dstooltk -- dynamical systems investigation (Tk version) > #68312 O: dstooltk-doc -- dynamical systems investigation (Tk version) > #68320 O: meschach -- library for performing operations on matrices and > vectors > O: plotmtv -- multipurpose X11 plotting program
Re: 100Mb/Full Duplex
I hope I understand your question. Donald Becker's web site has a few utilities, 'mdiag' is one, that let you manually set the speed. It worked for my pcmcia EEpro, but it does not work for all cards. *Tim Sailer wrote: > Hi folks. > > I'm having some trouble, actually with a Cisco 6509 switch, but getting > it to talk to 20 VALinux machines. My story: > > I have a rack of 20 machines needing to talk to a Pix firewall with > gigbit interfaces on it. To do this, we set up a test rig using an Alteon > switch with 1 gigabit interface and 24 100bT ports for the boxes. > When we run in this mode, everything performs well. Now, we switch this > over to the Cr^Hisco switch, and it all goes to hell. It seems like the > 6509 doesn't negotiate with the EEPro100 NICs in the linux boxes. Errors > out the butt, and the switch ports claim that they are talking 10/half > when they should be talking 100/full. > > I've looked at the NIC driver source, but it's non-obvious, to me anyway, > how to lock these puppies in 100/full. Any pointers? > > Thanks, > Tim > > -- > (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - > http://www.buoy.com/~tps > I have never found that criticism is ever inhibited by ignorance. > ** Disclaimer: My views/comments/beliefs, as strange as they are, are my > own.** > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Danger Will Robinson! Danger!
*Ari Makela wrote: > Joey Hess writes: > > Ari Makela wrote: > > > series kernel or newer XFree86. Neither it's difficult to change the > > > kernel on the rescue floppy if the provided kernel does not support > > > hardware. If, Samba, for example, is not new enough, it's not > > > difficult to fetch the sources and compile it. > > > > Have you ever actually tried to do this? > > Yes, I've installed Slink on an exotic AST server hardware. 2.0 didn't > work. There was nothing that was hard to fix. Maybe you find it easy. But you are relatively elite in debian knowledge. I got a notebook two months ago. The video, sound, and pcmcia are not supported by slink. I installed a minimum slink and then used another debian system to burn enough packages to upgrade on a CD (made an archive with apt-zip, I think) Then I got the pcmcia working by building a new kernel and pcmcia sources, then upgraded over my fast net connection. Maybe people who can't do that are lazy and stupid and don't deserve Debian. Maybe Linus was right. People can't ship stable Debian on new machines, but they can ship RH and SuSE. (I don't want to attack with the sarcasm, just to make a strong point). btw. I like the idea of releasing something like a semi-stable which differs mostly in that it supports new hardware. Maybe we can argue about whether the latest apache should be shipped. But I can't see how you can argue that our only stable product should not be able to run on most new machines. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: slink -> potato
Something I have noticed several times. If you are doing a remote upgrade (probably a crazy idea), the telnet daemon (maybe inetd or something) becomes unavailble for quite some time. Maybe it is between the time that netbase is unpacked and when it is configured. There are usually problems with a broken package or two so that apt-get upgrade does not work on the first try. If I lose my telnet connection, I can't telnet again to fix things. *andreas pÄlsson wrote: > Hello. > > I'm about to make an update of a base Slink-system to the unstable > Potato. > > Is there anything I should think of or preperations to be made before > updating? > > Why I do this is because I want to become a Debian-developer, and any > hints and tips are much appreciated. > > Sincerely... > Andreas > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: scanning my ports
*Nathan E Norman wrote: > Mr. Lapeyre, > > You do realise that pavlov.midco.net is part of the DNS rotation > http.us.debian.org? No, I didn't. I was using the mirror. I am in error. Obviously the connections to several ports on my machine were a legitmate part of the transfer of data to my machine. I made the accusations out of ignorance. > I see no evidence in the logs that you are being port scanned - I feel > it's more likely that your use of the mirror here is at issue. You may > of course disagree. No, I agree. The connection attempts in my log were made to transfer data that I requested. > > Nevertheless, I will shut down the mirror here and rebuild this machine > from scratch, implementing draconian and paranoid security measures. Please don't do this. I don't see any need to do this. > > If I receive further complaints of "abuse" from Debian project > participants, I will be forced to remove the mirror entirely. > Complaints to "[EMAIL PROTECTED]" are viewed by members of the > management team as well as members of the technical staff, and I regret > to inform you that one of the members of the management team has reacted > to your complaint in an abusive and non-productive manner that will > certainly impact our ability to help Debian in the future. I feel sorry for this person. > > I regret the "shoot the messenger" tone of this email; understandably > security is important and potential abuses should be dealt with swiftly > and forcefully, given the state of the Internet today. Nevertheless, > common sense can and should be exercised whenever possible. I made a mistake, and made a false accusation. I am very sorry to have wasted the time of your security team. Maybe you can avoid further waste of time, by accepting my retraction of accusations and realizing that now there is no evidence and no accusation of a security problem, and therefore, no reason to take action on a suspected security problem I apologize to the project for throwing a wrench in the mirroring system. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre pgp2l3B2xdxlN.pgp Description: PGP signature
Re: Announcing debconf, configuration management for debian
On Tue, 21 Sep 1999, Hamish Moffatt wrote: hamish>On Mon, Sep 20, 1999 at 02:57:42PM -0600, Scott Barker wrote: hamish>> dpkg -i hamish>> dpkg-reconfigure hamish>> hamish>> you could just run: hamish>> hamish>> dpkg -i --reconfigure hamish>> hamish>> I'm probably thinking too far ahead right now, though... hamish> hamish>Why would you install the package (which presumably includes hamish>configuration) and then immediately reconfigure it? I often make a mistake during configuration and then want to reconfigure immediately. Maybe others are not so careless ! John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Too many kernels in unstable
On Mon, 20 Sep 1999, Hirling Endre wrote: endre>On Sun, 19 Sep 1999, Roland Rosenfeld wrote: endre> endre>> which would reduce the effort of the ftp maintainer and speed up endre>> upgrading our ftp archive from 2.2.12 to 2.2.13. The dependencies endre>> between the kernels and the kernel depending modules could be realized endre>> using versioned dependencies, couldn't they? endre>> endre>> Maybe we should add an unstable kernel to the stable versions above: endre>> endre>> kernel-{doc,headers,image,source}-2.3 2.3.18- endre> endre> endre>The problem is that sometimes and for some architectures the 'stable' endre>2.2 series kernels are less stable than, say, 2.1's, or for some endre>architectures 2.2.x is stable, for others, 2.2.y... so older versions endre>shouldn't be removed from the distribution too easily. Some people have suggested providing a package, say 2.2, with all the 2.2.x source patches. (I didn't look at the size, but the patches are sometimes small and sometimes 1.5 MB). It is not too inconvenient to apply the patches to get to a specific kernel, and the source size is not too big. I never use the debian source packages; there are probably additional technical issues. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Too many kernels in unstable
On Fri, 17 Sep 1999, Brian Mays wrote: brian> brian>> [EMAIL PROTECTED] (Brian Mays) writes: brian> brian>>> Once 2.2.12 makes it out of Incoming, we will have 8 kernel brian>>> versions in the unstable distribution? Do we REALLY need to brian>>> provide that many versions of the kernel?? brian> brian>>>>>> "Guy" == Guy Maor <[EMAIL PROTECTED]> writes: brian> brian>> What about just keeping the last 2.0.x and the last 2.2.x ? brian> brian>That would be fine by me; however, some people might object because brian>kernel "improvements" sometimes break things -- even in stable kernel brian>branches. It is not so rare for someone to avoid upgrading to the next brian>kernel version, because it breaks some obscure feature that he needs. brian> brian>Perhaps we should keep the last two versions of each branch? In this brian>case, 2.0.35, 2.0.36, 2.2.10, and 2.2.12 (which is in Incoming). I brian>don't know. Let's see whether anyone objects to just keeping two brian>versions around. In another thread, I am dealing with exactly this problem. My machine hangs with 2.0.37 and 2.2.x, but is OK with 2.0.36. But had to take a piece of driver code from 2.0.37. There are quite a few new issues arising from two gcc branches and two stable kernel branches. Having a few kernels around gives some flexibility in trying to put together a working system. 11 kernels is probably too much, but a couple of each might be OK. We (someone !) could also package the patches, which is a bit more of a pain for the user, but we could get all 12 new kernels without adding so much bulk to the archive. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: building kernel 2.0.x under potato
On Fri, 17 Sep 1999, Chris Rutter wrote: chris>On Thu, 16 Sep 1999, John Lapeyre wrote: chris> chris>> The 2.0.37 and 2.2.x kernels keep hanging on my AMD K6-2. chris> chris>This sounds *bad*, BTW; have you checked around to see if anyone chris>else has had these kinds of freezing problems? Is your machine chris>unstable in any other way? chris> chris>You may find all you need to do is tweak a CPU register or two, chris>or apply some patch to the kernel to make the machine stable on chris>any kernel you like -- it's worth checking, because the kernel chris>*shouldn't* have become randomly unstable in 2.0.37. I found a few reports on the kernel mailing list. But, somehow, the search engine did not pick up references to AMD that I remembered. It is difficult to get controled information on bugs. Some people find problems and eventually admit that it was a hardware problem. Tweaking a register would be fine. I really don't know how to look into that, however. It really seems that something changed. I built the 200 MB tar file about 30 times under 2.0.36, and it was fine. Under 2.0.34, the file was built every night for over a year, w/o crashing. With 2.0.37 and 2.2.x, it is not totally predictible, but the machine hangs on roughly half the attempts to make the 200 MB file. As I said, I don't know enough to say to what extent hardware and the compiler are playing a part. It is, of course, quite time consuming to run these tests. I will post something to the kernel list. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: building kernel 2.0.x under potato
On Fri, 17 Sep 1999, Herbert Xu wrote: herber>On Thu, Sep 16, 1999 at 10:57:54AM -0700, John Lapeyre wrote: herber>Try herber> herber>make "CC=gcc272 -D__KERNEL__ -I`pwd`/include" zImage I love this man ! Well, I had tried messing around with the /include files, but didn't get it right. This line you gave builds 2.0.x kernels. I had finally gotten a working system, by compiling 2.0.36 patched for egcs with egcs-2.91.66 , and taking the ethernet driver rtl8139.c from 2.0.37 and compiling it with the 2.0.36 source. This finally produces both a stable network and filesystem. The 2.0.37 and 2.2.x kernels keep hanging on my AMD K6-2. Now that I can build with gcc272, I have more parameters to play with ! That line should perhaps be added to /usr/doc/gcc272/README.Debian. I cc'd this to the gcc maintainer group. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: building kernel 2.0.x under potato
On Thu, 16 Sep 1999, Herbert Xu wrote: herber>John Lapeyre <[EMAIL PROTECTED]> wrote: herber>> herber>> Hmm. Well my two potato systems are slightly different. One just herber>> compiled 2.0.36 with the patch. But the other one failed with the herber>> message herber>> fixed or forbidden register 2 (cx) was spilled for class CREG, herber> herber>This means that you're not using gcc272. I used the default compiler, which is "2.95". The patch is supposed to allow old kernels to be compiled with new compilers. So this is what I wanted. I also compiled it on a slightly older potato system with a version "egcs-2.91.66", and this has produced a kernel, which, so far, seems stable. (btw, both systems have binutils 2.9.1.0.25-2) There is a note here about the problem with 2.95: http://egcs.cygnus.com/faq.html/#asmclobber However, it just gives an example, but does not enumerate all of the violations in the linux source. This is what I get when I try to compile the patched 2.0.36 source with gcc272. This is similar to what I get when I try to compile un-patched source with gcc272: homey 38 > make 'CC=gcc272' zImage gcc272 -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o init/main.o init/main.c herber>-- init/main.c:23: linux/head.h: No such file or directoryherber>Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ ) In file included from /usr/include/linux/sched.h:14,herber>Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> from init/main.c:20:herber>Home Page: http://gondor.apana.org.au/~herbert/ /usr/include/linux/timex.h:159: field `time' has incomplete type The bottom line, from my point of view, is that make 'CC=gcc272' will not compile any kernel on potato, and that 2.95 will not compile even a patched (see http://www.suse.de/~florian/kernel+egcs.html) 2.0.36 kernel. There is still the possibility that my kernel crash is a hardware failure that is triggered under 2.2.x, but not under 2.0.36. Still, from a pratical point of view, I (or a user) should not be forced to upgrade the kernel because I want to build one more module, which is almost what happened. (I just happened to have a system with egcs-2.91.66 available.) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: building kernel 2.0.x under potato
On Thu, 16 Sep 1999, Chris Rutter wrote: chris>On Thu, 16 Sep 1999, John Lapeyre wrote: chris> chris>>The link to suse doesn't work at the moment, but I'll give it a try. chris>> The blurb at cygnus does not look encouraging. I think it is claiming chris>> that I have to "to change asm constructs" at various unspecified places chris>> in the source. chris> chris>Nah, they're just trying to cover their backs, so that people can't chris>whinge at them *if* things go wrong -- they're only *trying* to chris>worry you. Everyone I know who uses the patches says they're chris>fine. Hmm. Well my two potato systems are slightly different. One just compiled 2.0.36 with the patch. But the other one failed with the message fixed or forbidden register 2 (cx) was spilled for class CREG, which seems to be the problem that cygnus was talking about. I have not tracked down the difference. This is hard to believe. Maybe I have still missed something. I tried reapply the patch to a fresh source a couple of times. chris> chris> chris>> What should work? gcc272 ? I have tried it on two current potato chris>> machines. building with CC=gcc272 fails to build both 2.0.x and 2.2.x chris>> kernels. Building with the default compiler (egcs 2.95) will only build chris>> 2.2.x kernels. The kernel mailing list still claims that I should chris>> build with 2.7.2 before sending a bug report about my corrupted fs. chris> chris>Yeah, 2.7.2.* is the canonical compiler for 2.0 kernels. Can you chris>post what's actually going wrong? I could. The system hangs when I tar and gzip a large directory. I get no OOPS or any message in any log. It is hard to see what is happening. But it happens everytime I make the tar file with 2.2.10 and 2.2.12, and never (I tried 10 times in a row ) with 2.0.36. There is some noise on the kernel list of similar problems from people using an AMD K6-2. I still have not tried swapping CPUs, and memory, etc. chris> chris>> I have an old 2.0.36 kernel, but I need to compile a module for a driver. chris>> I think that given the number of instability reports regarding 2.2.x chris>> kernels it might be nice to be able to compile 2.0.x somewhat easily. chris> chris>What module's that -- does it not work under 2.2? Yeah, it *should* chris>be straightforward... Yes the module works under 2.2, but 2.2 gives crashes for me. I was running 2.0.34 happily for some time, but the ethernet card died, so I got different model, and discovered that I can no longer compile 2.0.34 modules. chris> chris>> Am I being obtuse, or are things pretty fucked up regarding kernels and chris>> compilers ? chris> chris>Er, a little, yeah. Unfortunately the Linux kernel is quite a chris>stressful bit of code to compile (it needs to get good x86 chris>performance), and so things got really tested to the full, w.r.t. chris>the compiler, but the compiler had bugs, and they had to be chris>worked around, etc. It's not that pretty. Well the patch worked on one machine, so I'll see if the new setup is stable. I am just a bit frustrated because this is the first time in four years that I can't just grab the source and type 'make zImage'; it has become much more complicated. Thanks again. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: building kernel 2.0.x under potato
On Thu, 16 Sep 1999, Chris Rutter wrote: chris>On Thu, 16 Sep 1999, John Lapeyre wrote: chris> chris>>Is it possible to build 2.0.x kernels under a reasonable chris>> potato build environment ? I tried "make CC=gcc272", but chris>> I still get failures from the assembler, I think. chris> chris>Erm, yeah, I had no problems as I remember. Just apply the chris>patches mentioned at <http://egcs.cygnus.com/faq.html/#linuxkernel>, chris>and you should be fine. The link to suse doesn't work at the moment, but I'll give it a try. The blurb at cygnus does not look encouraging. I think it is claiming that I have to "to change asm constructs" at various unspecified places in the source. chris> Alternatively (it *should* work if chris>binutils is sane, and you're pointing at the right gcc), chris>post the question to one of the egcs lists, and you should chris>get a quick response. What should work? gcc272 ? I have tried it on two current potato machines. building with CC=gcc272 fails to build both 2.0.x and 2.2.x kernels. Building with the default compiler (egcs 2.95) will only build 2.2.x kernels. The kernel mailing list still claims that I should build with 2.7.2 before sending a bug report about my corrupted fs. I have an old 2.0.36 kernel, but I need to compile a module for a driver. I think that given the number of instability reports regarding 2.2.x kernels it might be nice to be able to compile 2.0.x somewhat easily. Am I being obtuse, or are things pretty fucked up regarding kernels and compilers ? Thanks for the link , btw. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
building kernel 2.0.x under potato
Is it possible to build 2.0.x kernels under a reasonable potato build environment ? I tried "make CC=gcc272", but I still get failures from the assembler, I think. The 2.2.x kernels are unstable in some situations. With my AMD K6-2, I get a lockup when tarring a big tree. The 2.0.x kernels do fine in the same situation. I tried to find this issue in the archives, but did not find much. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Debian in a phrase
Well here is a little good press... http://cgi.pathfinder.com/time/personal/19990524/tech.html Says, Caldera Makers of OpenLinux. Debian High-quality volunteer Linux. Linux Pro Corporate-aimed implementation from WorkGroup Solutions. MkLinux: Linux for Power Macintosh Official site maintained by Apple. Red Hat Software Good general Linux site with a commercial twist -- an online store.
Re: Time to rewrite dpkg
*Marek Habersack wrote: > Yes, yes. But you won't be able to use perl with C++ libraries. If you use the C interface to the C++ libraries, and reimplement OO in perl, yes you can. And the C++ wrapping has improved to the point that people are using it directly for some projects. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Time to rewrite dpkg
*Marcus Brinkmann wrote: > On Thu, May 20, 1999 at 01:03:46AM +0200, Marek Habersack wrote: > > > 3. Most programmers would write code in C > > Yeah, uh. But that's the point isn't it? > > The current dpkg is written in C. How many programmers are working on it? I've often wondered about that. Occaisionally I see people getting involved, or offering patches, and it seems that IWJ is not interested. I will not speculate on what may be going on, but I have always found the development of dpkg to be rather curious. Anyone know what is going on ? > > The only contributions to our packaging systems today are done with C++ > (apt), and perl (install methods). > -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: evan leibovitch and the LPI certification tests
*Joseph Carter wrote: > First question: If some major cash was donated to Debian, what would we > do with it? Seriously, do we have a purpose for it, or would we just > re-donate it to other projects? Sure that might look good for a story on > Slashdot, but I'm more interested in making headlines for Debian because > we actually accomplished something cool rather than making them just to > make the average Slashdot reader think that Debian is as good as Redhat. A couple of salaried positions would be nice. Full time PR staff, ... -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: evan leibovitch and the LPI certification tests
*Manoj Srivastava wrote: > I can't speak for others, but *I* do it cause it pleases my > muse. Getting Debian out to the great unwashed masses rouses little > but mild curiosity in me, and certainly not eough to warrant the > amount of effort I put into my packages. In general, it seems that making Debian useful to the masses and making it useful to developers are not antithetical goals. There is a lot that can be done to make it better for both groups. I am worried about a minimum amount of interest in order to keep Debian (or something like it ) going. But it doesn't look like interest will wane in the near future. RH's rhetoric is that growth of Debian and Caldera helps RH. And I think they believe this rhetoric to a certain extent. If the time came when a significant number of people were asking companies to support their Debian boxes, RH would not hesitate to offer that support. Everything I have read makes me believe that VA and SGI and Compaq and whoever will have no problem responding to a demand to install and support Debian. If Debian developers want more commercial success, they can work for it. If enough (like Manoj) don't care, then we won't get commercial support and recognition. It's probably OK either way. They can't drive us out of business. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: stupid idea - metapackages
I really like the how-to-install-gnome page. Other packages that could use similar pages are X, emacs, and communicator. I and people I have talked to can get confused trying to decide which packages to download and install. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Intent to maintainer change: canna
*Adam Di Carlo wrote: > ISHIKAWA Mutsumi <[EMAIL PROTECTED]> writes: > I'm not sure I agree with Brian. The old maintain put out a "looking > for new maintainer" request on this list. Therefore, it is appropriate > that the agreed upon new maintainer would announce that here to. This > is to prevent others from possibly investigating the source with an > eye towards taking over maintenance. I thought the same thing. An announcement of change of maintainership is appropriate for this list. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
possibly broken X development environment
I was trying to compile ssystem, which compiled a couple of weeks ago. Now libc5 compatible libaries are trying to be linked. Is this a potato problem, or my problem ? cc -o ssystem cfgparse.tab.o lex.cfg.o ssystem.o init.o positions.o joystick.o cmdline.o keyboard.o mouse.o scrnsht.o sun.o timer.o util.o astrolib.o jpeg.o stars.o -L/usr/X11R6/lib -ljpeg -lglut -lMesaGLU -lMesaGL -lXext -lXmu -lXi -lX11 -lm /usr/lib/libc5-compat/libICE.so.6: undefined reference to _bsd_signal' /usr/lib/libc5-compat/libICE.so.6: undefined reference to xstat' /usr/lib/libc5-compat/libICE.so.6: undefined reference to _sigjmp_save' /usr/lib/libc5-compat/libICE.so.6: undefined reference to _setjmp' -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Release Plans (1999-05-10)
*Aaron Van Couwenberghe wrote: > Anybody remember the old slackware adage? The kernel can load its root FS > (compressed or not) from a separate floppy. this would bring us up to a > measly three floppies for floppy install. Besides, most ppl will be doing > CD boots anway I wouldn't mind installing from 2 or three floppies. I think if it has advantages, it's a good idea. There have been times when, for one reason or another, CD and network installs were giving me problems, and I said 'screw it' and made 7 floppies from a neighboring DOS machine and installed from them. For a single machine it is relatively painless. John -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: KDE debian stuff
*Ivan E. Moore II wrote: > So if you have beefs with how kde is currently being done from a debian > package > standpoint and would like to see them done differently please let me know. > Here > is a current list of things that people have already stated needed to be > changed > or was a "god it would be nice" Is the debugging info necessary ? I wonder if it slows things down. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Homapages in list of maintainers
*Taketoshi Sano wrote: > Hi, I'm one of the members in Debian JP, > and a self candidate to a maintainer in Debian. > > # I have sent application mail to [EMAIL PROTECTED] at May 05 1999. > # I have much curiosity at the processing time to join the Debian project. > # (I waited to join XFree86 as a non-voting member just 11days, 2 years ago) > > I have heard that some self-candidates from Debian JP felt > that the Debian Project rejects them as a maintainer, > because: > > one of them had not receive no answers for long time, > >more than a month is too long enough for ordinary people. > > one of them did not have no English-written certificate, > These complaints are very common on debian-devel, and debian-mentors. Many people from many countries, including the U.S. and in Europe feel that their application is taking too long to process. Some feel, I think, that they are given special bad treatment. I think the answer is always that the people processing the applications are overworked volunteers, usually doing several jobs for Debian. I have seen more that once, people sending email, and thinking perhaps they would never be accepted and now they are accepted and active developers. I think it would be great for Debian JP and Debian to find someone in Japan who can do interviews in Japan and report to the new-maintainer people in Debian proper (in Europe or U.S.) That is to say, it would be good to have a new-maintainer person located in Japan. This could speed up the process and improve communications. By the way, I want to see ruby packaged ! I hear that it is already packaged for Debian JP. I ran the fibonacci test in the source and it really beat perl badly. I even improved the perl version and ruby still won. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005 in potato
*Michael Stone wrote: > On Sun, May 09, 1999 at 10:47:16AM -0400, Zephaniah E. Hull wrote: > > IMHO we should not freeze until we have a number of things working, > > including fully functional boot disks, a cdrom generation setup, etc.. > > I agree with this. These are important things, and you can't do a dist > without them. Perl is really just another app. If gets in before the ( I am going to report you the secret perl police) > important things are done, great. But I think that delaying releases > soley for the sake of having one more shiny new app is not good. There's > already a lot of new stuff in potato that would be great to release--why > should it all wait on perl? (And, for that matter, if perl is really so > important, why isn't it already done?) Because it is difficult. Building and installing perl is easy-- the difficult part is ensuring smooth upgrades and partial upgrages, etc. I think quite a few of the more skilled developers have given opinions and there was no clear, easy, answer. It seemed to me that things were delayed by 1) delays in boot disks and building of CD images, etc. 2) delays in important links in the logistics , eg flattening the archive. 3) A few persistant release-critical bugs, which probably were not related to late uploads of large systems of packages. I suppose 1, and 2 are due to anarchy and overworked volunteers. At any rate, I predict that, perl will be uploaded, dependent packages will be uploaded, and then months will pass before the release, during which time, the perl problem will be fixed and forgotten. ( I suggest keeping this message so you can repost it when it is found that perl 5.005 has destroyed the entire distribution :) ) -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005 in potato
*Michael Stone wrote: > I'm still convinced that the reason slink's freeze took so long is that > some major packages were uploaded just prior to it, because they > "needed" to be in. Just like people want to do with perl... I am not sure where you are headed with this statement. AFAIK, no tentative freeze date has been set. Also, the problem of how to introduce the new package has been debated since before the slink freeze. It is apparantly a difficult problem. I imagine that, if the problem is solved before the freeze, perl 5.005 will be installed. John -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Intent to package gbdk.
There have been several packages allowed into main with a license like this. Some people don't like it however. Perl's license is even slightly more restricive. Except that now it can be licensed under the GPL as well. From: John Lapeyre <[EMAIL PROTECTED]> Date: 29 Jan 1999 12:44:51 -0700 In-Reply-To: Masato Taruishi's message of "Sat, 30 Jan 1999 00:21:22 +0900" Message-ID: <[EMAIL PROTECTED]> Lines: 28 X-Mailer: Gnus v5.5/Emacs 20.3 Masato Taruishi <[EMAIL PROTECTED]> writes: > At 29 Jan 1999 08:48:54 -0500, > Ben Pfaff <[EMAIL PROTECTED]> wrote: > > >Permission to use, copy, modify, and distribute this software for any > >purpose, subject to the provisions described below, without fee is > > ^^^ > > That doesn't make it non-free. It's in the standard BSD license. It > > means you don't have to pay the author, not that you can't charge a fee. > > That is the wrong quotation to show this is non-free (^^; > GBDK is free for non-commercial use: > > lcc is available free for your personal research and instructional use > under the `fair use' provisions of the copyright law. You may, however, > redistribute lcc in whole or in part provided you acknowledge its > source and include this CPYRIGHT file. You may, for example, include > the distribution in a CDROM of free software, provided you charge only > for the media, or mirror the distribution files at your site. > > > -- John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: GNOME in potato needs slink libs
ftp1.us.debian.org now has everything to install all the gnome stuff libgtop0 is there too. -- John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Reality check! [was: Re: Debian goes big business?]
Enrique Zanardi <[EMAIL PROTECTED]> writes: > On Sun, Jan 24, 1999 at 01:32:28PM -0700, John Lapeyre wrote: > > > > I guess I should add this to my last post about how bad the > > installation is. The boot floppies themselves and apt are quite good. > > Getting the base system on is easy for someone who knows what is going on. > > Probably not for a beginner. > > Suggestions for making the boot-floppies beginner-friendly are welcome > (but read the todo list first). Of course, code is even more welcome. > :-) The boot floppies are excellent for what they intend to do. They try to provide maximum flexibility, and then to be as friendly as possible. Perhaps a clueless-proof install should be on a separate disk. I won't say anymore, because I have not installed RH ors SuSE recently, and have no concrete suggestions. Also, in retrospect, I should have realized that picking the scientific workstation option could cause problems . That was over 500 packages . This is a severe test for any OS. -- John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Getting Slink compatible with Linux-2.2.0
The guys running the big machines are going to be a minority and should have no problem downloading util-linux. Even over a modem, its probably OK. It may be not worth it to risk the instability for the vast majority. The kernel source itself may be a problem for a slow or expensive modem link. I guess I don't care too much about the cachet of having 2.2 in slink. I wonder if we'll put 2.4 in slink -- John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Reality check! [was: Re: Debian goes big business?]
I guess I should add this to my last post about how bad the installation is. The boot floppies themselves and apt are quite good. Getting the base system on is easy for someone who knows what is going on. Probably not for a beginner. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Reality check! [was: Re: Debian goes big business?]
I did a fresh install yesterday from a hamm CD (our free CheapBytes CD). I chose the scientifc workstation option. This caused a minor nightmare. The only reason I was able to complete the install is because I have a few hundred hours experience in maintaining debian systems. I really like Debian, but it's installation is just terrible. (One problem is that fweb can get into a state in which it can be neither installed nor removed) I can't complain though, because I am not going to take the time to fix it in the near future. A commercial venture would be a good idea, because a full time employee could do quite a bit for the installation process in a few months, and contribute back to the project. -- John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Removing Packages in Slink for Debian 2.1
On Thu, 15 Oct 1998, Michael Meskes wrote: meskes>On Wed, Oct 14, 1998 at 12:19:30PM -0400, Brian White wrote: meskes>> libmagick4-dev19332 libmagick: ldconfig-symlink-before-shlib-in-deb LI#67 [217] ([EMAIL PROTECTED] (Scott K. Ellis)) meskes> meskes>I wish I would understand a message like that. :-) meskes> You can ! ... homey 11 > echo 'E: libmagick: ldconfig-symlink-before-shlib-in-deb' | lintian-info E: libmagick: ldconfig-symlink-before-shlib-in-deb N: N: In the package contents list, the shared library has to come before N: any symbolic links referencing the shared library. N: N: Refer to Packaging Manual, chapter 12 for details. N: John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Removing Gnome [was: Removing Packages in Slink for Debian 2.1]
On Thu, 15 Oct 1998, Stephen Crowley wrote: crow>That is ridiculous, there is no reason to remove gnome before the freeze, if you FWIW, one of the slashdot commenters on the slink-freeze, commends slink for including gnome ( he did install the packages, too) . John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Debian 2.[01] -- Only rudimentary support for Laptops?
On Thu, 15 Oct 1998, Alexander Kushnirenko wrote: kushni> kushni>If there were some Debian oriented database, where one could kushni>add his experience about installation of Debian on some kushni>unusual hardware, I would add mine about ThinkPad 380XD. THERE IS ! FAQ-O-MATIC ! (Excuse my yelling, I just wanted to advertise ;) ) Why don't you put an entry in this nice, underutilized tool. And reward Mr. Grobman for his effort. See: http://www.debian.org/fom/1.html John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Gnome 0.30 fix?
On Thu, 15 Oct 1998, Martin Alonso Soto wrote: masoto>to find anything wrong in the code. However, at a given time I added masoto>some printf statements to the code (to print certain values the masoto>debugger was not getting right) and the problem disappeared (!). This is characteristic of reading and writing outside of array bounds. (as determined by malloc) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Removing Packages in Slink for Debian 2.1
smb2www 27641 perl 5.005-02 breaks smb2www [0] (Craig Small <[EMAIL PROTECTED]>) This one also refers to the version of perl which has been removed. (It broke every module, so there are several such bug reports) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005.02
On 11 Oct 1998, Darren/Torin/Who Ever... wrote: torin>Andy Dougherty, in an immanent manifestation of deity, wrote: torin>>After some thought, I think I'd recommend that perl5.005_xx retain the torin>>same directory structure that perl5.00[34]_xx did. (with 5.005 in place of torin>>5.00[34], of course). torin> torin>That's good enough for me. I have boatloads of respect for Andy and his torin>understanding of Perl Install issues. That's how it will be for torin>5.005.02-3. Good, I think that will cause the least problems for the rest of Debian. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: KDE gone, Lyx next ?
On Sat, 10 Oct 1998, Shaya Potter wrote: spotte> spotte>-Original Message- spotte>From: John Lapeyre <[EMAIL PROTECTED]> spotte> spotte>> Lyx is currently in contrib. spotte>> Lyx is licensed under the GPL (version 2) . It is dynamically spotte>>linked against a non-free library (libforms) . spotte>> According to the GPL and our interpretation of it in the KDE spotte>>statement, this means we should not be distributing (binaries at least) of spotte>>Lyx. For instance, these binaries use .h files from libforms. spotte>> Unlike KDE, it may be all original code, so that a single change spotte>>of license from the developers will do. spotte> spotte> spotte>Boy, Mathias Ehtrich is going to think we have something against him. :) spotte> spotte>Shaya I had no idea he worked on both projects when I wrote that. Someone just mentioned something about lyx being under the GPL, and I looked into it. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: [conrad@srl.caltech.edu: ANNOUNCE: Fulcrum scientific plotting tool update]
On Sat, 10 Oct 1998, Martin Schulze wrote: joey>I wonder if somebody plans to package this one. joey> joey> Fulcrum Scientific Analysis/Plotting Tool for Unix/GTK I am swamped right now. But , I'll try to do it if no one else wants to. I wonder if this is a new incarnation of yorick, which is already packaged John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: KDE gone, Lyx next ?
On Fri, 9 Oct 1998, Darren Benham wrote: gecko>Has it been verified that lyx can't be linked against fltk? I haven't tried. But I read the fltk docs on the subject last week, and the upshot was that most large packages would take a good deal of work to port. eg, there is no canvas widget. (I don't know if lyx uses one) The fltk author says that he is not working towards compatibility with forms. I can't get through to the site now to get the exact statement. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: KDE gone, Lyx next ?
On Sat, 10 Oct 1998, Craig Sanders wrote: cas>nope. sounds right to me (but i haven't looked at the licenses cas>concerned, just going from memory of libxforms being no-source and cas>non-free). libforms is definitely no-source (so its not GPL'd !) /usr/doc/lyx/copyright definitly says that it is distributed under the GPL. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
KDE gone, Lyx next ?
Lyx is currently in contrib. Lyx is licensed under the GPL (version 2) . It is dynamically linked against a non-free library (libforms) . According to the GPL and our interpretation of it in the KDE statement, this means we should not be distributing (binaries at least) of Lyx. For instance, these binaries use .h files from libforms. Unlike KDE, it may be all original code, so that a single change of license from the developers will do. Am I missing something ? John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: LICENSES [was: Re: Have you seen this?]
On 9 Oct 1998, Ben Gertzfield wrote: che>This is a harder one. :) xforms is in the non-free distribution of che>Debian, which technically makes it not part of the operating che>system. I'm not sure how that interacts with the GPL. People keep telling me that you can distribute it with the GPL if a caveat is included. Of course this GPL with a caveat is not quite the GPL . If you use plain-vanilla GPL, then you aren't talking sense. I have seen software other than KDE with this problem. I didn't check further, but some of them probably have other pieces of GPL code. To do it right, you need to get each copyright holder licensing her code under GPL to allow the code to be distributed under another license, ie, the GPL+caveat. If you have a lot of code and a lot of sources, this could be a PITA. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl
On 10 Oct 1998, Ole J. Tetlie wrote: olet>*-John Lapeyre <[EMAIL PROTECTED]> olet>| olet>| Perl 5.004 was in Incoming yesterday. You can get it from a olet>| mirror of incoming or wait a day or two and it will be installed. olet> olet>I can only find the orig source package: olet> olet>ftp> ls perl* olet>200 PORT command successful. olet>150 Opening ASCII mode data connection for /bin/ls. olet>-rw-r--r-- 1 torinDebian2581713 Oct 8 19:40 perl_5.004.04.orig.tar.gz olet>226 Transfer complete. I checked, it has already been installed in slink. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl
Perl 5.004 was in Incoming yesterday. You can get it from a mirror of incoming or wait a day or two and it will be installed. On 9 Oct 1998, Ole J. Tetlie wrote: olet>I installed perl 5.005, but I understand that it has been revoked olet>and all packages in slink shall be built against perl 5.004, olet>is that so? Now where do I find 004? There's no perl in ftp.debian.org olet>and ftp.de.debian.org has 005. olet> olet>thanks olet> olet>-- olet>Eschew obfuscation(go on; look them both up) olet> (Brian White) olet>[EMAIL PROTECTED] [-: .elOle. :-] [EMAIL PROTECTED] olet> olet> olet>-- olet>To UNSUBSCRIBE, email to [EMAIL PROTECTED] olet>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] olet> John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: perl version depends
On Thu, 8 Oct 1998, Michael Stone wrote: mstone>What I'm trying to say is "why doesn't perl look in /usr/lib/perl5 mstone>anymore?" Was this just a gratuitous change, or was there a reason for mstone>breaking things? I can understand the change if there are modules that mstone>work in 5.004 but not 5.005, at least from the upstream perspective, but mstone>don't we already have a mechanism for handling conflicts that makes this mstone>redundant? What does /usr/lib/perl5/5.005 buy us? This is decided by the perl authors, not debian. Darrin can change things and install whereever he likes and change the include path, but we have to make sure it doesn't break things. So to the extent possible, we stay with the official perl installation. However, at least part of their rationale for the new scheme is to allow multiple versions of perl, a feature that debian is not interested in. Why they (perl guys) did not leave /usr/lib/perl5 in the search path is not clear to me. Perhaps because they assume that othe modules will install in site_perl or local. But systems with package managers, like ours don't use these dirs. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: perl version depends
On Thu, 8 Oct 1998, Richard Braakman wrote: dark>That "only" is a large source of packaging bugs. In fact, the (IMO) dark>most annoying upgrade problem in hamm was a pathname problem: two dark>packages had moved to a different directory at the last minute, and dark>the auto upgrade script hadn't been modified to match. Also some complicated packages have perl paths hardwired in relatively obscure places (eg pdl) , and these may not show up immediatley. I agree that there is a good possibility that releasing slink with half a perl upgrade could be a disaster. If we set a policy on the paths within a day or two and then have, say three weeks, and can count on people working hard, and allowing NMU's, we can probably get the critical packages fixed (I don't know what they are). But doing it all in 7 days is not a good idea. Re: installing in /usr/lib/perl5/debian . I have an uneasy feeling about it, but no concrete objections. My guess is that Darrin has a better idea about it than me. It may be ok, I'll follow it if its set. Just to summarize, I think we have to either go back to 5.004 , or push the freeze back a couple of weeks. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: perl version depends
On Thu, 8 Oct 1998, Martin Schulze wrote: joey>(I thought that debian-devel had reached a consensous that it's not joey>a good idea to change the perl version less than 14 days before joey>the code freeze.) Well perl 5.005 is now installed in slink, and when it is installed, alot of stuff breaks (anything for which perl has to include non-standard modules (there are some heavily used non-standard modules (web stuff, perl-tk perl-gtk, ... ). It was supposed to just be a scramble to recompile several things. But now its worse than that-- many more modules need to be repackaged. The worst thing is that we are facing a policy decision on how to handle the change in installation directories. It must be decided before people can begin to fix the 80 odd broken packages. And policy issues tend to get resolved slowly. Raphael suggested modules installing to /usr/lib/perl5/debian and then having the perl package include a symlink to the current version number. Raphael offered to do some NMU's if people asked. I could help too, once the policy is set. We could also force a rebuild (developers) and upgrade (users) every time x changes in 5.00x . Another option is to put the old perl back into slink until the issue can be resolved. Yet another is to configure perl to install stuff according to the old format (the perl configuration scripts can handle this easily ), since we will not have multiple version of perl in the distribution at one time, and this is what the new system is meant to handle. I wrote to perl5-porters asking for some possible tips, but have not heard back yet. I think we need to make a decision rather quickly. If there are some debian developers who know something about the perl development strategy, it would be good to hear from them. I don't know if the perl people really expect everyone to redo the 'perl Makefile.PL ... ' process for every perl package evertime perl is upgraded, but it certainly looks that way. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl policy for managing modules ?
On Wed, 7 Oct 1998, Raphael Hertzog wrote: rhertz>I propose to make package install the modules in /usr/lib/perl5/debian rhertz>and /usr/lib/perl5/debian/$arch. And the /usr/lib/perl5/$version would rhertz>be a link to "debian", and /usr/lib/perl5/$arch/$version a link to rhertz>"../debian/$arch". So the current perl will always find the modules rhertz>installed. And we'll have no problem for the transition to perl5.006 ... rhertz> rhertz>How to manage this in the source package for a CPAN module ? Here's rhertz>what I would have to do for my own package (I tested it) : rhertz> rhertz>- use this line for creating the Makefile : rhertz> perl Makefile.PL INSTALLDIRS=perl LIB=`pwd`/debian/tmp/usr/lib/perl5/debian rhertz>- and use "make pure_install" for installing files Thats how I build my perl modules as well (and I guess others), so it shouldn't be too much of a problem. (Acutally some of the more complicated packages will need more changes.) I can't think of a better solution. Re: packages with only perl source, many will probably not be affected by an upgrade, and it seems silly to require that they be rebuilt. I posted a message on perl5-porters asking for advice. We need to set a policy quickly, as quite a bit of slink has just become unstable. (Unfortunatley, I was using slink for daily science work. I don't have two machines.) John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: perl5.005 installation structure
On 7 Oct 1998, Darren/Torin/Who Ever... wrote: torin> torin>Yes, sorry I'm a bit slow; I'm working on buying a house. torin> torin>I do usually respond quicker to stuff in my inbox than just to list torin>stuff. Unacceptable! ;-) I pulled perl 5.005 out of Incoming over 6 hrs. ago. (Actually, I am quite pleased to see responses so quickly :) ) torin>/usr/lib/perl5 no longer contains *.pm files. If you're using torin>MakeMaker and/or pulling stuff from Config.pm, this shouldn't matter; torin>stuff should just work. Just wanted to make extra-special sure before I dig into my perl packages, some of which need help bad in any case. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
perl5.005 installation structure
Ah, ... you are reading now. Could you confirm or deny, that the /usr/lib/perl5 no longer contains *.pm files ? There seems to be some confusion, but on investigation at perl.org, it looks like this is really the case. Then people will not wait for a bug fix which won't come because its not a bug. btw. Looks like some really cool stuff in the new perl. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005.02
On Tue, 6 Oct 1998, Raphael Hertzog wrote: rhertz>Well it doesn't work out of the box as I expected it. First the rhertz>@INC isn't correct, it doesn't contain /usr/lib/perl5. Please rhertz>Darren can you correct it ? I downloaded the upstream source. It looks like the omission of /usr/lib/perl5 in @INC was intentional. >From INSTALL: =head1 Coexistence with earlier versions of perl5 WARNING: The upgrade from 5.004_0x to 5.005 is going to be a bit tricky. See L<"Upgrading from 5.004 to 5.005"> below.
Re: Perl 5.005.02
On Tue, 6 Oct 1998, Raphael Hertzog wrote: rhertz>And wait for a new perl package so that *.pm file will install themselves rhertz>in /usr/lib/perl5 instead of /usr/lib/perl5/5.005. O, I thought it was perhaps intentional. Could you please notify this list when you upload the new package ? Thanks. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005.02
The new perl breaks all my perl-module packages. How badly I don't know yet. I expected this because I see how the pdl developers scramble to keep up with new releases of perl. It can probably be sorted out, but it will take some effort from all who have perl-module-related packages . One problem is the new perl version is storing files in different places. So modules will have to be debugged to remove hard-wired references to the old paths. On the other hand, pdl , which is a large and sophisticated "module", works OK for the most part, although some path-related bugs are introduced. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Perl 5.005.02
Re: installing perl There is a problem, which is detailed below. I just used --force-overwrite to get around it. homey 3 > ls *.deb perl-base_5.005.02-1_i386.deb perl_5.005.02-1_i386.deb homey 4 > dpkg -i *.deb (Reading database ... 60093 files and directories currently installed.) Preparing to replace perl-base 5.004.04-6 (using perl-base_5.005.02-1_i386.deb) ... Unpacking replacement perl-base ... Preparing to replace perl 5.004.04-6 (using perl_5.005.02-1_i386.deb) ... Unpacking replacement perl ... dpkg: error processing perl_5.005.02-1_i386.deb (--install): trying to overwrite `/usr/man/man3/Data::Dumper.3pm.gz', which is also in packa ge data-dumper dpkg-deb: subprocess paste killed by signal (Broken pipe) Setting up perl-base (5.005.02-1) ... Errors were encountered while processing: perl_5.005.02-1_i386.deb John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: dh_make
On Tue, 6 Oct 1998, Craig Small wrote: csmall>[EMAIL PROTECTED] wrote: csmall>> I have recently created a debian/rules file with dh_make, it used "-g" for csmall>> CXXFLAGS and "-g -O2" for CFLAGS. Is there any reason for not using -O2 for csmall>> C++ compilation? Also do we really want debugging symbols in all the csmall>> binaries? csmall>> csmall>> The C++ code compiled with -O2 seems to run well, so I don't think there's csmall>> any compiler error for my setup (latest EGCS) at least... csmall> csmall>I don't think we need to include debugging code, I'm not sure where the -g csmall>comes from in the CXXFLAGS as I thought I didn't set that anywhere. csmall>scooter$ grep CXX /usr/lib/debhelper/dh_make/*/* csmall>scooter$ Maybe I don't understand what you-all are talking about,... but doesn't policy require compiling with -g and then stripping ? Last time I read the policy manual, this was the case. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Should Package Web page be changed for non-free (Re: glimpse on CD?)
On Mon, 5 Oct 1998, Peter S Galbraith wrote: Galbra>What I find strange if that I managed to download it without realising it Galbra>was non-free. I only *now* noticed that it's non-free by putting the Galbra>cursor on the `Download it!' ftp link and seeing the non-free part in the Galbra>path. I have built packages and uploaded them to main only to find later that they depend on non-free libraries that appeared free when I found them on the web page. (note that when the lib later shows up as a dependency, it is listed as non-free) . John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: GPL'd libforms dependent package
On 4 Oct 1998, Gregory S. Stark wrote: gsstar>a fltk package based on the last stable release (i think) of it before it went gsstar>non-free. It's a nice lightweight LGPL'd toolkit which is nearly drop-in gsstar>compatible with libforms. According to http://fltk.easysw.com/ , you did get the last stable release. I looked at your package, it looks well done (I saw some packaging rules that I haven't followed :( ) When you upload an recompiled version, I'll try some of my packages that use libforms. Its funny, I read on slashdot that fltk is going non-free, but there is a September 23 release which is still under the GPL . John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: GPL'd libforms dependent package
On 4 Oct 1998, Gregory S. Stark wrote: gsstar>However, a better solution would be to try compiling it against fltk. We have gsstar>a fltk package based on the last stable release (i think) of it before it went gsstar>non-free. It's a nice lightweight LGPL'd toolkit which is nearly drop-in gsstar>compatible with libforms. I was under the impression that it was not really a drop in replacement. But I see that you are the maintainer... I guess I can give it a try. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
intent to package tochnog
License: GPL tochnog is a finite element analysis program. http://info.uibk.ac.at/c/c8/c813/tn_release/tnhome.html The author calls the executable 'tn' . I should probably change this to 'tochnog' or 'tng' or something. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
GPL'd libforms dependent package
This a kind of interesting looking package. It is GPL'd but depends on a no-source-available library. I just reread the relevant portions of the GPL, but I'm no Talmudic scholar. Can the GPL be properly applied to this ? http://ifb.bv.tu-berlin.de/JOCHEN/XSTAB/xstab.html John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: An X version of dselect for slink
On Fri, 2 Oct 1998, Enrique Zanardi wrote: ezanar>Moving X to the base disks (Auch!) and configuring X just after the first ezanar>reboot (hard task for a newbie). I'm not excited about that. hard not just for the newbie ! I advocate, as usual, a sentence in install.txt asking the user to only install preselected packages on the first run through dselect. This would clear up many complaints. Then suggest installing X and running the Graphical-fe to dselect if the user prefers an X interface. The other option is to continue using terminal front end but again ask them not to do too much at once. A working GUI couldn't hurt in any case (unless it's buggy and trashes systems !) 15 days of testing isn't much. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Hamm Bug Stamp-Out List for June 25, 1998
On Thu, 25 Jun 1998, Dale Scheetz wrote: > The upstream maintainer (Ulrich D.) insists that the relative links are > correct and that making /usr a symlink to something else is "evil". I'm running out of space and wanted to move subdirs of /usr to another partition. But because of relative links pointing back up to '/', this is impossible. I hope there is a good reason for using relative links, because as it is , /usr must be on the same partition as '/' , or else consist of an entire partition. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bad kernel 2.0.34 bug ?
On Wed, 24 Jun 1998, Andreas Jellinghaus wrote: > i have 40 identical computers here, and one of them has the same problems. > i guess some trouble with the mainboard, but i'm not sure and could not > investigate till today. all other machines work fine (with hard disk, > 2 have network card problems, but that should affect this). I'm thinking that may be it too, since it occurs with all drives on both controllers. I fried the floppy controller a couple of months ago, but I don't recall this problem 'till recently. By the way, I have not been able to get the floppy controller on an IO board to function yet (tried three IO boards) , tried everything I could think of. Does anyone have experience with this? John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bad kernel 2.0.34 bug ?
Well , its already off. Thanks for the tip. I downgraded to 2.0.33, and things are much more stable , so far, but I've seen a couple of errors. I guess we'll have to wait a while longer and see if other people report the same thing. On 24 Jun 1998, Gregory S. Stark wrote: > Are you running with unmasked interrupts? > hdparm -v /dev/hdb > and look at the unmaskirq flag. > > If so try turning it off? John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bad kernel 2.0.34 bug ?
OK, I was wrong , its happening now with 2.0.33 too. However, its happening to all three ide drives. I'd better figure it out fast On Wed, 24 Jun 1998, Christian Meder wrote: > On Wed, Jun 24, 1998 at 12:24:52AM -0700, G John Lapeyre wrote: > > A typical error message is (this occurs on 2 of three drives): > > > > Jun 23 20:35:40 homey kernel: hdb: read_intr: status=0x59 { DriveReady > > SeekComplete DataRequest Error } > > Jun 23 20:35:40 homey kernel: hdb: read_intr: error=0x40 { > > UncorrectableError }, LBAsect=6766956, sector=211869 > > Jun 23 20:35:40 homey kernel: end_request: I/O error, dev 03:46, sector > > 211869 > > This looks rather like a dying harddisk. I saw it some time ago too ;-) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
bad kernel 2.0.34 bug ?
My file systems are getting trashed. I get errors and eventually the system hung (couldn't shutdown). I switched back to 2.0.33 and everything is fine. I'm not sure if overheating has something to do with it as well. A typical error message is (this occurs on 2 of three drives): Jun 23 20:35:40 homey kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } Jun 23 20:35:40 homey kernel: hdb: read_intr: error=0x40 { UncorrectableError }, LBAsect=6766956, sector=211869 Jun 23 20:35:40 homey kernel: end_request: I/O error, dev 03:46, sector 211869 John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
possible lurkftp bug
If lurkftp is killed and started again (happens alot) it gets everything that it already got again, even though its supposed to compare with the local tree. Tell me if I am missing something, otherwise, I'll file a bug. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Let's not add more complication to the installation of the distribution which is perceived to be difficult to install. Remember, doing a few things by hand is a much bigger pain for a busy sysadmin who is less experienced with Debian than the developers. I see a lot of developer-centric opinions on this list. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Sun, 21 Jun 1998, Alexander Shumakovitch wrote: > Unfortunately, dselect not only doesn't upgrade from 2.0.7pre1-4 to 2.0.7-1, > but it wants to upgrade FROM 2.0.7-1 TO 2.0.7.pre1-4 now! And moreover I have > broken dependencies now, since apt_0.0.16 depends on libc6 >=2.0.4pre1. It > implies that I should either "upgrade" to the previous version, or forget > about using apt method in dselect until it's fixed. :-( Apt works fine if everything else is perfect. I'd still like it to be more fault tolerant. The fix-it-up option added a few versions ago does help. But, for instance, I did an upgrade of a 2 mo. old hamm for a friend . I tried to fix problems using dpkg, but it was too much work. Tried apt via dselect, and it complained. Finally I had to use a dselect w/o apt to upgrade, which worked fine. After that, apt works again. Another example is a package with some kind of install problem. It can be a minor problem that interferes with nothing, but until I find the problem and solve it by hand, apt won't do anything else. I know I was on about this a couple of months ago, but I'm mentioning it again after more experience. I'm not complaining, just suggesting. In the meantime, I've used apt to easily upgrade many times and hundreds of packages. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MetroX installer.
Has anyone looked into a MetroX installer package, or the like? It comes tar'ed or rpm'd . I'm thinking of all the Thinkpads with a neomagic videocard. I was trying to help a friend install Debian on one. (The tecra boot disk didn't work, but who knows, maybe the floppies were bad...) He'll probably end up going with RH, or worse, keep lose95 . Just a thought ... John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
selling hamm CD 's ?
Does anyone have hamm CD's to sell yet ? I have a friend in Paris who wants to install on a laptop. I'd hate to see him go RH. I think he has a network card. Maybe apt and a remote archive works pretty well now for installing ? John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FIX FOR HAMM: timezone problem
I found the entire kernel/hw clock issue quite confusing. (eg , when to use the uct flag ) The man pages help a little. A clock howto would be quite helpful. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Building a connection with Kachina Tech.
To the extent that I have a goal in Debian , its packaging these things (I've already done three or four) . For the time being, I am putting it all in 'math'. We may want to change the name or granularity at some point, if packging these things really takes off. I agree that 'sci' would be a better description than 'math'. On Mon, 15 Jun 1998, Alexander Kushnirenko wrote: > Hi, Johnie! > > > > Some SAL classifications include chemistry, biology, artificial > > intelligence, physics, astronomy, relational DBMS, parallel computing, > > geographic information systems, and scientific data processing and > > visualization, some of which are poorly described by "math". > > > Agreed. But perhaps putting all of that in "math" is as good solution as > putting it all in "sci". Maybe finer granularity would do it, but I don't > know what are the consequences of that. Perhaps I don't quite realise the > problem :) > > Sasha. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.0.34
I haven't tested it, but it really looks like Gordon Chaffee's patches are included. homey 4 > rgrep -i -r 'fat32' . ./fs/fat/cache.c: fat_bits == 16 ? EOF_FAT16 : EOF_FAT3 2); ./fs/fat/inode.c: int fat32; ./fs/fat/inode.c: if (!b->fat_length && b->fat32_length) { ./fs/fat/inode.c: /* Must be FAT32 */ ./fs/fat/inode.c: fat32 = 1; ./fs/fat/inode.c: MSDOS_SB(sb)->fat_length= CF_LE_W(b->fat32_lengt h)*sector_mult; ./fs/fat/inode.c: fat32 = 0; ./fs/fat/inode.c: MSDOS_SB(sb)->fat_bits = fat32 ? 32 : ./fs/fat/misc.c:/* Flushes the number of free clusters on FAT32 */ ./fs/fat/misc.c:/* The fat32 boot fs info is at offset 0x3e0 by observat ion */ ./fs/fat/misc.c: MSDOS_SB(sb)->fat_bits == 16 ? EOF_FAT16 : EO F_FAT32); ./CREDITS:D: vfat, fat32, joliet, native language support ./include/linux/msdos_fs.h:#define EOF_FAT32 0xFF8 ./include/linux/msdos_fs.h: /* The following fields are only used by FAT32 * / ./include/linux/msdos_fs.h: __u32 fat32_length; /* sectors/FAT */ ./include/linux/msdos_fs.h: __u16 starthi;/* High 16 bits of clust er in FAT32 */ ./include/linux/msdos_fs_sb.h: fat32:1; /* Is this a FAT32 par tition? */ ./include/linux/msdos_fs_sb.h: unsigned long fsinfo_offset; /* FAT32 fsinfo off set from start of disk */ On Tue, 9 Jun 1998 [EMAIL PROTECTED] wrote: > I downloaded the sources for the 2.0.34 kernel and did a quick look through > the files. The fat-32 patches do not seem to be in here. If 2.0.34 is to > be released as a debian package, then I hope all of the patches that are in > the 2.0.33 package are added. > > Also has anyone packaged the Real Time linux kernel mods and utilities? > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About the Hamm Freeze (!)
My last message couldn't have been more wrong ! Maybe there is a difference between the perl interface to gdbm and some core perl function that relies on it ? On 7 Jun 1998, James Troup wrote: > Raul Miller <[EMAIL PROTECTED]> writes: > > > James Troup <[EMAIL PROTECTED]> wrote: > > > > > I don't know perl, and am only going on what Ray has been telling > > > me. It was my understanding that perl could be made to > > > dynamically load it's gdbm part on request and that way perl need > > > only recommend or (better) suggest gdbm. Is this not the case? > > > > A quick test using strace suggests that this is already the case. > > Blah. An even quicker ldd reveals this is already not the case. > > 20:45:[EMAIL PROTECTED]| ~ $ldd /usr/bin/perl | grep gdbm > libgdbm.so.1 => /usr/lib/libgdbm.so.1 (0x40015000) > 20:46:[EMAIL PROTECTED]| ~ $ > > Until _that_ changes, perl can't not Depend on gdbm. > > -- > James > ~Yawn And Walk North~ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: About the Hamm Freeze (!)
Yes this is clearly a dynamically loaded module. There is no question that the perl binary will run if /usr/lib/libgdbm.so or whatever is absent. homey 41 > locate GDBM /usr/lib/perl5/i386-linux/5.004/auto/GDBM_File /usr/lib/perl5/i386-linux/5.004/auto/GDBM_File/autosplit.ix /usr/lib/perl5/i386-linux/5.004/auto/GDBM_File/GDBM_File.bs /usr/lib/perl5/i386-linux/5.004/auto/GDBM_File/GDBM_File.so /usr/lib/perl5/i386-linux/5.004/GDBM_File.pm /usr/man/man3/GDBM_File.3pm.gz On Sun, 7 Jun 1998, Raul Miller wrote: > James Troup <[EMAIL PROTECTED]> wrote: > > I don't know perl, and am only going on what Ray has been telling me. > > It was my understanding that perl could be made to dynamically load > > it's gdbm part on request and that way perl need only recommend or > > (better) suggest gdbm. Is this not the case? > > A quick test using strace suggests that this is already the case. > > My not-always-correct memory suggests that the gdbm support code > currently lives in /usr/lib/perl5/i386-linux/5.004/auto/GDBM_File > (at least for the intel world). > > -- > Raul > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tetex-bin install bug ?
It appears that an old /etc/texmf/texmf.cnf was not being removed and the installation of tetex-bin would not overwrite it. I'm not sure if this was my fault or if I tried to do a normal upgrade and it went wrong. ( i did use apt once without sufficient disk space, and this broke a lot of stuff) On Fri, 5 Jun 1998, G John Lapeyre wrote: > > I sent a message to the maintainer , but haven't heard back. > Is this something broken on my system ? I tried forcing removal > of all my tetex packages and reinstalling. > I get this when trying to install tetex-bin . > > Setting up tetex-bin (0.9-5) ... > /usr/bin/texconfig: No $TEXMFMAIN; set the environment variable or in > texmf.cnf. > dpkg: error processing tetex-bin (--configure): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > tetex-bin > E: Sub-process returned an error code > homey 55 > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tetex-bin install bug ?
I sent a message to the maintainer , but haven't heard back. Is this something broken on my system ? I tried forcing removal of all my tetex packages and reinstalling. I get this when trying to install tetex-bin . Setting up tetex-bin (0.9-5) ... /usr/bin/texconfig: No $TEXMFMAIN; set the environment variable or in texmf.cnf. dpkg: error processing tetex-bin (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: tetex-bin E: Sub-process returned an error code homey 55 > John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
advantage of new kernel 2.0.34
They have included the FAT32 support. Many users need to mount their win95 partition. Many can't even install without support, as they need to install from a FAT32 partition. I had this problem installing on a machine a few months ago. You had to patch 2.0.33 to get it. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Consesus on Linuxconf?
On 4 Jun 1998, Andreas Degert wrote: > If you look at config files like .emacs or /etc/profile where it's > apparent that they use a structured language, it's much more clear > that a configuration program can't grok each possible config file the > user can write with an editor. It's also not uncommon to see config files which just contain perl code. (Majordomo comes to mind) . Probably python programs do this too. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Differences of Debian vs. the Other Guys
On Tue, 2 Jun 1998, Javier Fernandez-Sanguino Pen~a wrote: > > What are the main differences/advantages/disadvantages of > Debian's Packaging System vs The Other Guys (tm) ? > > I would appreciate any help in sorting these out (I already have So would we ! John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
leaving town for 1 week
There is no possiblity that urgent bugs could arise in my packages (because the packages are marginal) . But if the impossible happens, please feel free to upload a fix. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
corel porting apps to linux
Does anyone know if something official is released? I have only seen the irc transcript on slashdot. John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Intent to package SAML (math)
This is GPL'd, the package is nearly finished. Description: SAML is a C library for symbolic calculations, accompanied by some application programs (samuel, factorint, induce), and Python bindings. The library provides an object-oriented framework for defining and handling mathematical types, and implements the most common data types of computer algebra: integers, reals, fractions, complex numbers, polynomials, tensors, matrices, etc. The application programs consist of an interactive symbolic calculator (samuel), a programming language (induce) and a program to factorize integers (factorint). John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apt and caching .deb's
Apt downloads all the packages and then installs them. Every RH and Debian network method I've seen does this. Is there a way to download a package, install it and throw the deb away, to save disk space ? If I wait too long between upgrades, I run into big problems. Otherwise apt is impressive. When I show someone how it quietly upgrades 100 packages, it impresses the hell out of them. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [dpkg] Installing software as a non privileged user - A suggestion
This is a great idea.Sysadmins can't keep up with the needs of an experienced user. I am almost sure dpkg won't do this now. There will be all sorts of problems with locations of files. To make sure every package supports this would add complexity and burden. We could have something that makes a best guess on how to install it, with no burden on the maintainer to make sure it works. Developers will probably oppose this because it doesn't allow to aspire to perfection. But, in a less than perfect world (this one) it would be a good idea. Now, ... who is going to write it Sudhakar Chandrasekharan wrote: > I don't know if this has been discussed here before. > > Is it possible for a non privileged user to use dpkg to install a package > under the user's home directory? I know this kind of installation is not > perfect. But sometimes it is helpful. What are the pros and cons of this > kind of an approach? John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Run away TCSH
Luis Francisco Gonzalez wrote: > Mark W. Eichin wrote: > > someone on tcsh-dev found that bug - I sent in the particular patch as > > a bug report, but haven't heard anything (on this or on the > TCSH was orphaned for six months. I took maintainership three days before the > freeze. I have since solved five bugs. Among them the runaway problem althogh > all the credit goes to [EMAIL PROTECTED] who found the problem. The patch you > sent only solved the symptoms AFAICT, not the problem. I did answer the bug > report you sent. Go check the bug database. Mark's message didn't look too accusatory (perhaps not so tactful either). Luis took this package under duress because no one else would. Its a very important package , with a lot of bugs. The code is a mess. Nothing returns a status flag. Even the upstream author doesn't see an obvious fix to the runaway problem. Luis fixed some bugs and worked on internationalization. Luis should be thanked for making any progress at all. (btw, I looked at master a few days ago and couln't find the new tcsh in incoming , nor in hamm , I'll have another look.) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Time to say goodbye...
Michael Meskes wrote: > Jim Pick writes: > > I must admit, I've been entirely negligent in following the policy > > discussions - due to lack of time, I've skipped them entirely. > > Me too. Me three. I am but a humble physics student ( ;-) ) who wants to package a few science things for his own personal and political reasons. I don't have time to be a powerful maintainer, and don't want to get any ego tied up in it. (and I've only been here 8 months) I had to toe the line on Christian's opinion on some docs. A lot of us are willing to do that because we appreciate the magnitude of the work of some of the key players. I hope Ch. is not leaving because of losing one battle (maybe its more). ( I am not taking sides on the number-of-maintainers-per-package issue, or on the how-to-challenge-policy-issue. Those folks may have taken reasonable positions. ) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Run away TCSH
Jason Gunthorpe wrote: > > I recall there being a discussion on this some time ago, I just noticed on > master, There is a bit of dicussion on it in the bug system. I corresponded with the debian mainainter (Luis Gonzales) and the upstream author. They think it is a pretty tough problem. I spent several hours on it myself, but I don't have the skills/time required to fix it. I made a fix that works in some circumstances , but not all, and I am not sure it didn't break something else. Luis tried to upload a fix (from a debian maintainer) to chiark, but it got lost. I can't find it. Luis inquired about it a while ago and was instructed to wait. From the discussion on the fix, I doubt it will work, but I'll test it as soon as I see the package. If anyone's interested, I put detailed instructions in bug reports on how to produce it. Also I think I sent instructions on how to get it to occur under gdb (I had to use the 'attach' command) . John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: first proposal for a new maintainer policy
On 28 Apr 1998, Manoj Srivastava wrote: > Is that such a bad thing, really? I would rather that the > policy documents be corrected, and held as a set of rules htat > have to be followed, woth an exception for the items that happen to Debian is great and everything, but it is huge and decentralized. Read the write-ups about O'Reilly's sumit. They all thought that centralized control was an ingredient in their individual succeses. Perhaps Debian can get by without it. But without and central control AND no fast rules, it will probably degenerate. Strict rules and route for appeals for flexibility is the way to go. Rules are the only central authority holding things together. (Who holds the power to make rules is another matter.) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian GNU/Linux: Best of the Web! (fwd)
On Tue, 21 Apr 1998, Sudhakar Chandrasekharan wrote: > The Minig Co? Not likely. I did a little bit of part time work for them > and was even offered a job a year and half back. I refused to take it up > because they were Gung Ho about NT. For one of my projects for them I Yeah, it really looks like the bulk of the site is MS worship. But they have a linux zealot doing the linux corner. I don't know what he uses, seems pretty careful though. eg, there is a preamble to the list of news groups warning about interrupting work. Which reminds me , there is too much non-essential crap on this list ....... (!) John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian GNU/Linux: Best of the Web! (fwd)
On Tue, 21 Apr 1998, James A.Treacy wrote: > For those few of you who don't read http://slashdot.org, the > Mining Co has posted their Linux "Best of the Net" site awards. > Debian was number 1. I'd never heard of this company before, > but am not adverse to any good publicity for Debian. > The awards page is at http://linux.miningco.com/library/awards/blapr98.htm Looks like they've put a good deal of effort into their site. I don't know who made the ratings(has good taste, I imagine) ... but notice Debian is the #1 site, while no other distribution made the top 10. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: update-menus broken ?
> This means that you deleted a mwm conffile > /etc/X11/mwm/system.mwmrc-menu, or you never installed lesstif-bin. If > you touch that file, the error will go away. I have lesstif-bin installed and I didn't delete /etc/X11/mwm/system.mwmrc-menu . Some broken package may have deleted , but I didn't . Looks like two things are broken, whatever deleted or didn't install that file, and update-menus for not working when it's missing. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
update-menus broken ?
I think /usr/bin/update-menus may be broken. Several packages give me an error when they try to install. Fvwmconf was successfully added to the menus when I packaged it last month . Now installing it gives error messages and update-menus fails. Has anyone else seen this ? homey 5 > dpkg -i fvwmconf_0.18-1.deb Cannot open file /etc/X11/mwm//system.mwmrc-menu /etc/menu-methods//mwm-menumethod: Aborting Selecting previously deselected package fvwmconf. (Reading database ... 48261 files and directories currently installed.) Unpacking fvwmconf (from fvwmconf_0.18-1.deb) ... Setting up fvwmconf (0.18-1) ... Update-menus: waiting for dpkg to finish (forking to background) Update-menus: (checking /var/lib/dpkg/lock) homey 6 > Cannot open file /etc/X11/mwm//system.mwmrc-menu /etc/menu-methods//mwm-menumethod: Aborting John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Dictionary Packages
I like the idea of having all the material available in a form that is as convenient as possible (ie alread .deb) . But this is similar to the problem of packaging large scientific packages which are interesting to only a limited number of people. (similar, but different reasons for keeping it out of the archive). This discussion has come up several times in the nine months that I've been reading this list. It looks like the time is arriving for (someone with tons of time) splitting the archive in some way. John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tcsh infinite loop patch
I added one line to the tcsh code, which seems to fix the infinite loop problem. I sent the patch to the author and the Debian maintainer 24 hrs. ago. I expect to hear something over the next few days. Perhaps the author will make a better fix. If someone can't wait that long, mail me John John Lapeyre <[EMAIL PROTECTED]> Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]