Re: Bug#3795: ae should not be essential

[Craig Sanders]

On Thu, 1 Aug 1996, Guy Maor wrote:

> > Christian Hudon writes ("Re: Bug#3795: ae should not be essential"):
> > > Isn't it that some of the packages that look at EDITOR fall back
> > > to ae if there are problems with EDITOR?
>
> vipw and vigr do this. They're in passwd which is essential, but won't
> be as soon as I upload a new version.

Actually, they default to ae unless you override it with "export
EDITOR=/usr/bin/vi". I wouldn't mind so much if they just had a fallback
to ae if vi wasn't available but running ae by default from a command
named after vi just doesn't make any sense.

it's really disconcerting when you type 'vipw' or 'vigr' on a freshly
installed system (where you've spent 20 mins in dselect selecting
packages, including unselecting nvi & elvis and selecting vim), start
typing vi commands into the type-ahead buffer before it's finished
loading, and then find that the first line of /etc/passwd or /etc/group
is mangled with  or whatever.

I know this has been discussed before, but vipw does NOT mean ae.

maybe the best solution would be to have aepw & aegr as symlinks to vipw
& vigr. When, for example, vipw is executed, it checks for existence of
/usr/bin/vi. if vi doesn't exist, it either prints a message saying "vi
is not installed. try aepw" or just uses ae, or prints a warning message
before running ae.

Craig

Re: Bug#3990: xdm-errors location not what FSSTND says

[Craig Sanders]

On Thu, 1 Aug 1996, Michael Gaertner wrote:

> Package: xbase
> Version: 3.1.2-9
> 
> FSSTND R1.2 writes in chap. 5.3.5 to place xdm-errors in 
> /var/lib/xdm/. This is not the location xdm-errors get logged by default
> in above package.
> 
> Suggestion: change /etc/X11/xdm/xdm-config in line
> "DisplayManager.errorLogFile:" to 
> 
> "DisplayManager.errorLogFile: /var/lib/xdm/xdm-errors"

What's so special about xdm that it's error log files should go in
/var/lib?

Isn't /var/log (or subdirectories of /var/log) the right place for all
log files?


Craig

Re: Perl vs Python vs ....

[James A. Robinson]

Much of this discussion (talking about MS-DOS, assembler code, etc.)
has no real place for debian developers.  I've asked Bruce to say
something, and he told me to ask you all to please move this
discussion off the list.  Please take it to private e-mail or
something for now.


Jim

Bug#4014: netpbm is missing manual pages

[Daniel Quinlan]

Package: netpbm
Version: 1994.03.01p

Missing manuals: pbm.5, ppm.5, pgm.5, pnm.5

I suspect they might be in the netpbm-devel package.  If so, it's a
bug.  Section 5 is "file formats", not development.  It's basic
information about netpbm.

Re: IP-aliasing

[Craig Sanders]

On 3 Aug 1996, Rob Browning wrote:

> Craig Sanders <[EMAIL PROTECTED]> writes:
> 
> > what i will never understand, though, is why people use perl for
> > jobs that sh is much better suited to.
> >
> > perl is great if you want awk/sed/grep/kitchen sink all rolled into
> > one scripting language. but there's a price - perl's slower and
> > bigger and takes longer to load.
>
> What I will never understand is why people assume that perl is so much
> slower. For most things it's much faster since it doesn't have to
> launch a separate program for most operations.

sorry, my language was unclear - i implied that perl ran slower when all
i really meant was that it takes longer to load and is overkill for many
small tasks.

perl RUNS faster, that's a fact.

perl LOADS slower, that's also a fact.

perl also requires much more memory, which on a 4mb or 8mb system will
slow things down even further due to extra swapping.

therefore tiny scripts are better done in sh, which is a) smaller and
therefore loads faster, and b) almost always in memory/cache anyway.


Of course, as you say, if you need to fork sed (or whatever) many times
then perl is clearly a winner.


my basic rule of thumb is:

if the script is mostly a program launcher then use sh.  otherwise
use awk or perl or whatever language best suits the application.

one big advantage to sh for me is that if i find that i am entering
similar or repetitive commands at the prompt, i can easily cut and paste
the command line into a text file. Add "#! /bin/sh", some extra line
breaks to make it more readable, some comments to explain what it does
and what arguments it takes, and i have a new script.

