Bug#4327: hsearch(3) man page patches

[Richard Kettlewell]

Package: manpages
Version: 1.11-4

I suggest that the following patch be applied to
``/usr/man/man3/hsearch.3''.

-BEGIN--
--- hsearch.3.orig  Wed Aug 28 21:52:40 1996
+++ hsearch.3   Wed Aug 28 22:00:33 1996
@@ -29,11 +29,14 @@
 .nf
 .B #include 
 .sp
-.BI "ENTRY *hsearch(ENTRY " item ", ACTION " action ");
-.RE
+.BI "ENTRY *hsearch(ENTRY " item ", ACTION " action ");"
+.sp
+.BI "int hsearch(unsigned " nel ");"
+.sp
+.BI "void hdestroy(void);"
 .fi
 .SH DESCRIPTION
-This three functions allow the user to create a hash table of type
+These three functions allow the user to create a hash table of type
 \fIENTRY\fP (defined in \fB\fP) which associates a key 
 with any data. The implementation uses \fBmalloc(3)\fP.
 .PP
@@ -41,7 +44,7 @@
 \fInel\fP is an estimation of the table size which will suffice the
 needs. For better algorithms this value can be corrected upwards.
 .PP
-The corresponding function \fIhdestroy()\fP frees the memory occupied by
+The corresponding function \fBhdestroy()\fP frees the memory occupied by
 the hash table for that a new table can be constructed.
 .PP
 \fIhsearch()\fP is the function for searching and inserting. Which action
@@ -51,9 +54,9 @@
 and \fIFIND\fP means to only search. Unsuccesful actions result in a
 return value \fINULL\fP.
 .SH "RETURN VALUE"
-\fBhcreate()\fP return zero if the hash table cannot be succesfully installed.
+\fBhcreate()\fP returns zero if the hash table cannot be succesfully installed.
 .PP
-\fBhsearch()\fP return \fINULL\fP if either action is \fIENTER\fP and the
+\fBhsearch()\fP returns \fINULL\fP if either action is \fIENTER\fP and the
 hash table is full or action is \fIFIND\fP and the \fIitem\fP cannot be find
 in the hash table.
 .SH BUGS
-END

-- 
Richard Kettlewell   [EMAIL PROTECTED]   [EMAIL PROTECTED]
 http://www.elmail.co.uk/staff/richard/

uploading gs_4.01-3

[joost witteveen]

-BEGIN PGP SIGNED MESSAGE-

Date: 28 Aug 96 21:19 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: gs
Version: 4.01-3
Binary:  gs
Architecture:  i386 source
Description: 
 gs: Postscript interpreter with X11 and svgalib preview support.
