Re: the logo: logo selections now available!
On Wed 07 Apr 1999, Buddha Buck wrote: I think Bruce Perens gave a good definition earlier... 1) easily reproduceable 2) instantly recognisable 3) iconic (i.e., not language dependent) I've been watching all the discussions about this, and increasingly think we're not looking for a logo; we appear to be looking for a symbol. One of the criteria was that it shouldn't be based on the word `debian'. I've never really seen a good argument for this; many (if not most) commercial logos are based on the word (Sony, GMC, Canon, IBM, Kellogs, KLM, Nokia, (dare I say it) Microsoft, ...). A symbol, however, is a different kettle of fish. My question: Why are we discussing this on debian-devel-ANNOUNCE? Because debian-devel-announce doesn't set an automatic reply-to: debian-devel in the style of comp.os.linux.announce setting the followups to col.misc and no one notices / can be bothered to change that. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: ISDN problem ....
On Sat 03 Oct 1998, Martin Bialasinski wrote: MD == M Dietrich [EMAIL PROTECTED] writes: MD when installing isdnutils from slink, MAKEDEV complains about MD device names - something like 'don't know how t mail isdnctrl0' or MD something (don't remember exact device name). I believe this is already reported as http://www.debian.org/Bugs/db/26/26971.html (release critical!) Yes, I reported it. Apparently (from the makedev changelog) a new upstream version was used, and I'm assuming that that's when the ISDN stuff was lost. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Imlib NMU
On Sun 04 Oct 1998, Brian Almeida wrote: I just talked to Shaleh, the previous Imlib maintainer. It was intentional to use libjpegg6a for imlib. 6a and 6b do not play well together. Your NMU Is it necessary that they play _together_ ? breaks every Imlib-using GNOME package out there. Therefore I am overriding it. Please go through the correct channels next time, instead of going out and doing NMUs of other peoples packages without a so much as a by-your-leave. That is the whole point of the Bug tracking system. I check my mail regularly, as does Shaleh. Let us know before you go out doing stuff that affects other people's packages. Going to libjpegg6b is fine. But all the other packages have to make it there as well. Do you really mean _all_ other packages? AFAIK you can have libjpegg6a and libjpeg6b installed together (I didn't find a libjpegg6b package). Additionally, isn't it that so that those packages that use imlib and depend on libjpegg6a, depend on libjpegg6a only because imlib does? In other words, I think those packages don't directly link in libjpegg6a, only indirectly via imlib (after all, they're using imlib for the image manipulation, so why should they need libjpegxxx directly?) Forcing a package to depend on an older version will lead to a situation where everyone is waiting on someone else to make the first move; if for example gmc is rebuilt, it will still depend on libjpegg6a, because the current imlib stuff still depends on libjpegg6a. However, what I read from your message is that an imlib that depends on libjpeg6b must not be uploaded because there are still packages that depend on libjpegg6a. Chicken and egg problem a.k.a. circular dependencies. Do you see the problem? After all, slink is unstable; you can expect this sort of thing to happen... It's just necessary that those packages that use imlib have to be rebuilt. It worked fine on the Alpha architecture, where we can do that in one swell foop. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Imlib NMU
On Mon 05 Oct 1998, [EMAIL PROTECTED] wrote: On 05-Oct-98 Paul Slootman wrote: Do you really mean _all_ other packages? AFAIK you can have libjpegg6a and libjpeg6b installed together (I didn't find a libjpegg6b package). Additionally, isn't it that so that those packages that use imlib and depend on libjpegg6a, depend on libjpegg6a only because imlib does? No. Look at the output of 'imlib-config --libs' sometime. Yes, I see: -L/usr/lib -lImlib -ljpeg -ltiff -lgif -lpng -lz -lm -L/usr/X11R6/lib -lSM -lICE -lX11 -lXext Because imlib is used on more platforms than just linux, and on other platforms, linking shared libs to shared libs doesn't always work. So, every Then the question may well be that as it is supported on linux, why is 'imlib-config --libs' invoking all those libraries on linux? It may be necessary on other platforms, but as you implicitly say, it's not on linux. application that uses imlib uses the imlib-config program and links against all the necessary graphics libs as well. Really? The first package (chameleon) I checked that I've built myself that uses imlib shows (in the build log): gcc -O2 -pedantic -Wall `gtk-config --cflags` -c info.c gcc -o chameleon chameleon.o setrgb.o setname.o setfile.o info.o -L/usr/X11R6/lib -lX11 -lXext -lm -lImlib `gtk-config --libs` I see that -lImlib is explicitly linked, and no mention of imlib-config. I guess this should be considered a build bug of chameleon, however it shows that NOT every package that uses imlib also uses imlib-config. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Free, but crappy, kaffe.
On Tue 06 Oct 1998, Ean R . Schuessler wrote: I did, however, list my sex as a narcoleptic rat monkey with the spirit of an androgenous toaster in the chakras of a Kentucky NAMBLA representative or something along those lines. ;- Of course, that should have been listed as species, not sex. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: How about using bzip2 as the standard *.deb compression format?
On Mon 05 Oct 1998, Paul Slootman wrote: On Sun 04 Oct 1998, James Troup wrote: Joseph Carter [EMAIL PROTECTED] writes: Old/slow/lomem machines can't properly compile X or Mozilla anyway. Bzzt. I've compiled xfree86 for Debian/m68k on a 386/25 equivalent with only 14Mb (don't ask) of memory several times. Took 5 days, 14MB isn't that lomem... BTW, I just had a look at the new bzip2 version. This are the relevant lines from top while running 'bz2cat linux-2.1.124.tar.bz2 | bzip2 x': PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND 30413 paul 20 0 6820 6820 288 R 0 72.0 10.7 3:55 bzip2 30412 paul 0 0 3928 3928 288 S 0 23.5 6.2 0:48 bz2cat Decompressing doesn't take that much time nor memory, if I compare it for example with my X server: 265 root 0 0 15028 11M 1004 S 0 0.5 19.0 542:35 XF86_SVGA Of course, 4MB is still quite a lot, but I guess that should be doable for just about everyone. Alternatively, from the manpage: Compression and decompression requirements, in bytes, can be estimated as: Compression: 400k + ( 7 x block size ) Decompression: 100k + ( 4 x block size ), or 100k + ( 2.5 x block size ) and For files compressed with the default 900k block size, bunzip2 will require about 3700 kbytes to decompress. To support decompression of any file on a 4 megabyte machine, bunzip2 has an option to decompress using approximately half this amount of memory, about 2300 kbytes. Decompres sion speed is also halved, so you should use this option only where necessary. The relevant flag is -s. So, I think that some experimentation of what block sizes and flags to use may be in order. Besides, as decompression is done internally by dpkg (right?), dpkg could check the memory available on the machine and decide which decompression algorithm to use. In short, I don't really think that there are compelling arguments _not_ to consider bzip2. And yes, x ended up identical to linux-2.1.124.tar.bz2 in case you're wondering :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim really does need to be the standard MTA in slink
On Tue 06 Oct 1998, Robert Woodcock wrote: Just out of curiosity, what's the security track record on smail vs exim for the last two years? The standard MTA should have a chance of being secure from remote attacks for at least a year after release. In the words of Philip Hazel (the Exim author): I'm not trying to hold up Exim as a great secure system. I have tried my best to make it secure within the limits of the way it operates, and to describe it as well as I can. The code is there for anyone to read. It is up to you to decide whether to run it or not. Of course I am pleased when people choose to run my code, but as I am not selling it, I do not have to advertise or try to persuade anybody. You can read the rest of the story at http://www.mailbot.com/cgi-bin/archives/getln?eximusr1998-0900332 . I personally have confidence in Exim's quality in this regard. Demon (a large ISP in the UK and the Netherlands, www.demon.net) uses Exim as its customer-facing smtp interface, so I guess that they're convinced as well. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: what's after slink
On Thu 08 Oct 1998, Kai Henningsen wrote: [EMAIL PROTECTED] (Justin Maurer) wrote on 04.10.98 in [EMAIL PROTECTED]: On a related note, do we want to continue using names from pixar movies now that Bruce is gone? i see no reason not to. they are nice names, the only problem is that we may be running out of good ones (i admit, rc was a stretch) Nice? Hmmm ... just about nobody seems to recognize them, so I hardly think they are particularly nice. More like silly and annoying. I remember when I got my first debian cdrom (1.3.1); looking in the directory gave amongst other bo and boot. My first impression was that someone had screwed up when creating the boot directory the first time. It took a _long_ time for me to realize that bo was in fact the code name for the distribution (around the time I was in the process of becoming a developer, in fact; when I was just a user I never really understood what this bo was doing on my cd. Using something that is more clearly a codename (like Red Hat's Hurricane, for example) would be an advantage there. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim really does need to be the standard MTA in slink
On Wed 07 Oct 1998, Steve Lamb wrote:
On Wed, 7 Oct 1998 13:00:51 +0200, Paul Slootman wrote:
I personally have confidence in Exim's quality in this regard.
Demon (a large ISP in the UK and the Netherlands, www.demon.net)
uses Exim as its customer-facing smtp interface, so I guess that they're
convinced as well.
Just curious how you know this since when I telnet to their relay hosts
they are very non-descript about what they run.
[EMAIL PROTECTED]:/home/morpheus}telnet relay-1.mail.demon.net 25
Trying 194.217.242.51...
Connected to relay-1.mail.demon.net.
Escape character is '^]'.
220 relay-1.mail.demon.net Server SMTP (Complaints/bugs to:
Hmm. At least the NL people use Exim (haven't checked what the SMTP
banner says). But when I send mail from my demon account, a line like
the following is in the received headers:
Received: from [194.159.224.75] (helo=wurtel.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 2.02 #1)
id 0zQaxA-0003Hh-00; Tue, 6 Oct 1998 17:31:16 +
The SMTP banner is trivial to customize, of course... The default is
smtp_banner = ${primary_hostname} ESMTP Exim ${version_number} \
#${compile_number} ${tod_full}
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
contacting porters (was: Contacting authors)
On Thu 08 Oct 1998, Edward Betts wrote: And while we are doing it how about implementing @m86k.porter.debian.org or @arm.builder.debian.org for the person who has recomplied the package on different machines (m86k, powerpc, alpha, arm, etc). Now this _is_ a good idea! I've already asked on debian-alpha a couple of times who ported this package?. I port a lot of alpha packages myself, and don't always remember whether I did the current version or maybe a previous version... This list could be updated via the maor-installer thing (whatever also sends the email message; that has all the info right there). An easy way to implement this would be to simply add a line to the source section of debian/control of each package like Likewise with builder, or not? Would you need m86k-builder and arm-builder and powerpc-builder or would it be done differently? It's there in the changes file... Note that this would imply that there should also be a [EMAIL PROTECTED] which would usually be the same as [EMAIL PROTECTED] (but not always! The maintainer may use something else besides i386 as his platform). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: The freeze and IMMINENT 2.2.0p1!!
On Fri 09 Oct 1998, J.H.M. Dassen Ray wrote: and the message Linus just sent off to linux-kernel about 2.1.125 and 2.2.0p1 could the freeze be pushed back a week to see if we should QUICKLY re-target slink towards 2.2.0? I'm not aware of any software in slink that must be updated to work with 2.2 properly (with the exception of pcmcia-cs); slink currently runs fine with 2.1.x (which I suspect quite a few developers run). Isdnutils needs to be rebuilt; some of the structures passed in ioctl's have changed. The important stuff from isdnutils refuses to run on 2.2 (you get a message about wrong versions, so at least it doesn't crash). That said, it's trivial to rebuild (if perhaps a bit longwinded). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Ropes in stl (was Re: lack of wstring in libstdc++2.8-dev)
On Mon 12 Oct 1998, Chris Leishman wrote: On Mon, Oct 12, 1998 at 08:24:49AM +0100, M.C. Vernon wrote: void main(void) snippety BTW, main returns int, not void. See the comp.lang.c FAQ for the bit of the C standard that defines this - main is incorrectly said to return void in a number of texts though. Yeah, I know...but when I'm writing little 2second programs to check something I tend to not fuss with returns, etc, etc... Then you should just leave out the void in front of main; that's less typing and does the right thing :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: PROPOSAL: one debian list for all porting efforts
On Mon 12 Oct 1998, Hartmut Koptein wrote: to increase communication betweenm the ports and between porters and non-porters, I'd propose a new list: debian-porting or sim. I fully support this proposal (The name debian-porting seems fine to me) No, we haven't enough topics for this new list. It would be a useful way of communicating diffs that were necessary to build a package on a given architecture (those diffs usually involve fixing some silly packaging bug, and are then applicable to all other architectures on which the package is to be ported). IMHO, it makes sence to create a new list, since it seems 90% of the Debian developers use i386 only... :-) debian/i386 is also a port! No. For 90% (I think more) of the packages it is the primary architecture. The word port implies carrying to _another_ architecture. Hence the package on the primary architecture is _not_ a port. I'm thinking of using my Alpha as primary platform for my packages, let the i386 people take care of porting them! (Although I think that porting would never happen...) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Bug Report?
On Wed 14 Oct 1998, Drake Diedrich wrote: d) Try using NFS. This slows down the i/o bound resource hog enough to leave the machine usable for interactive tasks. Yes it's ugly, but scheduling in 2.0 is suboptimal, and nice doesn't have much effect on i/o, only CPU. An extra disk dedicated to the i/o hog would probably be better than an SMP for this problem. I've noticed that if something is doing heavy IO over a _large_ range of data, what happens is that RAM gets tied up in the buffers for the accessed data. Try something like dd if=/dev/hda of=/dev/null bs=500k to see what I mean. It's unfortunate that there's no way to tell the kernel that the data being read sequentially, so there's no point in keeping that data around in the buffer cache after it's been passed to user-land... Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: lilypond, egcs and libc6 2.0.7u? (or Cyrix?)
On Sun 11 Oct 1998, Anthony Fok wrote: it spitted out the following error messages: out/template2.o: In function `global constructors keyed to Cursorvoid *::operator-(Cursorvoid *) const': [...] I am using the following on my Cyrix P166+ (133 MHz) computer: ii libc6 2.0.7u-2 The GNU C library version 2 (run-time files) ii egcc2.91.57-3 The GNU (egcs) C compiler. ii g++ 2.91.57-3 The GNU (egcs) C++ compiler. What libstdc++*-dev / libg++*-dev do you have installed? I tried compiling lilypond on master, and it worked!! The following were used on master: ii libc6 2.0.7t-1 The GNU C library version 2 (run-time files) ii gcc 2.7.2.3-4.8The GNU C compiler. ii g++ 2.90.29-0.6The GNU (egcs) C++ compiler. And what C++ libraries are installed there? I'm asking this because I ran into a package lately that didn't build with libstdc++2.9-dev, it needed libg++-dev installed. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Removing Packages in Slink for Debian 2.1
On Thu 15 Oct 1998, Marcus Brinkmann wrote: On Wed, Oct 14, 1998 at 12:19:30PM -0400, Brian White wrote: strace26065 strace confused about sigaction flags [51] (Wichert Akkerman [EMAIL PROTECTED]) Hmm. Why is this bug important anyway? I've looked at the bug report and found no explanation. I think strace is too useful for debugging and should not be removed. Seconded! I agree fully. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: latest sysklogd broken?
On Wed 14 Oct 1998, Martin Schulze wrote: Thomas Lakofski wrote: Seems that the latest sysklogd package breaks sendmail's (and cron's, just checked) logging to syslog -- it works for a few minutes, and then no more logs. I don't know if this is universal (only checked 2 daemons), but it looks like it. What do you mean by break? If you restart syslogd you have to restart some other programs as well (squid, teergrube, inn, named come to my mind.) Can you explain this? This doesn't sound very normal to me. Unix is user friendly ... It's just picky about it's friends. To be picky it's should be its :-) Otherwise it says about it is friends (it's is short for it is). Besides that I agree. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Bug#27823: proftpd: non-maintainer upload (alpha) diffs
On Thu 15 Oct 1998, James Troup wrote: Joey Hess [EMAIL PROTECTED] writes: Why does a binary-only NMU give you the right to skip waiting, while a normal NMU does not? Why are they different? Because I'm not forcing my changes on anyone but the architecture I'm uploading for. If I'm wrong in some drastic way, only m68k suffers. Additionally, a normal NMU is to fix generic problems with the workings of the package itself, not the building process; at least, *I* have never seen an NMU (with source) done for i386 to fix a build problem. Hmmm, we should make it policy that i386 packages aren't allowed to be directly uploaded into Debian; instead, the source should be uploaded, and then another maintainer (not related in any way to the uploader) must download the source, build the package, and upload the resulting binary. If the build fails, either don't upload or upload a complete NMU with source. That should equalize things between i386 and the rest :-) Also, the speed at which updates come would be slowed to acceptable rates... Binary-only and normal NMU's are the same thing, No they're not. Why do you insist on this obvious falsehood? IMO the difference is that a binary-only NMU fixes building difficulties, and a normal NMU fixes the functionality or problems with installing. A binary-only NMU package should function that same way in all respects to the original binary. Do you want the ports to remain forever second class citizens, or do you want them to eventually mature to be equal with i386? Will you please get off your high horse and stop being so incredibly condescending? It doesn't help in anyway whatsoever and without some I have to agree that I fail to see any added value in Joey's comment here. Broken source package has nothing to do with a port at all. Of course they bloody do; we have to build them. And the breakage I'm talking about, is the sort of breakage which doesn't show up for 99.5% of i386/source maintainers. Precisely; couldn't the QA team check that packages build correctly for third parties? What's the point of supplying source packages if they're useless. I mean that we should converge on using the same build environment and build Source dependencies would be a *big* help. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Upcoming 2.1 Release Architectures
On Wed 14 Oct 1998, [EMAIL PROTECTED] wrote: On Wed, Oct 14, 1998 at 12:04:29PM -0400, Christopher C Chimelis wrote: slink/i386. A caveat, however, is that we need to resolve some big egcs issues SOON or else we can't release (as is, 1.1b will not compile two or three vital packages correctly). There is one, MAJOR, huge, massive, 'program' which egcs will not properly compile, this is the kernel, 2.0.x is officially not going to operate 100% correctly when compiled with gcc 2.8.x or egcs.. I last compiled (with success) 2.0.36pre2 with gcc version egcs-2.90.29 980515 (egcs 1.0.3 release) (according to /proc/version). That works perfectly with ISDN and all, and stayed up for a month until I upgraded sysvinit which then decided to run through all the init scripts etc ;-( Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Upcoming 2.1 Release Architectures
On Thu 15 Oct 1998, J.H.M. Dassen Ray wrote: On Thu, Oct 15, 1998 at 01:50:33PM +0200, Paul Slootman wrote: I last compiled (with success) 2.0.36pre2 with gcc version egcs-2.90.29 980515 (egcs 1.0.3 release) (according to /proc/version). That works perfectly with ISDN and all, and stayed up for a month until I upgraded sysvinit which then decided to run through all the init scripts etc ;-( Still, personally I wouldn't trust it. If I needed/wanted to compile a 2.0.x kernel with egcs, I'd apply the patches at http://www.suse.de/~florian/ first. I don't see how patching arch/i386/kernel/ioport.c and arch/i386/kernel/ksyms.c will help the stability of a kernel running on Alpha (which was the point here). If you do, please enlighten me :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Upcoming 2.1 Release Architectures
On Thu 15 Oct 1998, Christopher C Chimelis wrote: On Wed, 14 Oct 1998 [EMAIL PROTECTED] wrote: There is one, MAJOR, huge, massive, 'program' which egcs will not properly compile, this is the kernel, 2.0.x is officially not going to operate 100% correctly when compiled with gcc 2.8.x or egcs.. Any suggestions? On the Alpha? I've had nothing but success with all 2.0.x kernels on the Alpha using egcs and moderate success with 2.1.x kernels (but only because alot of the kernels had broken Alpha support...no fault of egcs). The last time I tried (about 10 sec. ago, on a.d.nl :-): make[2]: Entering directory `/extra/home/debian/psl/kernel/linux/drivers/net' gcc -D__KERNEL__ -I/extra/home/debian/psl/kernel/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -mno-fp-regs -Wa,-m21164a -DBWX_USABLE -DMODULE -DMODVERSIONS -include /extra/home/debian/psl/kernel/linux/include/linux/modversions.h -DEXPORT_SYMTAB -c slhc.c gcc: Internal compiler error: program cc1 got fatal signal 11 make[2]: *** [slhc.o] Error 1 $ gcc -v Reading specs from /usr/lib/gcc-lib/alpha-linux/egcs-2.91.57/specs gcc version egcs-2.91.57 19980901 (egcs-1.1 release) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Processed: Change Important Severities
On Sun 17 Jan 1999, Debian Bug Tracking System wrote: severity 31717 normal Bug#31717: fileutils: 'mv regularfile symlink' problems Severity set to `normal'. I think that this bug _should_ be important; it's just that it's not important for slink as the bug is only in the fileutils version in potato... So, if this is an effort to reduce the number of release- critical bugs (for _slink_), then IMHO it's the wrong way to go about it. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Debian v2.1 (Slink) Deep Freeze
On Tue 19 Jan 1999, Branden Robinson wrote: XFree86 3.3.2.3a-8pre9v4 is available at http://master.debian.org/~branden/xfree86/ . This doesn't seem to have the patches CRITICAL to the alpha port yet! I sent you a note around 7th January about this, saying where you could find the patches I needed to -8pre9v2. I'll say it again: http://master.debian.org/~paul/alpha/xfree86/xfree86-alpha.diff Without these, the X server crashes and burns. PLEASE add these patches before uploading -9 ! Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: No intend to package vbox
On Tue 19 Jan 1999, Roland Rosenfeld wrote: As far as I can see isdnutils-3.0-8 includes vbox 2.0.0 beta 5, which is a little bit newer than vbox 2 beta 4 with the following changes: I'm planning to split up isdnutils sometime into separate parts; there are many sites where for example vbox isn't used at all, so having it installed isn't useful. I was thinking of the following packages: isdnutilscontains the basic isdnctrl, ipppd stuff needed for networking isdnmonitoring isdnlog, imon, xisdnload, ... that sort of thing isdndocs the faqs and other docs isdnvbox vbox If anyone has better suggestions (I haven't really thought hard about this yet) I'd like to hear them (please include reasoning). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: No intend to package vbox
On Sat 23 Jan 1999, Craig Sanders wrote: On Wed, Jan 20, 1999 at 11:36:23AM +0100, Paul Slootman wrote: isdnutils contains the basic isdnctrl, ipppd stuff needed for networking isdnmonitoring isdnlog, imon, xisdnload, ... that sort of thing isdndocs the faqs and other docs isdnvbox vbox If anyone has better suggestions (I haven't really thought hard about this yet) I'd like to hear them (please include reasoning). i like the idea. i don't use vbox or isdnlog at all. 'isdnmon' is probably a better name than 'isdnmonitoring'. Yeah, except I have this feeling there's some program called isdnmon out there, in which case it's confusing. also, i've been meaning to submit a bug report about the following: one thing that would be really great would be if isdnutils could be upgraded WITHOUT taking down any running ippp connections. it's a bit There's already a wishlist bug outstanding on this topic (#29255). Sometime, when I have the time... :( Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: XFree86 3.3.2.3a-8pre9v6 at master.debian.org/~branden/xfree86
On Thu 28 Jan 1999, Steve Dunham wrote: BTW, There are two kinds of sparc64 support: usermode and kernel mode. Usermode stuff is a _long_ way off, currently Debian runs 32-bit sparc stuff on a 64-bit kernel. So Alpha patches don't help much there. The biggest issue on the 32-bit sparc is unaligned memory accesses. Alpha also suffers from unaligned accesses on 32-bit entities(*), so perhaps the unaligned accesses to see are also addressed (pun not intended) by the alpha patches? (*) on alpha, you can access 8-bit entities at any 8-bit aligned address (i.e. any byte anywhere). 16-bit entities need to be aligned on even addresses, 32-bit entities on (addr % 4 == 0) addresses, and 64-bit addresses must be aligned on (addr % 8 == 0) addresses. I'm guessing the same holds true for sparc(64). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Migrating to GPG - A mini-HOWTO
On Tue 14 Sep 1999, Michael Stone wrote: On Tue, Sep 14, 1999 at 11:55:39PM +0200, Martin Schulze wrote: Michael Stone wrote: Not really. What if the pgp key is compromised? The original owner can release a revocation certificate for the pgp key, but if someone creates a new gpg key that you sign based on the (compromised) pgp key then you've possibly validated a key that the original owner cannot revoke. That would be bad. So what do you propose? Not using any digital signing at all? How does that follow at all? Take a breath and calm down. I think his point is that if you can't trust a pgp signature to sign a gpg key, why should trust a pgp signature to do anything at all, e.g. accept an uploaded package. Seems like a reasonable argument. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Migrating to GPG - A mini-HOWTO
On Tue 14 Sep 1999, Jason Gunthorpe wrote: On 14 Sep 1999, Ben Pfaff wrote: Michael Stone [EMAIL PROTECTED] writes: Again, no it isn't. How do they know that someone didn't steal your pgp key?=20 How is this different from the question ``How does dinstall (or other person/program) know someone hasn't stolen [developer]'s PGP key?'' Because you can revoke the old key and have all of it's signatures become invalid. But, you cannot revoke this 'new' key that was created and passed around as real using your compromised old key. It now has real signatures that say 'I know for certain that this key belongs to this person'. OK, but still things may have been done because the old key was not yet revoked, or the revoking hasn't trickled through everywhere yet. I'm sure that most people don't check with the central key servers every time they check a signature. With dinstall a compromise is short lived and can be undone by erasing the effected package. Creating a new key and getting people to sign it cannot really be undone. How do you prove to whoever is able to erase the package that you are who you say you are? I.e. how do you convince them that they should in fact erase the package? In short, the problem just moves around; being able to revoke a key is great, but still leaves many problems open. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Migrating to GPG - A mini-HOWTO
On Wed 15 Sep 1999, Philip Hands wrote: I know there is some pathetic kudos about how many signatures you have Is the pathetic part the reason why you don't have any? :-) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Increasing regularity of build systems
On Wed 15 Sep 1999, Martin Schulze wrote: PS: I would appreciate its use as well, it sucks that some pkg's are rebuilding everything if one only is working on a patch in to one file If all I'm doing is trying fix something, usually just invoking 'make' will do it (or some subtle variation that a glance at the rules file will make clear). Once it builds, I do 'debian/rules clean' and then restart the package build, to ensure that the final package can be reproduced (restarting things from the middle sometimes leads to things happening differently). Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: NOT done!
On Wed 15 Sep 1999, Julian Gilbey wrote: Perhaps someone made a typo and closed the wrong bug? It was apparently done by the maintainer, and no further response from him. Curious. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: man preprocessor different than on Red Hat?
On Wed 15 Sep 1999, Peter S Galbraith wrote: The man page defines a table like so: What happens if you pass the -pt option to man? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Strange mail from Anders Arnholm (was Re: /opt/ again (was Re: FreeBSD-like approach for Debian? [was: ...]))
On Wed 15 Sep 1999, Philip Hands wrote: Is anyone else seeing all this header drivel in everything that Anders mails, or have I got something in my gnus setup totally screwed ? The scattering of CR's in the Subject seem somewhat suspicious to me. Actually, I can't find any Subject in the header you included (which you apparently included twice?). Nor do I see any To or Cc lines in your included header, which I _do_ have in my copy of Anders' message. Nothing especially strange there (besides the fact that he uses X-Face, which I thought had died out :-) Xref: sheikh.hands.com debian:30380 debian.devel:24066 You expand locally to a newsgroup? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: ITP: Rael's Binary Grabber
On Thu 16 Sep 1999, Joe Drew wrote: I've received an OK from the author of Rael's Binary Grabber to redistribute Perhaps you could shed some light on what `Rael's Binary Grabber' is? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Debian's involvement in another exhibition
On Wed 22 Sep 1999, Martin Schulze wrote: Web: http://oldenburger.linuxtag.de/ : The dnsserver returned: : : DNS Domain 'oldenburger.linuxtag.de' is invalid: Host not found : (authoritative). Doesn't look like the DNS is set up yet. Also no reference from www.linuxtag.de ... Where is Oldenburg geographically? E.g. how far from Holland? :-) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Use https://db.debian.org/ [was Re: Add your location ...]
On Wed 22 Sep 1999, James A. Treacy wrote: I should have used https://www.debian.org/ in the original mail. Sorry. Everyone who can (legally) use ssl should use that URL. I get 'connection refused by the server'... Moreover, I tried updating my info on the non-secure page, but my postcode is STILL not getting added (it is 7609 JD; yes, with a space), and also my coordinates (0521952 / 0063753) were not added. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Use https://db.debian.org/ [was Re: Add your location ...]
On Thu 23 Sep 1999, Paul Slootman wrote: I should have used https://www.debian.org/ in the original mail. No, you should have used https://db.debian.org/ ... I get 'connection refused by the server'... ... because db.debian.org does accept https connections, while www.debian.org doesn't. Moreover, I tried updating my info on the non-secure page, but my postcode is STILL not getting added (it is 7609 JD; yes, with a space), and also my coordinates (0521952 / 0063753) were not added. When I now look at my info again, it's all there... It's just not displayed directly after updating the info, which is a bit confusing! Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Packages to remove from frozen
On Thu 09 Mar 2000, Jacob Kuntz wrote: isn't the problem here that the server is misrepresenting itself? a one bit difference may not make a less secure key, but it could quite possibly be an indication of some deception. i worry that altering the client to ignore this type of error will only open us up to attack, be it man-in-the-middle or otherwise. Warning: my crypto knowledge is pretty poor. Someone somewhere in this thread said that the problem was that the old ssh could generate a key that had the MSbit off, and that was the cause of these messages. I'm now thinking: if the MSbit *MUST* be set, how does that increase the security? N bits of key is no less secure than N+1 bits where you know the value of one bit. Isn't openssh simply confused in this case? I myself notice that openssh complains about half the time when connecting to a random number of different hosts (I connect daily to a random 5-10 systems out of a collection 700 hosts (each running ssh 1.2.17), which IMHO means the sample is quite random, but then statistics lessons was a long time ago). Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
dpkg: dpkg-divert syntax error
Package: dpkg
Version: 1.6.10
Severity: important
Setting up tcsh (6.09.00-8) ...
Installing new version of config file /etc/csh.cshrc ...
syntax error at /usr/sbin/dpkg-divert line 208, near unlink
Execution of /usr/sbin/dpkg-divert aborted due to compilation errors.
This is the code:
if ($1 == ENOENT) {
$dorename = 0;
} else
unlink (${file}.dpkg-devert.tmp);
Note the missing braces round the unlink statement.
Besides, devert is spelled wrong (but that's not important).
Paul Slootman
--
home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/
work: [EMAIL PROTECTED] http://www.murphy.nl/
debian: [EMAIL PROTECTED] http://www.debian.org/
isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Potato fresh install
On Sat 11 Mar 2000, Philippe Troin wrote: - I had a few seemingly inoffensive warnings about a missing /etc/mailcap. I've noticed this for some time as well. Isn't the result that those packages that are installed before mime-support aren't registered in /etc/mailcap? If so, perhaps mime-support should be installed much earlier. Also, when upgrading mime-support, it always offers to replace the conffile /etc/mailcap, which is NEVER a smart thing to do. Maybe /etc/mailcap should be one of the base files, and not part of mime-support? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Danger, Branden Robinson! Danger!
On Sun 12 Mar 2000, Branden Robinson wrote: Ha ha ha ha. Just X servers? You haven't been reading the news. :) There is only one server binary in XFree86 4.0. The huge reorganizations are almost all going to revolve around that X server binary, too. There are exactly ONE HUNDRED server modules built by the stock 4.0 source tree. A separate xserver section might be useful for separating the servers (and fonts etc) and the applications. If you have a working X setup, then you don't need to look at xserver/*, only x11/* when looking for a certain app. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
mailcap stress (was: Potato fresh install)
On Mon 13 Mar 2000, Santiago Vila wrote: On Mon, 13 Mar 2000, Paul Slootman wrote: Also, when upgrading mime-support, it always offers to replace the conffile /etc/mailcap, which is NEVER a smart thing to do. Maybe /etc/mailcap should be one of the base files, and not part of mime-support? This is Bug #34294, which I reported more than a year ago and it has not been fixed yet. Glad to know I'm not the only one to think this is a bug. I have tried to convince the maintainer (Brian White) several times about the need to change this, without much success. He says /etc/mailcap almost never changes and he does not see the need to modify the way /etc/mailcap is handled. That's strange, as I've been asked whether to replace it on numerous occasions during upgrades to the current potato (every month or so). Maybe the conffile mechanism doesn't always work properly? Or was I confused... (it's been known to happen :-) Ans it still doesn't address the situation where packages are being configured but mime-support isn't yet. If this is not a bug in mime-support, then lots of packages would be violating policy because they modify /etc/printcap (a configuration file You mean /etc/mailcap I hope of another package) every time they register their MIME viewers... Well, if they do it with update-mime it should be OK (unless mime-support has been installed but not yet configured, that is). Time to make a policy proposal? It would be something like: Do not ever use the conffile mechanism to initialize a database. Sounds reasonable. Anything that gets updated via an update-foo thingie shouldn't be a conffile, as it is NEVER useful to upgrade to the version in the newest package on an installed system. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Danger, Branden Robinson! Danger!
On Mon 13 Mar 2000, Stephen Zander wrote: Joseph == Joseph Carter [EMAIL PROTECTED] writes: Joseph Only 6000? We must be getting lazy. 6000 is way too Joseph easy. Better try for 8000. Now one ever thought the Dow would break 10k: took 'em 10yrs to get from 3k to there. I'm sure we can do it in 2yrs (which is about when woody will be out, right? :)) I still think we should be honest and report the number of source packages, not binary packages; e.g. I find the following all parts of just one package: glibc-doc i18ndata libc6 libc6-dev locales It _is_ useful to be able to install these separate parts, of course... Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: ITP: manpages-da
On Fri 24 Mar 2000, Peter Makholm wrote: In SSLUG (swedish/danish LUG) we have begun translating man-pages to danish. when we have finished a nice set (like file-utils) I will make a debian package out of it. Wouldn't manpages-dk be the correct name? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: ITP: manpages-da
On Tue 28 Mar 2000, Peter Makholm wrote: Paul Slootman [EMAIL PROTECTED] writes: Wouldn't manpages-dk be the correct name? That depends The two letter language code is da and the two letter country code is DK (making the correct locale: LC_ALL=da_DK) There shouldn't be any problem using the manpages in Greenland (ie da_GL) but if you're speaking english in Denmark (en_DK) you shouldn't use them. Making a long story short: I think we should use the language code and not the country code. You're right, of course. I did indeed confuse the language and country. Paul Slootman (would be using LANG=en_NL if it existed) -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Advice on inetd Denial of Service Bug
On Thu 30 Mar 2000, Herbert Xu wrote:
As to the dependency on fuser, hmm, now what's that thing called netstat(1)
which happens to be in your package and also happens to have a flag called
-p? :)
$ man netstat
[...]
SYNOPSIS
netstat [-venaoc] [--tcp|-t] [--udp|-u] [--raw|-w]
[--groups|-g] [--unix|-x] [--inet|--ip] [--ax25] [--ipx]
[--netrom]
netstat [-veenc] [--inet] [--ipx] [--netrom] [--ddp]
[--ax25] {--route|-r}
netstat [-veenpac] {--interfaces|-i} [iface]
netstat [-enc] {--masquerade|-M}
netstat [-cn] {--netlink|-N}
netstat {-V|--version} {-h|--help}
DESCRIPTION
[...]
Hmm, I don't see -p
[...]
-p, --programs
displays process name and PID of the owner of each socket
it dumps. You have to be the owner of such process to have
all it's sockets matched to it or generally root user will
see all the necessary information in place.
Ah, it's not in the synopsis, but _is_ described.
BTW: it should be all its sockets, no apostrophe.
Paul Slootman
--
home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/
work: [EMAIL PROTECTED] http://www.murphy.nl/
debian: [EMAIL PROTECTED] http://www.debian.org/
isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: eximconfig: Option 4, Local delivery only
On Fri 31 Mar 2000, Jose Marin wrote: I was wondering if eximconfig is doing the right thing for this option. I have machines which are connected on a network, and I want to have a MTA but only for the benefit of apps like cron or debconf which need to send local mail. I expected that Option 4 of eximconfig (Local delivery only) would block any TCP/IP conections to exim, but it doesn't; I'm still able to send e-mail from a different machine successfully. Shouldn't eximconfig warn about this? Or am I missing something? (very likely) Anyway, what's the best way to achieve what I want? Run exim from inetd via tcp wrappers and protect it in hosts.deny? Run exim as a daemon and give it an option to not listen to port 25, or not use SMTP transport at all? All I want is local mail. IMHO configure it to not use SMTP at all, that should be the default (again, IMHO) if you choose option 4. I don't think that any daemons etc. try to deliver to a local user via SMTP. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: ITP: noffle
FYI: On Wed 28 Jun 2000, Paul Slootman wrote: The README says: Noffle is a Usenet news server optimized for few users and low speed dial-up connections to the Internet. It acts as a server to news clients running on the local host, but gets its news feed by acting as a client to a remote server. Noffle is written for the GNU/Linux operating system and freely available under the terms of the GPL. See COPYING for details. I've since packaged a version that installs itself into inetd.conf, has init.d, cron and ip-up/ip-down scripts, etc. which works pretty well for me. It's been sitting in incoming for a couple of weeks now; as potato is now officially released, I hope the incoming backlog will start to go down so that noffle is installed into woody. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: isdnutils dilemma
On Mon 07 Aug 2000, Ruud de Rooij wrote: Paul Slootman [EMAIL PROTECTED] writes: I'm in the process for building the latest version of the isdnutils, with the latest upstream sources. However, I've run into a glitch, licence-wise. The isdnlog people have decided to use CDB instead of DBM for the areacode etc. The problem is that CDB is written by D.J. Bernstein (of qmail fame), and the licence of CDB is vague at best. Maybe you could use freecdb instead? Success! I've managed to convince the upstream people to drop the CDB version they were using (from the current non-free CDB release) and use freecdb instead; this was done in the CVS version last night. Another triumph for free software. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: policy changes toward Non-Interactive installation
On Tue 15 Aug 2000, Decklin Foster wrote: Brian May writes: Just curious, why does realplayer have to do it in the postinst script? Binaries need to be downloaded from Real and we can't redistribute them. The user also has to fill out 'personal information' to be able to access the required files. This couldn't be handled by `expect' or similar? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Intel Assembly error
On Wed 16 Aug 2000, Branden Robinson wrote: I am not an assembly guru on any architecture, but here's what I think this means. Please be warned that these could be the ravings of a deranged lunatic. Ditto. The AX register is an old 16-bit register from 8086 days. When you're running in 32-bit mode, as all Linux systems do, the register should be accessed by its 32-bit name, EAX. Actually, I believe they are separate entities. I think at some point gcc (or gas) used to automatically convert such misreferences. There's a whole slew of register names on the IA32 from the old 16-bit days that have a 32-bit version with the E prepended. (I think, in some contexts, you can actually use the 16-bit register names to fetch the low-order 16 bits out of the actual 32-bit register.) No, you have AH to access the high 16 bits of EAX, and AL for the low 16 bits of EAX. Or was that the high 8 bits of AX etc... Apart from that, using assembler is evil (if there isn't a C language alternative) because then your source will never run on anything besides the processor the assembler code is written for. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Office Suite for Debian Linux
On Wed 16 Aug 2000, Peter S Galbraith wrote: Sam Sim wrote: Dear Debian Linux, I am familiar with you operating system and wanted to contact you. Wow. How familiar can he be? Yeah, just what I was thinking. we will be in your area towards the end of September. I would like briefly stop by your offices I wonder how he's going to be in dozens of countries across the world towards the end of September :-) This is so clearly a standard ploy to attract business; if someone responds, he goes to where ever the offices happen to be. Should this be considered spam? As far as I'm concerned, it's unsollicited commercial email, thus spam. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: I propose gazillion packages (LONG)
On Thu 17 Aug 2000, Juhapekka Tolvanen wrote: I propose these packages to be added to Debian GNU/Linux. I have proposed them once before, but they are not yet added. I think you should research a bit better. On browsing your list, I saw at least two packages that I already have installed: boxes and deroff. I'm sure there are more. But otherwise, some are probably good suggestions. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Bug#33993: general: Should log all the boot messages
On Thu 17 Aug 2000, Colin Watson wrote: dmesg doesn't log the output from init.d scripts. (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp However, sometimes I have wished that the init.d messages were in fact logged somewhere. E.g. after a day you notice something isn't running, and you wonder whether there was some message from the init.d script. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Bug#33993: general: Should log all the boot messages
On Fri 18 Aug 2000, Branden Robinson wrote: On Fri, Aug 18, 2000 at 10:20:48AM +0200, Paul Slootman wrote: On Thu 17 Aug 2000, Colin Watson wrote: (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp Of course, if you run a display manager, you lose your scroll back as soon as the X server starts... True, which is why I'd like the log. I noted the shift-PageUp in response to the ctrl-s suggestion; I'm usually too slow with the ctrl-s, but then shift-PageUp helps. And I usually start xdm by hand anyway :-) That used to be the safest way, although the new code (well, new since a long time) to prevent looping when the X config is wrong works very well. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: .bashrc (ls --color=auto setting)
On Wed 30 Aug 2000, Wichert Akkerman wrote: Previously Marcus Brinkmann wrote: What you mean is actually done by dircolors, which checks the terminal type in a rather dump way, using a database, and not verifying termcaps: Why do you need to run dircolors anyway? I don't and I still get coloured output.. Then you must have some other arrangement to get the colors; it's not enabled by default. Try a fresh install (I have). Maybe a direct setting of LS_COLORS in your .bash_profile or whatever? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
debian 2.2 review at http://www.securityportal.com/closet/
I've just read your article on debian 2.2. While you make many valid points, I'm confused about a couple of them. Moving on. Once the basic install is done, you will discover that several services are enabled in inetd that shouldn't be. Discard, daytime, time, shell, login, and exec (r services) are all enabled by default echo, daytime, time were specifically disabled on my installation. crypt passwords are trivial to brute-force when compared to MD5ed ones. I think the operative phrase is when compared to MD5ed ones. Besides, you need access to the crypted password to be able to brute-force it. /etc/shadow isn't readable for mortals. As an example, the ftp site ftp.win.tue.nl was cracked into some time ago, and several packages were replaced with Trojaned versions. TCP_WRAPPERS was compromised, among other things. Over 50 people downloaded these packages before someone noticed they were not properly signed with PGP, and raised the alarm. Doesn't this in fact indicate that signed packages aren't that useful, as people don't check them anyway? You'd think that now that 2.2 is out the door, Debian could focus a lot of activity on fixing it. Actually, the intention is to get 2.3 out of the door now. Unlike some vendors, debian tries to release _after_ problems are resolved, not release first, patch later. The freeze period, during which the system is tested and all serious bugs (as far as they are detected) are fixed, was a couple of months long. During this time no new packages are allowed in, which explains for example why apache is 1.3.9. Anyway, had you taken the time to do some investigation, you would have seen the following in the debian changelog for apache: * [RC, security] Backported security fix for Cross Site Scripting issue (CERT Advisory CA-2000-02) from apache 1.3.11 patch. This was done Sun, 16 Apr 2000. I haven't checked others, I expect that you will find that there too fixes have been backported. Please update your review to reflect any such findings. It would have been much more useful to have done your review during the freeze period, when these reports can make a difference. The freeze period is a time where debian encourages people like yourself to test the system and submit bug reports where necessary. I hope that when debian 2.3 is frozen you will take the time to do another thorough review _before_ it is released. Regards, Paul Slootman [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: .bashrc (ls --color=auto setting)
On Wed 30 Aug 2000, Wichert Akkerman wrote: Previously Paul Slootman wrote: Then you must have some other arrangement to get the colors; it's not enabled by default. Try a fresh install (I have). Maybe a direct setting of LS_COLORS in your .bash_profile or whatever? Nope: [tornado;~/cistron]-15 env|grep LS zsh: done env | zsh: exit 1 grep LS OK, so no setting of LS_COLORS. I have ls aliased to 'ls --color=auto', which works great. Ah, so you *do* have some other arrangement to get the colors. So why did you write nope as your first response (which would imply an response to my first statement)? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: imap mailbox killer
On Thu 31 Aug 2000, Cristian Ionescu-Idbohrn wrote: caused the daemon (or the client) screw up the magic. I ended up with a magic message looking like this: ,- | From MAILER-DAEMON Wed Aug 30 16:36:48 2000 | Date: 30 Aug 2000 16:36:48 +0200 | From: Mail System Internal Data [EMAIL PROTECTED] | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | Message-ID: [EMAIL PROTECTED] | X-IMAP: 0967646162 000339 =?iso-8859-1?Q?kettutyt=F6t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?= | Status: RO | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `- and a lot of NULL characters preceeding a few (5-6) of the messages in some boxes. Yuck. Smells like a serious buffer overflow somewhere. This needs to be fixed fast. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: imap mailbox killer
Package: imap Version: 4.7c-1 Severity: important On Thu 31 Aug 2000, Paul Slootman wrote: Yuck. Smells like a serious buffer overflow somewhere. Upon a quick glance, there indeed appears to be no checks at all for buffer overflows. A buf of 8k is allocated into which the From:, Status:, X-Status, and X-Keywords: headers are placed, with simple sprintf (buf + strlen (buf),... commands. So having extremely long X-Keywords in mail messages will screw things up. Double yuck. This is in imap-4.7c/src/osdep/unix/unix.c BTW. See the original message and the accompanying thread in debian-devel, archive/latest/67244 , Message-ID [EMAIL PROTECTED] from Cristian Ionescu-Idbohrn [EMAIL PROTECTED] Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: APT problem
On Thu 31 Aug 2000, Michael Meskes wrote: Which of course is correct. Not only the md5sum is different but also the filesize. Wonder what they did with the source. It doesn't take much to create a different filesize. E.g. different timestamps in the archive will lead to different compression behaviour, hence different sizes. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
va.debian.org is down?
I can't ssh to it, and www.debian.org doesn't work either. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#70269: automatic build fails for potato
On Fri 01 Sep 2000, Jaldhar H. Vyas wrote: What about for users who want to rebuild the package for whatever reasons? Many times you get half way through some huge package and it craps out because you didn't have some esoteric header file or library. Build-depends is invluable for avoiding those kinds of annoyances. It would be useful if dpkg-buildpackage checked it then. I thought it did, and exactly what you describe (crapping out) happened, even though there _were_ build-depends. That sucked to the extreme (yes, it was a huge package and yes, it happened near the end). Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Map on debian website - bug in apache?
On Fri 01 Sep 2000, Miquel van Smoorenburg wrote: On http://www.nl.debian.org/devel/developers.loc , there's supposed to be a jpeg of a world map with debian developers. On the main website, www.debian.org, there is. It seems that the .nl webserver is interpreting the filename developers.map.jpeg as a .map image-map file according to this error: It sounds like it's not recognizing the .jpeg, and using .map instead? Is .jpeg a recognized extension for .jpg? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: intent to package countrycodes
On Sun 03 Sep 2000, Dr. Guenter Bechly wrote: I intend to package Country Codes 1.0.3, a text-based ISO3166 country code finder (yes, I know there is a Perl module that does the same, but this little tool is easier and more flexible). The package is actually already made and lintian clean. It can be downloaded from http://www.bechly.de/debian/. I've had a quick look. The orig.tar.gz is 17k, and the diff.gz is 15k ?! I see you have all the debian/*.ex files that the helper make script creates; removing those will help greatly in reducing the size of the diff; they are examples after all, and if you haven't used those examples, there's not much point in leaving them in the diff (save them somewhere else if you want to refer to them at a later stage). I also see lines such as: --- countrycodes-1.0.3.orig/common.c +++ countrycodes-1.0.3/common.c @@ -0,0 +1,62 @@ in your diff, meaning the diff is creating those files completely. If there wasn't any source, only data, in the orig.tar.gz, then perhaps you should make two packages: one with the data, and one with the (your) software. However, I see: --- countrycodes-1.0.3.orig/iso3166.c +++ countrycodes-1.0.3/iso3166.c @@ -0,0 +1,631 @@ +/* + ISO 3166 Country Codes program + + Country Codes + + Copyright (C) 1999, 2000 Diego Javier Grigna [EMAIL PROTECTED] This means a file of 631 lines is created by your diff, with someone else's copyright. So, I'm guessing the package copies (or links?) source files from a subdir to the top dir. In that case, the clean target in debian/rules should undo those actions so that the diff is as small as possible. Until these basic packaging paradigms are mastered, I don't think this package is fit for uploading yet. Perhaps you should ask for more help in debian-mentors (which is for helping new maintainers)? Good luck, Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X and runlevels
On Mon 04 Sep 2000, Per Lundberg wrote: Sure. But whenever you install something that gets you a display manager, your system will boot up in X. To get it to boot up in console mode, you have to manually remove the symlinks in your runlevel's script directory. The next time you update the display manager, you'll have to do this again. It is not really convenient. Not quite, if you leave at least one symlink somewhere in the rc?.d directories, your config should be left alone (i.e. the symlinks won't be redone). See the update-rc.d manpage: : INSTALLING INIT SCRIPT LINKS :When run with either the defaults, start, or stop options, :update-rc.d makes links /etc/rcrunlevel.d/[SK]NNname :pointing to the script /etc/init.d/name, : :If any files /etc/rcrunlevel.d/[SK]??name already exist :then update-rc.d does nothing. This is so that the system :administrator can rearrange the links, provided that they :leave at least one link remaining, without having their :configuration overwritten. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X and runlevels
On Mon 04 Sep 2000, Per Lundberg wrote: Are you *absolutely* sure? The reason I ask is because I've been Yes. having this exact problem with gpm lately. I like to start it occasionally, because it interfers with my X configuration, so I use to remove the symlinks. Each and every time gpm is updated (two times Don't remove _all_ the symlinks, leave the K ones. Or move one of the symlinks to rc5.d or whatever. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X and runlevels
On Mon 04 Sep 2000, Ethan Benson wrote: also you mean that the symlinks are recreated, not just gpm being restarted right? there is an obnoxious behavior in debian where upgraded packages are started even if they were not running in the first place. (*cough* portmap *cough*) there was a bit of discussion on fixing this but i don't know if its being worked on actively or not. Debhelper (and one of the other helper things) does this, if you don't call dh_installinit with the --no-restart-on-upgrade (or such) option. I guess the reasoning is that (a) you're upgrading in multiuser mode because debian lets you :-) (b) in multiuser mode the daemon was running. It's unfortunate that there's no easy way to find the current runlevel (the usual who -r from Solaris etc. doesn't work), otherwise this piece of code could be used: RL=`who -r` if [ -x /etc/rc$RC.d/S??$PKGNAME ]; then /etc/rc$RC.d/S??$PKGNAME start fi That's ignoring file-rc, unfortunately. Is there an easy way of determining whether a certain init.d script should be started in the current runlevel that works also with file-rc ? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WARNING: potato has horrible broken locales
On Mon 04 Sep 2000, Peter Makholm wrote: handling of [a-z] discussion snipped ls /dev/tty[[:lower:]]0 Ugh. Whatever happened to lazy unix users? a-z is a lot easier to type than [:lower:] . I'd find it a lot more reasonable if [A-Z] was interpreted as [A-Za-z]. Next step will be renaming ls to List-Directory :-( On pandora I just did the following: $ touch a b c A B C $ echo [[:lower:]] a b c $ echo [[:upper:]] A B C $ echo [a-c] a b c The scary thing (for me :-) is that this also works on Solaris already. At least, with ksh, not in sh. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re[2]: X and runlevels
On Mon 04 Sep 2000, Michael Bravo wrote: Monday, September 04, 2000, 3:01:42 PM, you wrote: PS It's unfortunate that there's no easy way to find the current runlevel PS (the usual who -r from Solaris etc. doesn't work) /sbin/runlevel can be used to find the current runlevel So it does. It just reads /var/run/utmp, like who does, so it should be trivial to add the -r flag to who :-) Thanks, Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X and runlevels
On Mon 04 Sep 2000, Anton Ivanov wrote: Example: I had to go into an intermediate single user mode boot on some of my machines after forgetting to turn off xdm after changing video cards. Or during dealing with laptop docking gear. If there was a boot with X disabled and xdm installed it would have made life a bit easier. Actually, that used to be a problem (I've had that as well, where an incorrectly configured X e.g. for a different card caused an infinite loop of switching to X and back again, so that you never have the chance of switching with alt-ctrl-F1 and staying there). Nowadays xdm detects that the X server is looping, and after a couple of times stops restarting the X server. This has saved me once or twice. Thanks, Branden! (or was it someone else's work?) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian, daemons and runlevels (was: Re: X and runlevels)
On Mon 04 Sep 2000, Henrique M Holschuh wrote: This would be managed through a simple (for sysvinit. I don't believe it'd be very complex for file-rc either, but I didn't check), standard script/program added to the sysvinit and file-rc packages (and any other future packages of the same sort) which allows a script to query if a certain init.d script should be started [in the current runlevel]. This sounds like the most reasonable way of doing it IMHO. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
db.debian.org (was: libgd1 vs. libgd1g)
On Mon 04 Sep 2000, Antti-Juhani Kaijanaho wrote: Nondevelopers do not have access to the away information in db.d.o. Ugh. They _are_ presented with a form where the on vacation box can be checked, and the subsequent search simply returns 0, no errors explaining that this info can't be retrieved without logging in. Misleading. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new experimental ISDNUTILS packages available
I've been promising this for a while, but now it's happened:
The latest version of isdn4k-utils has been packaged.
I'm calling this experimental, because things probably WILL go wrong
here and there. However, I'm using it (at least parts of it), and it
works for me. Be sure to backup your configuration files first!
*** Only use these packages if you can live ***
*** with things perhaps breaking, and if you ***
*** can fix things yourself when they do break! ***
In this version, the isdnutils package has been split into smaller
parts. By popular demand there is a separate isdnutils-xtools package
so that those without X don't need to install any X libraries. These
are the packages:
- isdnutilsbase system e.g. isdnctrl, imon, isdn_cause
manpage. Enough to run rawIP interface and
X.75 with.
- isdnutils-docFAQ and MiniFAQ
- isdnutils-xtools xmonisdn, xisdnload
- ipppdStuff for syncPPP connections (e.g. ISP access)
- isdnlog Latest isdnlog binaries
- isdnlog-data rate, zone, etc. data files for isdnlog
- isdnvbox vbox ISDN answering machine
- isdnactivecards stuff for active ISDN cards including firmware
and capi. Large and not needed by most people.
- isdneurofile The eurofileftransfer protocol software.
These packages have been uploaded to the experimental distribution
(but not yet installed at this moment, maybe today?),
but are also available by using the following line in /etc/apt/sources.list:
deb http://www.murphy.nl/~paul/debian isdnutils/
After this, apt-get update; apt-get install ipppd isdnlog-data
should install isdnutils, ipppd, isdnlog, and isdnlog-data.
You should install any of the other packages that you need.
Isdnlog should ask you a couple of questions via debconf (e.g. what
country you're in, what your areacode is), and create an isdn.conf
file (if not there already). I recommend MOVING your old isdn.conf
out of the way before installation, the new isdnlog NEEDS a couple of
parameters not in the old version. In a later version I'll try to
convert any old isdn.conf automatically. After configuration there
should also be a /etc/isdn/rate.conf file, please check this.
While testing it may be useful to know that /etc/init.d/isdnutils
now accepts command like:
/etc/init.d/isdnutils reload isdnlog
to reload only isdnlog; this works for {start,stop,reload} {isdnlog,ipppd}.
Please let me know if you use this version, and keep me informed of
ANYTHING, good or bad. I *do* mean anything, like spelling errors
or a complete destruction of your /etc directory (I hope not :-)
(I already know that the text of the first isdnlog debconf message is
wordwrapped here and there, despite extra whitespace in addition to
the mandatory first space, which should be enough according to the
debconf docs. Anyone know what to do about it?)
Enjoy,
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with mail system? [Fwd: Returned mail: User unknown]
On Thu 07 Sep 2000, Hamish Moffatt wrote: On Thu, Sep 07, 2000 at 12:55:07AM -0500, Joseph Carter wrote: On Wed, Sep 06, 2000 at 11:37:55PM -0400, [EMAIL PROTECTED] wrote: yes. get an ISP that can do reverse DNS. YEESHHH! I'll happily bounce their mail until then. Are you willing to pay the difference between the cost of that user's current ISP and one which meets your standard? Until then, you have absolutely no right to tell someone what ISP they should use. In any case, reverse DNS lookup is reasonable, no matter what you think of DUL. I have to agree with this. The previous time, the discussion was using DUL to block email. This is about reverse DNS lookups failing, which is a completely different this. If the reverse DBS lookup fails, you either have a grossly incompetent ISP(*) or a malicious one. (*) Try this for size: $ nslookup Default Server: localhost Address: 127.0.0.1 set type=mx deanmoor.nl Server: localhost Address: 127.0.0.1 Non-authoritative answer: deanmoor.nl preference = 10, mail exchanger = mail.deanmoor.nl Authoritative answers can be found from: deanmoor.nl nameserver = ns01.deanmoor.nl deanmoor.nl nameserver = ns02.deanmoor.nl mail.deanmoor.nlinternet address = 193.203.225.35 ns01.deanmoor.nlinternet address = 193.203.225.35 ns02.deanmoor.nlinternet address = 193.203.225.36 set type=a 193.203.225.35 Server: localhost Address: 127.0.0.1 *** localhost can't find 193.203.225.35: Non-existent host/domain 193.203.225.36 Server: localhost Address: 127.0.0.1 *** localhost can't find 193.203.225.36: Non-existent host/domain www.deanmoor.nl Server: localhost Address: 127.0.0.1 Non-authoritative answer: Name:www.deanmoor.nl Address: 193.203.225.10 193.203.225.10 Server: localhost Address: 127.0.0.1 *** localhost can't find 193.203.225.10: Non-existent host/domain It used to be a different scenario: mail.deanmoor.nl - 193.203.225.35 - www.deanmoor.nl - 193.203.225.10 - unknown I contacted them about this (a couple of times), but they were convinced that their setup was correct. They also tried to convince me that I misunderstood the problem. Yeah, right. I recommended my client to go elsewhere for internet connectivity. He did, and now knows that it is possible to have a reliable internet connection. He now also pays in excess of US$1000 a year _less_ for it. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new experimental ISDNUTILS packages available
On Fri 08 Sep 2000, Michael Beattie wrote: On Thu, Sep 07, 2000 at 07:40:02AM +0200, Paul Slootman wrote: These packages have been uploaded to the experimental distribution (but not yet installed at this moment, maybe today?), but are also available by using the following line in /etc/apt/sources.list: I added the override entries last night I think... I dont see them installed.. - not sure why.. ...but your new upload will be rejected :) isdnutils_3.1pre1b-1_i386.changes REJECT Rejected: md5sum failed md5sum: MD5 check failed for 'isdnutils_3.1pre1b-1.dsc' [puzzled] For some reason the .dsc file was the old one. I've uploaded the correct one, so everything should be OK now. Thanks for the warning. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with mail system? [Fwd: Returned mail: User unknown]
On Thu 07 Sep 2000, Craig Sanders wrote: On Thu, Sep 07, 2000 at 11:58:33AM +0200, Paul Slootman wrote: In any case, reverse DNS lookup is reasonable, no matter what you think of DUL. I have to agree with this. The previous time, the discussion was using DUL to block email. This is about reverse DNS lookups failing, which is a completely different this. If the reverse DBS lookup fails, you either have a grossly incompetent ISP(*) or a malicious one. i'd have to disagree with this. screwed up the DNS isn't a good reason for bouncing mail (because there's no particular reason to believe it's I've seen lots of spam where the originating IP address doesn't resolve. OTOH, I've hardly ever received legitimate mail with the same problem. OTOH, DUL is good because their is bugger-all legitimate reason for anyone to be sending direct from a dialup dynamic IP address - there are many cheap reasonable alternatives to doing that. The name is badly chosen, it should be DDUL (dynamic dial up list). I have a dialup line, but it has a fixed IP address. more importantly, given that the number of die-hard DIYers with linux boxes who insist on delivering their mail from a dynamic IP address (and If the alternative was a smarthost with an ISP that can't get its DNS straight, I'm with the die-hard DIYers. wont consider any alternative for any reason) is insignificant compared to the number of spammers who try to do the same, there is excellent reason to believe that the incoming mail is probably spam. Sounds remarkably similar to my argument above about non-resolving IP addresses and spam. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new experimental ISDNUTILS packages available
On Thu 07 Sep 2000, Andreas Fuchs wrote: Today, Paul Slootman [EMAIL PROTECTED] wrote: I've been promising this for a while, but now it's happened: The latest version of isdn4k-utils has been packaged. Yippie! :-) deb http://www.murphy.nl/~paul/debian isdnutils/ After this, apt-get update; apt-get install ipppd isdnlog-data should install isdnutils, ipppd, isdnlog, and isdnlog-data. You should install any of the other packages that you need. Nope, doesn't. * ipppd is not there - 404 not found Bugger, I copied isdn*deb. I should have called it isdnpppd? :-/ * isdnutils won't be fetched by apt-get if there is an isdnutils already installed Bugger, I forgot the fscking epoch in the depends. Please let me know if you use this version, and keep me informed of Ah, yes. Where? Here, on -devel, privately, as BTS bugs, on a secret and mystical mailing list? (-8* I think if it isn't too much, -devel will be fine (at least it'll also be archived then). If necessary I can set up a mailing list at murphy.nl. BTW: I'll be unavailable electronically this weekend (starting Friday afternoon until Monday morning), so don't feel ignored if I don't reply during that time. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alternatives for MUA and NUA?
On Thu 07 Sep 2000, Junichi Uekawa wrote: In Wed, 6 Sep 2000 23:10:32 +1100 Hamish Moffatt [EMAIL PROTECTED] cum veritate scripsit : I looked at that configuration file. It appeared to me that there was enough info in there for reportbug just to use /usr/sbin/sendmail to deliver it, rather than using an MUA at all. Some people do not have sendmail. I use imput for internet mail, and sendmail only reaches my local network. I don't have sendmail; I have exim. However, I *do* have /usr/sbin/sendmail. Perhaps imput should have a /usr/sbin/sendmail - compatible wrapper? Perhaps it already does? Maybe I'm weird. No comment :-) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-move problem
On Thu 07 Sep 2000, Mika Fischer wrote:
On Thu, 07 Sep at 16:59 +0200, Andreas Tille wrote:
I wanted to give apt-move a try:
Unfortunately I get only syntax errors:
~# apt-move
/usr/bin/apt-move: line 122: syntax error near unexpected token `('
What am I doing wrong?
I guess nothing. I had the same problem a few weeks ago and solved it by
editing the file manually.
I don´t know what went wrong in the first place, though. The syntax errors
were so obvious that it can´t possibly be typos.
Please check the BTS for apt-move, this is discussed externsively.
Apparently it's a (for me non-obvious) bug in bash.
Paul Slootman
--
home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/
work: [EMAIL PROTECTED] http://www.murphy.nl/
debian: [EMAIL PROTECTED] http://www.debian.org/
isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new experimental ISDNUTILS packages available
On Thu 07 Sep 2000, Andreas Fuchs wrote: Today, I [EMAIL PROTECTED] wrote: Calling isdnrep is not working well: it's looking for the zone files in /usr/lib/isdn/zone, but they are in /usr/lib/isdn/: In /usr/share/isdn/ actually. Oh, silly me. I had configured isdnrep to look specifically there, in /etc/isdn/isdn.conf. Fixed this now, let's see if it works... tippety tip=tap / No. Misconfigured before and I am too lazy to tidy it up. Seems like I will configure-from-scratch it now (-: You can also copy an example isdn.conf for .de from /usr/share/doc/isdnlog/examples/isdn.conf.de.gz which should have the correct settings. Or throw away your /etc/isdn/isdn.conf and run dpkg-reconfigure isdnlog :-) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new experimental ISDNUTILS packages available
On Thu 07 Sep 2000, Andreas Fuchs wrote: You see, isdnconfig tries to copy from /usr/share/doc/isdnutils/examples/defaults/ipppd.DEVICE to /etc/isdn/ipppd.$device. Now, ipppd.DEVICE is named ipppd.DEVICE.gz (arghl, automatic gzipping in docs dir?). And it resides in /usr/share/doc/ipppd/...! Actually, that's not the problem, it's always been like that, also in the old version. The problem is that the new config script doesn't rename it properly (I had started to make a debconf script to configure an ipppd interface, but then ran out of inspiration :-/ and thought that it would be better to release what I had first, so that adventurous people could test the basics (thanks!) So, would you mind making a symbolic link to the doc dir? Removing .../ipppd.DEVICE from the documentation list should work, also. I just need to fix the script... Maybe tomorrow, otherwise early next week. Thanks, Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new experimental ISDNUTILS packages available
On Thu 07 Sep 2000, Paul Slootman wrote: These packages have been uploaded to the experimental distribution (but not yet installed at this moment, maybe today?), FYI: I got got mail from the installer that it's been put into experimental. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian and KDE: Appology
On Fri 08 Sep 2000, Paul Seelig wrote: about. They IMHO righfully complained about RMS' forgiving talk which is more like religious speech from a church or something. If the catholic pope would utter such words it could be silently ignored, though it would be appropriate speech in his ideological context. Well, he *does* consider himself a saint; from his page http://www.stallman.org/saint.html : Stallman is a saint in the Church of Emacs---Saint IGNUcius. :-) But RMS speaking like *this* is rather unappropriate and IMHO quite insulting. I wonder if the author of ncftp who was hurting the GPL by He _is_ sometimes a bit tactless, but gets his point across. Unfortunately, because he's such a prominent figure, people react strongly to him or are otherwise more critical of anything he does or says. RMS should IMHO publically apologize with the KDE people for this condescending part of his otherwise correct article. He should be So now _you_ are telling someone to ask for forgiveness? Paul Slootman (not a follower of RMS myself) -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
updated experimental ISDNUTILS packages available 1:3.1pre1b-1.1
I've fixed a couple of problems that were detected with the first version. Today's version is available from the www.murphy.nl site. Line for sources.list: http://www.murphy.nl/~paul/debian isdnutils/ This is the changelog extract: * I've taken the newest upstream CVS version again, which included quite a lot of what was in isdnutils_3.1pre1b-1.diff.gz . * Fixed dependencies (I had forgotten the epoch) * Fixed isdnconfig to get its default files from the right places; also removed isdnlog stuff from it as isdnlog has its own debconf stuff now. * Re-implemented some smart stuff in vboxmail and vboxplay that I had added in the 3.0 series of isdnutils. The old ones (3.1pre1b-1) is available in http://www.murphy.nl/~paul/debian/isdnutils/1/ if the need arises... Enjoy. I'll be back on Monday. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update excuses.. how to read them
On Sat 23 Dec 2000, Anthony Towns wrote: Since libadns0 and libadns0-dev seem to be out of date on all architectures, it probably means they're not being built anymore, and need to be removed from unstable. Whether there are up to date bins on an arch is more just to give a hint at what might be causing the problem, rather than anything particularly important. The same seems to be the problem with the following: * jed-ja 0.99.10.jp0-3 (currently 0.98.7.j055-2) (low) + Maintainer: Kikutani Makoto [EMAIL PROTECTED] + jed-ja is 106 days out of date! + out of date on alpha: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in alpha also + out of date on arm: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in arm also + out of date on i386: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in i386 also + out of date on m68k: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in m68k also + out of date on powerpc: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in powerpc also + out of date on sparc: jed-sl-ja (from 0.98.7.j055-2) + there are up to date bins in sparc also + not considered jed-sl-ja is not built anymore (note that it is out of date on ALL architectures). Does this mean it won't be installed into woody until someone manually removes jed-sl-ja_0.98.7.j055-2.deb from all architectures in sid? Is there a build-info for all the other platforms, too? How can I see why the alpha failed to build my package? See bug 81379 :-) Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: update excuses.. how to read them
On Sun 07 Jan 2001, Anthony Towns wrote: On Sun, Jan 07, 2001 at 01:05:57AM +0100, Paul Slootman wrote: jed-sl-ja is not built anymore (note that it is out of date on ALL architectures). Does this mean it won't be installed into woody until someone manually removes jed-sl-ja_0.98.7.j055-2.deb from all architectures in sid? Right. Is there a bug against ftp.debian.org about this? That's the done Apparently not, submitting now. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: Bug#81396: root shell fscked after upgrade to woody
On Sun 07 Jan 2001, Eray Ozkural wrote: About having telnet enabled: everybody on the campus knows how to use telnet but would be very surprised I didn't let them connect easily from windows clients. For me, using telnet is of course a bit insecure but when I'm not able to use an ssh client... it's easier. Search google for putty, if you need an ssh client for windows. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: Bug#81396: root shell fscked after upgrade to woody
On Sun 07 Jan 2001, Colin Watson wrote: Paul Slootman [EMAIL PROTECTED] wrote: Search google for putty, if you need an ssh client for windows. http://www.chiark.greenend.org.uk/~sgtatham/putty/ (hmm, I appear to have that memorized - I end up grabbing it any time I'm at a public Windows-based Internet terminal). :-) For what it's worth, I discovered entirely by accident that if you install telnetd-ssl then the telnet client in Windows 98 and above will connect to it and seamlessly do SSL negotiation, while of course non-SSL-capable telnet clients will still be able to connect insecurely. That's pretty amazing, I had no idea that something standard in windows would have such features. Usually only by adding all sorts of extras (such as putty) is windows capable of doing anything remotely useful. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: Bug#95975: mutt: doesn't use charset anymore
reopen 95975 thanks Package: mutt Version: 1.3.15-2 Since upgrading to testing, mutt refuses to display iso-8859-1 high-bit characters such as u-umlaut (ü). Instead, \374 is displayed. :set charset shows charset=iso-8859-1; the message's Content-Type is: Content-Type: text/plain; charset=iso-8859-1 so that shouldn't be the problem. Hitting 'v' and then piping the message body through 'cat' displays it all correctly. RTFM README.Debian. Thanks for this eloquent explanation. So I should now set en environment variable to get mutt working the way it used to, which was a reasonable mode of operation. IMHO that's in violation of policy section 10.9: A program must not depend on environment variables to get reasonable defaults. So what's the point of the charset setting? After all, the manual.txt (which isn't a plain text file, but that's beside the point for this discussion) still states: 6.3.20. charset Type: string Default: Character set your terminal uses to display and enter textual data. Obviously it doesn't work that way anymore! So don't say I should read the FM, I F did. README.Debian is NOT a manual. manual.txt is. So fix the FM if the way it works has changed. Perhaps even give an error if charset is defined, as it apparently isn't used anymore. Paul Slootman
Re: Bug#95975: mutt: doesn't use charset anymore
On Wed 02 May 2001, Marco d'Itri wrote: close 95975 I disagree about whether the bug is closed, as you forget to notice parts of my message. However, I don't feel like petty BTS games (*) On May 02, Paul Slootman [EMAIL PROTECTED] wrote: So I should now set en environment variable to get mutt working the way it used to, which was a reasonable mode of operation. IMHO that's in violation of policy section 10.9: A program must not depend on environment variables to get reasonable defaults. You'd better reassign this bug to libc then, guess what is mutt using to determine if a character is printable or not? Well, (as I wrote), mutt's manual.txt says that the charset setting is used for that. So what's the point of the charset setting? After all, the manual.txt It tells mutt about which charaset you are typing. The exact quote from the docs is: Character set your terminal uses to display and enter textual data. Note the display in addition to enter. So not only: It tells mutt about which charaset you are typing. but also what can be displayed. If that's no longer the case, at least fix the documentation! And perhaps add a note about the necessary environment variables. Obviously it doesn't work that way anymore! So don't say I should read It just does not work the way you think it does. Neither does it work the way it's documented. As this is a change from long-standing previous behaviour, I don't think you can skim over it in such a trivial manner. As a fortune quote says (paraphrasing): if the code and the comments disagree, both are wrong. I feel this also applies to the code and the documentation. (*) I really hate it when people close bugs with a one-liner (or less) answer, without any substantiating motivation. Especially when parts of the argumentation of the bug are ignored. What's the problem with leaving the bug open until the discussion is closed? Such behaviour is pretty childish. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: why dig ? I wanna use nslookup !
On Tue 01 May 2001, Marco d'Itri wrote: On Apr 28, Stefano Zacchiroli [EMAIL PROTECTED] wrote: OK, but who have choose that nslookup is deprecated in favour of the other two tools ? The people who wrote BIND and developed a very large part of the DNS infrastructure, the group of people who knows about DNS more than most other people in the world. Heh. *I* know more about DNS than most other people in the world (and that's not saying much). nslookup is broken, please let it die its long-deserved death. What's broken about it, apart from the brokenness that's in the current version about the verbose warnings and missing features (eg. ls) ? AFAIK it does exactly what it was designed to do. This is like saying ed is broken, use emacs, while ed performs its task perfectly. So, please explain what is really broken about it. After all, it's NSlookup, not HOSTlookup or whatever. Both dig and host are too noisy for me, although I won't hesitate to use them when I need their specific functionality. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: Bug#95975: mutt: doesn't use charset anymore
On Thu 03 May 2001, Michael Stone wrote: On Thu, May 03, 2001 at 05:51:53PM -0700, Ben Gertzfield wrote: Paul == Paul Seelig [EMAIL PROTECTED] writes: Paul I think that *mutt* is definitely broken in this regard, Paul because *no* other console program i know (e.g. mc or pine) Paul breaks like this using the very same libc. It's not just mutt. GTK+ has the same problem. ls does the same thing. It's a fact of life; locales need to be configured if you're not working in 7bit ASCII. Sure, whatever, but *my* original point is that there is a setting in mutt, namely charset, which is documented to tell mutt what character set the terminal is capable of displaying and entering. This used to work fine, but suddenly it doesn't anymore even though the docs have not changed one iota in this respect. I'd suggest that as long as the charset setting is still supported in mutt, mutt should use that to override an absence of any locale settings (as it in fact did in the past, effectively). Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Bug#191072: ITP: dirvish -- Filesystem based backup system using rsync
Package: wnpp Version: unavailable; reported 2003-04-28 Severity: wishlist Package name: dirvish Version : 1.1rc1 Upstream Author : J.W. Schultz of Pegasystems Technologies jw at pegasys.ws URL : http://www.pegasys.ws/dirvish/ License : GPL Description : Filesystem based backup system using rsync A utility to maintain multiple backups on online storage, each backup is available as a sort of snapshot directory, where common files are shared between the different backup generations. It uses rsync to do the actual copying. . Backups can be made locally or over the network (using ssh). A proposed version can be downloaded with the following lines in sources.list: deb http://www.wurtel.net local main deb-src http://www.wurtel.net local main Paul Slootman
Michael-John Turner MIA? (was: Debian MIA check)
On Tue 13 May 2003, James Troup wrote: Of the 191 pings were sent out: o 34 people's ping bounced[1]. o 28 people replied asking to be retired. o 29 people replied with various different responses. o 10 people replied who were active. o 90 people didn't reply within the 2 month deadline[2]. I've not had any response to a message I sent Michael-John Turner [EMAIL PROTECTED] a couple of months ago, asking him about his status. However, I don't see him on James' list. According to echelon he's not been seen since 10 Feb 2002. It's about bugs in mrtg that caused me to look for him. It may be necessary to hijack his packages if he is in fact MIA. A search on Google doesn't show any recent activity either. Paul Slootman pgpBUYYSNPpCQ.pgp Description: PGP signature
Re: Michael-John Turner MIA? (was: Debian MIA check)
On Fri 16 May 2003, Martin Michlmayr wrote: I didn't check yet whether he really made that upload. But yeah, the mrtg bug is certainly a good reason to contact him again... Feel I wrote to him (again) on the 13th about his, still zero response. free to NMU in the meantime. Done, mrtg 2.9.29-0.1 is accepted. I also needed to upload libsnmp-session-perl 0.95-0.1 as the new mrtg depends on this 0.93 or higher (only 0.90 was available), and MJ is also the maintainer for this package. Paul Slootman
Re: Daft Internet Stuff [Re: Returning from vacation. (MIA?)]
On Mon 19 May 2003, Colin Watson wrote: On Mon, May 19, 2003 at 10:17:40PM +0200, Josip Rodin wrote: (I'd quote a proverb about how small things lead to big things, but I can't currently think of any of those in English. :) Look after the pennies and the pounds will take care of themselves. As in penny wise, pound foolish ? :-) (I love proverbs, there's one to prove anything.) Paul Slootman
Re: Bug#194155: ITP: ehnt -- Extreme Happy Netflow Tool - Obtains useful information out of netflow data
On Wed 21 May 2003, Craig small wrote: * Package name: ehnt Version : x.y.z Upstream Author : Name [EMAIL PROTECTED] * URL : http://www.some.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : Extreme Happy Netflow Tool - Obtains useful information out of netflow data (Include the long description here.) You might have made the effort of filling in the fields; I can't believe the version is x.y.z, the upstream author is Name [EMAIL PROTECTED], etc. Especially the license... Paul Slootman
Re: Accepted bwidget 1.6.0-1 (all source)
On Mon 26 May 2003, Brian Nelson wrote: Umm, no, the changelog is for listing changes (*change* log, get it?), not for just closing bugs without any reason given whatsoever. Why do so many seem to have difficulty with this concept? Is it worthwhile to Cc this stuff to -devel, or should I just give up and let the proliferation of these IMO useless changelogs continue? (serious, not rhetorical, questions) Presumably the people who continue to do this don't read debian-devel, or at least not thoroughly (the subject line of your messages don't necessarily reflect the point you're trying to get across). Perhaps a separate, concise message to debian-devel-announce? Paul Slootman
Re: Which machine is best to build documentation package?
On Wed 17 Dec 2003, Osamu Aoki wrote: Since SSH upload has been disabled, it looks very slow and unreliable to upload. (Does dupload uses -C ? Somehow, I felt faster.) Using -C will not make it faster, as all the files to be uploaded are compressed already (except .changes and .dsc, which are tiny). Paul Slootman
