Re: ITH (Intent To Hijack) pilot-manager

>Just wanted to let people know that I'm going to hijack the >pilot-manager package. The current maintainer seems to be completely >MIA; he hasn't uploaded a version in over a year. I emailed him and Feel free to adopt the pilot-manager package... Darren -- <[EMAIL PROTECTED]>

Brendan O'Dea as Debian Perl developer

While off on yet more travel earlier today, I confronted my lack of progress in packaging Perl for Debian. For too long, I've been denying it. But I have to face that my life is simply not currently structured to have time to maintain Perl like I should. Brendan has been patient over the months

Re: determining if we're using db.h from libc6 or libdb2?

Domenico Andreoli, in an immanent manifestation of deity, wrote: >i don't know how much what i'm going to say would be of help, but if you added >a new check in configure.in in order to let your source know what kind of db.h >you have? you could be pretty sure that your sources are getting compiled

Re: determining if we're using db.h from libc6 or libdb2?

Ben Collins, in an immanent manifestation of deity, wrote: >On Tue, Sep 12, 2000 at 12:46:02AM -0700, Darren/Torin/Who Ever... wrote: >> Is there some set of defines such that I can determine with #ifdef that >> I've got a copy of glibc2 that has db.h as an include file? M

determining if we're using db.h from libc6 or libdb2?

Is there some set of defines such that I can determine with #ifdef that I've got a copy of glibc2 that has db.h as an include file? My plan is that if such a #ifdef is true, then I can #include . Thanks, Darren -- <[EMAIL PROTECTED]> <[EMAIL PROTECTED]><[EMAIL PRO

Re: possible problem with new perl, libc6 on Sep 23rd

-BEGIN PGP SIGNED MESSAGE- Ben Collins <[EMAIL PROTECTED]>, in an immanent manifestation of deity, wrote: >More specifically it is dpkg doing the breaking, but it's perl's fault on >how it is setting everything up. > >You will note that these two binaries are in the perl package itself > >

Re: removing perl-base

-BEGIN PGP SIGNED MESSAGE- Russell Coker, in an immanent manifestation of deity, wrote: >It's been a while since the versioned Perl was introduced into potato, so I >tried removing the fake package perl-base. >Should I report bugs against bug, dpkg-perl, data-dumper, and tetex-base? Or >i

Re: possible problem with new perl, libc6 on Sep 23rd

-BEGIN PGP SIGNED MESSAGE- Branden Robinson, in an immanent manifestation of deity, wrote: >apt problem or perl problem? perl is shipping with a mode 600 executable; that >seems pretty weird to me but I try to keep my distance from perl. >[0] 1014 apocalypse ~ > ls -dl /usr/bin/perl-5.005

Re: XEmacs 21

James LewisMoss, in an immanent manifestation of deity, wrote: >I have xemacs 21 packages aptable at >"deb http://va.debian.org/~dres xemacs21/". I would appreciate >some people trying them out and seeing what problems you find (please >report directly to me rather than bug tracking system). Well

Re: Perl 5.005.02

-BEGIN PGP SIGNED MESSAGE- Roderick Schertler, in an immanent manifestation of deity, wrote: >I don't think Andy is taking into account your plan of allowing both >threaded and non-threaded Perls present on the system at the same time. That's okay since a) threaded Perl has it's own archi

Re: Perl 5.005.02

-BEGIN PGP SIGNED MESSAGE- Andy Dougherty, in an immanent manifestation of deity, wrote: >After some thought, I think I'd recommend that perl5.005_xx retain the >same directory structure that perl5.00[34]_xx did. (with 5.005 in place of >5.00[34], of course). That's good enough for me. I

Re: Perl policy for managing modules ?

-BEGIN PGP SIGNED MESSAGE- Zephaniah E. Hull, in an immanent manifestation of deity, wrote: >Rename perl to perl5.005, version 02-2 or such.. >Then use the alternatives setup to decide which perl gets run when you >try to use just 'perl'.. That's possible but I'm not sure it's a good idea

Re: File renamer

-BEGIN PGP SIGNED MESSAGE- Ian Jackson, in an immanent manifestation of deity, wrote: >A whole .deb for such a simple problem seems overkill. The >file/manpage below is what I use. It was in the Perl4 distribution. >Presumably perl5 comes with it too in the source. I have it as >/usr/lo