Changes:
 * fixes: rounded-corners bug, patch provided by Thomas Koenig <[EMAIL 
PROTECTED]>
 * Applied a patch from Helmut Geyer <[EMAIL PROTECTED]>
   (Thanks, Helmut!), and gs now uses the shared libs for:
  png, jpeg, zlib. (as well as vga, X11, ...).
 * Gs still prints debugging info in xdvi (don't know why)
Files:
 6ae3475923b701639cf4ecd8eb9a7da9  2185258  non-free  -  gs_4.01-3.tar.gz
 eb24e408fdd3ab204b3f80657a55f93c  23493  non-free  -  gs_4.01-3.diff.gz
 3b3d3f81d6070a6c54e9c506f0772688  1079668  non-free  Optional  
gs_4.01-3_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMiS5NZNVaG8BiEBRAQHB7wQAmM0fh5rrP/mf5Oswz00CZS1gKx92De22
aFm0KMwn9ve66RrQB0G0zcEJ4MiLX5xo5fjTbiH5talo+VYZ2B4sJlcwVvNf6Dbk
V+uWGxKGfWWOYqgrUZNpOzpBUIZS45RGiPUFDgZpVTuade/t/OZ2bSFbGzs5HaUn
S2BZRHpgD/M=
=z9oj
-END PGP SIGNATURE-

Re: BSD lpr vs. LPRng

[Sven Rudolph]

In article <[EMAIL PROTECTED]> Richard Kaszeta <[EMAIL PROTECTED]> writes:

> >I created an LPRng package for Debian. LPRng is an enhanced BSD-like
> >print spooler and is nearly compatible. (It is available at
> >ftp://iona.ie/pub/plp/LPRng/ ).
> >
> >I'm thinking of obsoleting the lpr package by LPRng.
> 
> >Cons:
> >- minor incompatibility (needs addditional flag in printcap for
> >  printing to BSD lpd printers)
> >- not as widespread as BSD lpr
> 
> Well, if its not completely compatible with lpr (a rather
> well-entrenched standard), I certainly think it *should not* obsolete
> lpr.

The only incompatibility is that you might have to add a :bk: entry to
the printcap in order to print to a BSD-lpd-based network printer. But
especially in these environments LPRng can make life easier, so I
believe this to be acceptable.

Sven
-- 
Sven Rudolph <[EMAIL PROTECTED]> ; WWW : http://www.sax.de/~sr1/

Re: BSD lpr vs. LPRng

[Sven Rudolph]

In article <[EMAIL PROTECTED]> Michael Meskes <[EMAIL PROTECTED]> writes:

> Sven Rudolph writes:
> > 
> > I created an LPRng package for Debian. LPRng is an enhanced BSD-like
> > print spooler and is nearly compatible. (It is available at
> > ftp://iona.ie/pub/plp/LPRng/ ).
> 
> Is it's call compatible? Or does the user have to learn a new syntax?

The commands are the same as in BSD lpr (lpr, lpq, lprm, lpc,
lpd). They have additional options for new features.

Sven
-- 
Sven Rudolph <[EMAIL PROTECTED]> ; WWW : http://www.sax.de/~sr1/

Re: Packages to give away

[Guy Maor]

On Wed, 28 Aug 1996, Michael Meskes wrote:

> shadow

I will take shadow as I am integrating it into login, passwd, etc.
anyway.


Guy

uploading gs_3.33-1

[joost witteveen]

-BEGIN PGP SIGNED MESSAGE-

Date: 28 Aug 96 18:39 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: gs
Version: 3.33-1
Binary:  gs
Architecture:  i386 source
Description: 
 gs: Postscript interpreter with X11 and svgalib preview support.
Changes:
 - New upstream version.
 - Following a patch I got from Helmut Geyer <[EMAIL PROTECTED]>
   for gs-4.01, I manually patched gs-3.33 to use the shared jpeg libs.
 (gs-4.01-3 will also use the shared zlib, and png libs).
 - Now uses libpaper to parse the /etc/papersize file.
Files:
 a6974b4d80a5706aab919463c416c761  1659344  text  -  gs_3.33-1.tar.gz
 70adf6563ea3bcd94f0ba01301fbec69  12499  text  -  gs_3.33-1.diff.gz
 558aa7492f546118c20cdb76b3a1912b  793308  text  Optional  gs_3.33-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMiSTfpNVaG8BiEBRAQFNZwP+PvQ3sdqqUI8qV5He98IE7gPtuLIF+RhL
TwwhVqj4zWZaZbpzey+5Hor3quoiCuU9IcGa2wkiEyhi4i6pGzfmyoUKtk3fNyR7
oC63rIHFxSPmnCyujkN8AVav+QpV3Yf5o8ktaU19T1lETGpCFA7Jy/E5LV6HUhlA
ChMO5fvf2Jg=
=Y5hM
-END PGP SIGNATURE-

Re: Bug#4269: xosview has only XOSView as application resource file

[Owen Dunn]

In article <[EMAIL PROTECTED]> you write:
>> "jw" == joost witteveen <[EMAIL PROTECTED]> wrote:
>
>jw> do you want me to 
>jw>   1 move xosview to 'contrib', and stop maintaining it
>jw>   2 just go on maintaining a broken xosview?
>
>IMHO, you should stick with 1. There are other things that may do the
>same thing xosview is supposed to do.
>
>>>From sunsite.unc.edu:/pub/Linux/INDEX.whole: 
>
>/pub/Linux/X11/xutils/status
>procmeter-1.1.tgzdisplays a set of graphs with system stats
>xsysinfo-1.5.tar.gz  provides a graphical representation of system
> state

Debian has packages for both, I believe. (In fact, I'm told that both
I and someone else have packaged procmeter recently, so we'll see
which one gets into the distribution :-) )

(S)

Bug#4133: Earlier version doesn't exhibit the bug.

[TropiX Support]

I backed Samba out to version 1.9.15p4 (which is the 1.1.x stable
package) and this bug went away.  Hopefully someone with a lot more
experience than I with network code can track down and squish this, I
assume it happens to other people as well.  I'm pretty sure it is was
caused by an attempt to access a non-existant share (was there and then
removed when the files moved to a different machine).

Re: pgp docs missing.

[Guy Maor]

On Wed, 28 Aug 1996, Dale Scheetz wrote:

> In the pgp_us package both the readme.1st.intl and the readme.doc.us both
> refer to the file setup.doc, but I don't see that file anywhere in the doc
> directory for pgp. Is there some reason for this to be missing?

setup.doc is the installation guide; you don't need it because you
already have pgp installed.


Guy

Bug#4326: smail can lose bounce messages

[Ian Jackson]

Package: smail
Version: 3.1.29.1-14

Under certain obscure circumstances Smail can lose mail:

When it needs to send a bounce message it reinvokes itself with the
`-bS' flag, meaning to read SMTP commands from standard input but not
to produce responses.  It then feeds an SMTP `session' to the
subprocess.  Now, smail never produces error responses to
syntactically valid input (unlike, for example, some sendmails which
will fail a RCPT TO on a user that they think is local to them but is
unknown).

However, the subprocess may fail for some other reason.  Perhaps the
copy of Smail it wishes to reinvoke cannot be found, or has some
configuration error serious enough to cause it to fail to write the
message anywhere.

In this case the parent smail will write the message into its child
anyway and fail to notice the non-zero exit status.

I have reproduced the problem with a test setup under controlled
conditions, and can provide strace logs &c.

I'm not sure what happens if the disk is full.

Ian.

Bug#4325: majordomo -- incorrect quoting of '@'

[Brian C. White]

Package: majordomo
Version: 1.93-3

The "request-answer" does not properly quote the "@" character (as required
by perl-5) it its outgoing mail.

The offending lines are:

  print MAIL <<"EOM";
  To: $reply_to
  From: $list-request
  Subject: Your mail to [EMAIL PROTECTED]
  In-Reply-To: $in_reply_to
  Reply-To: [EMAIL PROTECTED]

  This pre-recorded message is being sent in response to your recent
  email to [EMAIL PROTECTED]


These should be changed to:

  print MAIL <<"EOM";
  To: $reply_to
  From: $list-request
  Subject: Your mail to [EMAIL PROTECTED]
  In-Reply-To: $in_reply_to
  Reply-To: [EMAIL PROTECTED]

  This pre-recorded message is being sent in response to your recent
  email to [EMAIL PROTECTED]


  Brian
 ( [EMAIL PROTECTED] )
 
---
  Want to get it together?  We can help!  http://www.verisim.com/coordinator/

Re: Packages to give away

[Syrus Nemat-Nasser]

I could take xcolors and xsysinfo.  I use sudo, so I would take
that package but I'm not a very experienced sysadmin and I suppose
there might be subtle security issues that would make me less than
qualified.

Let me know.  Syrus.

--
Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.

Bug#4323: xntp allows only one timeserver

[Michael Shields]

Package: xntp
Version: 3.5c-1

xntp's postinst only lets you input one timeserver.  It would be easy to
have it allow you to enter multiple space-seperated timeservers, and output
multiple `server' lines into /etc/ntp.conf.

--
Shields, CrossLink.

Bug#4305: metmail uses non-existent flag in postinst

[Susan G. Kleinmann]

Michael Meskes writes:
> Susan G. Kleinmann writes:
> > 
> > Package: metamail
> > Version: 2.7-6
> 
> Oops, wrong depends line. Please upgrade your mime-support package.
> 

(Perhaps this should be a seperate bug report; if you want one, please
let me know.)

I upgraded mime-support to  2.02-1 sometime yesterday.   

Today I re-ran dpkg --configure metamail.  This produced some odd
queries:

# dpkg --configure metamail
Setting up metamail (2.7-6) ...

New action 'view' for MIME type 'image/*'...
--> package=metamailview=showpicture -viewer "xloadimage -view 
-quiet" %s

1)  package=metamailview=showpicture -viewer xv %s

Place at what priority? (1-2) -->1
 ^^^<--- Notice that these indices do not match
 the choices above ["-->" and "1)"] 


New action 'view' for MIME type 'text/richtext'...
--> package=metamailview=shownonascii iso-8859-1 -e richtext -p %s; 
test=test "`echo %{charset} | tr "[A-Z]" "[a-z]"`" = iso-8859-1 -a "$DISPLAY" 
!= ""; copiousoutput

1)  package=metamailview=shownonascii iso-8859-8 -e richtext -p %s; 
test=test "`echo %{charset} | tr "[A-Z]" "[a-z]"`" = iso-8859-8 -a "$DISPLAY" 
!= ""; copiousoutput

Place at what priority? (1-2) -->1
 ^^^<--- Notice that these indices do not match
 the choices above ["-->" and "1)"] 


New action 'view' for MIME type 'text/richtext'...
--> package=metamailview=richtext %s; copiousoutput

1)  package=metamailview=shownonascii iso-8859-1 -e richtext -p %s; 
test=test "`echo %{charset} | tr "[A-Z]" "[a-z]"`" = iso-8859-1 -a "$DISPLAY" 
!= ""; copiousoutput
2)  package=metamailview=shownonascii iso-8859-8 -e richtext -p %s; 
test=test "`echo %{charset} | tr "[A-Z]" "[a-z]"`" = iso-8859-8 -a "$DISPLAY" 
!= ""; copiousoutput

Place at what priority? (1-3) -->1
 ^^^<--- Notice that these indices do not match
 the choices above ["1)" and "2)"] 




This seems to be a problem with install-mime; or perhaps I did 
something wrong.  ??

Susan

Bug#4322: lclint postinst gives error if no site-start.el

[Michael Shields]

Package: lclint
Version: 2.1b-1

While installing lclint, it says

grep: /etc/site-start.el: No such file or directory

This may or may not be cosmetic.
-- 
Shields, CrossLink.

Bug#4316: cron -- crontab -l prints excess header

[Brian C. White]

Steve Greenland wrote:
> > Would you mind stripping these first three lines from the "crontab -l"
> > output?
> 
> Yes, because I think there is useful information there (primarily
> the second line, with the file name (usually) and date).

Could you write them to STDERR and the rest of the info to STDOUT?


> Since it's in a script anyway, why not strip it yourself:
> 
>  crontab -l |sed -e '1,/^# (Cron version/ d'
> 
> (actually "sed -e '1,3 d'" would proably be sufficient.)

I thought about this, but it requries my script to know about the
internals of crontab.  If crontab ever changed, then a problem could
arise.  I prefer to keep related functionality as together as possible.


> I'm going to close this one.

Hold on just a sec...  Let's resolve how this is going to be handled,
first.
 
  Brian
 ( [EMAIL PROTECTED] )
 
---
 the difference between theory and practice is less in theory than in practice

Bug#3047: cron script problem? (fwd)

[Herbert Thielen]

Seems as if this message didn't find it's way to the debian bug log's,
because I didn't reply in the right way. So I send it again.

Regards
Herbert.

- Forwarded message from thielen -

>From thielen Sat Aug 17 13:03:38 1996
Subject: Re: Bug#3047: cron script problem?
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Sat, 17 Aug 1996 13:03:38 +0200 (MET DST)
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]> from "Bruce Perens" at May 17, 96 11:36:00 am
X-Mailer: ELM [version 2.4 PL24 ME7a]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1366  

Bruce Perens's mail:

> Package: cron
> From: "Ariel O. Garcia" <[EMAIL PROTECTED]>
> when running /etc/cron.daily/find, cron sends me the following mail:
> **
> From: root (Cron Daemon)
> Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
> X-Cron-Env: 
> X-Cron-Env: 
> 
> X-Cron-Env: 
> X-Cron-Env: 
> 
> run-parts: /etc/cron.daily/find exited with return code 1
> *
> the /etc/dron.daily/find file is:
> *
> #! /bin/sh
> #
> # cron script to update the `find.codes' database.
> #
> # Written by Ian A. Murdock <[EMAIL PROTECTED]>.
> 
> su nobody -c "cd / && updatedb" 2>/dev/null
> *

Don't know if anyone answered yet - I've read this through the mirrord
WebPages.

I had the same problem in April this year. The problem at my system was
that `nobody' didn't have a valid shell, so `su' didn't work. The
following change fixed it:

--- /etc/passwd 1996/04/24 09:15:14 1.4
+++ /etc/passwd 1996/04/29 13:18:45 1.5
@@ -24 +24 @@
-nobody:*:65534:65534:nobody:/dev/null:/dev/null
+nobody:*:65534:65534:nobody:/dev/null:


So it's not a problem of the cron package. I noticed that this is fixed
in base 1.1.0-14, probably earlier.


Regards
Herbert.

- End of forwarded message from thielen -

Bug#4320: dc fonts (t1enc) are much too big

[Herbert Thielen]

Package: latex
Version: 2e-7

Package: mfbasfnt
Version: 1.0-4

This didn't find it's way to the bug logging system as I used the old
mail address. So it's here again ...

Regards
Herbert.

- Forwarded message from thielen -

>From thielen Sun Aug 18 02:12:48 1996
Subject: dc fonts (t1enc) are much too big
To: [EMAIL PROTECTED]
Date: Sun, 18 Aug 1996 02:12:48 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL24 ME7a]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1133  

Package: latex
Version: 2e-7

Package: mfbasfnt
Version: 1.0-4


When I latex the following little document:

\documentclass[12pt,german,a4paper]{report}
\usepackage[T1]{fontenc}% T1 font encoding
\begin{document}
\chapter{One}
\end{document}

LaTeX reports:
[...]
Chapter 1.

Overfull \hbox (1288.91795pt too wide) in paragraph at lines 4--4
[]\T1/cmr/bx/n/24.88 Chapter 

Overfull \hbox (436.20694pt too wide) in paragraph at lines 4--4
[]\T1/cmr/bx/n/24.88 One  
[...]

When viewing it with xdvi, metafont creates new fonts (e.g.
dcr1200.3pk), and the characters are _BIG_.

I could resolve the problem after some hours of searching :-(  :
In latex-2e/base/unpack.ins (in the source tree) `newdc.ins' gets input.
But it seems as if the dc fonts provided in mfbasfnt_1.0-4 (and
mdcfnt_1.0-1_all - same metafont sources) are the old one (I don't know
anything about the new dc font's, just read about a version 1.2 in
cmfonts.fdd).

By

latex olddc.ins
mv T1*fd /usr/lib/texmf/tex/latex/base
cd /usr/lib/texmf/ini; initex latex.initex

I could generate a new latex format with the old dc description.

Regards
Herbert.


- End of forwarded message from thielen -

Bug#4321: doc-debian has old bug-reporting email address

[Herbert Thielen]

Package: doc-debian
Version: 1.0-2

In /usr/doc/debian/bug-reporting.txt.gz the email address for bug
reports is [EMAIL PROTECTED], but it seems as if mails send there
never go to the debian bug logs.

WebPages/Bugs/Reporting.html contains the right address [EMAIL PROTECTED]


Regards
Herbert.

Bug#4319: netbase and netstd packages overwrite config-files

[Stefan Petters]

Package: netstd and netbase

Upgrade from version 2.03-1 (each) to version netbase-2.04-1 netstd-2.06-1

Hi,

during the upgrade vom version 2.03-1 from netbase and netstd to
netbase-2.04-1 netstd-2.06-1 a number of config files were overwritten
without my confirmation and even without informing me. There were:

netbase:
/etc/hosts.deny
/etc/hosts.allow

netstd:
/etc/hosts.equiv
/etc/diphosts
/etc/exports
/etc/init.d/netstd_nfs
/etc/init.d/netstd_misc

There may be more, which I didn't find since they aren't needed on my
systems. Especially the /etc/hosts.deny is very annoying, since I've to
admin a system of several Linices which are directly connected to the
internet and I don't want my boxes to stand wide open to several attacks (I
know you can't get it water proof if your connected to the net, but it
doesn't have to be that easy to get me wasting my time in recovering the
machines).

If I remeber right, there was a question like ``Do you want our new
config-files to be installed (y/n)?'' in several packages installing things
in /etc and /etc/init.d which was a good thing. Additional there were
backups build like fiename.{debian|dpkg-old} to recover changes made.

Is there any chance the packages are constructed that way again?

[BTW] Thanks for providing debian at all. I had experiance with a
slackware--system before I changed my systems to debian, and it's much
easier to admin debian but my old slackware.

Regards
Stefan.
-- 
--
Stefan Petters   Lehrstuhl fuer Prozessrechner TU-Muenchen   -ooo
Arcisstr. 21 Tel: 089/289-23556 --
80290 Muenchen   Fax: 089/289-23555 oo
EMail: [EMAIL PROTECTED]  ---o 
--

Bug#4305: metmail uses non-existent flag in postinst

[Michael Meskes]

Susan G. Kleinmann writes:
> 
> Package: metamail
> Version: 2.7-6
> ...

A new version is underways.

Michael

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

pgp docs missing.

[Dale Scheetz]

In the pgp_us package both the readme.1st.intl and the readme.doc.us both
refer to the file setup.doc, but I don't see that file anywhere in the doc
directory for pgp. Is there some reason for this to be missing?

TIA,

Dwarf

  --

aka   Dale Scheetz   Phone:   1 (904) 877-0257
  Flexible Software  Fax: NONE 
  Black Creek Critters   e-mail:  [EMAIL PROTECTED]

 If you don't see what you want, just ask --

metamail_2.7-7

[Michael Meskes]

My first try with the new format. Could anyone who knows more about it than
I do (Ian?) please take a look at it to see if everything's correct? Also I
wonder since it suffices to upload diff + deb + changes + dsc for the next
version, how do I tell dpkg-buildpatch to adjust? Hmm, seems I have to read
the manuals once again. Anyway, here's the .dsc and .changes file:

-BEGIN PGP SIGNED MESSAGE-

Source: metamail
Version: 2.7-7
Binary: metamail
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Architecture: any
Standards-Version: 0.2.1.1
Files: 
 3401751ef93bd141f0179d3ad5b2f0a6 156075 metamail_2.7.orig.tar.gz
 bca60d4306283ca50410f6530f2cadbf 16931 metamail_2.7-7.diff.gz

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMiRRaCpaNcQEtuj1AQEX+QQAlT9lXE29wYSShmzvNvslx/xzr/Kb2I39
OiuYyltbb3BhSUNbCGC79sVTpH2+g8vYFA4txTpY5HcdBOn9wyv6mDcNpfeTWwX0
YznqnoCKq9zQxxIW3dJS0AsTgf7xLN4Pg7DJBzJ9cE+PU7dMh+YARJbHg6DeCEY3
PpyhVoX5w+U=
=Xrac
-END PGP SIGNATURE-

-BEGIN PGP SIGNED MESSAGE-

Format: 1.5
Date: Wed, 28 Aug 1996 14:05:10 +0200
Source: metamail
Binary: metamail
Architecture: source i386
Version: 2.7-7
Distribution: unstable
Urgency: low
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Description: 
 metamail   - An implementation of MIME.
Changes: 
 metamail (2.7-7) unstable; urgency=LOW
 .
   * Corrected dependency (Bug#4305)
   * New packaging scheme
Files: 
 cf0037d69058833c576cc0fb8d2a7afa 604 mail optional metamail_2.7-7.dsc
 bca60d4306283ca50410f6530f2cadbf 16931 mail optional metamail_2.7-7.diff.gz
 236cef17382cdfc80d81b2dc995fe6d0 147140 mail optional metamail_2.7-7_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMiRReipaNcQEtuj1AQE+hgP9Er9I8AxdaS4mIkJCcPr72aZS6XBBLojF
NBri4JXh3XHVopks5oe/ntYFh8Bdwr1cXGn8Q6j/YHZcT+F7ru28fFRlrYWOOuPf
sEdoyGDMewoh3Q9gLtdvgSGVmVOHereHxRojE3SahFbyo0CyinGIHwkqmgAg9C7R
BT0P3Qwsz5g=
=TU95
-END PGP SIGNATURE-

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

Bug#4318: important TeX fonts missing

[Thomas Koenig]

Package: mfbasfnt
Version: 1.0-3

The metafont base fonts are missing important fonts, for example
cmbx14.

Here's an example:

$ xdvi example.dvi
kpathsea: Running MakeTeXPK cmbx14 300 300 1+0/300 deskjet
Running MakeTeXPK cmbx14 300 300 1+0/300 deskjet
Running mf \mode:=deskjet; mag:=1+0/300; scrollmode; input cmbx14
This is METAFONT, Version 2.71 (C version 6.1)

kpathsea: Running MakeTeXMF cmbx14.mf 
I don't know how to generate cmbx14.mf!
! I can't find file `cmbx14.mf'.
<*> ...jet; mag:=1+0/300; scrollmode; input cmbx14
  
Please type another input file name: 
! Emergency stop.
<*> ...jet; mag:=1+0/300; scrollmode; input cmbx14
  
Transcript written on mfput.log.
MakeTeXPK failed to make cmbx14.300gf.

Here's the dvi file in question, uuencoded:

begin 600 example.dvi
M]P([EMAIL PROTECTED]'#L``^@;(%1E6"!O=71P=70@,3DY-BXP-"XQ,3HQ-3$YBP``
M``$```#_H`)Y
M``"-H/VC``"@`C\``([EMAIL PROTECTED]>0``(V-D3X``/,/`;#L2P`.9F8`#F9F``9C;6)X
M,32Z,8Z15=F44V.:CN]HEO]69G638I`M.7-P86YNDW5G;G-VF&60$/5R;&&1
M_V=;=6:.GQ7G&[EMAIL PROTECTED])<

Re: Packages to give away

[Heiko Schlittermann]

Michael Meskes wrote:
: 
: I will change jobs October 1st and I'm afraid I won't have enough time anymore
: to do as much work for Debian as I do now. Since I will keep an internet

...

For a first approach I'd take the lshell package.
  ~~

Perhaps one or two more ... but let's wait a bit ;-)


Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Re: BSD lpr vs. LPRng

[Michael Meskes]

Sven Rudolph writes:
> 
> I created an LPRng package for Debian. LPRng is an enhanced BSD-like
> print spooler and is nearly compatible. (It is available at
> ftp://iona.ie/pub/plp/LPRng/ ).

Is it's call compatible? Or does the user have to learn a new syntax?

Michael

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

Re: Bug#4051: access permissions for /usr/bin/fdmount

[Michael Meskes]

Ian Jackson writes:
> It should be 4754 - there's no point in stopping people reading it.
> (I've been saying 4754 all along, and this is what is in the policy
> manual.)

Oops, I thought that was a typo :-)

> Err, I strongly suggest that you compile the group check out of the
> executable.  This is only likely to lead to confusion.

I think I understand what you mean. But is it really that bad?

Michael

-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

New changelog format

[Michael Meskes]

Is there a reason why dpkg-parsechangelog is so picky about the number of
blanks used? Does it really matter if I have one or two blanks between my
email address and the date? I think it could be a bit more user friendly.
Please keep in mind that not everyone uses emacs.

Michael
-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

Packages to give away

[Michael Meskes]

I will change jobs October 1st and I'm afraid I won't have enough time anymore
to do as much work for Debian as I do now. Since I will keep an internet
account I won't be lost, though. Aynway, with this lack of time I have to
give away a lot of my packages. They are all in a pretty good state. In fact
there's only one outstanding bug report and I'm currently compiling a new
upload to close that one.

The packages are:

adjtimex
fdutils
hkgerman
html2latex
joe
lshell
lyx
metamail
modules
mtools
perforate
quota
shadow
sudo
symlinks
xautolock
xcolors
xforms
xsysinfo

Any takers?

Michael
-- 
Michael Meskes   |_  __  
[EMAIL PROTECTED] |   / ___// / // / / __ \___  __
[EMAIL PROTECTED]  |   \__ \/ /_  / // /_/ /_/ / _ \/ ___/ ___/
[EMAIL PROTECTED]|  ___/ / __/ /__  __/\__, /  __/ /  (__  )
Use Debian Linux!| //_/  /_/  //\___/_/  //

Bug#4294: gcc -bi486-linux can't find cc1

[Thomas Koenig]

David Engel wrote:
>Thomas Koenig writes:
>> David Engel wrote:
>> >> $ gcc -bi486-linuxaout hello.c 
>> >> gcc: installation problem, cannot exec `cc1': No such file or directory
>> 
>> >This isn't a bug.
>> 
>> To change a bug into a feature, it needs to be documented.
>
>This has been documented for ages.

It has been documented sufficiently that you need the "-V" flag
to get a particular version of gcc.

It has not been documented sufficiently that you need to specify
"-V 2.6.3" to compile an a.out package under Debian.  This violates
the principle of least surprise.
-- 
Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED]
The joy of engineering is to find a straight line on a double
logarithmic diagram.

Bug#4317: xosview should display cached mem

[joost witteveen]

> 
> Package: xosview
> Version: 1.3.2-6
> 
> The mem bar only shows shared/shared/buf/free which is incorrect.
> It should display: used/buffer/cached/free. Shared doesnt fit in that
> summary chart, and cached is missing (for recent kernels of course).
> The amount of shared isnt very easy to be displayed as bar, since its seatic
> has changd (can be more than physical memory for multiple usage).

Absolutely.

I'm stopping maintaining xosview, with the previous flood of bug-reports
that I cannot do anything about, and with the apearence of procmeter
(it's very nice, all you prospective xosview buggers: try procmeter!)


Although I guess the upstream maintainer would be interested
to correct this one, I think, togehter with the other ones, I'll
just try to move xosview to contrib.



-- 
joost witteveen
[EMAIL PROTECTED]
  [EMAIL PROTECTED]
--
Use Debian/GNU Linux!

Bug#4316: cron -- crontab -l prints excess header

[Steve Greenland]

Brian C. White wrote:
> 
> Package: cron
> Version: 3.0pl1-34
> 
> Running "crontab -l" has a bad habit of displaying header information
> that is not actually part of the crontab.
> 
> For example:
> 
> $ crontab -l -u gnats
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- installed on Mon Jul 29 14:07:28 1996)
> # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
> 5,15,25,35,45,55 * * * * /usr/lib/gnats/queue-pr --run
> 
> [snip]
>
> Would you mind stripping these first three lines from the "crontab -l"
> output?

Yes, because I think there is useful information there (primarily
the second line, with the file name (usually) and date).

Since it's in a script anyway, why not strip it yourself:

 crontab -l |sed -e '1,/^# (Cron version/ d'

(actually "sed -e '1,3 d'" would proably be sufficient.)

I'm going to close this one.

Steve Greenland

-- 
The Mole - I think, therefore I scream 

Bug#4317: xosview should display cached mem

[Bernd Eckenfels]

Package: xosview
Version: 1.3.2-6

The mem bar only shows shared/shared/buf/free which is incorrect.
It should display: used/buffer/cached/free. Shared doesnt fit in that
summary chart, and cached is missing (for recent kernels of course).
The amount of shared isnt very easy to be displayed as bar, since its seatic
has changd (can be more than physical memory for multiple usage).

Greetings
Bernd
-- 
  (OO)  -- [EMAIL PROTECTED] --
 ( .. )   [EMAIL PROTECTED],linux.de}  http://home.pages.de/~eckes/
  o--o *plush*  2048/A2C51749  [EMAIL PROTECTED]  +4972573817  *plush*
(OO)   If privacy is outlawed only Outlaws have privacy

Bug#4315: xfishtank problems

[Dirk . Eddelbuettel]

  Dirk> 1. The package contains nothing but the binary. It *must* contain at
  Dirk> least the copyright file. Docs would be nice.

  Christoph> There is no copyright. The packages origin are unknown.  I can
  Christoph> just generate a file with "Unknown" in it.

Are you sure there is nothing in the source code? I have yet to see a
(publicly released) program in which the author didn't leave a note.

  Dirk> 2. It has no Depends: on libc5 or elf-x11r6lib.

  Christoph> Hmm. Some other packages were taken without it. Where can I find
  Christoph> docs on these things?

Install a recent dpkg and read the html'ed policy and programmers manuals
below /usr/doc/dpkg, or download and study the debian sources of other
packages.

  Dirk> 3. It uses the old VERSION and PACKAGE_REVISION format which is
  Dirk> obsolete.

  Christoph> What are the new requirements.

See the policy and programmers manuals. 

--
Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd

Bug#4316: cron -- crontab -l prints excess header

[Brian C. White]

Package: cron
Version: 3.0pl1-34

Running "crontab -l" has a bad habit of displaying header information
that is not actually part of the crontab.

For example:

$ crontab -l -u gnats
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul 29 14:07:28 1996)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
5,15,25,35,45,55 * * * * /usr/lib/gnats/queue-pr --run


Those first three lines do not appear when using "crontab -e" and they
cause problems if trying to modify the crontab using a script since
reading the crontab via "crontab -l", modifying it, and the sending
the changed data to "crontab" will end up with a duplicate header stored.
The output of "crontab -l" would then be something like:

$ crontab -l |  | crontab; crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul 29 14:07:28 1996)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul 29 14:07:28 1996)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
5,15,25,35,45,55 * * * * /usr/lib/gnats/queue-pr --run


Would you mind stripping these first three lines from the "crontab -l"
output?
  
   Brian
  ( [EMAIL PROTECTED] )
  
---
 the difference between theory and practice is less in theory than in practice

Bug#4269: xosview has only XOSView as application resource file

[Emilio Lopes]

> "jw" == joost witteveen <[EMAIL PROTECTED]> wrote:

jw> do you want me to 
jw>   1 move xosview to 'contrib', and stop maintaining it
jw>   2 just go on maintaining a broken xosview?

IMHO, you should stick with 1. There are other things that may do the
same thing xosview is supposed to do.

>From sunsite.unc.edu:/pub/Linux/INDEX.whole: 

/pub/Linux/X11/xutils/status
procmeter-1.1.tgzdisplays a set of graphs with system stats
xsysinfo-1.5.tar.gz  provides a graphical representation of system
 state

I have not checked them out, though.

Ciao, Emilio.

-- 
 Emilio C. Lopes 
   Instituto de Fisica da Universidade de Sao Paulo
 Caixa Postal 66318, 05389-970 Sao Paulo - SP, BRAZIL
  Phone: (+55) (11) 818-6724 (Voice) / 818-6715 (Fax)

Re: Bug#4261: Ghostview -- needs MIME entry

[Emilio Lopes]

> "BCW" == Brian C White <[EMAIL PROTECTED]> wrote:

BCW> I suggest making ghostview "Recommends: mime-support".

I don't see why this is necessary. "mime-support" brings no extra
capabilities to ghostview, AFAIK.

Ciao, Emilio.

-- 
 Emilio C. Lopes 
   Instituto de Fisica da Universidade de Sao Paulo
 Caixa Postal 66318, 05389-970 Sao Paulo - SP, BRAZIL
  Phone: (+55) (11) 818-6724 (Voice) / 818-6715 (Fax)

Re: Bug#4315: xfishtank problems

[Christoph Lameter]

On Tue, 27 Aug 1996 [EMAIL PROTECTED] wrote:

Dirk.Eddelbuettel>
Dirk.Eddelbuettel>PACKAGE: xfishtank
Dirk.Eddelbuettel>VERSION: 2.2-1
Dirk.Eddelbuettel>
Dirk.Eddelbuettel>1. The package contains nothing but the binary. It *must* 
contain at least the
Dirk.Eddelbuettel>   copyright file. Docs would be nice.
There is no copyright. The packages origin are unknown.
I can just generate a file with "Unknown" in it.

Dirk.Eddelbuettel>
Dirk.Eddelbuettel>2. It has no Depends: on libc5 or elf-x11r6lib.
Hmm. Some other packages were taken without it. Where can I find docs on
these things?

Dirk.Eddelbuettel>
Dirk.Eddelbuettel>3. It uses the old VERSION and PACKAGE_REVISION format which 
is obsolete.
What are the new requirements.

{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
{}Snail Mail:   FTS Box 466, 135 N.Oakland Ave, Pasadena, CA 91182{}
{}FISH Internet System Administrator at Fuller Theological Seminary   {}
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
PGP Public Key  =  FB 9B 31 21 04 1E 3A 33  C7 62 2F C0 CD 81 CA B5 

Unanswered problem reports by maintainer and package

[Ian Jackson]

The following problem reports have not yet been marked as `taken up' by a
message to [EMAIL PROTECTED] or or `forwarded' by a
message to [EMAIL PROTECTED]

The maintainer listed against each package is derived from the Maintainer
field of the package as found in the development tree; there is an override
file that can be amended to get the right results if you have taken over a
package and do not expect to issue a new version soon.

Variant versions of the Maintainer field for the same actual package
maintainer will be listed separately.

Maintainers with few outstanding bugs appear first, to avoid those with few
bugs being lost deep in the message.

 Package RefSubject

Stuart Lamble <[EMAIL PROTECTED] (1 bugs):
 unzip4314  unzip is missing > in Maintainer field

Michael Meskes <[EMAIL PROTECTED]> (1 bugs):
 metamail 4305  metmail uses non-existent flag in postinst

Manoj Srivastava <[EMAIL PROTECTED]> (1 bugs):
 make 4073  make pattern rules delete intermediate files

Brian Mays <[EMAIL PROTECTED]> (1 bugs):
 cpio 4072  cpio package is missing rmt.8 manual

Martin Schulze <[EMAIL PROTECTED]> (1 bugs):
 zoo  3961  14 character file name limit in zoo

Nikhil Nair <[EMAIL PROTECTED]> (1 bugs):
 gnuchess 4123  "gnuchess" requires changes for multi-arch support

Dirk Eddelbuettel <[EMAIL PROTECTED]> (1 bugs):
 mirror   4238  mirror requires perl

Karl Ferguson <[EMAIL PROTECTED]> (1 bugs):
 unarj3641  unarj description: ext start indented, summary starts w/ pk

[EMAIL PROTECTED] (Brian C. White) (1 bugs):
 gnats3053  gnats: typo in postinst omits install-info

David Frey <[EMAIL PROTECTED]> (1 bugs):
 rpncalc  4156  rpncalc has unexecutable unwriteable /usr/man, /usr/man/man

Mike Coleman <[EMAIL PROTECTED]> (1 bugs):
 nn   4181  Searching for wrong active file

[EMAIL PROTECTED] (Bill Mitchell) (1 bugs):
 elv-ctags2503  elvis and emacs both provide ctags

Manoj Srivastava <[EMAIL PROTECTED]> (1 bugs):
 kernel-pac   4234  errors in /usr/man/man8/make-kpkg.8

Brian White <[EMAIL PROTECTED]> (1 bugs):
 ferret   4164  Ferret extended description has blank lines

Brian Sulcer <[EMAIL PROTECTED]> (1 bugs):
 mgt  4023  "mgt" requires changes for multi-arch support

Susan Kleinmann <[EMAIL PROTECTED]> (1 bugs):
 sp   4102  sp and LaTeX problems

[EMAIL PROTECTED] (Andrew D. Fernandes) (2 bugs):
 acs  3559  acs description: no ext
 acs  3851  "acs" requires changes to support multiple arches

Leland Lucius <[EMAIL PROTECTED]> (2 bugs):
 dialog   2591  rootdisk
 dialog   3514  Required package modconf depends on extra package dialog

Martin Schulze <[EMAIL PROTECTED]> (2 bugs):
 sysklogd 4163  syslogd loops
 sysklogd 4228  syslogd loops

Karl Sackett <[EMAIL PROTECTED]> (2 bugs):
 exmh 3824  exmh fails to start
 xpostitplu   4101  xpostitplus loses previous postit notes

Siggy Brentrup <[EMAIL PROTECTED]> (2 bugs):
 electric-f   3582  electric-fence description: no ext
 electric-f   4045  "electric-fence" requires changes for multi-arch support

Anders Christrom <[EMAIL PROTECTED]> (2 bugs):
 lists.debi   3199  Bizarre message from [EMAIL PROTECTED]
 lists.debi   3978  problem (re)subscribing to debian-devel

Kenneth MacDonald <[EMAIL PROTECTED]> (2 bugs):
 ispell   2425  ispell thinks `formated' is correct
 ispell   3196  ispell symlinks broken

Ray Dassen <[EMAIL PROTECTED]> (2 bugs):
 www.debian   3431  some packages have no information on WWW-server
 www.debian   3700  Web pages lack 

Christian Linhart <[EMAIL PROTECTED]> (2 bugs):
 xarchie   887  xarchie barfs when ftp closes unexpectedly
 xarchie  1275  xarchie clumsy with 2-button mouse

Steven B Dunham <[EMAIL PROTECTED]> (2 bugs):
 hdparm   2197  hdparm -c switch
 hdparm   3866  "hdparm" requires changes to support multiple arches

Maarten Boekhold <[EMAIL PROTECTED]> (2 bugs):
 slrn 4069  slrn gives error
 slrn 4103  slrn epends on unavailable slang-lib09931

Jeroen van der Most <[EMAIL PROTECTED]> (2 bugs):
 dmalloc  3925  "dmalloc" requires changes for multi-arch support
 dmalloc  4275  "dmalloc" requires changes for multi-arch support

Martin Schulze <[EMAIL PROTECTED]> (2 bugs):
 msql 4297  msql 1.0.16 cannot connect to remote DBs
 msqld4254  msql config problems

Wichert Akkerman <[EMAIL PROTECTED]> (2 bugs):
 grep 4182  grep on /proc/kcore dumps core
 strace   2177  "strace -ff -o file dpkg --install foo.deb" causes dpkg to 

[EMAIL PROTECTED] (D.J. Gregor) (2 bugs):
 cdtool   2450  `cdir' prints out huge chunks of /etc/passwd !
 unclutter4042  "unclutter" requires changes for multi-arch support

Raul Miller <[EMAIL PROTECTED]> (3 bugs):
 sam  4030  "sam" requires changes for multi-arch support
 ucbmpeg  3454  ucbmpeg control file problems
 ucbmpeg  3509  mpeg_play puts bogus statistics on stdout

Kenny Wickstro

Re: New virtual package names.

[Dale Scheetz]

On 27 Aug 1996, Rob Browning wrote:

> Dale Scheetz <[EMAIL PROTECTED]> writes:
> 
> > (Until they try to remove all editors)
> 
> I don't want to cause trouble, but why don't we just completely
> disallow the removal of ae.  It's harmless, and the entire package
> only takes up 54K.  I can't see that it's worth spending another
> second even thinking about.
> 
> Am I missing something?
> 
Well, this brings us full circle.
Rob, the declaration of ae as essential has been declared a bug. This kept
ae from being removed which caused some to complain. The current
discussion is an attempt to move beyond this. 
Ian's position is that it doesn't matter if ae and all other editors are
removed from the system. Yours is that it doesn't matter if ae can't be
removed. I hope that we can come to some middle ground here.

Thanks,

Dwarf

  --

aka   Dale Scheetz   Phone:   1 (904) 877-0257
  Flexible Software  Fax: NONE 
  Black Creek Critters   e-mail:  [EMAIL PROTECTED]

 If you don't see what you want, just ask --

Re: Do we ever retire packages?

[Lukas Nellen]

> [EMAIL PROTECTED] writes:
> > I have argued before that a2ps and a2gs are effectively replaced by
> > genscript, and that we should remove them. I think a similar case could be

Please don't do that. Personally, I am used to a2ps and I'm a lot more attached 
to my habits than to genscript :-). And I don't see why we should retire a 
package just because some other package with similar functionality is provided. 
Think of the different flavours of vi which are available as debian packages.

But I see the point that lack of interest might be a reason to retire a 
package. I can see two cases in which a package would be considered obsolete:

a) The package is obsolete because the functionality (in the low level sense 
of, say, the programs provided) is moved into some other package(s). An example 
would be what happened to libgr.

b) A package is orphaned for a long time and similar functionality (in the high 
level sense, like genscript vs. a2ps) is provided by another package available. 
Or the package is considered to be irrelevant for all but a small minority 
which doesn't express its interest. Maybe such a package should be moved into 
one directory like {unstable,non-free,contrib}/obsolete for a longer period (to 
preserve the effort of debianizing the package in case someone wants to take it 
up later). Eventually, packages can get purged from the obsolete directories if 
nobody expresses interest in maintaining them. 

By moving a package into one of the obsolete directories, the distribution 
maintaines and/or the developers express their opinion that a given package is 
not sufficiently important from their point of view. At the same time, this 
acts as a final call for a new maintainer to step forward and express his 
interest in keeping the package alive.

Lukas

---
   Dr. Lukas Nellen | Email: [EMAIL PROTECTED]
   Depto. de Fisica Teorica, IFUNAM |
   Apdo. Postal 20-364  | Tel.:  +52 5 622 5014 ext. 218
   01000 Mexico D.F., MEXICO| Fax:   +52 5 622 5015