I'd like to see a bourne-like shell with perl-like regexp stuff (mainly
sed & grep) built in - i'd switch to that in a flash. As a built-in it
would be extremely fast, and i'd still be able to test/debug/prototype
my scripts interactively on the command line :-)



Craig

Closing bug 1831

[Lars Wirzenius]

During yet another sleepless night, I was browsing the bug list, and
found this bug.

> Today I decided to configure pgp-i, and I came across 2 bugs.
> 1 is already listed as bug #1103, and is caused by a non excisting
> .pgp directory, and pgp doesn't create one, and so can't create it's
> output files. The other one isn't listed. When I run pgp -kg to
> generate a key, It ask me to choose 1, 2 or 3 or to type the number of
> bits. When I enter 2, It's says It will generate a 768 bit key, but
> when it is asking for random key presses, it only needs 4 random bits,
> which is 1 keypress. If I type 768 when asked the size of the key, 
> It needs 248 random bits. So the number of bits isn't correctly set at
> 768 bits when you choose 2 (and maybe 1 and 3, haven't tested that).

PGP collects randomness from all keypresses, that is, also while you
enter the number of bits, the username, and the passphrase. Depending
on how you enter the preceding information, PGP can need more or less
random key presses.  It is even possible to enter the preceding info
in such a way that no extra random bits are required (e.g., slow typing
and long usernames and passphrases tends to make the intervals between
keypresses more random).

Thus, there is no bug (although it was a good idea to be worried), and 
I'm closing this bug report.  I'm not the PGP maintainer, so I hope I'm
not stepping on Ian's toes.

-- 
Lars Wirzenius <[EMAIL PROTECTED]> 
Please don't Cc: me when replying to my message on a mailing list.




pgpKfp2eIne0y.pgp
Description: PGP signature

unzip_5.12-13 uploaded to master

[Mr Stuart Lamble]

Hmm. Forgot to mention that there's a new maintainer. Oh, well.
-BEGIN PGP SIGNED MESSAGE-

Date: 03 Aug 96 09:31 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Stuart Lamble <[EMAIL PROTECTED]
Source: unzip
Version: 5.12-13
Binary:  unzip
Architecture:  i386 source
Description: 
 unzip: De-archiver for .zip files
Changes:
 Uses dpkg-name to move the new .deb file rather than manually moving it;
 fixed lack of multi-architecture support (Bug #3916); added a long
 description (Bug #3693)
Files:
 283be7478726af74046fc37c958e65ce  376767  non-free  -  unzip_5.12-13.tar.gz
 61747a13a7163f0f7e9d247189e539d6  5410  non-free  -  unzip_5.12-13.diff.gz
 3a1a2042288e6a1a3e3ae64aadbaba4d  81566  non-free  extra  
unzip_5.12-13_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.3i
Charset: noconv

iQCVAwUBMgQX/dancbR/eGtJAQHMJAP+Pc4mV71x3UnrutnvsuYb9I9gt7OeVFfC
QGAVL0UrBbFoxH4msnwa6jpaueHN4a2NeefEzsnmmrDIRNmJcu+7y0Secbn3F7e3
l6od2hdWEghHqUTiRRsoAffctenF0g/n5PKDawaDp47u4iZmnSIVqSyEF2M5d3dJ
WVFVedlI+j0=
=z6hU
-END PGP SIGNATURE-

zip_2.01-13 uploaded to master

[Mr Stuart Lamble]

Another one that I forgot to mention the new maintainer in...oh, well,
put it down to a late night. :-)
-BEGIN PGP SIGNED MESSAGE-

Date: 03 Aug 96 09:37 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Stuart Lamble <[EMAIL PROTECTED]>
Source: zip
Version: 2.01-13
Binary:  zip
Architecture:  i386 source
Description: 
 zip: Archiver for .zip files
Changes:
 Uses dpkg-name rather than manually moving the .deb file; added
 multi-architecture support (Bug #3934); added a long description
 (Bug #3692)
Files:
 212592616f41a0802ca3c213b61ff458  232659  non-free  -  zip_2.01-13.tar.gz
 2a1d9db4160065719a8d6fa150d9ad14  5544  non-free  -  zip_2.01-13.diff.gz
 81aa10e764b4038207772ce46b60eaae  59380  non-free  extra  zip_2.01-13_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.3i
Charset: noconv

iQCVAwUBMgQYLtancbR/eGtJAQH+hQQAibLxVlr11FKerBman8PjDDbilI7AcJBf
fvgoG1tiRK8HRdsUtYhInAj5Dqt794UBNIzOrrA/Ra7C1zuquDjw8fRzc1E9BMhD
GfCZahwnkRiuzRF4fI8sVl6XQzwNGmNJt30hgxZN+Zy0IwcgUGnhRstjFJYCVX6t
RCFW8B/qtEA=
=lWdg
-END PGP SIGNATURE-

vim_3.0-6 uploaded to master

[Mr Stuart Lamble]

Hopefully, this will be the last modifications made to vim 3.0 - version
4.2 is out (with restrictions on distribution on CDs), and 4.3 is due in
a few weeks (without those restrictions). I'll be upgrading the sources
to 4.3 when it's released.

-BEGIN PGP SIGNED MESSAGE-

Date: 02 Aug 96 07:30 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Stuart Lamble <[EMAIL PROTECTED]>
Source: vim
Version: 3.0-6
Binary:  vim
Architecture:  i386 source
Description: 
 vim: VI iMproved - enhanced vi editor
Changes:
 New maintainer; fixed lack of multi-architecture support (Bug #3924);
 added a "Depends" field (now depends on libc5 and ncurses3.0, as it
 should); corrected the permissions of postinst and prerm.
Files:
 e0cd25093f4a8889f6f5a4a41ab9d4d3  470134  editors  -  vim_3.0-6.tar.gz
 6c9dbcfd3e864dd448d00114408b49b0  15989  editors  -  vim_3.0-6.diff.gz
 69ae44cfc446937a191785445c5f6bd2  20  editors  optional  vim_3.0-6_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.3i
Charset: noconv

iQCVAwUBMgQYGtancbR/eGtJAQE4+AQAlU7zHAV8gLtFxwMpbGVuaOXf47ka6UNT
N0pQ5br0go5WATQR6zlTsuBTzPZkZ8HPBnqqChH07LyKGRHrHPoMCXidorE380Ex
zwVM9yYY8peFHyYc4BJccyQLY7WZrd1eW1K3nS0J/+ldBTtAZVUT/fMd95W+zGO/
JBCUSCIvPlk=
=XlU+
-END PGP SIGNATURE-

Re: elm problems

[Guy Maor]

On Fri, 2 Aug 1996, Dale Scheetz wrote:

> cd lib; /usr/bin/pmake  -w all

> cd lib; /usr/bin/pmake  - all
   ^ (no w)

Was that a typo on your part?

Guy

Bug#4015: xterm & xterm.color sets broken TERMCAP

[Herbert Xu]

Package: xbase
Version: 3.1.2-9

These two programs exports TERMCAP of the form
co#80:li#24:
Where 80 and 24 can be replaced by the dimensions
of your xterm.  This is really braindead as you
often want to resize your xterm and many applications
simply worship TERMCAP as the most reliable source
of info.  It also makes anything that uses libslang
unusable as it thinks my TERMCAP is too simple :)

This should be disabled by default.
-- 
Debian GNU/Linux 1.1 is out! { http://www.debian.org/ }
A.  B <=> True  B.  A <=> False
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
PGP Key:  [EMAIL PROTECTED] or any other key sites

PAM libraries (libpam) uploaded

[Patrick Weemeeuw]

I have uploaded the initial release of libpam to chiark.  There is
also a copy available on
ftp://ftp.kulnet.kuleuven.ac.be/pub/people/patrick/debian.

The libpam package contains the PAM libraries (PAM = Pluggable
Authentication Modules [http://gluon.physics.ucla.edu/~morgan/pam
http://www.redhat.com/pam]).

The current libraries have an experimental nature: the main logic is
OK, but only a limited set of underlying authentication modules is
available for the moment (other modules are under development).
However, the libraries are stable enough to start making application
programs (authentication clients) PAM aware.

I am releasing this package now, because I think that it's now the
time to consider making applications PAM aware: development is
currently accellerating, and RedHat is PAM-ifying some authentication
clients for their next release.  As a consequence we can use the same
or similar diffs for most of our applications.

If you would PAM-ify your application, please join the Linux-PAM
mailing list ([EMAIL PROTECTED]).

-BEGIN PGP SIGNED MESSAGE-

Date: 04 Aug 96 06:53 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Patrick Weemeeuw <[EMAIL PROTECTED]>
Source: libpam
Version: 0.50-1
Binary:  libpam
Architecture:  i386 source
Description: 
 libpam: Pluggable Authentication Modules -- Libraries
Changes: initial release
Files:
 977e5542dd94866ba6030457035f6017  265966  -   libpam_0.50-1.tar.gz
 1cebc86544ded0b5d67cdd2abbb10a40  107224  -   libpam_0.50-1.diff.gz
 8cee7a269c830e413b207b1a43ef4978  224980  misc  extra  libpam_0.50-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQEVAwUBMgRJxugIvbi48kGNAQH1Vgf9GFUBTVE42+gCltXTCyzsa3k1zJtWAHJA
//fCKKr9Jk1wFNNXhZkE14ayNU4dbLSJK9LXnOJsGKMT53qfVUrDsgl9GeIvgfLx
lcMBblxCWqmYaPWgKCzmcBF3X8/n/wuezPTMQJvxS/7ILoqZiuES1Hm5HNRS48pj
ejEzXj6yJGmsWZQ901kY40tz6lUEL9K1wvYZERXFf/Zbt9tWN6MV5w/K9nKF8O4b
NyVfgbrdoNG3tA4yHCfUoZebCbc9N+EoSNPjjv9E0qIIleJUAThi8bbm1k3u9RoJ
IDpZv01FglO4mA/uOC99MVSxhTAvFIZVgb9zJJ7DPZPx3z1QLkg2FQ==
=3/QK
-END PGP SIGNATURE-

Is it okay to download orig source once only?

[Yves Arrouye]

Hello,

Erick asked the question, but I don't remember if there was an answer.
Would it be okay if, when uploading changes to a package, we only upload
a .deb and a .diff.gz file? This would help people like us who have slow
PPP connections but maintain big packages.

I propose that we upload once

somepackage_release.tar.gz

which unpacks to

somepackage-release.orig/

and then further uploads would be

somepackage_release-deb.diff.gz
somepackage_release-deb_arch.deb

Would that be okay?
Yves.

-- 

Re: editor virtual package

[Yves Arrouye]

On Aug 2, 11:17am, Dale Scheetz wrote:
} Subject: Re: New virtual package names.
} On Fri, 2 Aug 1996, Warwick HARVEY wrote:
} 
} > > On another note, is there an editor virtual package? Is there any interest
} > > in adding one? It could be valuable to add Provides: editor to ae (and
} > > others as well).
} > 
} > What would it be used for?  Are there packages that depend on having an
} > editor, or for which it would be appropriate to recommend one (and have any
} > old editor serve the purpose)?  If so, no problem...
} > 
} Here is a better reason:
} 
} I'd like to be able to remove `ae', but it won't deinstall.  It should
} be possible to remove ANY package if I really want to.  I don't like
} it when I'm treated like a child by the packaging system.