Re: Reverting to Perl 5.004

-BEGIN PGP SIGNED MESSAGE- Brian White, in an immanent manifestation of deity, wrote: >Perl 5.005 will be replaced in Slink with 5.004. The new version will >remain in the next unstable. > >Correct? Definitely. Sorry for the slow reply but my root disk started spewing scsi errors about

Re: Perl policy for managing modules ?

-BEGIN PGP SIGNED MESSAGE- Raphael Hertzog, in an immanent manifestation of deity, wrote: >What about also adding /usr/lib/perl5(/$arch)? at the end of @INC ? >Is it possible ? >In that way, recent packages that are installed in /usr/lib/perl5/debian >are used first and only if no package

Re: Perl policy for managing modules ?

-BEGIN PGP SIGNED MESSAGE- Raphael Hertzog, in an immanent manifestation of deity, wrote: >Yes, but it's better leaving site_perl empty. It can be used for manually >(modules not in a .deb file) installing modules. Yes, I realize this. But most people using Perl manually install modules.

Re: Perl policy for managing modules ?

-BEGIN PGP SIGNED MESSAGE- Raphael Hertzog, in an immanent manifestation of deity, wrote: >Darren, if you agree, can you modify the perl package in order to >install modules in /usr/lib/perl5/debian and make these symlinks ? > >- /usr/lib/perl5/$arch/$version => /usr/lib/perl5/debian/$arch

Re: perl5.005 installation structure

-BEGIN PGP SIGNED MESSAGE- John Lapeyre, in an immanent manifestation of deity, wrote: > Ah, ... you are reading now. Yes, sorry I'm a bit slow; I'm working on buying a house. I do usually respond quicker to stuff in my inbox than just to list stuff. > Could you confirm or d

Re: PERL: patch for glibc 2.1

-BEGIN PGP SIGNED MESSAGE- Matt McLean, in an immanent manifestation of deity, wrote: >It's no longer needed. 5.00502 now has a configure test for union semun. Cool. I thought I had seen that but I figured that I'd leave it for people that track that much closer. >I know what's going on

Re: Switch to perl-5.005_02 ?

-BEGIN PGP SIGNED MESSAGE- Joey Hess, in an immanent manifestation of deity, wrote: >Do you have any plans to offer it as something like /usr/bin/perl-t? (or >would modules need to be rebuilt too?) It will be available as /usr/bin/perl5.00502-thread. I could manage the /usr/bin/perl-t a

Re: About the Hamm Freeze (!)

-BEGIN PGP SIGNED MESSAGE- Stephen Zander, in an immanent manifestation of deity, wrote: >Not true Darren: dbmopen does the moral equivalent of the tie under >the covers. It's one of my pet peeves that perl links in libraries to >the main executable that are only required by extensions.

Re: Serious performance bug in Perl

-BEGIN PGP SIGNED MESSAGE- Daniel Martin, in an immanent manifestation of deity, wrote: >My... it's been a while since I was investigating perl internals >(writing C code that was callable from perl) - at least two years, >which somehow seems much longer. > >Well, I'll have my machine down

Re: About the Hamm Freeze (!)

-BEGIN PGP SIGNED MESSAGE- James Troup, in an immanent manifestation of deity, wrote: >Of course, I agree, but my point was that gdbm *Shouldn't* be required >and although it will need to be made so in hamm as a kludge, I tried >to get this fixed properly back in March. And the point that

Re: Serious performance bug in Perl

-BEGIN PGP SIGNED MESSAGE- Chris Fearnley, in an immanent manifestation of deity, wrote: >But yesterday I upgraded a bo system to hamm which has a 3000 line >/etc/passwd. Now adduser takes OVER ONE MINUTE to find a UID and GID >for the new user. And my staff is complaining about the wast

Re: About the Hamm Freeze (!)

-BEGIN PGP SIGNED MESSAGE- James Troup, in an immanent manifestation of deity, wrote: >"Darren/Torin/Who Ever..." <[EMAIL PROTECTED]> writes: >> It hasn't happened *intentionally*. I'm not going to break many >> Perl scripts without warning. We h

Re: Documentation/License freeness

