Bug#1897: apropos not resilient to index.db corruption

Alvar Bray: I have heard several other people say they have had corrupt database files - how do they get corrupted? I have never managed to corrupt mine (but then I, as the package maintainer, wouldnt would I) Possibly a SIGINT, SIGQUIT, SIGTERM, SIGKILL at an inopportune time.

miscutils snag/questions for all

I recently took over as maintainer of the miscutils package. I'm working on a new release, but I have several questions to ask before I continue. * miscutils is one of the few (only?) debian packages currently distributed without diffs. I'd like to distribute it with diffs. * The miscutils c

New Perl Packages, New Maintainer

I've uploaded new Perl packages to ftp.debian.org. These are based on the new Perl 5.002 beta which solves some SDBM issues on my end. I've generated both a "dld & a.out" as well as an elf version. I know that both packages install fine on my end but then again, I built them, they should. Could

inline-math-1.7 (fwd)

I haven't taken a look it this yet, but would we want to replace the mathematical functions mentioned below with these new routines? I caught this, and I believe that it points out a flaw (minor) in GCC, and improvements to the math functions. Ideas, comments, flames? --D.J. Gregor, qui

Bug#1897: apropos not resilient to index.db corruption

Alvar Bray: I have heard several other people say they have had corrupt database files - how do they get corrupted? I have never managed to corrupt mine (but then I, as the package maintainer, wouldnt would I) I imagine one technique might be to have the file system get full during a d

Bug#1897: apropos not resilient to index.db corruption

On Sat, 25 Nov 1995, Alvar Bray wrote: [...] > > I have heard several other people say they have had corrupt database > files - how do they get corrupted? I have never managed to corrupt > mine (but then I, as the package maintainer, wouldnt would I) I have no idea how mine got corrupted, sorry :

Re: Bug#1895: run-parts does not run scripts without #!/...

I think I am going to rewrite run-parts in C. I don't know perl and don't have the time to learn it just to fix run-parts. :) Jeff > Harald Schueler writes ("Bug#1895: run-parts does not run scripts without > #!/..."): > > Package: miscutils > > Version: 1.3-5 > > > > Run-parts does not run sc

Bug#1897: apropos not resilient to index.db corruption

Hi Austin, > Package: man > Version: 2.3.10-2 > > 'man -k' and 'apropos' with a damaged or corrupted index.db > segfaults. This is not a very friendly error message. > > I have traced the problem to the following piece of code: > ... > > Could this infelicity be passed on to the upstream mainta

Re: Some questions concerning further sysklogd upload

Martin Schulze writes ("Some questions concerning further sysklogd upload"): > We (Greg and myself) are now at a late stadium right before releasing > 1.3 of our sysklogd package. To have a smooth introtuction I have to > get some answers to some questions before can it for debian I > have. Hopeful

Bug#1898: getwd(3) contains falsehood

Package: manpages Version: 1.8-1 getwd(3) claims: getwd, which is only prototyped if __USE_BSD is defined, will malloc(3) an array big enough to hold the absolute pathname of the current working directory. However, the libc Info page says: - Function: char * getwd (ch

Some questions concerning further sysklogd upload

Hi folks! We (Greg and myself) are now at a late stadium right before releasing 1.3 of our sysklogd package. To have a smooth introtuction I have to get some answers to some questions before can it for debian I have. Hopefully the maintainers are willing to answer. :-) 1. Who is responsible for k

Bug#1895: run-parts does not run scripts without #!/...

Harald Schueler writes ("Bug#1895: run-parts does not run scripts without #!/..."): > Package: miscutils > Version: 1.3-5 > > Run-parts does not run scripts not beginning with #!/... This may not be > a bug, but it should be documented. run-parts --test, however, displays > _all_ scripts, which is

Bug#1897: apropos not resilient to index.db corruption

Package: man Version: 2.3.10-2 'man -k' and 'apropos' with a damaged or corrupted index.db segfaults. This is not a very friendly error message. I have traced the problem to the following piece of code: whatis.c 364: /* scan for the

dpkg problems? + one volunteer needed

I have nearly finished debianising the tripwire package. However, I have still some minor problems: 1. although I specified 'tripwire' (in lowercase) as package name in the debian.control file, after installation I get the package name capitalized: bash# dpkg -l | more Desir

Re: innd won't start on my ELF converted machine

> I am sending this to the devel list, assuming that not many others have > converted to ELF yet. > > Anyway, the subject says alot. I have had innd running on my system for > sometime. After loading all of the new ELF and A.OUT libs, innd doesn't > start. I get a message in the log that say