It could be nice to have packages providing editor to also update
an `editor' binary with update-alternative. This way, base packages
(or packages like quota) which actually default to 'ae' or 'vi' when
VISUAL or EDITOR are not set would default to 'editor'.

Talking about that, I think the packages could even provide editor *and/or*
visual, so that other programs could do something like:

ed = getenv("VISUAL");
if (!ed || !*ed) ed = getenv("EDITOR");
if (!ed || !*ed) ed = "visual";
if (!found_in_path(ed)) ed = "editor";

to choose an editor to use.

Yves.


-- 

Bug#4016: ref not in elvisctags

[Craig Sanders]

Package: elvisctags
Version: 2.0-4

/usr/bin/ref is in elviscmn, rather than in elvisctags.


Craig

Re: uploaded babel 3.6-4 to master

[Michael Meskes]

Emilio Lopes writes:
> EB> * added latin1.sty: Michael Meskens requested
> 
> What is wrong with 
> 
> \usepackage[latin1]{inputenc}

Note that as my fault. I've been using latin1.sty for so long I didn't even
realize that this was a possibility. Sorry for that.

But I still think we should keep latin1.sty for guess who are used to it
(like me, although I will probably change my files).

Michael

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

Bug#4017: boot disk doesn't recognize NCR scsi

[Richard Tietjen]

Package: bootdisk
Version: 1.1.1

Attempted to install Debian 1.1.1 from PHT cd rom. 
Bootdisk doesn't see my SCSI system, based on NCR
53c8xx PCI Rev 2.0 1993

This device worked find under Debian .93R6/ Linux
1.2.13

Updated Virtual Package Name List

[Warwick HARVEY]

  AUTHORITATIVE LIST OF VIRTUAL PACKAGE NAMES

Below is an authoritative list of virtual package names currently
in-use or proposed and not objected to.  Please check the list below
for things relevant to your packages.

New packages MUST use virtual package names where appropriate (this
includes making new ones - read on).

Packages MUST NOT use virtual package names (except privately, amongst
a cooperating group of packages) unless they have been agreed upon and
appear in this list.

The latest version of this file can be found in
doc/package-developer/virtual-package-names-list.text
on your local Debian FTP site.

The procedure for updating the list is as follows:

1. Post to debian-devel saying what names you intend to use or what
   other changes you wish to make.

2. Wait a few days for comment.

3. Mail the maintainer of the virtual package name list (Warwick Harvey
   <[EMAIL PROTECTED]>) notifying him of the consensus reached (or
   your suggestions if noone objected).  Please include a proposed brief
   description of the new virtual name(s) for the list.  The list
   maintainer will then post the new list to debian-devel and upload it
   to the FTP site.

4. Go and use the new or changed names.

Warwick.
(based on earlier version by Ian J.)


Now, the list:

X Windows:
--
X11R5   XFree86 R5, including base system (obsolete)
xR5shlibXFree86 R5 shared library only
X11R6   XFree86 R6, including base system
xR6shlibXFree86 R6 shared library only
xlibraries  XFree86 R6 shared library or stub library
xserver Any X server (used by other X packages)

Miscellaneous:
--
libc.so.4   An a.out shared C library, version 4.x.x.
info-browserSomething that can browser GNU Info files
kernel-source   Kernel source code
kernel-headers  Kernel header files (, )
kernel-imageKernel image ( vmlinuz, System.map, modules )
httpd   Any HTTP server
postscript-viewer   Anything that can display Postscript files
postscript-preview  Any preprocessor that creates Postscript output
metafontThe TeX Metafont program
dvilj, dvipsProvided by dviljk, dvipsk (? - iwj)
www-browser Something that can browse html files
awk Anything providing suitable /usr/bin/{awk,nawk}
c-shell Anything providing a suitable /usr/bin/csh
pdf-viewer  Anything that can display PDF files
pdf-preview Any preprocessor that creates PDF output
compressAnything that provides a true BSD compress command
emacs   Anything that provides the emacs editor

News and Mail:
--
mail-transport-agentMail transport agents (Smail, Sendmail, &c)
mail-reader Mail user agents (Pine, Elm, mailx, &c)
news-transport-system   Local news system (INN, C News or B News)
news-reader Any news reader (trn, tin, &c)
inews   /usr/bin/inews - local or remote news poster
pgp A version of PGP (International or US)
imap-client Any mail reader capable of accessing remote mail
folders using the IMAP protocol (e.g. Pine)
imap-server Any IMAP mail server

Names of superseded packages Provided by the current ones:
--
gs_x, gs_svga, gs_both  Provided by Ghostscript (gs).  Use gs.
xpmR6   Provided by xpm.  Use xpm.

Change history:
---
22 Sep 1995 Ian Jackson Initial revision.
26 Mar 1996 Andrew Howell   Added www-browser.
11 May 1996 Manoj SrivastavaAdded kernel-image, added new location of
this file
19 May 1996 Warwick Harvey  Took over maintenance of list, changed
instructions for updating list
25 Jul 1996 Warwick Harvey  Added awk as per Chris Fearnley's suggestion
Added c-shell, which seemed to have dropped
off at some stage
 2 Aug 1996 Added pdf-{viewer,preview}, compress, emacs
 5 Aug 1996 Added imap-{client,server}

Bug#4018: Subdirectory glimpse search

[Richard Tietjen]

Package: www.debian.org

When I go to a subdirectory as the instructions
indicate to narrow down my Glimpse search to just
bug reports, say, I get a Not Found page, that says
something about the referring page and the href
anchor points to ghindex.html  I din't understand
what the point of that is, why doesn't it just post
an email mentioning that page?

Re: Uploading compress-package 1.1 on master

[David Frey]

In message <[EMAIL PROTECTED]>, 
[EMAIL PROTECTED] writes:
>Description: 
> compress-package: fileset to build a Debian compress package
>Changes:
> * New organization (a la kernel-package)
> * Automatic diversion and addition of symlinks for gzip-provided commands
> * Can built compress packages from different sources
>Files:
> fa4c03063df6f2bf96ff8d88129e7bcf  7627  devel  -  
> compress-package_1.1-1.tar.gz
> 07b75ae335d55611a52dbb718c58d31f  7804  devel  extra  
> compress-package_1.1-1_all.deb

compress belongs into non-free, not into devel! 
Reason: Copyright-problems (Unisys-Patent)

David

-- 
David Frey <[EMAIL PROTECTED]>|Microsoft isn't the answer...it's the QUESTION.
Schlieren, Switzerland|``No'' is the answer.
PGP-Key available on request  |Use Debian GNU/Linux!

Re: elm problems

[Dale Scheetz]

On Sun, 4 Aug 1996, Guy Maor wrote:

> On Fri, 2 Aug 1996, Dale Scheetz wrote:
> 
> > cd lib; /usr/bin/pmake  -w all
> 
> > cd lib; /usr/bin/pmake  - all
>^ (no w)
> 
> Was that a typo on your part?
> 
No! Not a typo. This is the only difference between what gets executed
when debian.rules calls for a make, and when I call for the same make.

The line in the Makefile is:

cd lib; $(MAKE) $(MJ) -(MAKEFLAGS) all

There is no definition of MAKEFLAGS in debian.rules, or in the Makefile.
Does the shell set it when debian.rules runs?

confused,

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 --

Bug#4019: Decompression failure on Install Boot Disk

[Christopher R. Hertel]

Package: Boot1440.bin
Version: Debian 1.1

I have been unable to boot from the boot1440.bin image.  I have tried
the
following:

- downloaded the image from a variety of sources.
- used several different floppies
- erased (using dd if=/dev/zero ...) the floppies before writing the   
  image to them.
- formatted the floppies using a variety of tools

When I attempt to boot, I get the following:

 invalid compressed format (err=2)

Then it tells me that the system is halted.

I've tried entering boot options (such as 'linux ether=10,0x320,eth0').
When I do this, I get a slightly different error message:

 incomplete literal tree

Where do I go from here?

Chris Hertel -)-
[EMAIL PROTECTED]

epoch?? how to make squid-1.0.5 > squid-1.0beta16

[Craig Sanders]

I compiled squid 1.0.5 last night and made a new package for it, but when
i installed it with dpkg on my system i got a warning message about
"downgrading to earlier version due to --force".

which means that dselect can't be used to upgrade this package because it
won't do the forced "downgrade".  I don't want to upload the new package
until this is fixed.

I seem to recall some discussion a few months back about an "Epoch" header
or something like that which could be used to get around this problem.

Was epoch implemented?  How do I use it? 


(note for those waiting on a new version of squid: i probably wont get
time to finish this off now until the end of the week.) 

Craig

axe_6.1.2-5 uploaded

[joost witteveen]

-BEGIN PGP SIGNED MESSAGE-

Date: 04 Aug 96 14:33 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: joost witteveen <[EMAIL PROTECTED]>
Source: axe
Version: 6.1.2-5
Binary:  axe
Architecture:  i386 source
Description: 
 axe: An editor for X.
Changes: 
 * changed axinfo.c so that it now reads .gz files.
(wasn't that much changes after all)
Files:
 d93810377fe975ee622d6f8c37dc21a2  434741  editors  -  axe_6.1.2-5.tar.gz
 ad7d6914ed4f1ea31fa087a5aec3834e  30543  editors  -  axe_6.1.2-5.diff.gz
 da60b804a0ad3377261cd94dd97aaa18  197950  editors  Optional  
axe_6.1.2-5_i386.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.2i

iQCVAwUBMgS1BZNVaG8BiEBRAQEO8QP/b3+nrPm5yaJRJ1/zN6BYV5QAeDN/jHMV
+9AME+yb8Vb2MnEiHjiauoaleK1oVdidQdZL8sOeHOf2HoVIzJ2XNW82jct5gfSp
gHOgW9AxSERFa5kzUHjTONy4Qp2d/wcDczdwp7ADyMruwknIZNRIuGbSCjlalaLU
3GdP5Ie+HeY=
=OWHz
-END PGP SIGNATURE-