-BEGIN PGP SIGNED MESSAGE- Santiago Vila Doncel, in an immanent manifestation of deity, wrote: >- From [EMAIL PROTECTED] Tue Jun 2 21:45:40 1998 >Date: 28 May 1998 22:02:52 -0400 > >Once upon a time, I thought I would learn Perl. I got a copy of a >free manual, but I found it simply unre

Re: About the Hamm Freeze (!)

-BEGIN PGP SIGNED MESSAGE- Raul Miller, in an immanent manifestation of deity, wrote: >James Troup <[EMAIL PROTECTED]> wrote: >> No; perl shouldn't depend on libgdbmg1. libgdbmg1 is obsolete and >> deprecated. I asked the perl maintainer if he could fix this back in >> March or so, appar

Re: About the Hamm Freeze (!)

-BEGIN PGP SIGNED MESSAGE- James Troup, in an immanent manifestation of deity, wrote: >No; perl shouldn't depend on libgdbmg1. libgdbmg1 is obsolete and >deprecated. I asked the perl maintainer if he could fix this back in >March or so, apparently it hasn't happened. We had this discuss

Re: Uploaded less 332-2.1 (source i386) to master

-BEGIN PGP SIGNED MESSAGE- Joel Klecker, in an immanent manifestation of deity, wrote: > less (332-2.1) frozen unstable; urgency=high > . > * Non-maintainer release. I had thought I had uploaded this but I don't see it anywhere on master. I guess it was part of the master problem? Exp

Re: Bug#21691: perl-base is essential nothing should Depend: on it.

-BEGIN PGP SIGNED MESSAGE- Enrique Zanardi, in an immanent manifestation of deity, wrote: >> P.S. Why is data-dumper in base? >'Cause libnet-perl depends on it. Sorry, I mis-stated the question. Why does libnet-perl depend on data-dumper in base. I thought we (as in debian-devel) had di

Re: Possible new name for "deity"

-BEGIN PGP SIGNED MESSAGE- Anthony Fok, in an immanent manifestation of deity, wrote: >Actually, AFAIK, Mitsubishi stands for "Three Diamonds". Mitsu is "three" >in Japanese, so I guess that means "bishi" is diamond. :-) Yes, it's actually a geometric diamond as opposed to the stone...

Re: wu-ftpd important bug(s)

-BEGIN PGP SIGNED MESSAGE- >Yes, wu-ftpd is depreciated, since all it's functionality is in >wu-ftpd-academ. The only problem is: how can I handle this? Btw, folks, the term is deprecated. Note that there isn't an 'i'. It means (loosely) "It's still around but don't use it. It's going

packaging pilot-manager

-BEGIN PGP SIGNED MESSAGE- I've mentioned this on debian-pilot but I should probably also mention it here. I'm packaging pilot-manager (http://www.moshpit.org/pilotmgr/) for debian. It's actually packaged already and waiting on the new pilot-link to come out... Darren - -- <[EMAIL PRO

Re: less: extra entries for lesspipe

-BEGIN PGP SIGNED MESSAGE- Manoj Srivastava, in an immanent manifestation of deity, wrote: > I know that. The accepted way of using less used to be to use > a upstream filter. Right now, it is done like so: >__ >__>

Re: less: extra entries for lesspipe

-BEGIN PGP SIGNED MESSAGE- Manoj Srivastava, in an immanent manifestation of deity, wrote: > know how to do so. From the principle of least surprise, I say leave > the default alone (I hate how it does tar zvvft already; I used to be > able to look at text files in a tar.gz archive without

Re: less: extra entries for lesspipe

-BEGIN PGP SIGNED MESSAGE- Carl Mummert, in an immanent manifestation of deity, wrote: >useful information when you use it on different types of files-- gzip for >gz files, tar -t for tar files, groff for manpages, etc... If I _wanted_ >to look at the raw data of a gzipped file, I could d

Re: less: extra entries for lesspipe

-BEGIN PGP SIGNED MESSAGE- Richard Braakman, in an immanent manifestation of deity, wrote: >One reason I like less is that it's so fast. I sometimes use it on >thousands of files at once. (For example, when searching a source >package for uses of a particular identifier). I've been thin

Re: less: extra entries for lesspipe

-BEGIN PGP SIGNED MESSAGE- I can't add the /proc entries since you don't know the full pathname of the file you are viewing. I could use `pwd` to find out what directory I'm in. If you'd like me to do that, just say so but it would involve another fork/exec for every file. (All the othe

Re: Dumping core: root vs. normal user

-BEGIN PGP SIGNED MESSAGE- Eloy A. Paris, in an immanent manifestation of deity, wrote: >an easy one: why when root runs a program that faults core is not >dumped but when a normal user runs the same program a core is dumped? My educated guess on this is that there could be sensitive data

Re: Problems with equivs

-BEGIN PGP SIGNED MESSAGE- Manoj Srivastava, in an immanent manifestation of deity, wrote: >Darren> Now, I don't want to install mbr since I want lilo to manage >Darren> my boot-records. I have no reason to use another bm. > > Huh? mbr and LILO coexist on a system. There is no need t

Re: Problems with equivs

-BEGIN PGP SIGNED MESSAGE- Jason Gunthorpe, in an immanent manifestation of deity, wrote: >I'm not sure why you don't want to install mbr, all it is an image of the >boot record that lilo uses to generate it's boot record from, with out >/boot/mbr.b lilo will not work in some of it's capac

Re: version numbers on virtual packages

-BEGIN PGP SIGNED MESSAGE- Bart Schuller, in an immanent manifestation of deity, wrote: >I think you'd better make that perl5.004, because breakage could just as >well occur with 5.005 or 5.006, not just perl6. With 5.005 we'll need a >threaded and non-threaded version as well. Fun. (I'm

Re: Bug: #15573: perl should predepend on perl-base

-BEGIN PGP SIGNED MESSAGE- Santiago Vila Doncel, in an immanent manifestation of deity, wrote: >On 4 Dec 1997, Darren/Torin/Who Ever... wrote: >> Hmm. A thought as I spell-checked this. Can you pre-depend and depend >> on the same package? perl's contro

interesting problem in perl vs perl5-lib\d+

-BEGIN PGP SIGNED MESSAGE- I've got a slight problem that I "fixed" in a not completely elegant manner. There is a new libperl5.so.\d+ in the latest set of Perl packages. This means that if you just need to embed Perl into an application and you don't need all the libraries or the execut

perl pre-depends on perl-base (>=5.004.04-2)

-BEGIN PGP SIGNED MESSAGE- To solve a grave priority bug, I've made the perl package (from 5.004.04-3+) pre-depend on perl-base (>=5.004.04-2). This is needed due to the following: Assume you have an earlier version of Perl installed (say from the bo base disks) and you're installing perl

version numbers on virtual packages

-BEGIN PGP SIGNED MESSAGE- I was going to change perl to perl5 think weekend and just provide the virtual package perl. This would close a bug filed by Brian White who is worried about Perl6. While I was thinking about this during builds of Perl, I realized that I can't do that right now

Re: dpkg verify mode for security?

-BEGIN PGP SIGNED MESSAGE- Amos Shapira, in an immanent manifestation of deity, wrote: >Or an audit-trail of invocations of dpkg (e.g. "adduser 3.1-2 installed >and configured successfully on Wed May 29 1997 00:00:23, replaced >adduser-3.1-0") I asked for this a while back and was told th

Re: Perl issues

-BEGIN PGP SIGNED MESSAGE- Vincent Renardias, in an immanent manifestation of deity, wrote: >On 21 May 1997, Darren/Torin/Who Ever... wrote: >> 1. Split the main executable and a small set of base files into >>perl-base. This would be Priority: required, should

Perl issues

-BEGIN PGP SIGNED MESSAGE- I have some ideas on what I'm planning on doing with the Debian Perl package in the near future. 1. Split the main executable and a small set of base files into perl-base. This would be Priority: required, should it be Essential? There will still be a mai

Re: dpkg verify mode for security?

-BEGIN PGP SIGNED MESSAGE- Chris Fearnley, in an immanent manifestation of deity, wrote: >'Amos Shapira wrote:' >>many "use tripwire" answers, and one which says that RPM has a verify >>mode which checks for files which were changed since they were > >What does the rpm verify give you? As

Re: Perl 5.004, perl modules, and binary compatibility

-BEGIN PGP SIGNED MESSAGE- Scott Ellis, in an immanent manifestation of deity, wrote: >As the official version of perl 5.004 is finally out (I must admit I >haven't installed the debian package yet, but I run webservers with lots >of perl CGI and can't afford to break them), I have a few q

Re: pbmplus-10dec91-3

-BEGIN PGP SIGNED MESSAGE- Michael Meskes, in an immanent manifestation of deity, wrote: >As far as I can tell this package doesn't belong into non-free but could go >into graphics. Could anyone please check that? I think we have some other >packages with almost the same copyright in the t

Re: Too much information! (And what to do about it.)

Ian Jackson <[EMAIL PROTECTED]>, in a magnificent manifestation of deity, wrote: >In principle this sounds like a good idea. I don't have a strong >opinion on whether Optional should be included in the `distribution'. I think that it should be a part of the distribution (on the cd), it just gives

Bug#2096: xntp-3.4x-2 doesn't test for presence of /usr/sbin/xntpd

Package: xntp Version: 3.4x-2 /etc/init.d/xntpd doesn't check for the presence of /usr/sbin/xntpd before trying to start itself. Darren

Bug#2073: assembler problems in asm/io.h during build of kernel

>I saw this on comp.os.linux.development.system, but I haven't tried >if it still compiles the kernel with gcc < 2.7.x... > > >From: Russell Johnston <[EMAIL PROTECTED]> >Newsgroups: comp.os.linux.development.system >Subject: Re: gcc 2.7.2 and kernel 1.2.13 > >This patch allows compilation of kerne

Re: libgr

Ian Murdock <[EMAIL PROTECTED]>, in a magnificent manifestation of deity, wrote: >Is libgr safe to include in the distribution? Or does it suffer from >the GIF patent problem? (I'm leaving it in Incoming for now.) This package doesn't actually have gif handling capability. That's in the netpbm

Bug#2073: assembler problems in asm/io.h during build of kernel

[EMAIL PROTECTED] (Bruce Perens), in a magnificent manifestation of deity, wrote: >There was a change in the way that GCC handles embedded assembler that >made new compilers incompatible with the old kernels. Ugh. The io.h file >in the new kernel is similar enough to the old one that it may be a d

Bug#2072: MANOPT not parsed well?

[EMAIL PROTECTED] (Bruce Perens), in a magnificent manifestation of deity, wrote: >A work-around would be to construct a shell program that evaluated to >"less -c" and pass the name of that program in MANOPT. An alias won't You could also set the LESS environment variable. i.e. LESS=-c, personall

Bug#2073: assembler problems in asm/io.h during build of kernel

Package: source Version: 1.2.13-7 Hmmm. I was fooling around with dpkg and source/includes for 1.2.13-7 and I came across the following. Since I haven't touched assembler for about 10 years, I don't know the problem. This was after make config; make dep; make clean. I can include the .config f

New libgr

pgpdMv9tEK4p9.pgp Description: PGP message

libgr

pgpyjSIsQ7TTe.pgp Description: PGP message

libgr

I thought debian used to have libgr but I can't find it anywhere. I just grabbed the latest version from ftp.ctd.comsat.com and it looks fine so far. I could really use this for the netpbm package I'll be uploading soon. So, I'm going to build a debian package and upload it, it shouldn't take lo

Bug#1972: perl should suggest kernel sources

Austin Donnelly <[EMAIL PROTECTED]>, in a magnificent manifestation of deity, wrote: >Package: perl >Version: 5.001-4 > >Perl should suggest kernel sources, rather than grumble in postinst >later. fixed. Darren <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PRO

Bug#1951: perl is not exportable from the US

"Michael E. Deisher" <[EMAIL PROTECTED]>, in a magnificent manifestation of deity, wrote: >Package: perl (elf-perl, actually) >Version: 5.001 >Revision: 5 > >Perl contains a working crypt function and thus cannot be legally >exported from the US (someone correct me if I'm wrong). Probably, the >c

Re: why doesn't binutils-2.6-1 provide a shared library?

[EMAIL PROTECTED] (David Engel), in a magnificent manifestation of deity, wrote: >It could. There is already some support for it in the Makefiles. I >chose to leave it for the eventual maintainer to add since it has >packaging and support ramifications. BTW, I did the same for libg++. Who's goi

Re: ALPHA release of apache-1.0.0-1 now available

Chris Fearnley <[EMAIL PROTECTED]>, in a magnificent manifestation of deity, wrote: >'Michael Alan Dorman wrote:' >>On Sun, 17 Dec 1995, Chris Fearnley wrote: >>> This is a preliminary release. It seems to work, but I'm disatisfied >>> with my handling of httpd configuration (basically there is n

new Perl with new sonames

There is a new Perl in ftp://ftp.debian.org/debian/private/project/Incoming/ that uses the sonames in libdb1 (libdb.so.1) and libgdbm1 (libgdbm.so.1). It has the proper requires line so it won't let you install without them. This version of perl also includes some doc updates and includes the Saf

Bug#2050: bad(?) depends in libgdbm1-dev 1.7.3-6

Package: libgdbm1-dev Version: 1.7.3-6 There's a problem with libgdbm1-dev since when I install the corresponding shared library package, it should install also, right? It doesn't. I can't tell if the following is a problem with dpkg or with the Depends line: dpkg -i libgdbm1-dev-1.7.3-6.deb (R

Bug#2049: bad depends in libdb1-dev 1.7.3-6

Package: libdb1-dev Version: 1.7.3-6 The control file has a bad depends in it: grep '^Depends' libdb1-dev-control Depends: libc5-dev (>5.2.16-1), libdb1 (1.85.2.x) That final .x shouldn't be there. Output from 'dpkg -i libdb1-dev-1.7.3-6.deb' (Reading database ... 21499 files and directories cur

why doesn't binutils-2.6-1 provide a shared library?

Hopefully, this won't show my ignorance of binary objects off too badly. Shouldn't binutils-2.6 provide a shared bfd library? It used to in 2.5.2l.20-2? I'm asking here instead of posting a bug because I remember there being some discussion about this a little while back. Also, why is it that

Bug#1915: Perl doesn't like the number 0

Peter Tobias spoke unto the world and said: >Darren/Torin/Who Ever... wrote: >> I've not been able to duplicate this anywhere using a.out under linux or >> any other machines that I have access to. > >Strange, I get the same results on every linux system where I i

Re: Bug#1916: perl: wrong entries in Config.pm

Manoj Srivastava spoke onto the world and said: > You see, there are a number of add-ons (or extensions) to Perl > that are very useful, (the perlTk stuff, the CGI modules, and libwww > come to mind), and these use MakeMaker and Config.pm to determine > where to put the files on install. >

Re: Bug#1911: Perl postinst is unecessarily slow

Ian Jackson spoke onto the world and said: >[EMAIL PROTECTED] writes ("Re: Bug#1911: Perl postinst is unecessarily slow"): >> If it's acceptable that all the files will have the same permissions as >> the files under /usr/include and /usr/local/include, then there is no >> problems. > >Huh ? Perl

Re: Bug#1915: Perl doesn't like the number 0

Peter Tobias spoke unto the world: >Package: perl >Version: 5.002-1 (a.out) >The following program prints "0.e-1" instead of "0". >for ($j = 0; $j <= 7; $j++) { > print "$j\n"; >} I've not been able to duplicate this anywhere using a.out under linux or any other machines that I have access to

Re: Bug#1911: Perl postinst is unecessarily slow

Ian Jackson spoke unto the world and said: >>Package: perl >>Version: 5.001-6 (a.out) >>While running `top' to see how the Perl postinst was getting on I saw: >> >>root 8507 11.4 0.8 105 160 v02 S01:57 0:03 find >>/usr/lib/perl5/i486-linux -type f -exec chmod 644 {} ; > >This is stil

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

Jeff Noxon spoke unto the world and said: >My plan is to rewrite run-parts in C or C++. However, I probably won't >have that done until next weekend. I've never done any perl programming Could I ask a favor that run-parts *skips* directories rather than reporting "component /etc/cron.*/RCS is no

Re: Bug#1916: perl: wrong entries in Config.pm

BTW, I assume that followups to debian-bugs go to debian-devel. Is this correct? Peter Tobias spoke unto the world and said: >Package: perl >Version: 5.002-1 (a.out) > > >The following entries in /usr/lib/perl5/i486-linux/5.002/Config.pm >are wrong: > >installarchlib='/usr/local/src/debian-p

Re: Bug#1911: Perl postinst is unecessarily slow

Ian Jackson spoke unto the world and said: >Package: perl >Version: 5.001-6 (a.out) I've taken over the package and upgraded to version 5.002-1. This is my very first debian package, so I only put it in private/project/Incoming and asked people to comment on it on debian-devel. I wanted to make